What is EXIF — and why your photo tells people where you took it

Look what hides inside an ordinary JPEG. Next to the pixels sits a dossier on the photo itself: when it was taken, with what, at what shutter speed — and, if the camera was allowed, exactly where you were standing. This isn't some vendor's clever add-on either: fields for GPS coordinates landed in the official standard back in 1997.
The thing is called EXIF. If your app accepts photo uploads, it already concerns you personally — you just didn't know it yet.
What EXIF is, in plain words
EXIF (Exchangeable Image File Format) is a block of metadata inside a photo file. Metadata is data about data: the picture is one thing, the story of how it came to be is another — living in the same file.
The standard appeared in 1995 so cameras from different makers would write their housekeeping data the same way. It's still evolving: the latest revision is Exif 3.1, published in 2026. Your phone writes EXIF into every shot without asking.
What's actually in there
The version history reads like a list of what your photo knows about you:
- 1995, version 1.0 — capture date and time, camera model, shutter, aperture, ISO.
- 1997, version 2.0 — a GPS block: latitude, longitude, altitude. That's the moment a photo learned to say where it was taken.
- 2010, version 2.3 — fields for the camera owner and the serial number of the body; the standard describes this outright as a way to prove a shot's origin.
- 2018, version 2.31 — the UTC offset, plus temperature, humidity and pressure where sensors exist.
- 2023, version 3.0 — a block for arbitrary annotations, and the spec names the use case plainly: AI training data and inference results. Plus fields for who processed the image, with which software, at each step.
Reread that last one. A standard that had been running for two decades was opened up to neural networks in 2023: the file itself now has a place for "a model touched this — here's which one".
Why this is your problem if you accept uploads
The failure is mundane. A user photographs an item at home, uploads it to your app, you drop the original into object storage and hand out a URL. Done — the coordinates of their flat are now available to anyone who downloads the file and opens its properties.
You didn't hack anything. You carefully stored what you were sent, and served it.
Mobile apps get a bonus problem: even after someone turns location off in the camera, older shots already carry it inside. And the camera's serial number is identical across every photo from that device — which quietly links shots posted from different accounts into one pile.
The takeaway is simple: other people's files get cleaned on the way in, not "sometime later". It's the same hygiene as keeping user files private.
How to strip it — and why not to strip everything
It's tempting to nuke the whole metadata block in one command. Hold on: one field in there keeps the picture upright — Orientation.
A phone usually writes the pixels as the sensor saw them and files "rotate 90 degrees" as a separate EXIF note. Browsers honour it: in CSS the image-orientation property defaults to from-image, and it has worked that way across browsers since April 2020.
So here's what happens if you wipe metadata wholesale: the note vanishes, the pixels stay as they were — and half the portrait photos on your site fall on their side. The classic "works for me, sideways for users" bug.
Do it in this order instead:
- re-encode the image on the server, applying the rotation to the pixels themselves — nearly every image library does this with one option;
- then drop the metadata safely: the rotation is baked in, there's nothing left to rotate;
- keep the processed file, and either don't keep the original at all or park it in a private bucket with no public URL.
You get a lighter file as a bonus: EXIF with an embedded preview easily runs to tens of kilobytes per shot.
How to see what's inside your own photo
Fast, without installing anything odd:
- on a Mac — Preview, "Tools → Show Inspector", the camera tab;
- on Windows — right-click the file, "Properties → Details";
- in a terminal —
exiftool, which prints every tag there is.
Do it right now with your most recent photo. A line of coordinates is more convincing than any article.
Don't social networks strip all this anyway?
Many services re-encode uploaded photos, and metadata is usually lost in the process. But that's their internal decision, not a guarantee: rules change, and every service is different. What matters is the specific path your file travels — and you certainly can't outsource cleaning to someone else inside your own app.
What about images generated by a neural network?
They carry metadata too, just a different kind: instead of shutter speed and coordinates you more often find notes about the tool and generation parameters. That's precisely what version 3.0 widened the standard for. Don't treat such a note as proof that "AI made this" — it strips off as easily as EXIF does from a photo.
Does EXIF affect site speed?
On one photo, imperceptibly; across a hundred thumbnails, quite a bit — spare kilobytes in every file add up. If you're stripping metadata for privacy, the speed win comes free — more in how to speed up your website.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





