Video Metadata: The GPS and Device Data Hiding Inside Your MP4 and MOV Files

People strip EXIF from photos and then send raw video without a second thought. That order of operations makes no sense, because a video file often carries more identifying material than the photos taken next to it. An MP4 from an iPhone stores the GPS coordinates of where recording started, the exact device model, the lens, the recording date and time with timezone, and sometimes the direction the camera was facing. A MOV from the same phone keeps the same fields, because MOV is the container Apple writes before conversion.

Where the data lives

Photos keep their metadata in EXIF and XMP blocks. Videos use different containers. MP4 files store metadata in atoms, small labelled chunks inside the file. The one labelled udta holds user data, and inside it a newer Apple tag called mdcd or the older @MSG stores GPS. there's also the mvhd atom with creation and modification timestamps, and tags written by the recording app: make, model, software version. Android phones vary more. Some write location only if the camera app had location permission on, some embed a URL to a live wallpaper service or the vendor's own tagging scheme. Screen recordings often keep the device name of the phone that made them. Third-party cameras add their own quirks: dashcams write GPS tracks as a separate stream you can replay as a route, doorbell and IP cameras stamp the unit's serial and the account name it belongs to into every clip they export, and drone footage carries a full telemetry block from takeoff to landing. A shared doorbell clip can so reveal a home address without a single frame showing the house number.

What a plain file listing won't show you, but a metadata reader will:

GPS coordinates accurate to a few metres, recorded at the moment recording started Device model and iOS or Android version at time of recording Lens and camera module, which narrows the phone model further Creation timestamp with timezone, which combined with the video content tells a viewer your daily routine Sometimes altitude, speed and heading on newer iPhones

Telegram is the exception worth knowing about. A video sent the normal way gets re-encoded. A video sent as a file, which is what people choose to preserve picture quality, travels byte for byte, GPS included. Signal strips what it processes, but its unencrypted-attachment flow still hands the platform the original file briefly. X strips location from uploaded video. TikTok, YouTube and Facebook all re-encode, and their encoder settings are well documented in the forensics literature, which is why re-encoded clips from those platforms are identifiable by the toolmarks of the pipeline that touched them.

What platforms strip, and what they keep

Instagram, WhatsApp and Telegram re-encode every video you send, and re-encoding drops most location atoms. that's the good news. The bad news is what survives the re-encode. Timestamps in the mvhd atom usually survive. Rotation metadata survives. And the re-encode itself is a fingerprint: the encoder settings identify which platform processed the file, which matters when a clip's provenance is in question, as it increasingly is for footage used as evidence.

Sharing via cloud links is worse. Send someone a file through Google Drive, Dropbox or iCloud and the original bytes go up untouched, GPS included. Downloading a shared file and running a metadata check on it's how people routinely discover where a clip was filmed before they even watch it. The same applies to video files attached to email. Email servers don't transcode attachments.

The check takes one command

ExifTool reads video metadata the same way it reads photos:

Exiftool -a -G1 -s video.mp4

The -a flag shows duplicate tags, -G1 groups them by their container location, and -s prints them in a compact list. Look for GPSLatitude, GPSLongitude, CreationDate, and Make or Model. If the output shows coordinates, the file will tell anyone who runs the command where the recording started, to within about 10 metres on a good fix.

How to remove it before sharing

Re-encoding through an editor removes most tags, but it's slow and loses quality. The faster route is to strip in place:

Exiftool -overwrite_original -gps:all= -mdcd= -@MSG= video.mp4

For a batch of files, point ExifTool at a folder and add -ext mp4 -ext mov -r. Afterwards, re-run the read command and confirm the fields are gone. Some phones also write a companion sidecar file with location data, particularly some Samsung models, so check the folder for small.xml or.xmp files sitting next to the clips.

If you'd rather not install anything, our tool handles MP4 and MOV directly in the browser: drop the clip in, the metadata is removed on your device, and nothing is uploaded. The 5 minute auto-delete means the file doesn't sit on a server afterwards, because there's no server in the path at all.

Two traps worth knowing

First, a video that has already been shared and re-encoded once may look clean, but the original still exists on your phone with full GPS. Check the source file, not a copy someone sent back to you. Second, frames inside the video can show more than the metadata does. A street sign, a house number, a delivery van with a name on it, the view from your window. Metadata removal makes the file anonymous, it doesn't make the footage anonymous. Think about both before you post a clip publicly, the same way you'd think about photos you take at home.

The habit that fixes this permanently: treat every video like a photo. Strip before it leaves the device, and check with a metadata reader whenever a clip's origin matters to you.

Published 16 October 2026