EXIF and Image Privacy: What Photos Reveal

EXIF (Exchangeable Image File Format) is metadata that cameras and phones embed in JPEG and many other files. It typically records the camera or phone model, lens, exposure settings, the date and time, and often the orientation used to display the photo the right way up. Photo apps read it to sort by date, show camera details and rotate images automatically. Most of it is harmless and genuinely handy.

EXIF is not the only passenger. Editors add XMP blocks, newsroom workflows add IPTC fields for captions and credit, and colour-managed files carry an ICC profile. Together these routinely account for 20–60 KB, and occasionally far more when a large camera profile or a full-size embedded preview thumbnail is included — on a small web image the metadata can outweigh the picture itself. EXIF can also record a camera body's serial number, which ties every photo from that camera back to the same owner.

The sensitive part is GPS. Many phones, unless told otherwise, tag each photo with the exact latitude and longitude where it was taken. Post that image somewhere that keeps metadata and you may be publishing your home address, a child's school, or a routine, along with a precise timestamp. Large social platforms usually strip EXIF on upload, but direct file shares — email attachments, cloud links, messaging apps that send "as a file" — often keep it fully intact.

The precision is what people underestimate. Coordinates are stored as degrees, minutes and seconds with fractional parts, which in practice places a photo within a few metres — enough to identify which flat in a building, not merely which street. Alongside them many phones record altitude, the compass direction the camera was facing and, on some models, how fast you were moving at the time.

Re-encoding an image can remove metadata as a side effect. When a tool decodes a photo into raw pixels and writes a brand-new file — which is exactly what canvas-based compression does — the original EXIF block is not carried over, so the GPS tags and timestamps are dropped. That means running a photo through a browser compressor before sharing both shrinks it and quietly cleans off location data. Because PixelPress does all of this locally, the image and its metadata never leave your device in the first place.

Removing EXIF is not anonymity. The picture itself still shows a street, a view from a window, a school uniform, a number plate or a reflection in a mirror, and those identify a place far more reliably than a coordinate pair. Filenames leak too: a name like IMG_20240712_180233.jpg carries a date and a time whether or not the file has any metadata left inside it.

It also does not reach copies. If the photo has already been sent, uploaded or backed up, cleaning your local file changes nothing about the versions elsewhere, and some services keep their own record of what you uploaded regardless of what the file contained. Treat metadata removal as one useful step before sharing, not as a guarantee after the fact.

Stripping is not free. The orientation tag goes with everything else, so a photo processed by a tool that ignores rotation can come back sideways — good tools apply the rotation to the pixels before discarding the tag, which is why a compressed copy usually looks correct. The ICC profile goes too, and if the original was in a wide gamut such as Display P3 or Adobe RGB, browsers will read the remaining numbers as sRGB and the colours will look flat or oversaturated. Converting to sRGB before stripping avoids that entirely.

For your own archive the metadata is worth keeping. Capture dates are what let a photo library sort thirty years of pictures correctly, exposure fields are how you learn from your own work, and the copyright and credit lines are often the only thing connecting a published image back to its author. The sensible pattern is to keep full metadata on the master file and strip only the copies you send out.