Do Videos Have EXIF? — What's Actually Buried Inside MP4 and MOV Files

Open a JPEG and you'll see capture date, camera body, lens, aperture, ISO — EXIF lays it all out. Right-click a video file and the system properties give you size, length, maybe a codec name. That's it.

The information is actually in there. It's just stored under different names, in different places, using different conventions. This post walks through what's really inside a video file's metadata: where it lives, what you can read out, and why so much of it goes missing by the time the file lands in your edit.

The Short Answer — No EXIF, But Equivalents Exist

First, the vocabulary. EXIF (Exchangeable Image File Format) is a still-image specification. It's not embedded as-is inside an MP4 or MOV. Video uses different mechanisms to carry equivalent information.

If by "EXIF" you mean "the camera and capture info from when this was shot," the answer is yes, it's in there — just not under that name. On pro gear, the metadata can be richer than what stills typically carry.

What's Actually Stored

Common items you can extract from a video file:

• Capture date and time — almost always present (time zone handling varies by camera)
• Camera make, model, firmware/software version
• GPS coordinates — common on phones, action cams, and recent mirrorless bodies
• Resolution, frame rate, codec, bitrate — strictly container-level rather than "metadata," but readable the same way
• Color space, color matrix, transfer characteristics (Rec.709, Rec.2020, HLG, PQ)
• SMPTE timecode — effectively mandatory on broadcast gear
• Lens info, aperture, shutter speed, ISO — usually in vendor-specific regions
• White balance, picture profile — same caveat as above

That last category is where the inconsistency lives. Pro Sony XML output is astonishingly detailed; a consumer Canon MP4 might omit the same fields entirely. Whether a field exists depends heavily on the camera, the recording format, and the firmware version.

How to Look Inside

A few tools handle this well:

• ffprobe (ships with FFmpeg) — perfect for container-level info: resolution, frame rate, codec, bitrate, color space
• ExifTool — yes, the name is misleading. It reads video metadata too, including most vendor-specific extensions. The de facto standard
• macOS "Get Info" — shows a sliver of QuickTime metadata. Fine for a glance, not enough for real work
• NLE clip properties (Premiere Pro, DaVinci Resolve, FCP) — surfaces what matters during the edit: timecode, color tags, frame rate

Try running exiftool on one of your own clips. Most people are surprised how much of the shoot is still embedded.

Metadata That Disappears During Editing

This is where it gets practical. No matter how much your camera embedded at capture, most of it doesn't survive the round trip through an NLE.

• Vendor-specific metadata is mostly stripped the moment a clip enters a project
• What makes it to export depends on the container (MP4 / MOV / MKV) and the encoder
• Some editors don't preserve even GPS or capture date

The result: a camera original and an exported delivery file carry vastly different amounts of metadata. This is one more reason not to throw away your camera originals (see the archive section in the codec article).

Sidecars — the .XML / .ALE / .CSV World

In broadcast and cinema workflows, it's normal to put significant metadata in separate files alongside the video.

• Sony — .XML sidecars with capture info, timecode, picture profile
• ARRI — .ARI / .ALE, the latter bridges to Avid-centric edits
• Canon — .CPF / .XML
• Script supervisors on set — .CSV and .EDL files with shot notes

Sidecars are easy to lose. Copying a single .MP4 out of a card structure and leaving the .XML behind is a classic accident. Always copy by folder, preserving the original card layout, until you're sure you've harvested everything the camera wrote.

Phone Footage Is Surprisingly Rich

.MOV and .MP4 files from a recent iPhone or Android pack more metadata than you'd expect.

• Capture date, GPS, device model
• Orientation flag (this is how players auto-rotate vertical footage)
• Apple HEVC / HEIF gyro and motion data (raw signal behind on-device stabilization)
• HDR flags (Dolby Vision adds its own metadata track)

If a library mixes phone footage with pro camera footage, knowing what each side exposes makes a huge difference in how well you can search the result later.

VideoTagger Reads This "Video EXIF" Automatically

VideoTagger pulls metadata out of every clip it imports. Beyond container basics (codec, resolution, frame rate, bitrate, color space), it extracts capture date, camera make and model, GPS, timecode and similar fields whenever the file carries them — and makes all of it searchable and filterable.

• "Show me only clips shot on a Sony α7S III in 2024"
• "Pull every clip with GPS data and group them by location"
• "Find every 4K ProRes master tagged Rec.2020"

These queries run against extracted metadata, not against filenames or folder structure. Teams that didn't realize how much info their footage already carried tend to feel the biggest jump when they switch.

Summary

• There's no literal EXIF inside a video file. But MP4 udta / meta, QuickTime atoms, XMP, and vendor schemas carry equivalent or richer information
• Capture date, GPS, camera model, timecode, color space — all of it can be there, depending on the camera
• Most of it gets stripped during editing and export. Keep your camera originals.
• Pro cameras add sidecar files (.XML, .ALE). Copy by folder, never by single file
• ExifTool and ffprobe will show you what's actually inside

The metadata is there. Once you start treating it as a first-class asset — not just a curiosity — the library you've been building suddenly becomes a lot more valuable.