b2KIT

Video Metadata Viewer

View video file metadata including codec, resolution, bitrate, and duration.

Tested tool guide Tested browser tools Checked August 16, 2026

What Video Metadata Viewer does and how it behaves

Video files wrap their picture and sound in a container that carries metadata describing what is inside: the codecs used, the resolution and frame rate, the duration, and the bitrate. This tool extracts those fields. You select a file or drag one onto the page, and it reports the container format, video and audio codec identifiers, dimensions, duration, frame rate, and an average bitrate, all parsed locally in your browser, so nothing is uploaded and the file never leaves your device. The common surprise: the tool reads what the file declares about itself, not what its frames actually contain. Headers can be stale, edited, or corrupted, and the reported values can disagree with how the video really plays.

How the result is produced

1

File reading

You pick a file or drop it onto the page, and the tool parses the container structure in the browser. It works from the header data that describes each stream rather than from the encoded frames, so the process is local: nothing is uploaded, no transcoding happens, and the original file is left untouched.

2

Where the numbers come from

Duration, dimensions, frame rate, and codec identifiers are stored in the container and stream headers, and the tool reports them as declared. Bitrate is different: most containers do not store a single bitrate value, so the figure shown is an average computed from the file size and the declared duration. It is an average over the whole file, not the rate any single moment plays at.

Good uses

  • Checking web compatibility before publishing: confirm the file uses a browser-safe combination such as H.264 video with AAC audio in an MP4 container, or VP9 or AV1 in WebM, by reading the exact codec identifiers the tool reports.
  • Verifying a file you received: check that resolution, duration, and bitrate match what was advertised, for example spotting a 1080p download that turns out to be 720p upscaled, or a screen recording whose average bitrate is too low for the detail you need.
  • Estimating re-encode size before compressing: with duration and average bitrate in hand, size in bytes is roughly bitrate in bits per second times duration in seconds divided by 8, which lets you predict whether a recording will fit a size limit before running the encoder.

Limits and checks

  • Declared, not verified. All values come from container headers. A truncated, repaired, or hand-edited file can declare a duration or bitrate that its frames do not match, and the tool has no way to know. Cross-check the reported duration against actual playback when the file history is uncertain.
  • An average hides spikes. Variable-bitrate video has no single bitrate. The average the tool shows understates the peak rate, which is the number that matters for streaming, buffer sizing, and hardware decoders that cannot absorb fast bursts.
  • Coverage is limited to known containers. The parser understands common formats and rejects or only partially reads others. A file the tool cannot open may still play fine in a desktop player, so a failed read is a parser limitation, not proof the file is broken.

Common questions

Is my video uploaded somewhere while I check it?

No. The file is parsed entirely in your browser and its bytes never leave your device. The check itself makes no network request, so there is no upload step and no upload size limit to worry about. This also means the tool is safe to use on recordings you would not want copied to a server.

What does a codec string like avc1.64001F mean?

It is an RFC 6381 codec identifier. The prefix names the codec: avc1 is H.264 carried in an MP4-style container. The six trailing hex digits encode profile, constraint flags, and level: 0x64 is High profile and 0x1F is level 3.1 (the level_idc for level 3.1 is the decimal value 31, which is 0x1F in hex), which the H.264 specification classes for typical use up to 720p at 30 frames per second.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools