EXIF Metadata and Privacy: What Your Photos Are Telling People

Every photo from a phone or camera carries a block of metadata alongside the pixels. Most of it is harmless. Some of it is a precise record of where you were and when.

What is actually in there

Three overlapping standards live in the same file:

EXIF — written by the camera. Make and model, lens, exposure settings, ISO, orientation, timestamp, and — if location services were enabled — GPS latitude, longitude and altitude. Often also a thumbnail of the original image.

IPTC — editorial fields. Caption, credit, copyright, keywords. Added by humans or by software like Lightroom.

XMP — Adobe's extensible container. Edit history, ratings, and anything an application chooses to store, including the original filename and sometimes the local file path.

The parts that leak

GPS coordinates are the obvious one, and they are precise enough to identify a specific room in a building. A photo posted from home discloses the home address.

Timestamps establish a timeline. Combined across several photos they reconstruct movements.

Device serial numbers appear in some camera EXIF, linking otherwise unrelated photos to one device.

Embedded thumbnails are the surprising one. The thumbnail is a separate copy of the image generated at capture time. Crop the main image to remove something sensitive and, depending on the editor, the thumbnail may still show the uncropped original. This has produced real disclosures.

Software and path fields in XMP can reveal a client name from a folder path, or that a "photo" was in fact a composite.

What platforms do

Behavior varies and is worth knowing:

Major social platforms generally strip EXIF on upload — partly for privacy, mostly because re-encoding discards it anyway. They keep their own copy of the original.
Messaging apps vary widely. Sending as a "document" or "file" rather than as a photo typically preserves everything.
Cloud storage and shared links preserve the file byte for byte. A shared Drive folder shares the metadata too.
Your own website serves whatever you uploaded. Nothing strips it for you.
Email attachments preserve everything.

The rule: assume metadata survives unless a platform explicitly re-encodes.

Stripping it

Any operation that decodes to a bitmap and re-encodes drops metadata as a side effect. Browser-based tools do this by design — drawing to a canvas and exporting produces a file with pixels and nothing else. That is why converting or compressing an image in the browser also anonymizes it.

Two consequences of that mechanism:

Orientation goes with it. Some photos are stored rotated with an EXIF orientation flag telling viewers to correct it. If a tool strips EXIF without applying the rotation first, the image comes out sideways. Check portrait photos after processing.

Color profile goes with it. An image tagged Adobe RGB, stripped to untagged, will be interpreted as sRGB and look desaturated. Convert to sRGB before stripping.

When you want to keep it

Metadata is not only a liability:

Copyright and credit in IPTC travel with the file and support attribution claims
Capture settings are the useful part of a photography portfolio
Keywords and captions drive search inside asset libraries
Timestamps matter for documentation, insurance and legal evidence

The workable policy: keep a full-metadata archive privately, and publish stripped derivatives. Never strip your only copy.

A short pre-publish routine

Decide whether location is acceptable for this specific image
If not, re-encode to remove metadata — cropping alone does not do it
Verify orientation and color after processing
Re-check the crop on the output file, not the input, so you know the thumbnail went with it
For portfolios, add back only the fields you want public: credit and copyright

Try it

Image Compressor — compresses locally, dropping metadata as a side effect; the file never leaves your device
Format Converter — converting between PNG, JPEG and WebP re-encodes and strips metadata
Image Cropper — crop and rotate, then export a clean re-encoded file

Related reading: How Image Compression Actually Works explains the canvas round-trip behind the stripping, and Color Spaces for Web Work covers the profile problem in step 3.