Why won't the merged TS file play, or why does it say the format isn't supported?

Most often the segments themselves are incomplete (a truncated download or a missing clip), or the codec isn't something your player handles. Open the first .ts on its own in a player like VLC to confirm the source is fine. If the source plays but the merged file is black, it's usually a container/muxing issue. Re-merge with stream copy using the TS File Merger, which only swaps the container without re-encoding.

My merged TS has no audio. How do I fix it?

Three usual culprits: 1) the source TS had no audio track to begin with; 2) the audio codec isn't MP4-friendly (AC-3 is a common one) and needs to be transcoded to AAC; 3) the audio stream got dropped during merge. Use a tool with a re-encode mode to normalize audio to AAC, or just run it through the in-browser TS Merger, which handles this automatically.

The audio and video drift out of sync after merging. What now?

That happens when the TS segments have mismatched timebases or frame rates. Stream copy can't fix it, you need a re-encode pass to unify the parameters. If the source came from an HLS stream, it's cleaner to convert the whole M3U8 to MP4 directly with the M3U8 to MP4 tool, which keeps A/V in sync for you.

The merged video jumps around — the segment order is wrong. Why?

TS filenames often don't contain a sortable sequence number, so a tool that sorts them alphabetically (1.ts, 10.ts, 2.ts) gets it wrong. Rename them by capture/download time (0001.ts, 0002.ts…) before merging. For M3U8 batches, keep the original playlist order, the TS Merger concatenates strictly in the order you list.

Encrypted TS (.key / AES-128) merge fails saying the key is missing?

Encrypted TS needs its key file, usually a .key in the same folder or the key URL declared in the m3u8. Put the .key next to the .ts files and make sure it's reachable, then merge. If the key is remote and behind auth, download it locally first. Our TS Merger lets you point at a local key path to do the AES-128 decrypt-and-merge.

The browser freezes or runs out of memory on large merges?

In-browser processing is bounded by RAM, so loading hundreds of segments at once can blow the memory budget. Merge in smaller batches (a few dozen clips each), or if it's a very long recording, process the M3U8 to MP4 in one go to avoid repeated large local reads/writes.

Why does the merged video look worse than the original?

That's the re-encode mode doing lossy compression. For a lossless merge, use stream copy (no re-encode, just change the container). In FFmpeg that's -c copy, and TS→MP4 only swaps the wrapper with zero quality loss. The TS Merger uses stream copy by default, so output matches the source.

TS Merge Failed or Won't Play? A Practical Troubleshooting Guide

First, figure out: is it a merge failure or a playback failure?

When people say "the merge failed," they usually mean one of two different things:

The merge errors out or hangs — the tool can't stitch the clips together. Usually a corrupted source, a missing segment, or an encrypted stream with no key.
It merges, but playback is broken — you get an MP4 that's black, silent, or stuttering. The problem is in the codec or muxing parameters.

Below, we go through the issues by how often they actually show up.

The 7 most common problems (and how to fix them)

1. Black screen after merge / "format not supported"

Cause: a segment downloaded incompletely (missing header or tail), or the player doesn't support the codec. Check: open the first .ts alone in VLC to confirm the source plays. If the source is fine but the merge is black, it's a muxing problem — re-merge with the TS File Merger using stream copy, which only swaps the container without re-encoding and gives the best compatibility.

2. No audio after merging

Cause: ① the source TS simply had no audio track; ② the audio codec isn't MP4-friendly (e.g. AC-3) and needs to be transcoded to AAC; ③ the audio stream was dropped during the merge. Fix: use a tool with a re-encode mode to normalize audio to AAC. The in-browser TS Merger does this automatically, no FFmpeg install required.

3. Audio/video drift, getting worse over time

Cause: the TS segments have mismatched timebase or frame rate. Fix: plain stream copy can't correct this — you need a re-encode merge to unify the parameters. If the source is an HLS stream, the cleaner path is to convert the whole M3U8 to MP4 with the M3U8 to MP4 tool, which keeps A/V in sync automatically.

4. Wrong order, picture jumps around

Cause: TS filenames usually don't carry an incrementing index, so alphabetical sorting (1.ts, 10.ts, 2.ts) breaks the sequence. Fix: rename by capture/download time, like 0001.ts, 0002.ts…, then merge. For M3U8 batches keep the original playlist order — the TS Merger concatenates strictly in the listed order.

5. Encrypted TS (AES-128 / .key) merge fails

Cause: missing key file, or the key is remote and needs auth. Fix: place the .key next to the .ts files and make sure it's reachable; if it's a remote key, download it locally first. The TS Merger supports entering a local key path to do the AES-128 decrypt-and-merge. For more on encrypted HLS, see M3U8 to MP4 Failed?.

6. Browser freezes / runs out of memory on big merges

Cause: in-browser processing is capped by available RAM; loading too many segments at once exhausts it. Fix: merge in batches (a few dozen clips each); for very long recordings, use the M3U8 to MP4 tool to process the whole thing at once and skip the repeated local read/write.

7. Quality dropped after merging

Cause: you used re-encode mode (lossy). Fix: pick stream copy (stream copy) for a lossless merge. The FFmpeg flag is -c copy, and TS→MP4 only changes the container with zero loss. The TS Merger uses stream copy by default, so quality matches the source.

TL;DR decision tree

Can a single .ts play on its own?
├─ No  → source is corrupt / incomplete → re-download the segments
└─ Yes → is there a problem after merge?
        ├─ black / unsupported format → re-merge with stream copy (/en/ts-merge)
        ├─ no audio → transcode audio to AAC (re-encode mode)
        ├─ A/V desync → re-encode to unify params (or use /en/m3u8-to-mp4)
        ├─ wrong order → rename by time, then merge
        └─ encryption error → add the .key, then decrypt-merge

Which tool, and when

No local software, just want it done: the in-browser TS File Merger — stream-copy lossless merge, AES-128 decrypt, encrypted TS supported.
Source is an HLS live/VDN stream: go straight to the M3U8 to MP4 tool for a one-step, sync-correct result.
Need fine-grained control: use FFmpeg on the command line — see TS File Merge Tutorial: 4 Methods Compared.

Wrapping up

Most TS merge failures boil down to four things: incomplete source, missing encryption key, codec incompatibility, wrong segment order. Confirm a single segment plays first, then pick stream copy / re-encode / decrypt-merge accordingly. Use the right tool for the job — TS merge handles the "stitch," M3U8 conversion handles the "whole" — and you can fix almost everything right in the browser.

Further reading: M3U8 to MP4 Failed? Black screen / encryption / 403 · TS File Merge Tutorial: 4 Methods Compared

First, figure out: is it a merge failure or a playback failure? ​

The 7 most common problems (and how to fix them) ​

1. Black screen after merge / "format not supported" ​

2. No audio after merging ​

3. Audio/video drift, getting worse over time ​

4. Wrong order, picture jumps around ​

5. Encrypted TS (AES-128 / .key) merge fails ​

6. Browser freezes / runs out of memory on big merges ​

7. Quality dropped after merging ​

TL;DR decision tree ​

Which tool, and when ​

Wrapping up ​