Free local video utility
Read the records inside any MP4 or MOV file, instantly.
See the container dates, movie duration, file brands and every track header in seconds. This video metadata viewer reads the records on your device and gives you a downloadable report with the original integer values and clear interpretation notes.
Up to 512 MiB. File contents stay in this browser. The viewer reads the container headers without playing or uploading the video.
Load and inspect a 3-second, 320 × 180 synthetic test pattern on your device. No video is uploaded.
Try a controlled example
Download the 3-second test-pattern video. Then choose it above. It is a 320 × 180 synthetic animation, not footage of a person or event. Its creation date was deliberately set to September 27, 2026 UTC.
The expected movie duration is 3 seconds. The video track’s unrotated dimensions are 320 × 180. Compare those observations with the generation record below. Encoding versions change the file bytes.
Generation command, checksum and independent ffprobe report. Example scope and CC0 license.
Start with the original file
- Pick a local MP4 or MOV file you are authorized to inspect. A social-media page URL is a web page, not a video file.
- Compare the movie and media-track dates and durations. Different values describe different parts of a file; on their own they are not signs of manipulation.
- Save the JSON report alongside the original. It includes the file size and header values, leaves out the original filename and carries no cryptographic file identity.
- Open the video frame extractor for a visual reference. An extracted PNG is a fresh derivative without the full video’s records.
Why a date is not proof of when a video was filmed
The stored movie-header creation date is a container record, and software writes, copies and edits it independently of the scene. This viewer interprets nonzero values using the 1904 UTC epoch and preserves the raw seconds in the JSON. A zero value stays unspecified.
A file downloaded today can carry an old header date, and a freshly exported copy of an old recording can carry a new one. Corroborate the event’s date with the original publisher, the production history and other evidence.
Movie duration, track duration and rotated dimensions
The movie and each media track use their own time scales. The report divides every duration by its matching time scale and leaves unspecified durations clearly marked. Audio and video tracks regularly differ in duration.
The width and height shown here are fixed-point values from the track header before its display matrix, so a portrait video can store landscape dimensions while displaying upright. This tool reads headers; it decodes no samples, applies no edits and infers no frame rate.
What this viewer inspects
It reads MP4/QuickTime file-type brands, movie timing headers, track dimensions, media timing headers and handler types. It skips the media payloads and reads up to 2 MiB of headers within a 512 MiB file, covering up to 4,096 boxes and 64 tracks. Malformed headers and unsupported header versions produce an explicit error instead of a guess. It is a header reader, not a full-container conformance check.
Fragmented files can carry zero or incomplete header durations. A fragmentation notice means the viewer encountered a relevant marker; the fragments themselves are outside its scope.
MKV, WebM and AVI containers are outside this viewer’s scope, as are GPS, camera identifiers, custom tags, subtitles, codecs, signatures and private metadata payloads. An empty or missing field means it was not read here; it is neither a privacy clearance nor proof that no metadata exists.
Does video metadata prove AI generation?
No, and we say so plainly. These editable records document a file; they establish neither authorship nor authenticity. The viewer detects no deepfakes, verifies no identities and authenticates no Content Credentials. Combine source checks with file observations and state exactly what each one shows.