MP4 Metadata Viewer
Inspect MP4 atoms for location, timestamps, codec/bitrate, rotation, and track titles without re-encoding.
Drag & drop a file here, or click to select
Max file size: 100 MB
Looking to remove metadata instead? Go to the Metadata Remover.
Why view MP4 metadata?
Checking MP4 metadata helps you protect privacy, verify authenticity, and understand how the file was created.
Trust capture and timing
Check GPS, creation_time, rotation, and timecode in your MP4 files before sharing.
Validate streams
Review codec, bitrate, resolution, FPS, and audio layout so your MP4 meets delivery specs.
See source apps
Surface encoder/muxer tags and chapters to track edits or conversions on your MP4.
Preview the report layout
See how we surface EXIF, PDF, and video metadata before you upload your own file.
Example Metadata Report
After uploading, you'll get a detailed breakdown of your file's hidden data, similar to the example below.
Want to check your own file's metadata? Upload it above - no signup required.
Our secure process
We show you exactly what happens when you upload a file, so you know where your data goes and what stays untouched.
Upload over HTTPS
Pick or drop your MP4. Transfers are secure.
Parse metadata only
We read headers and metadata blocks; the file content is not changed or recompressed.
Highlight key signals
We group timestamps, authorship, location, and technical fields so you can spot what matters quickly.
Display readable results
You see structured metadata grouped by sections for fast review with no downloads required.
Delete temporary copy
The transient server copy is purged right after processing completes.
Want to try it out? Upload your file above, no signup required.
What MP4 metadata can you view?
Here are the fields you can inspect before you share or archive the file. Use them to verify provenance, quality, and privacy.
- creation_time and GPS (when present) plus rotation/orientation
- Video/audio codec, bitrate, resolution, and frame rate per track
- Track titles, languages, and encoder/muxer signatures
What metadata lives inside an MP4
MP4 is structured as a tree of "atoms" (also called boxes), with the moov atom containing everything metadata-related. Inside moov you find mvhd (movie header with creation/modification times in seconds since 1904), udta (user data) with iTunes-style ©xyz GPS tags and ©too encoder strings, and per-track trak atoms each carrying their own tkhd transformation matrix (which encodes rotation), mdia media info, and stsd sample description with the exact codec profile and level.
GPS in MP4 is weird because there is no standard for it. iPhone writes an ISO 6709 string (`+37.7749-122.4194/`) into udta/©xyz. Android writes a similar but often slightly different ISO 6709 to udta/©xyz. GoPro writes GPMF metadata tracks with per-sample GPS. Some drones use a custom udta entry or XMP in the moov. The viewer tries all of these paths and surfaces whatever it finds with the source atom labeled, so you can tell whether coordinates came from the device or were re-injected by an editor.
Beyond location, the per-track stsd atom carries the codec-specific configuration (avcC for H.264, hvcC for H.265, esds for AAC) which encodes profile, level, bit depth, pixel format, and color primaries. For screen recordings and phone captures, the tkhd rotation matrix (0, 90, 180, 270 encoded as a 3×3) is usually more reliable than the video stream orientation — which is why social platforms sometimes rotate your video incorrectly on upload. The viewer shows the matrix value so you can tell what orientation flag travels with the file.
MP4 metadata FAQs
Where does GPS live in an iPhone MP4?
Inside moov/udta/©xyz as an ISO 6709 string like `+37.7749-122.4194/`. The viewer parses this and shows decimal coordinates next to the raw atom value.
Why is my MP4 rotated on upload but plays fine locally?
The rotation is encoded in the tkhd transformation matrix, not the pixel stream. Some upload pipelines ignore the matrix and treat the video as its native orientation. The viewer shows the matrix rotation value so you can confirm.
What is the difference between mvhd creation_time and the per-track tkhd creation_time?
mvhd is the file-level timestamp; tkhd is per-track. They usually match on a fresh capture but diverge after editing — an editor might rewrite the file-level time but leave the track times intact. A mismatch is a clean signal that the file was re-muxed.
Can I tell what app made an MP4?
Often yes. moov/udta/©too, the ftyp major brand (`isom`, `mp42`, `qt `), and the writing application string in meta/ilst leave fingerprints. Camera manufacturers, FFmpeg, and platform encoders all write distinctive values.
Does this viewer read GoPro GPMF telemetry?
It lists the GPMF metadata track when present and shows the first-sample fields. Full per-sample GPS/gyro decoding requires a dedicated telemetry tool, but you will see whether the track is there.