What your photos reveal: EXIF data, GPS location, and how to remove it

A photo file is two things: the pixels you see, and a block of metadata you don’t. The metadata — EXIF, plus its siblings XMP and IPTC — is written automatically by the camera pipeline and travels with the file through most copies, emails, and uploads. Most of it is harmless. Some of it is a street address with a timestamp. This guide covers what’s in there, when it matters, and how to remove it without breaking the image.

What EXIF actually contains

EXIF (Exchangeable Image File Format) is defined by CIPA, the camera industry’s standards body, and is embedded in JPEG, TIFF, and HEIC files. Typical contents of a smartphone photo:

• GPS coordinates. Latitude, longitude, often altitude, plus a separate GPS timestamp. Written whenever location services are enabled for the camera. Precision is typically a few meters — enough to identify a specific building.
• Date and time. When the photo was taken (DateTimeOriginal), separate from the file-system timestamps, which change on copy.
• Device identity.Make and model (“Apple iPhone 15 Pro”), lens details, and on some dedicated cameras the body serial number and lens serial number — enough to link separate photos to the same physical camera.
• Capture settings. Shutter speed, aperture, ISO, focal length, flash state. Harmless for privacy; useful for photographers.
• Software trail. The Software tag records the app or editor that last wrote the file, which can reveal editing history.
• An embedded thumbnail. EXIF carries a small preview image generated at capture time. Some editors update the pixels but not the thumbnail — there have been real cases where a cropped or redacted photo still contained the original, uncropped scene in its EXIF thumbnail.

Why it matters

One photo with GPS tags is a location leak. A stream of them is a pattern: where you live (photos taken at home, clustered at night), where you work, when you travel and when your house is empty. The timestamp plus coordinates is the sensitive combination — and it’s exactly what the GPS block stores. Privacy frameworks such as NIST SP 800-122 treat precise location and persistent device identifiers as personally identifiable information for this reason.

Serial numbers are the quieter risk. A camera body serial embedded in EXIF links every photo from that camera together, including ones posted under different identities. For most people this never matters; for anyone posting pseudonymously, it can.

Where metadata survives — and where it doesn’t

Whether your metadata reaches the recipient depends entirely on the path the file takes.

• Large social platforms generally strip it. Major social networks re-encode uploads (resize, recompress, convert format), and the file other users can access generally has the EXIF block removed. Two caveats: the platform itself typically reads and retains the metadata server-side before stripping, and stripping the downloadable file is a platform behavior, not a guarantee — verify with a test upload if it matters.
• File-transfer paths generally preserve it. Email attachments, files synced to a cloud-drive folder, direct file transfers, and anything sent explicitly “as a file” or “as a document” moves byte-for-byte. The recipient gets the full metadata.
• Messaging apps vary. Many recompress photos sent the default way (which tends to remove EXIF) but pass originals through untouched when you choose a full-quality or file-attachment option. The same app can behave both ways depending on how you send.

The safe rule: assume metadata survives unless you removed it yourself. Relying on a platform’s stripping behavior means trusting an implementation detail that can change without notice.

How to see what a photo carries

Inspect before you share. Our EXIF viewer parses the metadata entirely in your browser — the file is read locally by JavaScript and never uploaded anywhere, which is the right property for a tool whose whole purpose is checking for sensitive data. Drop a photo in and look for a GPS section: if one exists, the photo is geotagged.

On the command line, exiftool photo.jpg prints every tag in every metadata block. ExifTool, by Phil Harvey, is the reference implementation for photo metadata — it reads and writes EXIF, XMP, IPTC, and dozens of maker-specific formats, and it’s what most GUI tools wrap internally.

How to remove it

Ordered from most convenient to most thorough:

1. OS-level share options.Both iOS and Android provide ways to share or export photos with location data removed, and iOS lets you toggle location per-share. Windows Explorer’s file Properties dialog offers “Remove Properties and Personal Information.” Convenient, but scope varies — some options remove only location, not the rest of the block.
2. Re-export through an editor or converter. Tools that decode the image and write a fresh file usually drop metadata unless they deliberately copy it. Our compressor, resizer, and crop toolre-encode through the browser canvas, which produces a clean file — the canvas API has no access to the source’s EXIF, so none can leak through. Note that professional editors often do the opposite by design: preserving metadata is a feature for photographers, so check the export settings.
3. Screenshot the photo.Crude but effective for metadata: the screenshot is a new image generated by the OS with no camera metadata. The costs are real, though — you lose resolution and add recompression, and the screenshot can still carry its own creation timestamp and OS identifiers. It removes the camera’s story, not necessarily all of yours.
4. exiftool, for certainty. exiftool -all= photo.jpg removes every metadata block and keeps a _original backup. Add -overwrite_original to skip the backup. This is the only option on this list where you can be confident that EXIF, XMP, and IPTC are all gone — and it works in batch across a whole directory.

Whichever route you take, verify: run the cleaned file back through an EXIF viewer. The most common failure mode is a tool that strips EXIF but leaves an XMP packet behind with the same GPS coordinates in it.

Beyond EXIF: XMP and IPTC

EXIF is not the only metadata container in an image file, which is why “remove EXIF” is not the same as “remove metadata.”

• XMP (Extensible Metadata Platform) is an XML-based block, originally from Adobe, written by most professional editing tools. It can duplicate EXIF fields — including GPS — and additionally records edit history, creator information, and ratings. A file whose EXIF was stripped can still be geotagged via XMP.
• IPTC metadata, standardized by the International Press Telecommunications Council, is the news-industry block: captions, bylines, copyright notices, and location names (city, country) entered by humans rather than measured by GPS. Less common in personal photos, routine in published ones.

All three blocks can coexist in one JPEG. Thorough removal means clearing all of them — which is exactly what exiftool -all= does and what a full re-encode through a metadata-unaware pipeline achieves implicitly.

A reasonable default policy

• Photos of documents, your home, or anything you post publicly: strip metadata first, verify after.
• Photos sent as files (email, cloud folders, “send as document”): treat as metadata-intact and clean them yourself.
• Your own archive: keep the metadata. GPS tags and timestamps are what make photo libraries searchable by place and date. Strip copies at the point of sharing, not the originals.

Start by looking: open a recent phone photo in the EXIF viewer and see what it says about you. It runs locally in your browser, so checking costs nothing — the file never leaves the page.