You film something in your living room to sell it, post the clip on a marketplace, and the file carries the coordinates of your front door. Nobody decided to publish an address. It travelled with the video.
Video files store location the same way photos do, and far fewer people know about it. The field is smaller, quieter and just as precise.
Does video have GPS data, and where does it sit?
Yes, when the recording device wrote it. Unlike photos there is no single standard field, so each platform picked its own place.
The value is normally an ISO 6709 string — something like +51.5073-000.1277+014.000/, which is latitude, longitude and altitude run together with their signs. Ugly to read, precise to a few metres.
Our video metadata viewer parses it and shows the coordinates plainly, in your browser, without uploading the clip. If a file carries a location, it appears at the top of the results rather than buried among codec fields.
The iPhone QuickTime location atom, in detail
Apple stores it in a field called com.apple.quicktime.location.ISO6709, inside the user data box of the container.
It is written when the camera has location permission, which is granted per app in Settings under Privacy and Security. Denying the camera leaves maps, weather and everything else untouched — a distinction worth knowing before switching location services off wholesale.
Two things make this field particularly leaky. It survives AirDrop and the Files app intact, because both hand over the original container. And it is not stripped by the export options people assume cover it — the share sheet has a location toggle, and it has to be used deliberately each time.
Android video location tagging, which is less consistent
Android has no single answer, because the camera app varies by manufacturer.
Most write coordinates into an MP4 ©xyz atom in the same ISO 6709 form. Some use their own key names. A few write nothing at all even with permission granted. The setting lives inside the camera app under a name like Save location, Location tags or Store location, and it moves between versions.
The reliable route is the system permission rather than the app setting: Settings, Apps, your camera, Permissions, Location, Don't allow. That survives camera updates that sometimes reset in-app preferences, and it is the same approach we recommend for photographs in stopping your phone geotagging.
Why a video location is a single point rather than a route
This surprises people who expect a five-minute walk to produce a five-minute track.
Consumer phones write one coordinate, usually the fix at the moment recording began, stored once in the container. Walk a mile while filming and the file still claims the starting point. That is a limitation of how the field was designed rather than a privacy feature, and it cuts both ways — the recorded point can be a genuinely misleading answer to where a clip was filmed.
The recording date beside it behaves in much the same way: written once, by the device, with no later correction. That is part of why working out when a video was recorded is less straightforward than the file makes it look.
Action cameras and drones are the real exception and the bigger risk. Many write continuous telemetry: coordinates, altitude and speed sampled throughout. That is a route, a pace and a pattern of movement, which is a different order of disclosure from a single pin. If you share footage from either, treat it with more care than phone video.
Removing location from a clip without wrecking it
Coordinates live in the container rather than the picture, which is the good news. Rewriting the container removes them and leaves every frame untouched.
Our video metadata remover works that way: the compressed streams are copied across bit for bit and only the box around them is rebuilt. It makes no difference whether the file is H.264 or H.265, because the streams are never opened. Nothing is re-encoded, so quality is identical and a large clip finishes in seconds rather than the many minutes a re-encode would take.
Two honest caveats. A small number of containers store location somewhere a straight rebuild does not reach, so we read the finished file back and report what survived rather than announcing success. And removing the field does nothing about what the footage shows — the street sign, the house number, the view from the window.
When it actually matters
Not every clip needs cleaning, and treating it as universal is how the habit collapses.
Clean anything filmed at home going to a marketplace listing, a rental advert, a public forum or a dating profile. Those are direct uploads seen by strangers, and several platforms serve back what you gave them. Email attachments too, since mail clients pass files through byte for byte.
You can usually skip it for the large social platforms, which re-encode and drop the tags as a side effect of processing. That is a side effect rather than a promise, and it happens after they have received the original. The same logic applies to photographs, tested in what social networks strip on upload.
And skip it entirely for footage that may matter later. Insurance claims and incident recordings benefit from an untouched original, a point we go through in whether video metadata can be faked.
The setting that saves you remembering
Cleaning per file works while you remember. Turning camera location off works forever and asks nothing of you again.
It takes two minutes on either platform and it costs you the map view in your gallery for future recordings, which is a real trade rather than a free win. Existing files keep whatever they were given, so the back catalogue still needs handling one clip at a time.
If you want to know what a particular file holds before deciding, drop it into the viewer and look. And while it is open, the technical fields are worth a glance too — our codec and bitrate checker covers what will play where, and what video metadata is explains the rest of the container. For photographs rather than clips, the photo GPS viewer does the equivalent job.