2026-08-29

Does sending a photo share your location — and how do you strip the data without uploading it anywhere?

Apple maintains a document called the Personal Safety User Guide — the manual it points people to in stalking and domestic-abuse situations — and one of its pages is about photos. Not about what's in the picture: about what's attached to it. "When photos and videos that include location metadata are shared," the guide warns, "the people you share them with may be able to access the location metadata and learn where it was taken." That's Apple's own safety documentation saying, in plain words, that a photo can carry your location to whoever receives it. So does sending a photo actually share where you live? The honest answer is: it depends entirely on how you send it — and the rules for when you're protected and when you're not are worth two minutes to learn.

What's riding along inside the file

Every photo a phone takes gets a block of invisible metadata called EXIF written into the file alongside the pixels. Proton's engineering blog lists what's typically in there: the GPS coordinates where the shot was taken (if location services were on), the exact date and time, the camera or phone model, the camera settings — shutter speed, aperture, ISO — and even which editing software touched the file. None of it is hidden in any technical sense: any free EXIF viewer, the file's Properties panel on Windows, or a right-click Get Info on a Mac will show it. The photo looks like a picture of your dog. The file says where your dog sleeps at night, down to GPS coordinates.

The photo that found a fugitive

The canonical demonstration happened in December 2012, and it's still the cleanest example there is. Antivirus pioneer John McAfee was on the run — wanted for questioning in Belize — and had vanished, with journalists worldwide trying to find him. Vice magazine got the exclusive: its reporters traveled with McAfee and posted a photo of him with the headline "We Are with John McAfee Right Now, Suckers." The iPhone that took it had embedded GPS coordinates in the file, and within hours — as NBC News reported at the time — readers had pulled the EXIF data and pinpointed him at a resort in Guatemala, near the Rio Dulce. He was arrested by Guatemalan authorities days later. Nobody hacked anything. Someone just read what the file was already saying.

When you're protected without knowing it — and when you're not

Here's the part most people half-know: posting a photo to a mainstream social feed usually does not hand your GPS coordinates to other users, because the platform re-encodes your image and the public copy loses its metadata. This isn't a courtesy aimed at protecting you, and the proof is who's complaining about it: the IPTC — the standards body for news photo metadata — ran a formal test across fifteen social media sites and found ten of them removed at least some embedded metadata from downloaded images, a result the IPTC publishes as a problem, because the same stripping that deletes your GPS trail also deletes photographers' names and copyright notices. Stripping is a side effect of platforms recompressing images at scale; your privacy is collateral benefit. Two caveats follow directly. First, the platform itself read your metadata at upload — stripped means stripped from the copy other users see, not unseen. As Proton puts it about cloud photo services: storing photos there grants the company access to the full EXIF metadata. Second — and this is the one that catches people — the protection only exists where re-encoding happens. Send the original file and everything travels with it: an email attachment arrives byte-for-byte identical, metadata and all. A file shared through a cloud drive is the original — Proton notes its own Drive doesn't strip EXIF from images, and that's typical of file-storage services, whose whole job is to preserve your file exactly. Messengers that recompress photos generally drop metadata in the process, but their "send as file" or "document" modes exist precisely to skip recompression — and skip the stripping with it.

Turning it off at the source

Apple's Personal Safety User Guide covers the prevention side for iPhones, and it takes seconds. Per-share: pick your photos, tap Share, tap Options at the top of the share sheet, and switch Location off — that one send goes out without coordinates, though the photo itself keeps them for next time. Per-photo: open the photo, tap the menu, choose Adjust Location, then No Location. And globally: Settings → Privacy & Security → Location Services → Camera → Never, which stops coordinates from being recorded at all — at the cost of losing the map view and location search in your own photo library, which is the honest trade-off to weigh. Android offers equivalents in the camera and Google Photos settings. All of this, though, governs photos you take from now on, and per-toggle sends you remember to toggle. The photos already sitting in your camera roll still have their coordinates — which is where the last section comes in.

Why a NearIMG pass strips metadata — structurally, not as a feature

Every NearIMG image tool works the same way under the hood: the browser decodes your file into raw pixels, redraws those pixels onto a canvas, and encodes a brand-new file from the canvas. The output isn't your original with some fields scrubbed — it's a fresh JPG, PNG, or WebP that never contained camera metadata in the first place, because the canvas encoder only ever saw pixels. GPS coordinates, capture timestamp, device model, camera settings: none of it is carried across, on any tool — run a photo through Compress, Resize, Crop, or Convert (even converting a JPG to JPG) and the result is metadata-free. One detail this pipeline gets right that naive strippers get wrong: the EXIF block also contains the orientation tag that keeps phone photos displaying upright, and NearIMG applies that tag to the pixels during decode — the output is upright without needing the tag, rather than sideways because a tool deleted it blindly. And there's a structural irony worth savoring: most online "remove EXIF from photo" services ask you to upload your GPS-tagged photo to their server — sending a stranger your location data in order to delete it. NearIMG runs entirely in your browser; the file, coordinates and all, never leaves your machine.

What re-encoding doesn't fix

Three honest limits. Re-encoding a JPG is a lossy step — at NearIMG's default quality the difference isn't something you'll see, and PNG output is fully lossless, but a re-encode is not the bit-identical original; that's the price of a genuinely fresh file. The filename is metadata too: many Android phones write the capture date straight into it (PXL_20260829_… style), so a "clean" file can still say when it was taken — NearIMG's Rename tool handles that in the same batch. And nothing about metadata removal changes what's visible: a street sign, a storefront, or a reflection can place a photo without any EXIF at all — that's a different checklist, and it's what the Blur tool's solid-block redaction is for.

The one-line version

A photo from your phone carries GPS coordinates, a timestamp, and your device model inside the file — enough to locate a fugitive in 2012 and enough that Apple's own Personal Safety User Guide warns about it today. Social feeds strip it from the public copy as a side effect of re-encoding (after reading it themselves); email attachments, cloud drives, and "send as document" pass it along intact. Turn off camera location if you don't need it, use the iPhone share sheet's Location toggle when you do — and for the photos already on your device, one pass through any NearIMG tool produces a fresh file with no embedded camera metadata at all, without your photo (or its coordinates) ever leaving your machine.