Geotagged Photos Explained: EXIF, GPS Accuracy, and Why It Can Be Faked
EXIF location data is trivially editable. If your proof of placement depends on it, you don't have proof — you have a suggestion.
Ask most teams how they verify field placements and they'll say "the photos have GPS data in them." That's technically true and practically meaningless. Here's what geotagging actually is, where it breaks, and what verification requires instead.
What EXIF geotagging is
When a phone takes a photo, it can write metadata into the image file: camera model, exposure settings, a timestamp, and — if location access is granted — latitude and longitude. That metadata block is called EXIF.
Three reasons EXIF isn't proof
1. It's editable in seconds
Free tools rewrite EXIF coordinates and timestamps. Nothing in the file resists it, because EXIF was designed for photo organization, not for evidence.
2. It's often stripped
Messaging apps, email clients, and social platforms remove EXIF on upload for privacy reasons. A photo texted to a manager typically arrives with no location at all.
3. The device clock is user-controlled
A timestamp that comes from the phone's own settings can be changed by anyone holding the phone.
Understanding GPS accuracy
Even honest coordinates aren't perfect. Typical smartphone accuracy is 3–10 meters in the open, degrading to 20–50 meters between tall buildings or under heavy canopy. That matters for verification thresholds: requiring a pin within 5 meters of a target address will generate false failures in a downtown core.
- Open suburban street: usually 3–8m.
- Urban canyon: 15–50m with multipath reflection.
- Indoors or in a vehicle: unreliable; wait for a fresh fix.
Good systems record the accuracy radius alongside the coordinates so you can judge each pin fairly.
What tamper-evident proof requires
- In-app capture only. If a camera roll upload is allowed, everything downstream is optional.
- Server-side timestamps. Time recorded when the upload lands, not when the device claims.
- Coordinates read at capture time from the device location API, stored separately from EXIF.
- Authenticated identity bound to the record.
- Immutable storage so the record can't be quietly edited later.
Practical implications for field teams
If your current process is "text me a photo," you're relying on trust plus a metadata field that half your tooling deletes. Moving to in-app capture doesn't add work for agents — it's the same photo, one tap — but it changes the evidentiary value completely.
See what a tamper-evident placement record looks like on your next campaign.