Convert MOV to FLV

Why Convert MOV to FLV?

Converting MOV to FLV serves the RTMP live streaming ecosystem. Mac-based content creators using Final Cut Pro or iPhone recordings in MOV format need FLV to feed content into RTMP streaming pipelines — the backbone of live broadcasting on Twitch, YouTube Live, Facebook Live, and custom streaming servers. FLV is the native container for RTMP protocol, making this conversion essential for anyone broadcasting pre-recorded MOV content as a live stream.

A common workflow involves recording or editing on Mac in MOV format, then converting to FLV for scheduled or simulated live broadcasts. Streamers running 24/7 content channels queue pre-recorded FLV files for continuous RTMP delivery. Event production teams convert recorded segments from cameras (which output MOV) to FLV for insertion into live broadcast mixes. OBS Studio and similar tools can play FLV files as media sources during live productions.

Legacy enterprise systems also drive this conversion. Many corporate training platforms and e-learning systems built during the Flash era (2005-2015) require FLV uploads. Organizations updating their video content — now commonly recorded on iPhones or exported from Apple editing tools as MOV — must convert to FLV for these aging but still-operational platforms.

The conversion is straightforward for MOV files with H.264 video and AAC audio — these can be remuxed to FLV without re-encoding. ProRes or HEVC MOV files require transcoding to H.264, which adds processing time. All of MOV's professional features (timecode, alpha channel, multiple audio tracks) are lost in the conversion.

Key Benefits of Converting MOV to FLV:

• RTMP Native: Required format for RTMP live streaming protocol
• Mac to Stream: Bridge between Apple production tools and streaming platforms
• OBS Compatible: Play as media source in live broadcast software
• H.264 Remux: MOV with H.264/AAC converts instantly without re-encoding
• Platform Ingest: Accepted by Twitch, YouTube Live, Facebook Live RTMP endpoints
• Legacy LMS: Compatible with Flash-era learning management systems
• Low Latency: Optimized for real-time delivery

Practical Examples

Example 1: Final Cut Pro Export to Twitch Stream

Scenario: A content creator edits gameplay commentary in Final Cut Pro, exports MOV, and needs FLV to simulate a live stream on Twitch during scheduled broadcast hours.

Source: commentary_ep15.mov (3 GB, 1920x1080, H.264, AAC stereo)
Conversion: MOV → FLV (RTMP-ready for Twitch)
Result: commentary_ep15.flv (3 GB, same H.264/AAC streams)

Workflow:
1. Remux H.264/AAC from MOV to FLV (instant, lossless)
2. Add FLV keyframe metadata for seek support
3. Push to Twitch via FFmpeg RTMP
✓ Lossless conversion — bit-identical streams
✓ Conversion takes seconds (remux only)
✓ FFmpeg streams directly to Twitch RTMP ingest
✓ Viewers see content as live broadcast

Example 2: iPhone Recording for Corporate LMS

Scenario: An HR manager records training videos on their iPhone in MOV and must upload them to the company's Flash-era learning management system that only accepts FLV.

Source: onboarding_welcome.mov (450 MB, 1920x1080, HEVC, AAC)
Conversion: MOV → FLV (LMS upload compatible)
Result: onboarding_welcome.flv (380 MB, H.264, AAC)

Workflow:
1. Transcode HEVC to H.264 Main Profile (FLV compatible)
2. Keep AAC audio (supported in FLV)
3. Package in FLV container
4. Add metadata with yamdi for seek support
5. Upload to corporate LMS
✓ LMS accepts and plays FLV without issues
✓ HEVC quality preserved through H.264 re-encode
✓ Seeking works in legacy Flash-based player
✓ No LMS infrastructure changes needed

Example 3: Multi-Platform Live Broadcast

Scenario: An event producer records ceremony segments on cameras saving MOV and needs to inject them into a multi-platform live stream running on nginx-rtmp during breaks.

Source: ceremony_segment_b.mov (1.5 GB, 1920x1080, ProRes 422, PCM)
Conversion: MOV → FLV (live broadcast insertion)
Result: ceremony_segment_b.flv (800 MB, H.264 4Mbps, AAC 192k)

Workflow:
1. Transcode ProRes to H.264 at 4 Mbps (stream bitrate)
2. Convert PCM to AAC stereo at 192 kbps
3. Match live stream encoding parameters exactly
4. Push FLV to nginx-rtmp server during break
✓ Seamless insertion into live broadcast
✓ Matching bitrate prevents viewer rebuffering
✓ nginx-rtmp handles FLV natively
✓ Simultaneous delivery to YouTube/Facebook/Custom

Frequently Asked Questions (FAQ)

Q: Can I remux MOV to FLV without re-encoding?

A: Yes, if your MOV contains H.264 video and AAC or MP3 audio: ffmpeg -i input.mov -c copy -f flv output.flv. This is instant and lossless. ProRes and HEVC codecs are not supported in FLV and must be re-encoded to H.264. ALAC and PCM audio must be converted to AAC or MP3.

Q: Why do I need FLV if I can stream MOV directly?

A: RTMP protocol requires FLV as its container format. You cannot push MOV directly to an RTMP server. FFmpeg can convert on-the-fly during streaming: ffmpeg -re -i input.mov -c:v copy -c:a aac -f flv rtmp://server/live/key, but the output is still FLV. The FLV conversion happens whether you pre-convert or stream live.

Q: What happens to ProRes quality during conversion?

A: ProRes must be re-encoded to H.264 for FLV. At CRF 18-20, the quality is excellent and visually indistinguishable from ProRes for streaming purposes. The file size will be dramatically smaller (ProRes is 100+ Mbps; streaming H.264 is typically 4-8 Mbps). You're going from editing quality to delivery quality — appropriate for streaming but not for further editing.

Q: Does FLV support 4K resolution?

A: The FLV specification doesn't explicitly limit resolution, and H.264 in FLV can technically handle 4K. However, most RTMP servers and players are tested for 1080p maximum. For reliable streaming, 1080p at 30fps or 720p at 60fps are the standard configurations. 4K streaming typically uses HLS/DASH with MP4/TS segments, not RTMP/FLV.

Q: Will my MOV's timecode and chapters transfer to FLV?

A: No. FLV has no support for timecode tracks, chapter markers, or professional metadata. All MOV-specific features (timecode, chapters, alpha channel, multiple audio tracks) are lost during conversion. FLV is a simple delivery container — it holds one video stream and one audio stream, nothing more.

Q: Is there a better alternative to FLV for streaming?

A: For RTMP ingest (sending to streaming servers), FLV is still required and there's no alternative. For delivery to viewers, platforms convert from RTMP/FLV to HLS (TS/fMP4 segments) or DASH (fMP4 segments) automatically. Newer protocols like SRT and RIST are emerging for professional broadcast but haven't replaced RTMP for public streaming platforms yet.

Q: Can I convert multiple MOV files for a playlist stream?

A: Yes. Convert each MOV to FLV, then use FFmpeg's concat demuxer to stream them sequentially: create a playlist.txt file listing each FLV, then ffmpeg -f concat -i playlist.txt -c copy -f flv rtmp://server/live/key. This creates a continuous stream from multiple pre-recorded segments — perfect for 24/7 content channels.

Q: How do I handle iPhone HEVC MOV files?

A: iPhone HEVC (H.265) MOV files must be re-encoded to H.264 for FLV compatibility: ffmpeg -i iphone_video.mov -c:v libx264 -crf 22 -c:a aac -b:a 128k -f flv output.flv. The re-encoding adds processing time (roughly real-time speed on modern hardware) but produces FLV files compatible with all RTMP infrastructure.