MetaPurge

What is EXIF metadata? The hidden data inside every photo

Every photo your phone takes arrives with a second file attached — a structured record of where you were, what you shot it with, when, and sometimes who edited it afterwards. This is what that record contains.

By Rajat Malik Updated 9 min read

EXIF stands for Exchangeable Image File Format. It is a standard, published by what is now the Camera & Imaging Products Association, for storing camera settings alongside image data. A camera writes it automatically. Your phone writes a much richer version of it, because a phone knows more about you than a DSLR does.

The important part is that EXIF is not part of the picture. It is a separate block of bytes inside the same file. Deleting it does not change a single pixel, which is why a correct metadata remover never needs to re-compress your photo.

What EXIF actually stores

The standard defines a few hundred tags. In practice, a modern phone photo carries these groups:

GroupTypical tagsWhat it reveals
Location GPSLatitude, GPSLongitude, GPSAltitude, GPSDateStamp Where the photo was taken, to within a few metres.
Device Make, Model, LensModel, BodySerialNumber, LensSerialNumber Exact hardware, including serials that can link two photos to one owner.
Time DateTimeOriginal, SubSecTime, OffsetTime When it was taken, to the fraction of a second.
Author Artist, Copyright, OwnerName, ImageUniqueID Who took it, and a per-image identifier.
Processing Software, ProcessingSoftware, XMP history Which editor was used, and often every step since import.

On top of EXIF there are two more metadata systems that often travel in the same file: XMP, an XML block that Lightroom and Photoshop use for edit history, ratings and creator details, and IPTC, the older press-agency standard for captions, by-lines and rights. A photo exported from Lightroom can easily carry all three.

Where it hides in each format

There is no single place to look. Each container stores metadata differently, which is why the same photo can look clean in one tool and dirty in another.

FormatWhere the metadata lives
JPEGAPP1 segment after the SOI marker — one for EXIF, often a second for XMP. ICC profiles sit in APP2.
PNGeXIf chunk plus tEXt, zTXt and iTXt text chunks; colour profile in iCCP.
WebPEXIF, XMP and ICCP chunks in the RIFF container, flagged in the VP8X header.
GIFComment extension blocks and non-essential application extensions.
TIFFNative IFD structure — the format EXIF itself is modelled on.
HEIC / AVIFAn Exif item inside the ISO media meta box.
Why this matters Stripping a JPEG by re-saving it in an image editor removes metadata but also re-compresses the pixels. A container-level remover deletes the metadata segments and copies the compressed image data byte for byte, so quality is untouched.

Two tags you should not delete

Almost everything in EXIF is removable. Two tags are worth keeping, because removing them breaks the image rather than protecting you:

  • Orientation (0x0112). A phone stores the sensor data in one orientation and records how to rotate it for display. Remove the tag and portrait photos appear sideways in viewers that trust EXIF.
  • ICC colour profile. A wide-gamut photo without its profile is interpreted as sRGB, which makes it look flat or oversaturated. It describes the colour space, not you.

Neither tag identifies a person or a place. Everything else — GPS, serials, timestamps, software history — can go.

Why it matters in practice

Metadata is not a theoretical risk. A photo of a bicycle listed on a marketplace site can carry the coordinates of the seller's home. A screenshot posted in a support forum can carry the account name of whoever captured it. A press photo can carry the photographer's home address in an IPTC field, or the exact camera body serial that links every image they have ever published.

None of this is visible when you look at the image, which is exactly the problem. The file looks clean because the leak is not visual.

Check first, then remove

The reliable way to know what a file carries is to parse it, not to guess from the extension. MetaPurge reads the container directly, groups the tags by what they reveal, and lets you remove them by category or one at a time.

If you only want to know whether a file is clean — without changing it — drop it in and read the dashboard. Nothing is uploaded, so the check costs you nothing but a tab.

See what your photos are carrying

Drop an image in. MetaPurge lists every tag, then rewrites the file without touching a pixel.

Open the metadata remover

Where to go next

Rajat Malik Frontend architect and the author of MetaPurge. Builds browser tools that keep files on the device, and writes about the parts of the web that leak by default. rajatmalik.dev