How to Check Whether a Photo Contains GPS Data

Why GPS in photos is easy to miss

Phones often store location in the background when the camera has permission to use GPS. Nothing in the visible preview has to scream “this file knows where you were.” The coordinates sit in metadata until something (or someone) reads them.

Checking for GPS before sharing is a short habit that prevents accidental disclosure of home addresses, travel routes, and workplaces.

What “GPS data” usually means

In JPEG EXIF, location is typically stored as latitude, longitude, and sometimes altitude or a GPS timestamp. Some files also include a human-readable place name written by an editor. PNG files less often carry classic EXIF GPS, but they can still hold location-related XMP or other tags depending on the app that saved them.

Absence of a map pin in your gallery app does not prove the file is clean. Gallery UIs hide fields all the time.

A simple inspection workflow

1. Prefer the original export

If you edited the photo in an app that “shares a copy,” you may already be looking at a re-encoded file. For privacy checks before a sensitive send, inspect the file you are about to attach, not a thumbnail cache.

2. Use a metadata inspector

Load the image in a tool that lists GPS fields explicitly. You want a clear yes/no for coordinates, not only a camera model string. Filewillow offers an Image Metadata Cleaner that summarizes common privacy-sensitive fields in the browser.

3. Interpret empty results carefully

No GPS detected can mean:

• Location was never written.
• A previous export already stripped it.
• The format or field layout is uncommon and not shown by that inspector.

If the photo is sensitive, confirm with a second reader or strip supported metadata anyway and re-check the output.

4. Check related clues

Even without GPS tags, look at:

• Capture time (narrows when you were there).
• Device model (less sensitive, still identifying in some cases).
• Filename patterns like IMG_20260312_184402.jpg that encode dates.
• Visible street signs or reflections in the image itself.

Platform myths worth discarding

• “I turned off location in the camera once, so old photos are fine.” Old files keep whatever they already stored.
• “Social upload always removes GPS.” Behavior varies by product and by whether someone downloads the original vs. a compressed preview.
• “PNG is always safe.” Format choice is not a privacy guarantee.

After you find GPS

If coordinates are present and the recipient does not need them:

1. Create a cleaned copy with supported location fields removed.
2. Keep the original offline if you still want the archive with location.
3. Re-inspect the cleaned file before sending.
4. Share the cleaned file, not the original attachment from your camera roll.

Cleaning supported GPS fields from a typical JPEG is a common, legitimate privacy step. It does not rewrite the pixels to hide landmarks, nor does it claim to purge every obscure vendor tag in every container.

When you should keep GPS

Keep location when you are mapping a hike for yourself, delivering geotagged survey photos to a client who requested them, or preserving a personal archive. Intentional geotagging is fine; accidental geotagging to strangers is the problem.

Summary

Checking photo GPS is mostly about inspecting the actual file you will send, reading location fields explicitly, and verifying after cleanup. Make that a default step for anything leaving your device toward a public or loosely trusted audience.

Related reading

After you confirm GPS is present, use Removing location data from JPEG photos. For the wider privacy picture, read what image metadata reveals.