When you send a photo to a stranger, how much do they learn about you? If the file came straight off your phone, the answer is usually more than you think. EXIF data is metadata embedded in JPEG, TIFF, and HEIC files that can carry your approximate GPS coordinates, the make and model of your device, the exact timestamp the shutter fired, and the software that later touched the file. None of it is visible in the image. All of it ships with the file unless something strips it.

What EXIF is and what it stores

EXIF stands for Exchangeable Image File Format, standardized by JEITA and extended through the CIPA DC-008 specification. It dates to the late 1990s, built so downstream software could know how a digital camera captured a photo. The tags live inside the image file in a structured block that any spec-aware reader can parse.

The tags that matter for privacy are a handful:

  • GPS coordinates — latitude, longitude, and sometimes altitude, populated when location services were on. Accuracy is typically within tens of meters.
  • Camera and lens — make, model, lens, focal length, aperture, shutter speed, ISO.
  • Timestamps — the original capture time (DateTimeOriginal), distinct from the filesystem modification date.
  • Software — the editing program that last saved the file (Lightroom, Photoshop, GIMP).
  • Orientation, exposure mode, white balance — harmless individually, identifying in aggregate.

A single photo from a phone can carry 100+ tags. Most you don’t care about. The GPS block and the device identifiers are the ones that leak.

When EXIF leaks

The risk depends entirely on where the file lands. The same photo that’s harmless in your camera roll becomes a problem the moment it leaves your control.

Social platforms behave differently, and the rules shift. Instagram strips EXIF server-side on upload. Twitter (X) strips most metadata from inline images. Reddit strips EXIF on uploaded images. These are policies, not contracts; they have changed before, so verify the current behavior on the platform you use.

Email and messaging are riskier. Apple Mail attached to an SMTP relay often preserves EXIF intact. Gmail’s web compose strips some tags but historically not all. Signal and WhatsApp strip metadata on sent images by default. Discord strips EXIF from photos you upload directly, though videos keep their metadata, which is the real leak vector there.

Public uploads and cloud shares are where EXIF bites hardest. A photo posted to a forum, a bug tracker attachment, a shared Dropbox folder, or a real-estate listing is usually the original file. So is a picture you paste into a support chat. Anyone who can download the file can read the GPS block in seconds. There are documented cases of people locating a stranger’s home address from a single photo shared through a back channel that didn’t strip metadata.

The threat model isn’t only stalkers. EXIF can place you somewhere at a specific time, which matters for journalists, activists, and anyone whose safety depends on not being geolocatable.

How to inspect it

Before you worry about stripping, look. Drag any photo into the EXIF Viewer and it parses the tags locally in your browser; the file never leaves your machine, which is the right property for this kind of inspection. Check whether the GPS block is present, what device string is recorded, and whether the timestamp matches reality. For a folder of hundreds, ExifTool (Phil Harvey’s command-line tool, the de facto reference implementation) will dump every tag to CSV.

How to strip it

Three layers, depending on your threat model.

OS-level, one file at a time. On Windows, right-click the file, Properties, Details tab, “Remove Properties and Personal Information.” On macOS, Preview’s Export has a “Remove Location Info” option, though it’s not a full strip; for full removal use ImageOptim or exiftool -all= file.jpg in Terminal. On iOS, when sharing from Photos, toggle off “All Photos Data” if you want the original preserved; leave it on and iOS hands the recipient a re-encoded, EXIF-stripped version.

Re-export through a tool. Re-encoding an image through an image resizer or any pipeline that recompresses the pixels typically drops the EXIF block by default, since the output is a fresh file. This is convenient but sloppy; verify the output actually lost the tags rather than assuming.

The reliable path. ExifTool with -all= writes a clean copy. ImageMagick’s convert -strip does the same. For a web upload pipeline, run images through one of these before they hit storage. The EFF’s “Cover Your Tracks” guidance makes the same point: don’t trust downstream services to strip for you. By the time the file reaches them, it’s already left your device.

A note on screenshots: screenshots taken by the OS generally do not carry EXIF. They may carry a filesystem creation timestamp, but no GPS or camera tags, because no camera was involved. That makes screenshots a safer format for UI captures and receipts.

FAQ

Does Instagram remove EXIF data?

Yes. Instagram strips EXIF from photos uploaded to feeds and stories server-side. Viewers of your post won’t see your GPS or device tags. This is a platform policy, not a guarantee; it has held for years but could change, and it doesn’t cover images shared through Instagram’s direct messaging in the same way.

Can EXIF data be faked?

Yes, trivially. EXIF tags are plain bytes in a known structure, so anyone with ExifTool can write arbitrary GPS coordinates, timestamps, or device strings into a file. EXIF is a claim by the capturing device, not a signed assertion. Treat it as a hint about provenance, never as forensic proof.

Do screenshots have EXIF data?

Generally no. A screenshot is a pixel capture by the OS, not a camera output, so the camera-related tags never get written. The file will still have a filesystem creation timestamp, and some screenshot tools add their own Software tag, but GPS, lens, and exposure data are absent.

What about HEIC files?

HEIC (Apple’s High Efficiency Image Container, standardized as HEIF) carries the same EXIF structure inside its metadata track. The privacy exposure is identical to JPEG: GPS, device, and timestamp all travel along. HEIC adds orientation and burst/sequence metadata on top. iOS strips HEIC metadata on share by default when “All Photos Data” is off, but the original file in your camera roll has the full block.

Is EXIF the same as IPTC and XMP?

No. EXIF is the camera-capture block. IPTC is a journalism-oriented schema (caption, credit, copyright, byline) added by news agencies and editing tools. XMP is Adobe’s XML-based metadata framework that can carry all of the above plus rights and workflow fields. All three can sit in the same image file independently. A full strip needs to clear all of them, which is why exiftool -all= (not just “remove EXIF”) is the safe command to reach for.

Check one photo today

Open your most recent photo — the one you’d send without thinking — and drop it into the EXIF Viewer. If the GPS block is populated, every file you’ve shared from that device has carried the same kind of data unless something downstream stripped it. That’s the check worth doing before the next share.