The field that writes your address into every frame

Every modern phone quietly runs a location fix whenever the camera app is open. When the shutter fires, the result is written into the file’s GPS IFD — a dedicated block inside EXIF with latitude, longitude, altitude, a UTC timestamp, and often extras like camera-facing direction, speed and a horizontal-accuracy figure. It costs the user nothing to produce and nothing to overlook. That’s the problem.

How precise “precise” is

Outdoor phone fixes typically land within 3–10 meters. At that resolution, coordinates don’t say “somewhere in Lisbon” — they say “the third-floor flat on the corner of Rua X.” The viewer shows the exact decimal coordinates and a map link so you can see what a recipient would see. It’s worth doing once with a photo you took at home; the experience tends to change sharing habits permanently.

Where it leaks and where it doesn’t

Geotags survive only where the file isn’t re-encoded:

• Survives: email attachments, cloud-drive original files, “send as file/document” modes in chat apps, forum and classified uploads that keep originals, AirDrop.
• Stripped: the mainstream social feeds (Instagram, Facebook, X, LinkedIn) re-encode uploads and drop metadata — though the platform may still read and store it server-side before discarding it from the public file.

The uncomfortable middle ground is everything else: portfolio sites, dating apps, small forums, work attachments, the file you hand to a stranger to “just share it.” Nobody warns you because nothing looks different.

It’s not only where — it’s when, and with what

A GPS block is rarely alone. The same file typically carries the UTC timestamp (your movements, dated), the camera’s local clock (your timezone), and the device model or serial (a fingerprint linking this photo to other geotagged shots from the same device). Combined across a few files, the metadata reconstructs a person’s pattern-of-life with unsettling ease — which is why the documented leaks keep repeating.

Stopping it at the source

• iPhone: Settings → Privacy & Security → Location Services → Camera → Never. Existing geotags aren’t retroactively removed — strip old files before sharing.
• Android: Camera app → Settings → disable Location tags / Save location (wording varies by maker). Google Photos’ share sheet can also remove location per-share.
• Real cameras: many mirrorless bodies get geotags via a paired phone app (Canon Camera Connect, Sony Imaging Edge, Nikon SnapBridge). Disable “add location” in the app or break the pairing for shooting you intend to share.
• Before sharing anything existing: run it through the viewer and strip a copy — the clean file carries pixels only, and the report tells you exactly which fields were inside.

The honest footnote

Geotagging isn’t malicious — it’s how “photos near me” albums, hiking-log cameras and photo-map features work. The design failure is that it’s invisible: nothing in the sharing flow ever shows you the coordinates you’re about to publish. Seeing them once, on your own file, is usually enough to fix that.

Frequently asked questions

How accurate is the GPS data in a photo?

Typically 3–10 meters outdoors with a clear sky view — good enough to identify a specific building. Some files also store a horizontal-positioning-error figure showing exactly how confident the fix was. Indoors or in dense cities it degrades, but even a 50-meter fix narrows a photo to one side of a street.

If I see no GPS fields, am I safe?

From that file, yes. But the pixels can still leak location — landmarks, street signs, license plates, even the sun angle narrows a search. GPS tags are just the part that makes it effortless and machine-readable. Also note: a stripped copy on your screen doesn't remove the copy a platform already received.

Why does my camera's GPS say the time is wrong?

GPS timestamps in EXIF are recorded in UTC, not local time — a dinner photo can carry a timestamp that looks like it belongs to the next day. It's not a bug; it just lacks a timezone field. Some cameras separately record the local clock in the normal date fields, which is itself a leak: UTC GPS time plus local camera time reveals your timezone.

Does disabling location for the camera app also affect other apps?

Only the Camera app's geotagging stops. Social apps that attach location do it at *post* time from the OS location service, not from photo metadata — that's controlled separately inside each app. Killing camera geotagging prevents location being baked into the file itself, which is the durable leak.