Video Inspector

Open any video file and read its real container structure: every stream, its exact codec and profile, resolution, frame rate, language — plus why it will not play, and what to do about it. Reads MP4, MOV, MKV, WebM, AVI, MPEG-TS, Ogg and FLV. Nothing is uploaded.

Inspector Media & Files Updated Sep 24, 2026
How to Use
  1. Drop a video file in. Nothing is uploaded — the parser reads a few kilobytes of header from your own disk, so a 4 GB file is as quick as a 4 MB one.
  2. Read the verdict first. It answers the only question that matters: is the file broken, or is it your browser?
  3. The stream list shows what is really inside — each track, its exact codec profile, and whether this browser can decode that specific track.
  4. Follow the suggested tool at the bottom if something needs fixing.

Opens the container and reads it, rather than asking the browser what it thinks — which is the whole point, because a <video> element can only describe files it can already play. Every stream, its exact codec profile, and a straight answer to why won’t this play. Nothing is uploaded, and only the header is read.

Video file
🎥
Drop a video
MP4 · MOV · MKV · WebM · AVI · MPEG-TS · Ogg · FLV
Try it with a sample

Drop a file above to read it.

Playback check — the empirical half. What the file says and what the browser actually does are not always the same thing.

How it reads a file

1 · Identify
By content, not by extension
A .mp4 that is really a Matroska file is a common cause of “it won’t play”, so the name is never trusted.
2 · Parse
Atoms, EBML, RIFF chunks
The real container tree, walked in place. Only header bytes are read, never the frames.
3 · Probe
avc1.640028, not “H.264”
The exact profile and level come out of the codec config record, then the browser is asked per stream.
4 · Play
Hand it over and watch
A browser that claims support can still refuse the file, so the claim is tested.
Speed
Independent of file size
Headers are kilobytes. A 4 GB file reads as fast as a 4 MB one.
Privacy
Nothing leaves the tab
No upload, no server round trip, no copy kept.

What it can tell you apart

Unsupported codec
The file is fine
HEVC, AV1 or a surround track your browser has no decoder for. Convert to H.264 and it plays everywhere.
Truncated file
No index found
The download stopped early, or it is one fragment of a larger recording.
Index at the end
Plays, but only after a wait
The moov atom follows the frames, so nothing shows until the whole file arrives.
DRM
Nothing can open it
Encrypted. Only the service that issued the licence keys can decode it.
Video fine, audio not
Per-stream answers
Each track is tested separately, which is why “silent video” gets a specific answer.
Wrong extension
Named by its bytes
The container is whatever the first bytes say it is, whatever the filename claims.

Worked Example

Decoding a codec string. A track reports avc1.640028. After “avc1” (H.264) come three bytes in hex: 64 is the profile, 00 the constraint flags and 28 the level. 0x64 is 100, which is High profile, and 0x28 is 40, which is level 4.0. The tool asks the browser whether it can play exactly that, not just “H.264”.

Checking a bitrate. A 1,500,000,000-byte file that runs 3,600 seconds averages 1,500,000,000 × 8 ÷ 3,600 = 3,333,333 bits per second, about 3.3 Mbit/s for video and audio together. If the filename promised a high-quality 4K rip and the average is that low, it deserves a closer look.

The common mistake: blaming a broken file. A video that will not play in one browser but plays in another is almost always a codec the first browser does not include, such as HEVC, not damage. The verdict separates a missing codec from a truncated file or a missing index, which need different fixes.

Show Work

Codec stringavc1.64 00 28 in hex = profile 0x64, flags 0x00, level 0x28
Profile0x64 in decimal = 100, High
Level0x28 = 40, divided by 10 = level 4.0
Average bitrate1,500,000,000 B × 8 ÷ 3,600 s = 3,333,333 bit/s
Frame rate30,000 ÷ 1,001 = 29.97 frames per second
Header bytes readkilobytes, whatever the file size = a 4 GB file reads as fast as 4 MB

Formulas

Average bitrate
bit/s = file bytes × 8 ÷ seconds
Includes every stream and the container overhead
File size from bitrate
bytes = bit/s × seconds ÷ 8
5 Mbit/s for 60 s is 37,500,000 bytes
Fractional frame rate
fps = time scale ÷ frame duration
30000 ÷ 1001 = 29.97, 24000 ÷ 1001 = 23.976
H.264 codec string
avc1.PPCCLL
PP profile, CC constraint flags, LL level × 10, all in hex

Containers and Codecs

A video file is two things: a container and the streams inside it. The container (MP4 and MOV atoms, Matroska’s EBML elements, AVI chunks) keeps the streams, timing and index together; the codec (H.264, HEVC, AV1 for pictures; AAC, Opus and others for sound) decides how each stream is compressed. A file can have a perfectly good container and still not play because the browser has no decoder for the codec inside it.

MP4 puts its index in a moov atom. If it sits after the frames, a player has to fetch the whole file before starting, which is why a “faststart” re-save moves it to the front. The 1001 in 29.97 fps dates from NTSC colour television, which slowed 30 frames per second by a factor of 1000 ÷ 1001.

About This Tool

Video Inspector opens a video file’s container and lists every stream with its exact codec, profile, resolution, frame rate and language, then tells you in plain words whether the file is damaged, unsupported by your browser, encrypted or just slow to start, and what to do next. It reads MP4, MOV, MKV, WebM, AVI, MPEG-TS, Ogg and FLV.

It reads only the header bytes from your own disk, so nothing is uploaded and large files open quickly. It is for anyone whose video will not play, or who wants to check a download or export before using it.

Related tools: Video Converter, File Inspector, Video to MP3 Converter and Metadata Scrubber.

Frequently Asked Questions

How is this different from Video Info?

Video Info hands the file to a <video> element and repeats what it says, which only works for files that already play. This opens the container itself — the MP4 atom tree, the Matroska EBML tree, the AVI chunk list — so it can describe a file precisely because it will not play.

Why does it say my browser cannot play the video?

Usually HEVC (H.265) or a surround-sound track. Browsers ship decoders for a limited set of codecs, mostly for patent-licensing reasons rather than technical ones, and it differs between browsers and even between operating systems. The file is fine; converting it to H.264 makes it play everywhere. If it says the file is encrypted instead, it carries DRM, and nothing can decode that without the licence keys only the original service holds.

What is a "codec string"?

Browsers do not answer "can you play H.264?" — they answer "can you play avc1.640028?", where those digits are the exact profile and level. This reads them out of the codec configuration record in the file and asks with the real value, so the answer is accurate rather than a guess.

What does "the index sits after the video data" mean?

An MP4 keeps its table of contents in an atom called moov. If it is written after the frames, a player must download the entire file before it can show anything. Re-saving the file moves it to the front — usually called "faststart".

Is my video uploaded anywhere?

No. Everything runs in your browser, and only the header bytes are ever read. Close the tab and nothing remains.

How do I use the Video Inspector?

Just type your numbers. The answer shows up right away — there is no button to press. Change anything and it updates by itself.

Is it free? Does it work without internet?

Yes to both. It is free with no sign-up, and once the page has loaded it keeps working even with no internet.

Where does my data go?

Nowhere — every calculation runs on your own device. Nothing you enter is uploaded, logged, or stored.

Common Use Cases

Find out why it will not play

Separates a damaged file from a codec your browser simply does not ship — two problems with completely different fixes.

Check a download before you keep it

See the real resolution, frame rate and bitrate instead of trusting the filename.

Confirm an export came out right

Verify profile, level, bit depth and audio layout after rendering, before sending it anywhere.

Diagnose a slow-starting video

Catch an MP4 whose index is at the end, which is why it buffers forever before starting.

Last updated: