Read the container, codec, duration, resolution, frame rate and audio track of a video or audio file - locally in your browser. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Every video or audio file carries, alongside the actual picture and sound, a set of technical facts: which container it sits in, which codec encodes it, how long it runs, what resolution and frame rate the picture has, and how many audio channels at what sample rate are present. This tool reads exactly that metadata and shows it clearly - much like the well-known programs MediaInfo or ffprobe, only right in your browser.
To do this, the file is only analyzed (demuxed), never played or re-encoded. The container is read and the tracks are measured - not a single frame is decoded. That is why the tool needs no WebCodecs and runs in every browser, even where re-encoding videos is not possible. You can choose between a readable text report and a structured JSON output; JSON is handy when you want to process the values further or feed them into a script.
As with all tools here, the file stays entirely on your device - it is not uploaded and no foreign library is loaded from a server. That is especially valuable when checking private recordings. Typical questions the report answers: why does this video not play, which codec is inside, how high is the bitrate, is the resolution right for the upload, and is there an audio track at all?
| Input formats | MP4, M4V, WEBM, MOV, MKV, MP3, M4A, AAC, WAV, OGG, OGA, OPUS, FLAC |
|---|---|
| Output format | TXT |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: The tool reads metadata; it does not edit the file and does not play it. Frame rate and bitrate are estimated from an initial portion and marked with a tilde (~) as an approximation. Very exotic or damaged containers may not be readable; the tool then says so honestly instead of inventing wrong values. Very large files (over 2 GB) are rejected.
No. The analysis runs entirely locally in your browser; the file never leaves your device and is not stored.
Common video and audio containers such as MP4, WebM, MOV, MKV as well as MP3, M4A, WAV, OGG and FLAC. It reads container, codec, duration, resolution, frame rate, channels and sample rate.
The text report is meant for reading, the JSON output for further processing in a program or script. Both contain the same values.
No. Only the container is read (demuxed); no frame is decoded and nothing is re-encoded. That is why the tool needs no WebCodecs and is very fast.