The Location Data Hidden in Your Photos

What a stranger learns from one photo

Suppose you list a bike for sale and upload three photos taken in your driveway. If those files still carry their original metadata, anyone who downloads them can read, without any special tooling:

• The exact latitude and longitude where each shot was taken.
• The date and time each shutter fired, down to the second.
• The make and model of your phone or camera, and often the lens.
• Exposure settings, and an orientation flag describing how the camera was held.

Individually these are trivia. Together they answer questions you did not intend to answer: where the bike is stored, that the address in the listing is a home rather than a shop, which hours you are there, and — across a set of photos taken over weeks — a rough pattern of when you come and go. None of it is visible in the picture. All of it travels inside the file.

This is not a reason to stop sharing photos. It is a reason to know which files carry the data and to spend ten seconds checking the ones that matter.

What EXIF actually stores

EXIF is a metadata block that cameras and phones write into the image file at the moment of capture. Editing software adds its own records on top. The fields fall into a few groups:

The GPS block only exists if location services were enabled for the camera at the time. Turn that permission off and the coordinates are never written, which is the cleanest fix of all — though it also breaks the map view in your own photo library, so most people prefer to keep tagging and clean up on the way out.

How precise are the coordinates?

Precise enough to matter. Cameras store position the way navigation charts do — in degrees, minutes and seconds — and converting to the decimal form maps accept is simple arithmetic: degrees + minutes ÷ 60 + seconds ÷ 3600, negated for south latitudes and west longitudes. A photo tagged 37° 49′ 17.4″ N becomes a latitude of 37.8215.

Our EXIF viewer does that conversion for you and prints decimal latitude and longitude rows you can paste straight into a map. As a sense of scale, the fourth decimal place of latitude is worth about 11 meters — narrower than most buildings. Phone GPS is not always that accurate in practice, but the stored figure is specific enough to point at a house rather than a neighborhood.

Where metadata survives and where it disappears

The single most useful thing to understand is that the answer depends on the route the file takes, not on the photo:

Note the asymmetry in the first row. Platforms that strip EXIF are protecting other viewers from your metadata, not you from the platform: the coordinates were in the file you uploaded. If you would rather a service never receive them, remove them before the upload rather than relying on it to clean up afterward.

If you publish photos on a site you run

Test it rather than assume it. Many publishing pipelines resize and re-encode uploads, which drops metadata as a side effect, while others store exactly what you gave them. Take one image already live on your site, download it from the public URL — not from your own folder — and check that file. Whatever you find is what every visitor gets, and it is the only version that counts.

A workflow that takes under a minute

1. Look first. Drop the photo into the EXIF viewer. It parses the metadata bytes on your device — reading the first 64 KB of the file, where EXIF lives, and a few more chunks only if needed — and lists what it finds. Latitude and longitude rows are the ones to look for. If nothing appears, the file is already clean and you are done.
2. Strip a copy. The EXIF remover decodes the image, redraws it onto a blank canvas and exports a new file. Only pixels survive that round trip, so there is no EXIF, GPS, XMP, IPTC or embedded thumbnail in the output — nothing is selectively deleted, because nothing but the picture is written. PNG input comes back as lossless PNG; everything else is re-encoded as JPG at 95% quality, and the download is named clean- plus your filename.
3. Verify. Drop the cleaned file back into the viewer. It should report no metadata found. Verifying takes five seconds and turns an assumption into a fact.
4. Check the filename. Metadata removal does not rename anything, and filenames leak too — camera sequence numbers, export dates, sometimes a client or place name typed in by whoever saved it.
5. Share the cleaned copy, and keep your original in your own library.

Rotation is worth one sentence of reassurance, because it is the thing people expect to break. Browsers apply the EXIF orientation flag while decoding, so the rotation is baked into the pixels before the flag itself is discarded — a portrait photo comes out upright even in software that ignores orientation entirely.

What removing metadata does not do

It is one layer, and it is worth being precise about the limits:

• Visible information stays visible. House numbers, street signs, storefronts, license plates, the view through a window, a distinctive skyline, a reflection in a mirror — all pixels, all untouched. Metadata removal is not redaction; cropping or blurring is a separate job.
• Faces are still faces. Nothing about a metadata strip affects recognition of people, pets, tattoos or a bedroom you have photographed before.
• Context you supply is not metadata. The caption, the listing address, the account you post from and the time you post all carry information.
• Copies already sent are already out. Cleaning your local file does nothing about the version in someone’s inbox.
• Color shifts slightly. Embedded color profiles go with everything else, so the output is standard sRGB. Wide-gamut photos may look marginally different on capable displays — a fair trade in nearly every sharing scenario, but worth knowing if color accuracy is the point of the image.

Prevention at the source

Cleaning files works, but not writing the data is easier to sustain:

• Turn off location permission for your camera app, either permanently or before an occasion you would rather not have tagged. No permission, no GPS block.
• Use your operating system’s share sheet options where they exist — most current phones offer a way to share photos without location data attached.
• For a one-off, screenshot the photo and share the screenshot. You lose resolution and gain a file with no camera metadata at all.
• Set a habit around categories rather than individual files: anything involving your home, your children, your workplace or a document scan goes through a check before it leaves your device.

All of the tools referenced here run entirely in your browser — the photo is decoded, inspected and redrawn locally and never uploaded — so checking a sensitive image does not itself create a copy somewhere else. The flip side is the reason any of this matters: anyone holding your original file can run exactly the same check.