This inspector uses the MediaInfo engine in WebAssembly. It does not need to play or transcode the video, and large files are read incrementally instead of copied into browser memory in full. You can search every reported field or export the untouched MediaInfo result as JSON.
Video Metadata Viewer
Runs entirely in your browser - no upload, no sign-up.
Your video is inspected locally with incremental file reads and is never uploaded.
What does a video metadata viewer show?
A video metadata viewer reads the technical information stored in a media file, including its container, codecs, dimensions, duration, reported frame rate and bitrate, audio streams, subtitle streams, and embedded tags. This viewer runs MediaInfo locally and reads only requested file chunks, so the video never leaves your device.
How to use
- 1Choose a video. Drop a local video into the viewer, pick one from your device, or open the small sample report.
- 2Wait for local analysis. The browser loads MediaInfo WebAssembly on demand and supplies the file through incremental slice reads.
- 3Review reported and derived values. Check the container summary and each video, audio, subtitle, or other stream. Estimated values carry a Derived label.
- 4Search or export. Filter the complete field list, copy the JSON report, or download it for troubleshooting and records.
Who it's for
- Editors and producers can confirm a deliverable's container, codec profile, resolution, frame rate, bitrate, color details, and audio layout before import.
- Developers and support teams can inspect codec IDs and stream structure when a file fails to play, upload, or process in another application.
- Archivists can inventory multiple audio languages, subtitle tracks, creation dates, encoding tools, and descriptive tags without changing the source file.
- Privacy-conscious users can see which titles, comments, dates, language labels, or creator details are embedded before sharing a video.
FAQ
Is my video uploaded anywhere?
No. The selected File object is passed to a browser worker, and MediaInfo requests local byte ranges through File.slice(). CanDoYa does not receive the video or its metadata. The only network-loaded item is the site's own WebAssembly asset when the inspector starts.
Is this video metadata viewer free?
Yes. You can inspect videos, search all reported fields, copy JSON, and download the report without an account, subscription, or watermark. Processing stays in your browser, so there is no server upload quota. Available device memory and browser file handling are the practical limits.
Is there a video file size limit?
The viewer does not impose an arbitrary file-size cap. MediaInfo reads requested slices instead of loading or transcoding the whole file. Very large, remote, damaged, or unusually indexed files can still take longer, and your browser or device may impose its own storage and memory limits.
Which video formats and containers are supported?
MediaInfo recognizes many common containers, including MP4 and QuickTime MOV, Matroska MKV, WebM, AVI, MPEG program and transport streams, MXF, WMV, FLV, Ogg, 3GP, and VOB. A damaged, encrypted, proprietary, or very unusual file may return incomplete metadata or an error.
Can it show audio and subtitle streams?
Yes. Each reported audio stream can include its codec, channels, sample rate, bitrate, language, title, and flags. Text or subtitle streams are listed separately with their format, codec ID, language, title, and default or forced status when those fields exist in the container.
Why is frame rate or bitrate missing or different from playback software?
A container may omit a field, report a nominal value, or store variable timing. MediaInfo may expose an average frame rate while another app rounds it or measures decoded frames. The same applies to nominal versus overall bitrate. Missing fields remain blank instead of being guessed silently.
What is the difference between reported metadata and a derived estimate?
Reported metadata is read from the container or stream headers by MediaInfo. A derived estimate is calculated by this page from reported values, such as multiplying duration by frame rate when no frame count exists. Derived cards are marked so you do not mistake an estimate for an embedded field.
Does viewing metadata change or remove anything from the video?
No. The viewer opens the file read-only and never writes back to it. Copying or downloading the JSON creates a separate text report. The original video's streams, metadata, timestamps, and bytes remain unchanged on your device.