What is inside a .ts file
A transport stream is a sequence of fixed 188-byte packets. Each packet belongs to one stream, identified by a 13-bit packet identifier (PID). Some PIDs carry the table that says which programs exist and which PIDs belong to them; the rest carry the audio and video data itself. That structure is why a .ts file plays without a central index: a player can join at any packet boundary and start reading.
This page reads the file and lists what it finds: how many packets there are, which PIDs are in use, which program they belong to and which codec each one carries.
What the report shows
- Packets and size — how many 188-byte packets were found, and how many bytes they account for.
- Sync errors — packets where the 0x47 sync byte was not where it should be. A few usually mean the file starts with something else; many mean truncation or corruption.
- Programs — the PAT lists the programs in the stream and the PID of each program's PMT. The PMT in turn lists the elementary streams.
- Elementary streams — the codec type of each stream and its PID. H.264, HEVC, AAC, AC-3 and SCTE-35 are common answers.
- Packets by PID — the busiest PIDs, which usually means the video first, the audio second, and the tables far behind.
Why inspect a transport stream at all
A .ts file often arrives without documentation: a recording from a set-top box, a capture from a stream, an export from a broadcast tool. Looking at the PIDs tells you quickly whether there is a second audio track, whether the stream is interlaced H.264 or HEVC, whether a subtitle stream exists, and why an editor refuses to open it. A file with no PAT is usually a raw capture that starts mid-stream.
What this analyzer does not do
It does not remux, repair or play the file, and it does not decode the frames. It reports what the headers say. It also reads only a limited prefix of large files — 64 MB — because the table structure repeats and the first stretch is enough to describe the stream. That limit is printed with the result when it applies.
Why run it in a browser
Broadcast captures can be large and are frequently not something you want to hand to a random server. Here the file is read locally by the page, parsed in memory, and nothing is transmitted. Close the tab and nothing is retained.