What is a TS File?
A TS file contains an MPEG transport stream of fixed-size packets that multiplex video, audio, and metadata. The format tolerates transmission errors and is widely used for broadcasting and traditional HLS segments.
How TS Files work
A .ts file stores an MPEG transport stream as an ordinary file rather than a live transmission. MPEG-TS is a fixed-packet, error-tolerant container. The same layout can come from a broadcast capture, a contribution feed, or an HTTP Live Streaming packager, and its design favors continuous scanning over compact file indexing. Media packagers still emit .ts segments for established HLS and broadcast-compatible paths, while newer pipelines often prefer fragmented MP4.
Key facts
- 1Traditional HLS delivers video as a playlist of short .ts segment files; each transport-stream segment must contain a single program and carry its own PAT and PMT signaling tables unless a playlist-level media-initialization tag supplies them.
- 2HLS also defines fragmented MP4 media segments, so .ts packaging is a compatibility choice for established players and broadcast tooling rather than the only segment format the protocol allows.
- 3.mts files from AVCHD camcorders also carry MPEG transport streams. Ingest tools should therefore identify the actual stream layout by probing content rather than trusting the extension.
When TS Files matter
Use TS segments when compatibility with established broadcast or HLS systems is required. Packet overhead and target-player support may make newer fragmented MP4 packaging preferable for other workflows.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically TS Files.
- 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 TS Files.
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.