Video Metadata Viewer

How to use

1. 1Drag a video file onto the drop zone or click to browse. MP4, WebM, MOV, and OGG decode reliably across browsers; AVI, WMV, FLV, and MKV may not be supported natively.
2. 2Read the headline card for resolution, aspect ratio, duration timecode, resolution class, megapixels per frame, and the estimated frame rate at a glance.
3. 3Scroll the file, stream, duration, and frame rate panels for the detailed report. Each row has its own copy button so you can grab a specific value.
4. 4Check the platform fit panel to see whether the video matches YouTube 16:9, TikTok or Reels 9:16, Instagram square 1:1, or Instagram portrait 4:5 without cropping.
5. 5Use Copy full report to grab a plain-text version of everything for a bug report, an upload checklist, or a video brief.

About this tool

Video Metadata Viewer reads any local video file your browser can decode and surfaces its properties without uploading the bytes anywhere. The tool opens the file with the File API, hands it to a hidden HTMLVideoElement, and once loadedmetadata fires it reports videoWidth and videoHeight as the exact pixel resolution, computes the simplified aspect ratio using the greatest common divisor (so 1920 by 1080 becomes 16:9, 3840 by 2160 also becomes 16:9, and 2560 by 1080 becomes 64:27), derives the decimal ratio and a CSS aspect-ratio value you can paste directly into a stylesheet, classifies the resolution against the standard ladder (8K UHD, 4K UHD, 1440p, 1080p, 720p, 480p, 360p, 240p), and labels orientation as landscape, portrait, or square. The duration appears as raw seconds, a precise HH:MM:SS.mmm timecode, a friendly hours-minutes-seconds summary, and as milliseconds for scripting. The file panel reports name, on-disk size in bytes plus a human size, MIME type as the browser sees the container, and the last-modified timestamp from the File handle. Frame rate is estimated using requestVideoFrameCallback on a separate hidden probe: the file plays muted for a short sample window while the API exposes the presentedFrames counter, and the average of the gap becomes the reported fps. Browsers that do not yet ship requestVideoFrameCallback (mainly Firefox at this time) report fps as unavailable and the rest of the report stays valid. Audio presence is checked through the audioTracks list where available, Firefox's mozHasAudio when it is exposed, and Safari's webkitAudioDecodedByteCount as a fallback, with channel count surfaced when the browser provides it. The platform fit panel runs the resolution against the most common social and video targets (YouTube 16:9 at 1080p, TikTok and Reels and Shorts 9:16, Instagram feed 1:1, and Instagram portrait 4:5) so you can tell at a glance whether the file needs cropping or letterboxing before upload. Every result is copyable on its own or as a single plain-text report. Everything runs in your browser; no bytes are uploaded.

Free to use. Works in your browser. No signup, no login.