photometadata.netEXIF · GPS · METADATA

Fake GPS EXIF Data: How to Spot a Spoofed Photo Location

The GPS coordinates inside a photo are ordinary bytes in the file's EXIF header. Nothing signs them, nothing checks them, and any metadata editor can overwrite them in a second. So the question is never "can this be faked" — it can. The question is whether a particular file shows the seams.

Six signs a photo's GPS was faked

  1. The GPS clock disagrees with the camera clock. GPSTimeStamp comes from the satellites; a coordinate pasted in later does not update it.
  2. Latitude and longitude arrive alone. A real fix drags altitude, a GPS date, and often speed and heading along with it.
  3. The coordinates are too round. Satellites do not produce numbers a human would type.
  4. Several photos share byte-identical coordinates. A handheld fix jitters between shots. A pasted one does not.
  5. An editor left fingerprints. A Software tag, a ModifyDate after the capture date, or a mangled maker note.
  6. The picture contradicts the pin. Shadows, signage, architecture, and weather are far harder to forge than a number.

None of these is proof, and one spoofing method defeats all six. Jump to the checks, legitimate vs. malicious use, or stripping your own GPS.

What "Fake GPS EXIF Data" Actually Means

A geotagged photo stores its location in a small block of EXIF tags: GPSLatitude, GPSLongitude, the N/S and E/W reference tags, and usually altitude and a UTC timestamp. Fake GPS EXIF data means those tags say one place while the shutter fired in another. There are two routes to it, and they leave very different traces.

Route one: rewrite the tags after the fact.

Open the file in a metadata editor and set the coordinates to whatever you like. This is how the ordinary, legitimate cases work too — geotagging a DSLR photo from a GPS logger track, or fixing a bad fix. The write itself is one command:

exiftool -GPSLatitude=48.8584 -GPSLatitudeRef=N \
         -GPSLongitude=2.2945 -GPSLongitudeRef=E photo.jpg

The image data is untouched. Nothing in the JPEG records that the coordinates changed, because EXIF has no revision history and no signature — a point worth sitting with if you have ever treated a photo's location as evidence of anything.

Route two: lie to the camera.

Android's developer options include a mock location provider, and iOS location can be simulated from a connected Mac. The camera app receives the false position from the operating system and writes it into EXIF itself, through its normal code path. The file that comes out is not an edited file. It is an original photo that happens to contain a coordinate the phone was told to believe.

Every detection technique below targets route one. Route one is also the overwhelming majority of what you will encounter, because it takes ten seconds and no preparation. But keep the distinction in mind before you tell someone a photo is authentic.

How to Tell if a Photo's GPS Is Fake

You cannot verify a coordinate from the coordinate. What you can do is look for the things a genuine satellite fix drags along with it, and ask whether they agree with each other. Start by dumping every GPS tag in the file rather than reading the pretty map pin:

# Every GPS-group tag, with group prefixes and short names
exiftool -a -G1 -s -GPS:all photo.jpg

# Raw numbers instead of pretty-printed degrees
exiftool -n -GPSLatitude -GPSLongitude -GPSAltitude photo.jpg

# The timestamp cross-check, all four fields at once
exiftool -GPSDateStamp -GPSTimeStamp -DateTimeOriginal -OffsetTimeOriginal photo.jpg

1. The two clocks

This is the strongest single check. GPSTimeStamp and GPSDateStamphold the UTC time delivered by the satellite signal — they come from the fix, not from the phone's clock. DateTimeOriginalis the camera's local wall-clock time, and since EXIF 2.31 a well-behaved phone also writes OffsetTimeOriginal holding its UTC offset.

Convert the capture time to UTC using that offset and compare. On a real photo the two land within seconds of each other. A coordinate pasted in afterwards leaves the old GPS timestamp untouched, or has no GPS timestamp at all — and someone forging one rarely thinks to recompute it for the location they invented. A photo whose camera clock says 14:30 in Paris while the satellites say 19:12 UTC is telling you something.

2. The missing entourage

A phone that has a real fix knows more than two numbers. iPhones routinely write GPSAltitude, GPSHPositioningError (the accuracy radius, in metres), GPSSpeed, GPSImgDirection, and GPSDestBearing. Many Android camera apps write GPSProcessingMethod, recording whether the position came from satellites, the network, or a fused estimate.

A file with nothing but latitude, longitude, and their two reference tags — from a device you would expect to write the rest — was probably geotagged by a tool rather than a satellite. The inverse is also worth noticing: a DSLR with no GPS chip has no business carrying coordinates at all unless someone added them.

3. Precision, and the shape of the number

EXIF stores each coordinate as three rational numbers — degrees, minutes, seconds. A genuine fix fills the seconds field with unlovely precision, because it is the output of a trilateration and not a decision. Coordinates that round off cleanly, or that land exactly on the centroid of a place a mapping service would return for a search, suggest someone picked a pin rather than stood somewhere.

Read this as a hint, never a conclusion. A spoofer who copies real coordinates from a real photo inherits real precision.

4. Identical coordinates across a set

When you have several photos that claim the same outing, compare their coordinates side by side:

exiftool -T -filename -GPSLatitude -GPSLongitude -n *.jpg

Held in a human hand, a receiver drifts. Two photos taken minutes apart from the same spot almost always differ somewhere in the last decimal places, because the fix is re-acquired and the person moved. Byte-identical coordinates across a batch mean one value was written to all of them.

5. Traces the editor left

Some editors sign their work without meaning to. A Software tag naming an image editor on a photo presented as straight-from-camera, or a ModifyDate hours after DateTimeOriginal, says the file was rewritten — though it does not say which tag changed.

Deeper down, rewriting EXIF re-serialises the whole directory. Maker notes are the fragile part: they are full of internal byte offsets, and tools that move them without fixing those offsets leave a maker note that no longer parses. A photo that claims to come from a Canon body but has a corrupt or absent maker note has been through something.

Now the uncomfortable half. ExifTool, by default, adds no Software tag, does not touch ModifyDate, and goes to considerable trouble to fix maker-note offsets correctly. A careful edit leaves none of these traces. Their absence is not evidence of authenticity — it is evidence of nothing at all.

6. The photograph itself

Metadata is the easiest thing in the file to forge and the pixels are the hardest. Does the sun fall where it should for that latitude, that date, and that hour? Do the vegetation, road markings, licence plates, plug sockets, and script on the signs belong to the country in the pin? Does the weather match what the record says it was doing there? Open-source investigators put the coordinate last for a reason: they geolocate the image, then see whether the EXIF agrees. That order is much harder to fool.

Where the Checks Run Out

Every signal above describes a file that was edited after capture. None of them fires on a photo taken with a mock location provider feeding the camera app. In that case the app computed the whole GPS block itself, in the same code path it always uses: the timestamps agree, the entourage tags are present, the precision looks native, the maker note is pristine. The metadata is internally consistent because it was never inconsistent — it was simply built on a false premise.

So the honest statement of the limit is this. EXIF can raise your suspicion, and it can sometimes confirm a lie. It cannot certify the truth. A photo whose metadata survives every check is a photo you have failed to disprove, which is a much weaker claim than a photo you have verified. In any setting where the answer carries real consequences — a claim, a case, a story going to print — the coordinate is a lead to corroborate, not a fact to rely on.

The industry's answer to this is provenance signed at the moment of capture rather than inferred afterwards. C2PA Content Credentials attach a cryptographic signature to a photo's origin claims, and a small number of camera bodies now support it in firmware. Where those credentials exist you can verify a location claim rather than argue about it. Where they do not — and that is nearly everywhere, today — you are reading tea leaves, carefully.

Legitimate and Malicious Uses

Writing a coordinate into a photo is not inherently deceptive. Photo managers, GPS loggers, and every "set location" button in every gallery app do it. What separates the two columns below is whether the coordinate is being presented to someone as a factual claim they will act on.

Ordinary and legitimate

  • Geotagging a camera without a GPS chip. Matching timestamps against a GPS logger track and writing the result. The coordinates are real; only the path into the file is unusual.
  • Correcting a bad fix. Phones cache stale positions and hand them to the camera — the reason iPhone photos sometimes show the wrong location. Replacing a wrong number with the right one is a repair, not a forgery.
  • Coarsening a sensitive location. Photographers publishing images of nests, dens, or rare plants routinely blur the coordinate to a wide area so the animal is not found. The same logic protects archaeological sites and a source's neighbourhood.
  • Test data and research.Software that reads location needs fixtures "taken" in many places, and teaching people to detect spoofing requires spoofed samples to practise on.

Deceptive, and often criminal

  • Insurance and warranty claims. Photographs offered as proof that damage occurred at the insured address, or on the covered date.
  • Proof-of-presence fraud. Delivery confirmations, field-service inspections, and site verifications where a photo stands in for having been there.
  • Fabricated evidence and alibis. Photos submitted in a legal dispute to place someone somewhere they were not.
  • Disinformation. An image presented as documenting an event in a place it never depicted, with EXIF offered as the corroboration.
  • Listing and identity scams. Rental, marketplace, and dating profiles using location metadata to make a fabricated story check out.

The consequences in the right-hand column are legal rather than technical. Fabricating a photograph to support an insurance claim or a court filing is fraud in most jurisdictions, and the metadata is usually the least of the evidence against the person who did it.

Strip Real GPS Before Sharing — Don't Fake It

Plenty of people arrive at fake GPS looking for privacy: they want to post a photo without publishing their home address. Faking the coordinate is the wrong tool for that job.

A false coordinate is a claim, and claims can be tested. Every check in this article works against you: an inconsistent GPS timestamp or a missing altitude tag tells a reader you edited the file, which invites them to wonder what else you edited and why. Worse, if you shift the pin only a few streets to feel safe, you have published a coordinate close enough to your home to matter.

An absent tag makes no claim. Most photos on the internet carry no GPS at all — a stripped file is unremarkable, tells nobody anything, and cannot be tested for consistency because there is nothing to test. Remove the coordinates instead of replacing them.

Remove GPS and keep everything else:

# Clear the whole GPS group — camera model, ISO, and aperture survive
exiftool -gps:all= -overwrite_original photo.jpg

# A whole folder tree at once
exiftool -gps:all= -overwrite_original -r ~/Pictures/Album

# Confirm nothing is left (prints nothing on a clean file)
exiftool -gps:all photo.jpg

On a phone you can skip the command line. iOS drops location from a shared copy through Share → Options → Location, and Google Photos has an equivalent toggle — both are covered step by step in our guide to stripping metadata before sharing, along with which platforms clean your uploads for you and which quietly pass the EXIF straight through.

Read every GPS tag in a photo — including the ones that give a fake away

Drop a file into our viewer and open the All tab: it lists GPSTimeStamp, GPSDateStamp, altitude, and the rest beside the map pin, so you can run the two-clock check by eye. Then click Strip Metadata & Download for a clean copy. Everything runs in your browser — the photo is never uploaded.

Open the EXIF Viewer

Related Guides

GPS Data in Photos

Which devices geotag by default, how the coordinate fields work, and how to turn geotagging off.

Strip Metadata Before Sharing

Which platforms strip EXIF, which leak it, and the workflow to clean a photo before you upload it.

Photo Privacy Guide

What your photos reveal about you and a checklist for sharing safely.

What Is EXIF Data?

A reference for every field a camera writes, GPS tags included.

How to Change EXIF Date and Time

The timestamp equivalent of this page — the three date fields and how editing one leaves the others disagreeing.

iPhone Photos Show Wrong Location?

Stale fixes and cached positions — wrong GPS is far more often a bug than a forgery.

Frequently Asked Questions

Can you fake EXIF location data?

Yes, easily. GPS coordinates live in the photo's EXIF header as ordinary unsigned bytes, and any metadata editor can overwrite them — ExifTool does it in a single command, and photo managers such as Lightroom, Apple Photos, and Google Photos all expose a "set location" control. Nothing signs or validates the value. The same coordinate can also be faked at capture time by feeding the camera app a mock location from the operating system, in which case the phone writes the false position itself.

How to tell if photo GPS is fake?

Cross-check the coordinate against everything a real satellite fix leaves behind. Compare GPSTimeStamp and GPSDateStamp — which come from the satellites in UTC — against DateTimeOriginal and OffsetTimeOriginal from the camera clock; they should agree. Look for the companion tags a real fix produces (altitude, positioning error, speed, heading) and be suspicious when latitude and longitude appear alone. Watch for suspiciously round numbers, for byte-identical coordinates across photos supposedly taken minutes apart, and for editor fingerprints such as a Software tag or a corrupt maker note. Finally, geolocate the image itself from shadows, signage, and architecture, and see whether the picture agrees with the pin.

Can EXIF data prove where a photo was taken?

No. EXIF carries no cryptographic signature, so a coordinate that survives every consistency check is only a coordinate you have failed to disprove. Metadata can expose a clumsy fake and it can corroborate other evidence, but on its own it establishes nothing. C2PA Content Credentials, supported by a small number of recent camera bodies, sign a photo's origin claims at the moment of capture and are the only mechanism that turns a location into something verifiable.

Should I fake my GPS coordinates to protect my privacy?

Strip them instead. A false coordinate is a claim that can be tested — an inconsistent GPS timestamp or a missing altitude tag tells a reader the file was edited — and a pin nudged a few streets is still close enough to your home to matter. An absent tag makes no claim at all, and most photos online carry no GPS, so a stripped file is completely unremarkable. Run exiftool -gps:all= -overwrite_original photo.jpg, or use our browser-based viewer to strip and download a clean copy.

Is it illegal to change the GPS data in a photo?

Editing metadata in a photo you own is not itself a crime — it is what every photo manager does when you set a location by hand, and photographers legitimately geotag images from a GPS logger or coarsen the location of a wildlife nest before publishing. What matters is the use. Presenting a fabricated coordinate as fact to an insurer, a court, an employer, or a buyer is fraud in most jurisdictions, and the offence lies in the deception rather than in the file edit.

Does removing GPS data leave a trace that something was removed?

Not in any way that distinguishes you from the millions of photos that never had GPS in the first place. Cameras without a GPS chip, phones with location services off, and images downloaded from any platform that strips EXIF all arrive with no coordinates. Stripping the GPS group with exiftool -gps:all= leaves the remaining EXIF intact and the image data untouched, which is exactly what a photo from a DSLR looks like.

Inspect a photo's location metadata yourself

See the coordinates on a map alongside every raw GPS tag, then strip them in one click. Nothing is uploaded — it all runs on your device.

Open Photo Metadata Viewer