What photo metadata can reveal — and how to remove it

A photograph is two things at once: the picture, and a structured record of how it came to exist. The second part is invisible in every viewer, survives most ways of sharing a file, and on a phone photo routinely includes the coordinates of where you were standing.

This is not a reason for alarm — the data is useful, which is why it exists. It is a reason to know what is there before you publish.

Three standards, not one

“EXIF” gets used as a catch-all, but a single JPEG can carry three separate metadata blocks written by different software for different reasons.

EXIF (Exchangeable Image File Format) is what the camera writes at the moment of capture: exposure, aperture, ISO, focal length, lens model, camera make and model, the date and time, and — if location services are on — GPS latitude, longitude and often altitude. Many cameras also write a body or lens serial number.

IPTC came out of the news industry and describes the picture rather than the equipment: caption, headline, keywords, credit line, copyright notice, and the name of the photographer. If a photo has passed through a picture desk or a stock library, this is where the attribution lives.

XMP is Adobe’s XML-based container, and it is the broadest of the three. Editing software uses it for ratings, labels, edit history and its own proprietary settings. Because it is extensible, XMP is where unexpected things end up.

The practical consequence: a tool that removes “the EXIF data” may leave IPTC and XMP untouched. The photo still names you.

What is actually sensitive

Not every field matters. Sorting the noise from the risk:

• GPS coordinates are the sharp end. Consumer GPS is accurate to a few metres, so a photo taken indoors identifies a building — and a series of photos identifies a routine.
• Camera make, model and serial number link separate photos to the same device. A serial number is a persistent identifier across every photo that camera has ever taken.
• Original timestamp records when, to the second, often with time zone.
• Software names the editing application and version.
• Artist, copyright and credit may carry your legal name even when the account that posted the photo does not.
• The embedded thumbnail is the subtle one. EXIF can hold a small preview generated at capture, and in a handful of well-documented cases that thumbnail preserved the uncropped version of a photo that had been cropped before publication.

Why copying or converting may not remove it

Several intuitions here are wrong:

Copying the file copies the metadata with it — it is inside the file, not attached to it.

Renaming or moving changes nothing.

Taking a screenshot of the photo does remove EXIF, and is a genuinely effective if crude method. The screenshot is a new image; it carries only what your device writes about the screenshot.

Converting to another format usually strips most metadata, because the converter rebuilds the file — but this depends entirely on the converter, and some deliberately carry metadata across. Do not assume.

Uploading to a social platform typically strips it from the copy the platform serves to others. Facebook, Instagram and X all do. But email attachments, marketplace listings, cloud-drive links and forum uploads generally do not — and those are exactly the informal contexts where a home address is most likely to be attached to a photo of a sofa for sale.

Removing it without wrecking the image

The obvious approach — open the photo, save a copy — works, and costs you quality. JPEG is lossy, so every re-save re-compresses and accumulates artefacts. That is a poor trade when the goal is deleting a few hundred bytes.

The better approach exploits how these formats are built. A JPEG is a sequence of marker segments, and the metadata lives in its own segments (APP1 for EXIF and XMP, APP13 for IPTC, COM for comments). Those segments can be deleted and the compressed image data copied across byte for byte. PNG is a chunk stream, so tEXt, iTXt and eXIf chunks can be dropped the same way. WebP is a RIFF container with EXIF and XMP chunks.

That is what the EXIF viewer and remover here does, which is why it reports the file getting smaller while the pixels stay identical.

Two consequences worth knowing:

Orientation. Cameras often store the sensor image unrotated and record “rotate this 90°” as an EXIF field. Remove the metadata and that instruction goes too, so an image that relied on it can appear sideways. If that happens, run the original through the rotate tool first — it bakes the rotation into the pixels — and remove the metadata afterwards.

Colour profiles. The ICC profile is technically metadata but tells the viewer how to interpret the colours. Dropping it can visibly shift a wide-gamut photo, so it is worth keeping unless you need the smallest possible file.

Verifying, rather than trusting

No tool can honestly promise that every byte of every private extension is gone — a file could carry data in a vendor block nobody has documented. The sensible habit for anything genuinely sensitive is to check the result rather than trust the claim: run the cleaned copy back through a viewer and confirm the fields are gone. Checking with a different tool from the one that did the removing is better still.

The realistic goal is not metaphysical certainty. It is making sure the photo you are about to post does not carry your coordinates, your camera’s serial number and your full legal name — and that much is entirely achievable in a few seconds.