Video Metadata Viewer
Inspect a video's container metadata — codec, resolution, frame rate, duration, bitrate — without uploading it anywhere.
What is Video Metadata?
A media inspector for checking exactly what is inside a video file before publishing, uploading or troubleshooting playback.
How it works
Basic details come instantly from the browser's own demuxer. For a full report, the bundled ffprobe reads every stream — codec names, profiles, pixel formats, frame rates, channel layouts and metadata tags — and the result can be downloaded as JSON.
- Load your file. Drag a file onto the drop zone or pick one from your device. It is read locally by the browser and never uploaded.
- Set the options. Adjust the handles, format, quality or threshold controls — the preview updates as you change them.
- Process and download. Run the tool, then download the result. Compare the reported before/after size for compressors and converters.
Examples
A 42 MB podcast episode → 9 MB MP3
Trim the intro, normalise to −16 LUFS, and export at 96 kbps mono — a typical interview lands around a fifth of the original size.
A phone video with the wrong orientation
Rotate 90° and the width/height swap in the output, so it plays upright in every player instead of relying on metadata flags.
Common mistakes
Expecting instant encoders
Video encoding runs in single-threaded WebAssembly, so a clip takes roughly its own length (or a little longer) to re-encode. Stream-copy operations are near-instant by comparison.
Re-encoding when a copy would do
Trimming, removing audio and joining same-codec clips can copy streams without re-encoding — pick the copy option when it is offered to avoid any quality loss.
Ignoring the first-load download
The media engine is about 31 MB and is fetched on first use, then cached. The first conversion on a connection is slower than every later one.
Frequently asked questions
What can I check here?
Codec and profile (including whether a browser can play it), resolution, frame rate, duration, bitrates, audio channels and sample rate, plus embedded tags such as encoder and creation time.
Why do the browser numbers differ from ffprobe's?
The browser reports what it will actually decode; ffprobe reports what the file contains. A mismatch usually means an unusual profile the browser falls back on.
Is any of this private?
Everything is read locally. Note that metadata itself can be sensitive — camera and encoder tags often include software versions and timestamps.