The format is called EXIF, short for Exchangeable Image File Format. It was designed in the 1990s for camera manufacturers to embed technical details, shutter speed, aperture, focal length, so photo editing software could read them back. GPS tagging came later, added as phones started shipping with location chips. Neither addition considered what happens when the photo leaves the photographer's hands.
A typical smartphone photo's EXIF block can include the exact latitude and longitude of capture, the device make and model, the orientation the phone was held in, the exact timestamp down to the second, and in some cases a unique identifier for the camera sensor. None of it is visible in the image itself. All of it travels with the file unless something strips it out.
The case that made this concrete
In December 2012, Vice published a photo of the antivirus software founder John McAfee, who was evading Belizean authorities at the time, with the caption "we are with John McAfee right now, suckers." The photo had been taken on an iPhone and uploaded with its EXIF data intact. Readers pulled the GPS coordinates out of the file within hours and placed McAfee at a specific location in Guatemala. He was arrested there shortly after.
The story became a standard case study in operational security precisely because nothing exotic happened. No hacking, no informant, no intercepted communication. A journalist uploaded an unmodified photo file, and the file told everyone where it was taken.
Which platforms actually strip it
Most messaging apps that compress images for fast delivery strip EXIF as a side effect of that compression, whether or not privacy was the motivating design goal. But "most messaging apps" is not "everything you might photograph and send," and the gaps are where people get caught out.
| Sharing method | GPS and camera metadata |
|---|---|
| Signal, standard message attachment | Stripped |
| WhatsApp, compressed photo send | Stripped |
| Email attachment (original file) | Intact |
| AirDrop / Nearby Share (original file) | Intact |
| Cloud storage direct download link | Depends on export settings |
| "Send as document" / "send original quality" toggles | Usually intact |
The pattern is consistent: anything designed to preserve the original file for a recipient, rather than optimize it for quick viewing, tends to preserve the metadata along with it. That includes the "send original" or "high quality" options a lot of apps now offer as an alternative to their default compression, which quietly reintroduces the exposure that the default behavior removed.
Checking and stripping it yourself
On a desktop, the fastest check is the operating system's own file properties. On Windows, right-click the file, choose Properties, then the Details tab, where GPS and camera fields are listed directly, with a "Remove Properties and Personal Information" link at the bottom. On macOS, Preview's Tools menu has a "Show Inspector" option with a GPS tab, though Preview's built-in removal is limited to certain fields.
For anything more thorough, the open-source tool exiftool handles every field in one command: exiftool -all= photo.jpg strips the entire metadata block in place. It runs on Windows, macOS, and Linux, and it's the tool most digital forensics guides point to because it's actually complete, unlike a lot of the "photo metadata remover" apps that only touch GPS and leave the rest.
iOS and Android both let you strip location from a photo before sharing through the system share sheet, but the option is opt-in per share, not a standing setting. If you forget once, that one photo carries its full metadata regardless of how careful you were with the last twenty.
Turning it off at the source
Stripping metadata after the fact treats a symptom that's easier to prevent. Both major mobile platforms let you disable location tagging for the camera specifically, separate from location services for every other app, buried a few menu levels deep: on iOS, Settings, Privacy and Security, Location Services, Camera, set to Never; on Android, the exact path varies by manufacturer but is typically Settings, Apps, Camera, Permissions, Location. Turning this off means new photos never carry GPS data in the first place, which removes the entire category of "I forgot to check before sharing this one." The trade-off is losing the location tagging in your own photo library, useful for anyone who relies on Photos or Google Photos to auto-organize a trip by place. Most people who make this trade only do it selectively, off at home, back on while traveling somewhere they want the record.
Why this matters more for some people than others
For most people this is a minor hygiene issue. For someone being tracked by an abusive partner, a stalker, or an employer conducting surveillance, it's a live safety risk, and it's one that's easy to miss because the exposure is invisible in the app that's sharing the photo. A person fleeing a domestic violence situation who posts a photo from a new city, or sends one to a friend through a channel that doesn't strip metadata, can undo weeks of careful relocation with a single upload. We've written a fuller technology safety planning guide for that specific threat model, and metadata stripping belongs on that checklist alongside account separation and device audits.
A habit, not a one-time fix
There's no universal setting that solves this permanently, because the risk reappears every time you choose a new app, a new sharing method, or a new "send as original" option. The workable habit is treating metadata stripping the way you'd treat locking a door: check before you send anything that reveals where you are, particularly photos taken at home, at work, or anywhere you don't want a stranger to be able to point at on a map.