MPEG-TS — MPEG Transport Stream — is the old, broadcast-era container format that wraps video and audio into small fixed-size packets. Designed in the 1990s for over-the-air digital television (DVB, ATSC, ISDB) and satellite broadcasting, MPEG-TS was built for one thing: surviving lossy transmission. Each 188-byte packet stands on its own, carries its own synchronisation header, and can be partially recovered even if some packets get corrupted or dropped along the way.
For decades, MPEG-TS was also the standard segment format for Apple's HLS streaming protocol — every HLS segment was a .ts file containing a chunk of compressed video and audio. That changed around 2017 when Apple added CMAF/fMP4 support to HLS, and the industry began migrating away from MPEG-TS to fragmented MP4 segments. Today, MPEG-TS lives mostly in legacy contexts: traditional broadcast TV, satellite feeds, contribution links between broadcasters, IPTV systems built before the streaming-protocol consolidation.
For a product team in 2026, MPEG-TS comes up in two scenarios. Ingest from broadcast or live sources: contribution feeds from cameras, encoders or playout systems often arrive as MPEG-TS over SRT, Zixi, RIST or raw UDP — your pipeline transmuxes them into fMP4 for streaming delivery. Legacy IPTV and STB delivery: if you're targeting older set-top boxes or operator-managed networks, you may still need to output MPEG-TS for compatibility. For everything else — modern web streaming, mobile apps, smart TV apps — fragmented MP4 via CMAF has replaced MPEG-TS as the universal container.
