Before you post a photo, you can find out in under a minute whether it's carrying your location — and if you've never checked, you should assume it is. Phones geotag by default the moment you grant the camera app location permission, and the coordinates they write are not "somewhere in your city." They're accurate to a few meters. Post a photo taken at home and you may as well have typed out your address; ask John McAfee, whose 2012 hideout in Guatemala was exposed when Vice posted a photo of him with the iPhone's GPS coordinates still embedded.
This guide covers three things: how coordinates are physically stored in the file (briefly — it explains some odd behavior you'll see), how to actually view them on each platform, and what to do when you find them.
How coordinates are stored in a photo
Location data lives in a dedicated section of the photo's EXIF metadata called the GPS IFD — a separate directory from the camera and exposure fields, which is why tools can remove location without touching anything else. Inside it, GPSLatitude and GPSLongitude are each stored as three rational numbers — degrees, minutes, seconds — paired with GPSLatitudeRef and GPSLongitudeRef holding N/S and E/W. So a photo taken in central Paris carries something like 48° 51' 29.6" N, 2° 17' 40.2" E, encoded as fractions.
The block usually doesn't stop at coordinates. Depending on the device you'll also find GPSAltitude (height above sea level), GPSTimeStamp and GPSDateStamp (the fix time in UTC — useful for catching edited timestamps, since it often survives when someone changes the main date), GPSImgDirection (the compass bearing the camera was pointing), and sometimes GPSSpeed. A single photo can record where you were, how high, which way you were facing, and how fast you were moving — all in one small block near the top of the file.
Why fractions instead of a plain decimal? Because the format was designed in the mid-nineties for camera firmware, and rationals were the cheap, exact way to store fractional values. The practical consequence today: different viewers convert those rationals to decimal degrees slightly differently, so if two tools disagree in the sixth decimal place, that's a rounding artifact — about the width of a hand — not a sign that something's wrong with the file.
Checking on your phone
iPhone
Open the photo in the Photos app and swipe up, or tap the ⓘ button. If the photo has coordinates, you'll see a map with a pin, plus the capture time and device info. Tapping the map opens the full location. On iOS 17 and later, the Adjust link next to the map is also where you can remove or change the location. No third-party app needed — Apple's info panel is genuinely one of the best built-in metadata views on any platform.
Android
Open the photo in Google Photos and swipe up (or tap the three-dot menu → details). Geotagged photos show a map thumbnail with the address Google reverse-geocoded from the coordinates. Samsung's Gallery app has an equivalent details view. If you see an estimated location marked as inferred from your location history rather than from the file, note the difference — that one isn't embedded in the photo itself.
One caution for both platforms: an empty location panel on a photo someone sent you doesn't tell you much. Most chat apps strip GPS in transit, so the sender's original may still be fully tagged. The check that matters is on your own originals, before they leave your device.
Checking on your computer
Windows
Right-click the file → Properties → Details tab, then scroll to the GPS section. Windows shows latitude and longitude as raw degree/minute/second values — no map, so you'll have to paste them into a maps site to see the actual spot. Clunky, but it works on any Windows machine with zero extra software.
macOS
Open the photo in Preview, press Cmd+I, click the ⓘ tab, then the GPS tab. Preview shows the coordinates on a small map and — usefully — includes a Remove Location Info button right there. The GPS tab only appears if the file actually contains coordinates, so its absence is itself an answer.
Any platform: a browser-based viewer
The OS tools show you their interpretation of the data; a dedicated viewer shows you the actual fields. Our photo metadata viewer runs entirely in your browser — the file is parsed locally and never uploaded — and displays the full GPS IFD alongside every other EXIF and XMP field, with the coordinates plotted on a map. It's also the honest way to verify that a "cleaned" photo is actually clean, rather than trusting whatever dialog claimed to have done the job.
Here's the whole check as a routine you can run in under a minute:
- Open the photo in a metadata viewer (or your OS's info panel) before you post it anywhere.
- Look for a GPS section or map pin. No GPS block means no embedded location — you're done.
- If coordinates exist, decide: does this photo's location matter? A mountain vista is different from your living room.
- Strip the location (see below), then re-open the cleaned copy in the viewer to confirm the GPS block is gone.
- Post the cleaned copy — and keep the original for yourself, since the location data is genuinely useful in your own library.
How accurate are the coordinates, really?
Accurate enough to matter. A modern smartphone outdoors with a clear sky typically fixes within about three to five meters — consistent with the official GPS performance figures — and phones blend satellite fixes with Wi-Fi positioning and cell data, so even indoors the recorded point often lands on the right building. Some devices also write GPSHPositioningError, an explicit estimate of the fix's accuracy in meters — when it's present you don't have to guess.
The failure modes run in both directions and both are worth knowing. Sometimes the fix is stale: a phone that just left a tunnel or an airplane can stamp a photo with coordinates from minutes earlier, so a photo's location isn't courtroom-grade proof by itself. And sometimes it's more precise than the situation suggests — a photo taken by a window gets a crisp fix that puts the pin on your apartment, not just your block. In our tests, photos taken in a backyard consistently resolved to the correct half of the property. That's the level of precision you're publishing when you post an ungeoscrubbed photo.
Remember too that nobody has to work for this. Every viewer, including the OS info panels, reverse-geocodes coordinates into a street address automatically. Reading a photo's location isn't a hacker skill; it's a swipe.
Treat embedded coordinates as "which doorway," not "which neighborhood." The people most surprised by EXIF GPS are always surprised in the same direction.
Don't count on platforms to scrub it for you
A common objection: "Instagram strips EXIF anyway, so why bother checking?" Two reasons. First, the platforms that strip do it on their servers — after receiving and reading your original, coordinates included. Second, the stripping is wildly inconsistent across services: Instagram, X, WhatsApp and Signal remove GPS from normal photo sends, while iMessage, email attachments, cloud-drive links, and anything sent "as a file" in Telegram or WhatsApp deliver every field intact. We tested nine services and wrote up the results in a separate scorecard; the short version is that unless you know exactly which send button does what in every app you use, "the platform handles it" is a coin flip.
Checking and scrubbing locally, before the file leaves your device, is the only version of this that works everywhere and protects you from the platforms themselves.
Found coordinates? Here are your options
First, the sledgehammer that prevents the problem: revoke location permission for your camera app (iOS: Settings → Privacy & Security → Location Services → Camera → Never; Android: the camera app's permissions). Your future photos will be clean — though you lose the ability to browse your own library by place, which is honestly one of the nicer features of a photo library, so plenty of people reasonably keep geotagging on and scrub at share time instead.
For photos that already have coordinates, you've got a choice of blast radius. If the location is teh only thing you care about — you want to keep capture dates and camera settings, say, for a photography forum — use a targeted tool like our GPS metadata remover, which deletes the GPS IFD and leaves the rest intact. If you'd rather the file carry nothing at all — no device model, no timestamps, no thumbnail, no XMP — run it through the full metadata remover instead. Both run locally in your browser, and both take a few seconds.
If you post regularly, make the scrub part of your export routine rather than a thing you try to remember at the last second — the McAfee photo wasn't posted by someone careless, it was posted by a professional newsroom on a busy day. Habits beat vigilance.
Whichever tool you pick, close the loop: open the output in the viewer and confirm the GPS section is actually gone. It's a ten-second habit, and it's the difference between believing a photo is clean and knowing it is.