Convert TS to FLV

Why Convert TS to FLV?

Converting TS to FLV serves a specific niche: preparing broadcast content for RTMP-based live streaming infrastructure. While FLV is a deprecated format for general web video, RTMP (Real-Time Messaging Protocol) continues to be the dominant ingest protocol for live streaming platforms including Twitch, YouTube Live, and Facebook Live. These platforms accept RTMP/FLV ingest even though they deliver content to viewers via HLS or DASH. When you need to re-stream broadcast TS content to these platforms, converting to FLV is the standard approach.

The most common workflow involves capturing live broadcast television (DVB, ATSC, or IPTV) as a Transport Stream and re-streaming it via RTMP to an online platform. The TS-to-FLV conversion happens in real-time using FFmpeg as a transcoding bridge. The broadcast feed enters as TS with MPEG-2 or H.264 video, gets transcoded to H.264 with AAC audio, and exits as an FLV stream directed to the RTMP endpoint. This is how many re-broadcasting and simulcasting workflows operate.

Another scenario is converting archived broadcast recordings from TS to FLV for integration with legacy Flash-based content management systems. Some educational institutions and corporate training platforms still maintain Flash-based video delivery infrastructure that expects FLV files. While migrating to modern formats is advisable, converting existing TS archives to FLV provides a quick compatibility bridge during the transition period.

The limitations of this conversion are significant: FLV supports only a single audio track, no subtitles, no chapters, and a maximum resolution of 1080p. Any broadcast-specific metadata (EPG, teletext, DVB subtitles) from the TS source is lost entirely. For non-RTMP use cases, converting TS to MP4 or MKV is strongly preferred. FLV should only be the target format when RTMP streaming or legacy Flash system compatibility is the specific requirement.

Key Benefits of Converting TS to FLV:

• RTMP Streaming: Required format for live streaming ingest to major platforms
• Low Latency: FLV/RTMP provides minimal delay for live content delivery
• Broadcast Re-streaming: Bridge TV broadcasts to online streaming platforms
• Compact Files: Efficient H.264+AAC encoding for small output sizes
• Real-time Processing: FFmpeg can convert TS to FLV in real-time for live workflows
• Platform Compatibility: Accepted by Twitch, YouTube Live, Facebook Live RTMP endpoints
• Legacy Support: Works with existing Flash-based CMS and video platforms

Practical Examples

Example 1: Live Broadcast Re-streaming to Twitch

Scenario: A community TV station wants to simulcast their local broadcast to Twitch. The broadcast feed is captured as a continuous MPEG Transport Stream from their DVB-T encoder.

Source: live_broadcast.ts (continuous stream, 1920x1080, MPEG-2, MP2)
Conversion: TS → FLV (real-time RTMP ingest)
Result: RTMP stream to rtmp://live.twitch.tv/app/STREAMKEY

Live streaming pipeline:
1. Receive DVB-T broadcast as TS input
2. Transcode MPEG-2 to H.264 at 6 Mbps
3. Convert MP2 audio to AAC at 160 kbps
4. Output FLV stream to Twitch RTMP endpoint
5. FFmpeg runs continuously during broadcast
✓ Sub-5-second latency from broadcast to Twitch
✓ H.264 High Profile for maximum quality at bitrate
✓ Audio normalized for consistent volume
✓ Automatic reconnection on network interruptions

Example 2: IPTV Recording to Flash LMS

Scenario: A corporate training department records internal IPTV training sessions as TS files and needs to upload them to a legacy Flash-based Learning Management System that only accepts FLV files.

Source: training_compliance_2026.ts (1.8 GB, 1280x720, H.264, AAC)
Conversion: TS → FLV (for legacy Flash LMS)
Result: training_compliance_2026.flv (680 MB, 1280x720, H.264, AAC)

LMS upload workflow:
1. Convert TS container to FLV container
2. Re-encode video to H.264 Baseline for Flash compatibility
3. Add FLV metadata with yamdi for seeking support
4. Upload to Flash-based LMS
✓ File size reduced by removing TS packet overhead
✓ Seeking works properly with injected keyframe metadata
✓ Plays in legacy Flash-based course viewer
✓ Compatible with SCORM Flash wrapper

Example 3: Multi-Platform Simulcasting

Scenario: A sports event organizer captures their venue cameras as TS feeds and needs to simultaneously stream to YouTube Live, Facebook Live, and a custom RTMP server.

Source: venue_cam_main.ts (continuous, 1920x1080, H.264, AC-3)
Conversion: TS → FLV (multi-destination RTMP)
Result: 3 simultaneous FLV/RTMP streams

Simulcast setup:
1. Receive TS feed from venue encoder
2. Transcode to H.264 + AAC (single decode/encode)
3. Split output to 3 RTMP destinations as FLV
4. YouTube: rtmp://a.rtmp.youtube.com/live2/KEY
5. Facebook: rtmp://live-api-s.facebook.com:80/rtmp/KEY
6. Custom: rtmp://stream.example.com/live/KEY
✓ Single transcode, multiple RTMP outputs
✓ Platform-specific bitrate adaptation per destination
✓ AC-3 surround downmixed to AAC stereo
✓ Less than 3-second glass-to-glass latency

Frequently Asked Questions (FAQ)

Q: Is FLV still relevant in 2026?

A: For file storage and playback, no — FLV is effectively dead since Flash Player's end-of-life in 2020. However, FLV remains the container format used by RTMP, which is still the dominant ingest protocol for live streaming platforms. When you stream to Twitch, YouTube Live, or Facebook Live via RTMP, you are sending FLV-packaged data. So FLV is still very relevant for live streaming infrastructure, just not for file-based video.

Q: Can I do a lossless remux from TS to FLV?

A: Only if your TS file uses H.264 video and AAC audio — these codecs are compatible with FLV. Use ffmpeg -i input.ts -c copy -f flv output.flv for a lossless remux. If the TS uses MPEG-2 video or MP2 audio, you must re-encode to H.264/AAC since FLV does not support MPEG-2 codecs.

Q: What happens to subtitles and EPG data from the TS file?

A: All broadcast-specific metadata is lost. FLV has no support for DVB subtitles, teletext, EPG data, or multiple audio tracks. Only the primary video and audio streams are carried over. If you need to preserve subtitles, convert to MKV or MP4 instead.

Q: How do I convert TS to FLV for RTMP streaming in real-time?

A: Use FFmpeg with the RTMP output URL: ffmpeg -i udp://@239.0.0.1:1234 -c:v libx264 -preset veryfast -c:a aac -f flv rtmp://server/live/key. The -preset veryfast ensures real-time encoding speed. Adjust the bitrate with -b:v to match your upload bandwidth.

Q: What resolution should I use for the FLV output?

A: For RTMP streaming, common resolutions are 1920x1080 (6 Mbps), 1280x720 (3-4 Mbps), or 854x480 (1.5 Mbps). Match the resolution and bitrate to your upload bandwidth and the platform's recommendations. YouTube Live recommends 1080p at 4.5-9 Mbps, while Twitch recommends 720p-1080p at 3-6 Mbps.

Q: Can FLV handle H.265/HEVC from my TS file?

A: No. FLV does not support H.265/HEVC. If your TS file uses HEVC video, it must be transcoded to H.264 during the conversion. This means quality may decrease slightly or bitrate must increase to maintain quality. Enhanced RTMP (a newer extension) adds HEVC support, but it is not yet widely supported by all platforms.

Q: Why is my FLV file smaller than the original TS?

A: TS files have significant packet overhead — each 188-byte packet includes sync bytes, PID headers, and adaptation fields. FLV has much less container overhead. Additionally, if you re-encoded from MPEG-2 to H.264, the more efficient codec produces smaller files at equivalent quality. A 2 GB MPEG-2 TS file might produce a 700 MB H.264 FLV at similar visual quality.

Q: Should I convert to FLV or MP4 for web video?

A: Always use MP4 for web video playback. FLV requires the deprecated Flash Player for browser playback and has no HTML5 support. The only reason to use FLV is for RTMP live streaming ingest. For any file-based web video — downloads, embeds, progressive streaming — MP4 with H.264 is the correct choice.