What is MPEG-TS?
MPEG-TS is a packetized transport container for multiplexing audio, video, subtitles, and program information; files that carry it commonly use the .ts extension. Its synchronization and error-tolerance features suit transmission over unreliable channels.
How MPEG-TS works
An MPEG transport stream divides elementary streams and signaling tables into fixed-size packets identified by packet IDs. Receivers use continuity counters, timestamps, and regularly repeated tables to reconstruct programs and keep playback aligned after tuning or packet loss. A single multiplex can carry several programs, each mapping video, audio, and ancillary streams through program-specific metadata. This design sits between compressed essence and broadcast, IPTV, or segmented delivery systems.
Key facts
- 1Standard TS packets are 188 bytes and begin with sync byte 0x47; some delivery systems add outer bytes for error correction or timestamps.
- 2The Program Association Table points to each program’s Program Map Table, which lists the packet identifiers carrying its elementary streams.
- 3Remultiplexing can change program selection, packet timing, or transport bitrate without recompressing the audio and video payloads.
When MPEG-TS matters
Choose MPEG-TS for broadcast, IPTV, contribution feeds, or traditional HLS segment delivery. Its resilience and multiplexing support add overhead compared with containers optimized for reliable file storage.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically MPEG-TS.
- Accepting heterogeneous uploads while producing a controlled set of delivery formats.
- Moving assets between cameras, editors, browsers, archives, and downstream APIs.
- Separating long-lived source files from compact derivatives optimized for a particular channel.
Working with file formats & compression
This guidance covers file formats & compression broadly, not just MPEG-TS.
A parser reads the file structure, identifies contained streams and metadata, and exposes them to a decoder or application. Conversion usually decodes the source representation and writes compatible information into a different structure or encoding.
This category covers file and bitstream formats, their structures, and the compression methods they use. A filename extension can be misleading, so evaluate the detected format, decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
What you gain
- A suitable format preserves the properties a workflow actually needs.
- Standardized structures allow files to move between compatible tools and systems.
- Format conversion can improve delivery size, editability, or long-term accessibility.
What it costs
- Modern formats can save bandwidth but may need fallbacks for older clients and production tools.
- Converting to a simpler format can discard transparency, animation, metadata, color precision, or editability.
- Archival suitability, browser support, and editing support often favor different choices.
Before production
- 1Inspect the detected container, codec, MIME type, and magic bytes instead of trusting a suffix.
- 2Verify decoder support and preserve metadata, color, transparency, or timing when required.
- 3Retain the source when the chosen delivery format is lossy or tied to current software.