Convert AVI to FLV

Why Convert AVI to FLV?

Converting AVI to FLV serves two primary purposes: RTMP live streaming and legacy Flash-based content management. RTMP (Real-Time Messaging Protocol) remains a core technology for live streaming to platforms like Twitch, YouTube Live, and Facebook Live, and FLV is the native container for RTMP transmission. Converting AVI content to FLV enables pushing pre-recorded video to RTMP endpoints as simulated live streams or for VOD delivery through RTMP-based infrastructure.

Many organizations still operate Flash-based content management systems built during the 2005-2015 era. Corporate training portals, e-learning platforms, and digital signage systems that were built around FLV video may still be in active use. Converting AVI content — especially from DV cameras and legacy surveillance systems — to FLV ensures compatibility with these existing platforms without requiring a complete system migration.

FLV offers significantly smaller file sizes compared to AVI with DivX/Xvid codecs, thanks to the efficient H.264 encoding within the FLV container. A 700 MB AVI DivX file might convert to a 200-300 MB FLV with equivalent quality using H.264. This compression advantage was one of the reasons FLV became the dominant web video format before HTML5 — and it remains relevant for bandwidth-constrained delivery scenarios.

The conversion requires re-encoding from AVI's codecs (DivX, Xvid, MJPEG) to FLV-compatible codecs (H.264, VP6). FFmpeg handles this efficiently, with options for bitrate control, resolution scaling, and FLV metadata injection. For RTMP streaming, the -f flv output format can pipe directly to an RTMP endpoint using FFmpeg's built-in RTMP support.

Key Benefits of Converting AVI to FLV:

• RTMP Streaming: Native container for RTMP live streaming to any platform
• Smaller Files: H.264 in FLV compresses better than DivX/Xvid in AVI
• Legacy Systems: Compatible with Flash-based CMS and e-learning platforms
• Progressive Download: Optimized for web delivery with fast seeking
• Metadata Support: Rich FLV metadata for duration, seeking, and cue points
• Streaming Infrastructure: Works with Wowza, nginx-rtmp, and Red5 servers
• Simulated Live: Push pre-recorded content as live stream via RTMP

Practical Examples

Example 1: Streaming Pre-Recorded AVI Content via RTMP

Scenario: A small broadcaster wants to stream their library of AVI-format content as a 24/7 live channel on Twitch, converting and pushing content to the RTMP endpoint in real-time.

Source: documentary_episode_01.avi (700 MB, 720x480, Xvid, MP3)
Conversion: AVI → FLV (real-time RTMP push)
Result: FLV stream pushed to Twitch at 2500 kbps

RTMP streaming workflow:
1. Create playlist of AVI files to stream
2. FFmpeg converts and pushes each AVI as FLV to RTMP
3. Twitch receives FLV stream and transcodes for viewers
4. Next AVI file automatically starts when previous ends
5. 24/7 channel runs from AVI content library
✓ AVI library becomes live streaming content
✓ H.264 re-encoding ensures Twitch compatibility
✓ Real-time conversion at streaming bitrate
✓ Seamless transition between episodes

Example 2: Migrating DV Camera Archives to Flash-Based CMS

Scenario: A production company has years of DV camera footage stored as AVI files and needs to convert them for their client's Flash-based video asset management system.

Source: corporate_event_2008.avi (12 GB, 720x480, DV, PCM 48kHz)
Conversion: AVI → FLV (CMS-compatible, H.264 + AAC)
Result: corporate_event_2008.flv (850 MB, 720x480, H.264, AAC 192kbps)

CMS integration workflow:
1. Batch convert DV-AVI files to FLV with H.264
2. Inject FLV metadata with yamdi for seeking
3. Upload FLV files to Flash-based asset management system
4. Client accesses video library through web interface
5. FLV player provides playback with seek functionality
✓ 14x compression from DV-AVI to H.264 FLV
✓ Metadata enables proper seeking in FLV player
✓ Compatible with Flash-based CMS without upgrades
✓ Batch conversion handles entire archive efficiently

Example 3: Converting Surveillance AVI for Web-Based Monitoring

Scenario: A security company has surveillance footage recorded as AVI (MJPEG) and needs to convert clips to FLV for their legacy web-based video review portal that uses a Flash video player.

Source: camera_03_2024-01-15.avi (2.5 GB, 1280x720, MJPEG, PCM)
Conversion: AVI → FLV (web review portal)
Result: camera_03_2024-01-15.flv (180 MB, 1280x720, H.264, AAC)

Security review workflow:
1. Convert MJPEG AVI to H.264 FLV
2. Upload to web-based surveillance review portal
3. Security team reviews footage in Flash player
4. Flag incidents with FLV cue point timestamps
5. Export flagged segments for evidence
✓ 14x compression from MJPEG to H.264
✓ Flash player enables web-based remote review
✓ Cue points mark incident locations in timeline
✓ H.264 provides smooth playback at full resolution

Frequently Asked Questions (FAQ)

Q: Why convert to FLV instead of MP4 for streaming?

A: FLV is the native container for RTMP protocol, which is still the standard ingest format for most live streaming platforms (Twitch, YouTube Live, Facebook Live). While MP4 is better for file-based delivery, RTMP/FLV is the standard for pushing live or simulated-live content to streaming servers. If your goal is file playback rather than RTMP streaming, MP4 is the better choice.

Q: How much smaller will the FLV file be compared to AVI?

A: It depends on the AVI codec. DV-AVI (13 GB/hr) converts to FLV H.264 at roughly 1/10-1/15 the size. DivX/Xvid AVI converts to FLV H.264 at roughly 1/2-1/3 the size (H.264 is more efficient). Uncompressed AVI sees the largest reduction — 50-100x compression ratios. MJPEG AVI typically compresses 10-15x when converted to H.264 FLV.

Q: Can I push AVI directly to RTMP without creating an FLV file?

A: Yes. FFmpeg can convert and stream in one step: ffmpeg -re -i input.avi -c:v libx264 -preset veryfast -c:a aac -f flv rtmp://server/live/key. The -re flag sends at real-time speed, and -f flv formats the output as FLV for the RTMP connection. No intermediate FLV file is created — the conversion and streaming happen simultaneously.

Q: Do I need to add FLV metadata after conversion?

A: For file-based FLV playback, yes. FLV files need an onMetaData event at the beginning for proper duration display and seeking. Use yamdi -i input.flv -o output.flv or flvtool2 -U input.flv. For RTMP streaming, the server handles metadata automatically. FFmpeg can also inject metadata during conversion with -flvflags add_keyframe_index.

Q: What H.264 preset should I use for RTMP streaming?

A: For real-time streaming, use -preset veryfast or -preset superfast to ensure the encoding can keep up with real-time playback speed. For file conversion where speed isn't critical, use -preset medium or -preset slow for better compression efficiency. Always use H.264 Baseline or Main Profile for maximum RTMP server and player compatibility.

Q: Can modern media players still play FLV files?

A: Yes. VLC, mpv, PotPlayer, KMPlayer, and all FFmpeg-based players handle FLV files without issues. The Flash Player deprecation only affects web browser playback — standalone desktop and mobile players decode FLV natively through their FFmpeg/libavcodec backends. For local file playback, FLV works as well as any other format.

Q: Is there a resolution limit for FLV files?

A: With H.264 encoding, FLV supports up to 1080p resolution. The older Sorenson Spark and VP6 codecs in FLV are limited to lower resolutions. For most practical purposes, 720p or 1080p H.264 in FLV provides the best balance of quality and compatibility. For RTMP streaming, most platforms recommend 720p at 2500-4000 kbps or 1080p at 4500-6000 kbps.

Q: Should I convert my AVI collection to FLV or MP4?

A: For archival and general playback, convert to MP4 — it's universally supported, plays in browsers, and works on all devices. Choose FLV only if you specifically need RTMP streaming capability, have a legacy Flash-based system that requires FLV, or are working with existing FLV-based streaming infrastructure. For 99% of use cases, MP4 is the better target format.