Every photo your camera takes writes a diary entry about itself: which device, which lens, what settings, what moment, and, if location was on, exactly where on earth it happened. That diary is EXIF, it travels inside the file, and it is simultaneously a photographer’s best learning tool and the most underestimated privacy leak in everyday sharing. This guide covers both faces, with our free EXIF viewer reading the diary and the EXIF remover shredding it, both in your browser.
In this guide
What is actually in there
EXIF rides inside JPEG and other photo formats as a structured block of tags. The standard inventory of a phone photo: device make and model (often with OS version), lens and exposure (focal length, aperture, shutter speed, ISO), timestamps (when taken, separate from the file’s modified date), software that last touched it, and, when location services were on, GPS coordinates with altitude. Drop any photo into the viewer and the full inventory appears; most people’s first look at their own photos’ EXIF is a small shock, which is the healthy response. Conceptually it is the same hidden-companion-document story as PDF metadata, told in the metadata guide, with one escalation: documents leak your name, photos can leak your address.
The GPS field: the one that matters
The coordinates EXIF stores are not “city-level”: they are typically accurate to a few meters, which for a photo taken at home is a map pin on your door. The risk scenarios are concrete and ordinary: a marketplace listing photographed in your living room, a child’s photo sent outside the family circle, a pet photo posted while on holiday announcing the empty house. None of this requires an attacker, just a recipient who looks. The mechanical fix takes ten seconds, check with the viewer, strip with the remover, and the upstream fix is a phone setting: camera apps can be denied location permission entirely, which solves the problem at the moment of capture for every future photo. The redaction-side companion, blurring what the pixels show, is covered in the photo privacy guide; pixels and metadata are two separate leaks needing two separate fixes.
Who strips it for you, and who does not
The major social platforms remove EXIF on upload, processing photos through their own pipelines, which is why “but I post photos all the time” has mostly not burned people. The gap is everything that is not a major platform: email attachments, many messengers’ “send as file” modes, cloud-drive share links, marketplace uploads, and your own website commonly pass the original file through, EXIF intact. The asymmetry makes memorizing the list a losing game; the durable habit is stripping before the photo leaves your machine whenever the photo or its location is sensitive, and treating platform stripping as a bonus rather than a defense. One more wrinkle: “share as document/file” options that preserve quality also preserve metadata, the trade nobody mentions in the menu.
The orientation flag: EXIF you can see
One EXIF tag is visible in every photo library: orientation. Cameras save the sensor’s pixels as-is and record “rotate this 90° for display” as a tag, and software that ignores the tag shows the photo sideways, the classic upload-looks-rotated bug. It also explains a stripping side effect: remove EXIF carelessly and a portrait photo can fall over, because the rotation instruction left with the metadata. Good removers, ours included, apply the rotation to the pixels before discarding the tag, so the photo keeps standing. If you have ever wondered why one app shows a photo upright and another sideways, two programs disagreed about a metadata field, nothing more.
When EXIF is worth keeping
EXIF earns its bytes in three honest cases. Learning photography: exposure data on your best and worst shots is free coaching, the record of what 1/250 at f/2.8 actually did. Organizing archives: taken-dates and locations power every photo library’s timeline and map view; strip your archive and the map empties. Provenance: copyright fields and capture timestamps support authorship claims, weakly but usefully. The working policy that falls out: keep EXIF on your originals, strip on copies that leave, the same master-and-export discipline as every lossy operation in the image formats pillar.
Frequently asked questions
Do screenshots contain EXIF?
Screenshots carry minimal metadata, typically device and timestamp, and no GPS or camera data, since no camera was involved. Screenshotting a photo is in fact a crude but effective metadata strip, at the cost of quality.
Does editing a photo remove its EXIF?
Inconsistently: some editors preserve it, some rewrite parts (adding themselves as software), some drop it. After any edit, the only way to know what survived is to look, which takes one drop into the viewer.
Can EXIF be faked?
Yes, trivially: the tags are plain data and any tool can write them. EXIF is evidence in the casual sense, useful and suggestive, never proof; courts and platforms treat it accordingly.
Does stripping EXIF reduce the photo’s quality?
No: metadata and pixels live separately, and a proper strip touches only the metadata (plus baking in the orientation, which is lossless in the ways that matter). The image looks identical and the file gets slightly smaller.