Video Metadata Viewer
Inspect any video to see its codec, resolution, frame rate, bitrate, audio sample rate, channels, pixel format, and full FFmpeg probe output. Files are analyzed entirely in your browser with FFmpeg WebAssembly.
About Video Metadata Viewer
Video Metadata Viewer is a self-contained video editing and conversion workspace. Inspect any video to see its codec, resolution, frame rate, bitrate, audio sample rate, channels, pixel format, and full FFmpeg probe output. Files are analyzed entirely in your browser with FFmpeg WebAssembly. Open the page, get the result, close the tab — that is the entire workflow.
Video Metadata Viewer runs on FFmpeg compiled to WebAssembly — an open-source, well-audited engine that performs the video editing and conversion natively in the browser. It accepts MP4, WebM, MOV, MKV, AVI, FLV, and OGV and produces output that opens in any standard video viewer. Per-run input is capped at 500 MB.
Video Metadata Viewer sees the most use from educators editing lecture clips and support agents preparing screen recordings, but the design is intentionally generic enough that you do not need a specialist background to get a good result. The defaults aim at the most common case so a first-time user can get the right output without changing any settings.
The architecture is local-first by design. Once the page is loaded, you can disconnect from the network and the tool still completes the job. The processing stack — FFmpeg compiled to WebAssembly and the small UI shell wrapping it — ships with the page itself, so the tool keeps working in offline conditions, on a captive-portal Wi-Fi, or behind a corporate proxy that limits what the tab can reach.
Reach for Video Metadata Viewer when you need a predictable result on a single file. The page works on the first visit, the controls are visible without a menu, and the output is delivered the moment the engine finishes.
Once the engine finishes, `{name}-edited.{ext}` is offered as an immediate download. There is no preview gate, no email-wall, and no "register to download" intermediary — the file is yours the moment it is ready.
The only practical limit is the 500 MB per-file ceiling, which keeps the tool responsive across a wide range of devices. Run the tool ten times in a row, run it ten thousand times — it behaves the same way and produces the same quality of result.
For multi-step jobs, Video Metadata Viewer sits next to Video Metadata Remover, Video Resolution Checker, and Video Frame Counter. None of them depend on each other — you can use Video Metadata Viewer on its own — but together they cover the common variations of the task this page exists to handle.
Some notes on the design of Video Metadata Viewer. The page is intentionally narrow: one input, the controls relevant to the task, and one output. Adding unrelated features would make the common case slower for the majority of users, so the surface is held to what people actually use.
Video Metadata Viewer is structured around the idea that a useful tool should be its own page. Open the page, do the work, close the tab — the page is the entire product. There is no onboarding flow because there is nothing to onboard into.
Video Metadata Viewer fits the gap where opening a desktop app feels heavy and writing a script feels overkill. The page handles the common video editing and conversion task with sensible defaults so a single visit usually completes the job; for highly specialised work, a dedicated desktop application can offer more knobs to turn.
A few practical tips that experienced users of Video Metadata Viewer pick up over time. First, keep your default browser updated — the engine relies on standard web APIs and newer browser versions are noticeably faster than ones from a few years ago. Second, close other heavy tabs before processing a large input; the engine shares CPU and memory with whatever else is open. Third, if you re-run the same kind of job often, your last-used settings are remembered for the rest of the tab session, so subsequent runs are essentially one click.
When something goes wrong, the cause is usually one of three things: a malformed input, a browser that is out of memory, or a corporate proxy that is interfering with the page's static assets. The first two are easy to diagnose; the third typically requires asking your IT team to allow FFmpeg compiled to WebAssembly to load.
That is essentially everything Video Metadata Viewer does and how it does it. Open the tool above, drop in your input, and the work happens in the page. If you find yourself reaching for it often, bookmark the page — it loads quickly on subsequent visits, and your most-recent settings are remembered for the rest of the session.
How it works
- 1Open Video Metadata Viewer in your browser. The page loads quickly and the tool is ready to use the moment it becomes interactive.
- 2Add your MP4, WebM, MOV, MKV, AVI, FLV, and OGV input by dropping it onto the page or browsing for it.
- 3Tweak the controls if the defaults are not quite right for your input. The options are kept short and labelled in plain language.
- 4Trigger processing. FFmpeg compiled to WebAssembly reads your input, applies the transformation, and writes the result back into the page.
- 5Download the result as `{name}-edited.{ext}`. The file is generated in your browser and saved through your normal download flow.
- 6Run additional jobs as needed. The same controls and defaults apply on every run.
Common use cases
- Convert a desktop recording into a GIF for documentation using Video Metadata Viewer.
- Re-encode a clip so it plays on an older device without stuttering.
- Stitch several short clips into a single uploadable video.
- Strip the audio track from a screencast for a silent loop.
- Convert a phone-recorded clip into a web-friendly MP4.
- Add a quick caption overlay before posting to social.
- Trim the silent intro from a screen recording before sharing it.
- Rotate a portrait phone clip into landscape for embedding on a site.
- Compress a demo video small enough to attach to an email.
Frequently asked questions
How does the viewer work without uploading?
A WebAssembly build of FFmpeg loads in this page and runs an `-i` probe against your file. The probe output is parsed into the structured panels you see — entirely on your device.
Why is in-browser metadata reading slower than online tools?
Server tools have native ffprobe and parallel I/O. WebAssembly is single-threaded and reads the file through JavaScript, typically 2–5× slower for large files. The trade-off is total privacy: your video never leaves your device.
What information do I see?
Container info (file name, size, duration, overall bitrate), the video stream (codec, resolution, aspect ratio, frame rate, pixel format), and the audio stream (codec, sample rate, channels). You can also download a plaintext metadata report.
Can I download the report?
Yes — there is a "Download metadata.txt" button. The report includes the structured fields plus the full FFmpeg probe output, useful for bug reports or technical documentation.
Why are some fields shown as Unknown?
Some containers (especially exotic ones) do not expose every field, or FFmpeg cannot parse them in single-threaded WASM mode. The structured panels show what we can extract reliably; the full log in the report contains everything FFmpeg saw.
Will it work for DRM-protected files?
No. Encrypted commercial streams cannot be probed. Use only files you own or have the rights to analyze.
How big a file can I inspect?
Up to 500MB. The probe itself is fast — most of the time is the initial file read.
Is my video uploaded?
No. The probe runs entirely in your browser tab. Nothing is transmitted, stored, or logged. Closing the tab erases the file from memory immediately.
Is the source for Video Metadata Viewer available?
Video Metadata Viewer is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript and WebAssembly to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (FFmpeg compiled to WebAssembly) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.
Which file formats does Video Metadata Viewer accept?
Video Metadata Viewer accepts MP4, WebM, MOV, MKV, AVI, FLV, and OGV. If your input is in a format that is not directly supported, convert it first using one of Favtoo's converter tools — every Favtoo converter outputs a file that is a clean input to the next tool in the chain.
Can I process multiple files at once with Video Metadata Viewer?
Video Metadata Viewer processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
Will Video Metadata Viewer keep working if my Wi-Fi drops mid-task?
Once the page is loaded, Video Metadata Viewer can complete jobs without an active internet connection — the engine is bundled with the page, so there is no per-job network call. The initial page load does require a connection (to fetch the static assets), but after that you can disconnect entirely and the tool will still work. This is a side-effect of the local-first architecture, not a deliberate "offline mode" feature.
Do I need to install anything to use Video Metadata Viewer?
No installation is needed. Video Metadata Viewer runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use Video Metadata Viewer on any computer you have temporary access to without leaving anything installed on it.
Is it safe to use Video Metadata Viewer on confidential files?
Your file is processed inside your browser by FFmpeg compiled to WebAssembly. The engine reads the file's bytes from your tab's memory, computes the result, and writes the result back into the tab. You can confirm what the page does by opening developer tools and watching the Network tab during a run — the requests you see are for the tool's static assets only.
How many times per day can I use Video Metadata Viewer?
Inputs are capped at 500 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run Video Metadata Viewer as often as you need; every run produces a full-quality result.