How Transport Stream Works
TS (MPEG Transport Stream) is a video format built for a very specific job: broadcasting and streaming over unreliable channels. Instead of a single neatly-indexed file like MP4, an MPEG-2 Transport Stream multiplexes audio, video, and data into a continuous series of small, fixed-length 188-byte packets. Each packet carries a packet identifier (PID) labeling which elementary stream it belongs to, so a receiver can pick out the video, audio, and metadata it needs from the interleaved flow.
This packetized design exists for resilience. In broadcast and live streaming, data can be lost or a viewer can tune in partway through, so the format must let a player start decoding from the middle of the stream and recover from errors. The small fixed packets and periodically repeated program information (tables that describe what streams the program contains) make that possible: a receiver does not need the start of the file or a complete index to begin playing, which is exactly what live TV and adaptive streaming require.
That same design is why TS underpins so much modern delivery. It is the container used in digital television broadcasting (DVB, ATSC), on Blu-ray discs (as M2TS), and in HTTP streaming protocols like HLS, where video is chopped into short .ts segments delivered one after another. So even though you rarely create a TS file yourself, the format is everywhere in how live and streamed video reaches you.
TS Files vs MP4
The difference between TS and MP4 comes down to streaming robustness versus tidy storage. TS is optimized to be broadcast and recovered from mid-stream, so it repeats information and tolerates loss, but it is not as compact or as cleanly seekable as MP4 for a stored file. MP4, by contrast, is built around a single index (the moov box) that makes it efficient to store and seek but assumes you have the whole, intact file. They serve different stages: TS for transmission, MP4 for storage and sharing.
This is why converting TS to MP4 is so common. When you record live TV, capture a stream, or end up with .ts segments, the result is awkward to edit, share, or play in everyday apps. Repackaging the same video and audio into MP4, often without re-encoding, just rewrapping, produces a single tidy file that behaves the way people expect: easy to seek, edit, upload, and play anywhere.
When You Encounter TS
You meet TS files when you are close to broadcast or streaming: recordings from a TV tuner or set-top box, captured live streams, HLS video segments, or footage pulled from Blu-ray. In all these cases the TS format did its job of delivering the video reliably, and the natural next step is to convert it to MP4 for storage and use. You would not choose TS to author a normal video; you encounter it as the transport format and then move the content into MP4.
Limitations
TS's limitations are the cost of its streaming-first design. Because it repeats program information and uses fixed packets, it carries more overhead than MP4 and is less convenient as a stored file: editing, precise seeking, and playback in consumer apps are all clumsier than with MP4. It is also frequently split into many segments rather than one file. None of this is a flaw, it is exactly what makes TS robust for transmission, but it is why TS is a delivery format you convert from rather than a format you keep video in.
