Guide · Photo privacy
What Your Photos Reveal: EXIF and GPS
A photo file is not just pixels. Alongside the image, most cameras write a block of structured data recording where the shot was taken, when, and with what — and that block travels with the file every time you send it. This guide covers what is in there, where it actually leaks, and what removing it does and does not protect you from.
Converting a photo through this site decodes it to raw pixels and writes a fresh file, so the metadata block does not survive the trip. That happens in your browser — the photo is not uploaded in order to be cleaned.
What is actually in the file
EXIF — Exchangeable Image File Format — is a convention for embedding tagged data inside a photo, and it has been standard equipment on cameras and phones for over two decades. The tags sit in the file's header, invisible when you view the image, fully readable by anything that knows to look.
The one worth caring about is location. If location services were on when you took the shot, the file carries latitude and longitude, usually altitude, and on many devices the compass direction the lens was pointing. Phone GPS is typically accurate to a handful of meters outdoors, which is usually precise enough to pick out a specific building or address. Many phones also record an altitude, though that figure is considerably less reliable than the horizontal position.
The rest is a detailed portrait of the moment and the equipment: the capture timestamp, often to the second and sometimes with a time-zone offset; the camera make and model; the lens; shutter speed, aperture, and ISO; the orientation the camera was held in; and the software that last touched the file, which quietly announces which editor and which version you use. Dedicated cameras go further — the standard includes fields for body and lens serial numbers, and some manufacturers populate them, along with an owner-name field if it has ever been set. Phones generally do not write serial numbers, but a serial number in a photo is a durable identifier that links every image from that body together, forever.
None of this is malicious. It exists because photographers wanted their exposure settings back, and because a map of your own library is genuinely useful. It only becomes a problem when the file crosses from your library into someone else's hands.
Where it leaks, and where it usually doesn't
Sending the original file is the main leak. Email attachments, messaging apps set to send full-quality or original files, AirDrop, a cloud storage share link, a USB copy, a photo attached to a support ticket. In every one of these the recipient receives the bytes you have, header and all. So does anyone they forward it to.
Sites that host the file as-is. Classifieds and marketplace listings, community forums, wikis, personal blogs, and smaller self-hosted galleries frequently store and serve exactly the file you handed them. The photo of a couch for sale can carry the coordinates of the living room it is standing in.
Large social platforms usually strip it — but do not build a habit on that. The major networks generally re-encode uploads for delivery, and that process typically discards EXIF from the copy other users can download. That is a convenience, not a guarantee. The behavior differs between platforms, differs between upload paths within the same platform, has changed over the years, and can change again. More to the point, stripping metadata from the public copy says nothing about whether the platform read and kept it on the way in — it did receive the original.
The workable rule is to strip before sending, and treat any platform's cleanup as a second layer you were not counting on.
How to check what a photo carries
You do not need special software; every desktop operating system will show you. On Windows, right-click the file, choose Properties, and open the Details tab — latitude and longitude appear there as plain numbers if they are present. The same dialog has a Remove Properties and Personal Information link that can write a cleaned copy.
On macOS, open the file in Preview and choose Show Inspector from the Tools menu; the inspector's tabs include the full EXIF list and a GPS tab that plots the location on a map. In the Photos app, Get Info shows the same thing.
On a phone, open the picture in your photo app and pull up on it or tap the info button. iOS shows a map beneath the photo when location data exists, and offers an Adjust Location control that can clear it. Android's Google Photos shows an equivalent details panel with the device, the settings, and a map.
Do this once with a photo you took outdoors with location services on. Seeing your own street on that little map is more persuasive than any amount of explanation, and it calibrates how careful you need to be with the rest.
Why converting removes it
Stripping metadata is not a special feature of a converter so much as an unavoidable consequence of how conversion works. Decoding turns the compressed bytes into a raw grid of pixel values. That grid contains no tags — it is just color numbers. Re-encoding then writes an entirely new file from that grid, and the new file contains only what the encoder chooses to write. The old header is not copied because it was never part of what came out of the decoder.
The one piece of metadata that does survive, in effect, is orientation: a decoder applies the rotation tag while decoding, so the pixels come out the right way up and the now-absent tag is no longer needed. Everything else — coordinates, timestamps, device, lens, serial numbers, editing history — is simply gone from the output.
That makes a format conversion a reliable scrub as a side effect. Converting a HEIC to JPG for an upload cleans the file in the same pass that makes it openable — one step, two problems solved.
There is a cost worth naming: you also lose the capture date, which is often the one tag you wanted. If a photo matters chronologically, note the date first, or keep the original as your archive and send the converted copy.
What a metadata scrub does not do
The pixels still identify the place. This is the limit that catches people out. A street sign, a house number, a distinctive skyline, a reflection in a window, the view from a balcony — any of these can locate a photo as precisely as a coordinate pair, and no amount of header cleaning touches them. The same goes for a visible screen, a name badge, a license plate, or a distinctive tattoo. Look at the image before you worry about the file.
It is not anonymity. Whoever receives the photo still sees the account, address, or profile that sent it, and a site you upload to still records the connection. Removing EXIF narrows what a stranger can learn from a file passed along later; it does not make you unidentifiable to the party you handed it to.
It does not retract anything already sent. If the original went out last week, cleaning a fresh copy today changes nothing about the copy that is already in someone's inbox.
Filenames and file dates are outside the image. A file named for what it contains, or a creation date recorded by your file system, travels alongside the picture and is untouched by re-encoding. Rename before sending when it matters.
Stripping metadata is a cheap habit with a clearly bounded benefit: it removes the machine-readable facts a file volunteers to anyone who opens it. Worth doing every time — and not a substitute for looking at what is in the frame.