A TS file is an MPEG transport stream, the container used for digital broadcasting and for many recordings from TV tuners, set-top boxes, camcorders, and streaming captures. It is built to survive transmission over an unreliable channel and to be joined or split at any point, which makes it robust but awkward: not every player and editor handles it cleanly, and some show the wrong duration or refuse to scrub through it. Converting TS to MP4 repackages that same video into the standard container that essentially everything understands.
The good news is that TS and MP4 very often carry the same underlying video codec, typically H.264, and the same audio, typically AAC or AC-3.[2] When that is the case, the conversion is a simple remux: the compressed streams are copied straight across into an MP4 wrapper with no re-encoding at all, so it finishes in seconds and loses no quality whatsoever. This guide explains exactly why TS is shaped the way it is, when the fast lossless path is available, and how to do the conversion in your browser.
What a TS file is and why you convert it
Transport stream was designed for delivery, not for tidy storage on a hard drive. It packages audio and video into a continuous series of small, fixed-size packets, each 188 bytes long, so that a receiver can lock onto the stream partway through, which is exactly what happens when you change the channel and a broadcast appears almost immediately. Every packet carries an identifier telling the decoder which stream it belongs to, and the format periodically repeats the tables that describe the stream layout so a late-joining receiver can catch up. That design is brilliant for broadcasting and terrible for casual editing: recordings are sometimes saved as several TS chunks, timestamps can wrap around or restart, and the file has no single tidy index of its contents the way MP4 does.
So the usual reason to convert is compatibility and tidiness. You want a single clean file that plays on your phone, imports into an editor without complaint, seeks instantly to any point, and shares without anyone asking what a TS file even is. MP4, built for storage and playback rather than transmission, gives you all of that while keeping the original picture and sound completely intact.
TS holds the same video as MP4 but in a broadcast-oriented, packet-based wrapper. Converting is mostly about repackaging those streams into a container everything supports.
How transport stream and MP4 are built
The two formats solve opposite problems, and seeing the difference explains why the conversion is usually painless. MPEG-2 transport stream is defined in the MPEG-2 Systems standard, formally ITU-T H.222.0, and its whole architecture is oriented around resilience during transmission.[2] Because it is a stream of small packets with the structural tables repeated over and over, a transport stream can be broken, rejoined, or started midway and still be decodable, which is essential when the signal arrives over the air or a lossy network. The Library of Congress catalogs it as a robust delivery format, noting its packet structure and its role in broadcast and recording.[1]
MP4 is built on the ISO base media file format and assumes a reliable file on storage.[4] Instead of endlessly repeated tables, it keeps a single organized index, the moov box, that maps out exactly where every frame lives and how the streams line up in time.[3] That index is what lets a player jump instantly to the twenty-minute mark or report the precise duration, and it is why MP4 imports cleanly into editors. The conversion, then, is really about discarding the transport packaging and building that clean index around the same compressed video and audio, which is a repackaging job, not a re-encoding one.
How the conversion works under the hood
A TS-to-MP4 converter runs a short pipeline. First it demultiplexes the transport stream, walking through the 188-byte packets, sorting them by their stream identifiers, and reassembling the fragmented packets back into whole compressed video and audio frames. This is the step that undoes the broadcast packaging. Next it examines the codecs: it reads what the video and audio streams are actually encoded with, because that determines whether the fast path is available.
If the codecs are ones MP4 accepts, which for TS they usually are, the converter takes the remux path: it writes those exact compressed frames into an MP4 structure and builds the moov index around them, correcting the timestamps as it goes so playback is smooth from the first frame. No pixel is ever decoded or re-compressed, so the output is bit-for-bit identical in quality and the job finishes almost instantly. Only if a stream uses something MP4 cannot hold does the converter fall back to re-encoding that stream, decoding it to raw frames and compressing it again into an MP4-friendly codec. Understanding this branch is the key to the whole conversion, because it decides both the speed and whether any quality is lost.
There is a subtlety in the audio worth calling out. Broadcast transport streams frequently carry their sound as AC-3 (Dolby Digital) rather than the AAC that MP4 uses most often. MP4 can carry AC-3, so a remux may keep it untouched, but some target players expect AAC, in which case only the audio is re-encoded while the video is still copied losslessly. This mixed outcome, a copied picture with a converted soundtrack, is common with TV recordings and is perfectly fine: the video, which is the part that would show any quality loss, is preserved exactly, and a re-encoded audio track is imperceptibly different at normal bit rates. Knowing this explains why a "lossless" TS conversion sometimes still spends a moment on the audio.
Convert TS to MP4, step by step
Open the converter and add your TS file
Open the FileFormer video converter and add the TS file. It is processed on your device and never uploaded.
Set the output to MP4
Choose MP4 as the target. The tool reads the streams inside the TS and prepares to place them in a standard MP4 container.
Let it copy the streams if it can
When the video codec is already MP4-compatible, the tool copies it across without re-encoding. This is fast and keeps the picture identical to the source.
Export and download
Convert and save the MP4. It will now open in any player or editor without the quirks TS sometimes causes.
Remux versus re-encode
The speed and quality of this conversion depend entirely on whether it can remux or has to re-encode. A remux copies the existing compressed streams into a new container; a re-encode decompresses and compresses again. You want the remux path whenever possible.
| Aspect | Remux (stream copy) | Re-encode |
|---|---|---|
| When it applies | Codec already MP4-friendly | Codec needs changing |
| Speed | Fast | Slower |
| Quality | Identical to source | Small loss |
| Typical case for TS | Common (H.264 inside) | Occasional |
If the conversion finishes almost instantly, it remuxed. If it takes a while and works your device hard, it re-encoded because the codec inside the TS was not directly compatible.
Timestamps, packets, and playback quirks
Most of the odd behavior people see with TS files, and the occasional glitch after conversion, traces back to how transport stream handles time. Every packet in a transport stream carries timing references, and a program clock reference keeps the audio and video in sync as the stream plays. Because the format is built for continuous broadcast, those timestamps are stored as counters that periodically wrap back to zero, and a recording that started midway through a broadcast may begin with timestamps that do not start at zero at all. This is why a raw TS can report a nonsensical duration or refuse to seek smoothly.
A good converter cleans this up during the remux. As it builds the MP4 index, it normalizes the timestamps so the file starts at zero and runs monotonically, which is what gives you accurate duration and instant seeking in the result. Occasionally a recording with a corrupt or missing packet at the very start produces a brief stutter or an offset between picture and sound; when that happens, trimming the first fraction of a second, or letting the tool re-encode rather than remux, usually resolves it. These are edge cases, but they are worth knowing about because they explain the rare TS file that does not convert perfectly on the first try.
Real-world scenarios and the right approach
What you should expect depends on where the TS came from. A few common cases:
| Scenario | What to expect |
|---|---|
| A recording from a TV tuner or DVR | Usually H.264 inside, so a fast lossless remux. Check which audio track came across if the broadcast carried more than one. |
| A stream captured from the web | Almost always H.264 and AAC, the ideal case for an instant remux with no quality loss. |
| Several TS chunks from one recording | Join them in order, then convert; the result is one clean MP4 with a correct duration. |
| An older MPEG-2 broadcast recording | MP4 can carry MPEG-2, but for broad device support you may prefer a re-encode to H.264. |
| A file that seeks or reports duration wrong | The remux rebuilds the index and normalizes timestamps, which typically fixes both. |
The theme is that TS almost always holds video a modern MP4 can accept, so the overwhelmingly common outcome is a quick, lossless repackage. Re-encoding is the exception, reserved for older codecs or the odd damaged capture.
A few things to watch for
Recorded TS files sometimes include multiple audio tracks or embedded subtitles from a broadcast. When repackaging, confirm the audio track you want came across, especially with recordings that carried more than one language, and remember that some broadcast subtitle formats do not survive the move to MP4. It is also worth checking playback timing, since TS from a live capture can occasionally have an odd start point that the timestamp cleanup usually, but not always, resolves.
Beyond that, there is little downside. Because the common case is a lossless remux, converting TS to MP4 is one of the safest, most useful video conversions there is: you get a friendlier, universally playable file with no quality cost at all, and you can keep the original TS if you ever need the untouched broadcast source.
It is also worth knowing what the conversion cannot do. A remux copies the picture exactly as the broadcast delivered it, so if the original transmission was low bit rate or already showed compression artifacts, the MP4 inherits them unchanged; converting never improves a source. Similarly, a TS captured from an interlaced broadcast stays interlaced after a plain remux, because remuxing does not touch the frames. If you want to deinterlace such footage for a modern progressive screen, that specifically requires a re-encode, since the pixels have to be recomputed. For the vast majority of TS files, though, none of this applies: the source is already clean progressive H.264, and the remux hands you a perfect, portable copy in seconds.
Turn your TS into an MP4 now
Add the TS file, choose MP4, and download a clean standard video, all in your browser.
Key takeaways
- TS is a packet-based broadcast and recording container; MP4 is the storage standard everything supports.
- The conversion is often a fast, lossless remux because the video codec already fits MP4.
- An instant finish means it remuxed; a slow one means it had to re-encode an older codec.
- The remux rebuilds the index and normalizes timestamps, fixing wrong durations and jumpy seeking.
- Check the audio track and start timing on recordings that captured multiple streams.