How to Extract GPS Coordinates From a Video File

GPS data in a video file is one of those things that is invisible until you know where to look, and then it can be remarkably revealing. When a smartphone records with location services enabled, the device often writes latitude and longitude into the file’s metadata container alongside the recording time, device model, orientation, and sometimes even altitude and speed. That information does not appear in the pixels you watch, it lives in the structural metadata that wraps the video stream. For journalists verifying where a clip was shot, for investigators building a timeline, for archivists documenting provenance, or for anyone simply curious about a personal video, extracting that location data can be the difference between an anonymous file and a verifiable piece of evidence. The challenge is that video formats store metadata in different ways. An MP4 or MOV file, which is built on the ISO Base Media File Format, keeps metadata in atoms or boxes such as moov and udta, often using QuickTime style keys like com.apple.quicktime.location.ISO6709. MKV and WebM files use Matroska tags. Some cameras write GPS as standard EXIF data in a still image extract, while others duplicate it into XMP. Because of this fragmentation, a generic viewer will not show you GPS coordinates, and simply renaming a file will not remove them. Understanding the format and having a reliable way to read the technical metadata without altering the original file is the first step toward a responsible extraction workflow.

Most people assume GPS is either in EXIF or it isn’t. That is partly true for photos, but video is messier.

Phones are the most common source of GPS-tagged video today. iPhones write location into the MOV container using the QuickTime location atom, and Android devices typically write GPS latitude, longitude, and timestamp into the MP4 moov/udta metadata, sometimes also into XMP. The data is written at the time of recording, so the timestamp embedded in the metadata should align with the recording time, although clock drift can occur. Professional cameras, drones, and action cameras vary widely. Some embed precise GPS tracks per frame, others only store a single location for the entire clip, and many consumer models offer a simple on/off toggle for location tagging. Editing software adds another layer of complexity. Re-encoding, exporting, or passing a file through a messaging app can strip location metadata entirely, while some editors preserve it and others rewrite it. That means the presence or absence of GPS is itself a clue about the file’s history.

If you want to check manually, the traditional tools are ffmpeg and exiftool. Running ffmpeg -i input.mp4 will print stream information and sometimes show location tags in the metadata dump, though the output can be noisy and format dependent. exiftool -gps:all -a -u input.mp4 is more direct and will list GPSLatitude, GPSLongitude, GPSAltitude, and related tags if they exist. Those tools are powerful for technical users, but they require a command line, careful handling to avoid overwriting the file, and interpretation of the output. For a non-technical workflow, or when you need a documented, tamper-evident record, a web-based forensic metadata extractor is often more practical. That is where a service like FilesAudit becomes useful for documentation purposes. You can upload a file to extract its metadata, hashes, and AI-provenance evidence, and receive a professional PDF report that records what was found at a specific time without modifying the original. The report includes SHA-256 and MD5 fingerprints, file size, format identification, and a structured listing of extracted metadata fields, including any GPS coordinates present.

Privacy is the other side of this capability. GPS coordinates in a video can pinpoint a home, a protest site, a medical clinic, or a private event with high precision. Sharing a video without stripping location data can unintentionally disclose where you were. Many social platforms strip GPS automatically on upload, but not all do, and the original file you keep on your device usually retains the data. Before distributing footage, especially in sensitive contexts, it is prudent to check what metadata is embedded and decide whether to remove it. Tools that extract metadata for auditing purposes do not change the file unless you explicitly request redaction, which is why a read-only extraction and reporting step is important for transparency.

A practical example helps illustrate the workflow. Imagine a journalist receives an MP4 clip from a source claiming it shows flooding in a specific neighborhood. The first step is to preserve the original file unchanged and generate a cryptographic fingerprint. Next, extract the technical metadata to see if GPS is present. With FilesAudit, you upload the video and the platform parses the container, lists the moov atoms, and displays any QuickTime location tags, XMP blocks, and EXIF data that survived encoding. If GPSLatitudeRef, GPSLatitude, GPSLongitudeRef, and GPSLongitude are present, you can read the coordinates in decimal degrees and cross-reference them with a map. The report also shows creation time, device make and model if embedded, and software used for encoding. If the coordinates match the claimed neighborhood and the timestamp aligns with weather records, that strengthens the technical consistency of the file. If no GPS is found, that does not prove the claim is false, it only means location was not embedded or was stripped. The full list of supported formats covers most common video types, from MP4 and MOV to MKV, AVI, and HEIC video, so you do not need to convert files before inspection. For a deeper dive on how MP4 stores this information, the MP4 metadata guide explains the common atoms and tags you are likely to encounter.

Limitations matter. Extracting GPS location from a video file is a technical metadata analysis, not a legal determination of where the recording actually took place. Metadata can be forged, copied from another file, or injected by editing software. A GPS tag can be present but inaccurate due to poor satellite reception, or it can be deliberately altered. FilesAudit documents what is technically present in the file at the time of analysis, computes hashes for integrity verification, and provides timestamped reporting to support auditing and compliance workflows. It does not establish legal ownership, authenticity, or intent. For bulk or sensitive investigations, the FilesAudit Desktop App for unlimited local/bulk metadata analysis, with pricing offers offline processing so files never leave your environment. When you need to compare two versions of a video, comparing SHA-256 hashes is a fast way to confirm whether they are bit-for-bit identical. If you are building a chain of custody, keep the original file, keep the PDF report, and note the extraction date and tool version. That combination of technical evidence, cryptographic fingerprints, and clear documentation is what makes GPS extraction useful in journalism, digital investigations, software verification, and compliance, without overstating what metadata alone can prove.