What your photos reveal: EXIF metadata explained

Every photo taken with a phone or digital camera carries a hidden payload of metadata called EXIF (Exchangeable Image File Format). It rides along inside the JPEG file itself, invisible in the picture but readable by anyone with the file and a free viewer. Most of it is harmless. Some of it is a precise map to where you were standing.

What EXIF actually stores

EXIF data lives in a structured block near the start of a JPEG (or HEIC, or TIFF) file. Typical fields include:

• GPS coordinates — if location services were on when the photo was taken, latitude and longitude are embedded to several decimal places. Six decimal places is roughly 10 cm of precision; even four places pins you to a specific building. Altitude and the direction the camera was pointing are often included too.
• Timestamps — the exact date and time of capture, separate from the file's modification date. A set of photos becomes a timeline of your movements.
• Device identification — camera or phone make and model ("Apple iPhone 15 Pro"), and sometimes the lens, firmware version and editing software used. Some cameras embed a unique body serial number.
• Camera settings — shutter speed, aperture, ISO, focal length, flash. Genuinely useful to photographers, harmless to everyone else.
• Embedded thumbnail — a small preview image stored inside the file. Historically, some editors updated the main image but not the thumbnail, so a "cropped" photo could still carry a thumbnail of what was cropped out.

Why the GPS field is the one that matters

The recurring privacy failure is simple: someone shares a photo, the photo contains coordinates, and the coordinates say more than the picture does. The pattern has produced real incidents for over a decade:

• Photos taken at home and posted online reveal a home address — a particular problem for people selling items on marketplaces, or anyone with a stalker. In one widely reported 2012 case, a fugitive's location was identified from GPS coordinates in a photo attached to a magazine interview.
• In 2007, insurgents used geotagged photos that US soldiers had uploaded of helicopters at a base in Iraq to target and destroy several of them — the US Army has since used the incident in operational-security training.
• Fitness and photo-sharing apps have repeatedly leaked the home locations of users who assumed "sharing a photo" meant sharing pixels, not coordinates.

None of this requires sophistication from an attacker. Reading EXIF takes one right-click in many operating systems, or any of hundreds of free tools.

Who strips EXIF for you — and who doesn't

Here is the part most people get wrong. The big social platforms learned this lesson years ago:

Strip metadata on upload: Facebook, Instagram, X/Twitter, LinkedIn, Reddit, TikTok. Photos you post there are re-encoded and served without your GPS data (the platform itself still receives and may keep the original metadata — stripping protects you from other users, not from the platform).

Do not reliably strip it:

• Email attachments — the file arrives byte-for-byte as you sent it, EXIF intact.
• Cloud drive links — Google Drive, Dropbox, OneDrive and similar share the original file. That is the whole point of them.
• Messaging apps, sometimes — WhatsApp strips metadata from photos sent as normal images (which it recompresses) but "send as document/file" transmits the original untouched. Telegram behaves similarly: compressed photos are stripped, files are not.
• Your own website or blog — whatever you upload is what visitors download, unless your CMS strips it.
• Marketplace and classified sites — behaviour varies; assume nothing.

The rule of thumb: if the service recompresses your image, metadata usually dies with the recompression. If it delivers the original file, everything you embedded travels with it.

How stripping works

EXIF removal is genuinely lossless when done properly. The metadata sits in its own segments of the file (APP1 segments in a JPEG), separate from the compressed image data. A remover tool deletes those segments and rewrites the file; the image pixels are copied through untouched, so there is no quality loss and the file gets slightly smaller. This is different from "re-save the image", which strips metadata but also re-encodes — and re-encoding a JPEG costs quality every time.

A good EXIF remover runs entirely in your browser: the file never needs to leave your machine just to have bytes deleted from it. That matters, because uploading a sensitive photo to a random "metadata cleaner" website in order to protect your privacy is a self-defeating move.

When you should keep EXIF

Metadata is not the villain; unintentional disclosure is. There are solid reasons to keep it:

• Your own photo library. Timestamps and GPS are what let your photo app organise pictures by place and date. Strip your archive and you lose that forever.
• Photography work. Camera settings in EXIF are how photographers learn from their own shots and prove how an image was made.
• Copyright and provenance. Creator and copyright fields support ownership claims, and newer provenance standards (C2PA content credentials) build on embedded metadata to fight image misattribution.
• Insurance and documentation. A timestamped, geotagged photo of storm damage is stronger evidence than a bare image.

The sensible policy is: keep metadata on the originals you store, strip it from the copies you share — and before sharing anything sensitive, spend ten seconds looking at what the file actually contains. It is your data; you should be the one who decides where it goes.