EXIF Viewer and Remover
See what your photo gives away, and take it back out, without uploading it.
Runs entirely in your browser
Loading the tool…
Nothing is uploaded. The file is read in this tab, and this page is not permitted to open a connection anywhere.
- —Latitude
- —Longitude
- —Altitude
Open in OpenStreetMap — that link leaves this site, so only follow it if you mean to.
The picture itself is copied through untouched: this removes the metadata segments rather than re-encoding, so nothing is recompressed and no quality is lost.
A photograph off a phone is not only a picture. It usually carries the exact coordinates it was taken at, to within a few metres, the second it was taken, and often the serial number of the camera body, which links every photograph that camera has ever taken to the same device. People post those files daily without knowing any of it is in there.
Choose a file and this page shows you what is actually in it, then removes it if you want. The file never leaves your browser. That is worth saying twice for this tool in particular: every other EXIF viewer asks you to upload the photograph to a server to find out whether it reveals your home address, which is a strange way to answer that question. This page is served with a header forbidding it to open a connection at all.
Removing is lossless. The metadata sits in its own segments in the file, so they are deleted and the compressed picture is copied through byte for byte. Nothing is decoded and nothing is recompressed, which is what happens if you strip metadata by re-saving through an editor.
How to use it
- Choose a photo. It is read in this tab; nothing is uploaded.
- Read what it carries, starting with the location and any serial numbers.
- Press Download without metadata to save a clean copy of the same picture.
Questions
What is EXIF?
A block of metadata cameras write into a photograph alongside the picture. It holds the settings the shot was taken at, the make and model of the camera, the date and time, and on a phone almost always the GPS position. It rides along in the file itself, so it survives being emailed, copied to a USB stick, or uploaded anywhere that does not deliberately remove it.
Does my photo get uploaded?
No. The file is read into memory by your own browser and parsed by WebAssembly inside this tab. The page is served with a Content-Security-Policy whose connect-src is none, so the browser will not permit a connection even if the page attempted one. Open the network tab and choose a file: nothing happens.
Does removing the metadata reduce the quality?
No, and that is the reason this does it the way it does. The metadata lives in its own segments in the JPEG, separate from the compressed picture, so those segments are deleted and every byte of image data is copied through unchanged. Stripping metadata by re-saving through an editor decodes and re-encodes the photograph, which loses a little every time. This does not, and the test suite compares the image data before and after to prove it.
Why can it not remove metadata from a PNG or WebP?
It could, but not without decoding and re-writing the picture, which is a different operation with a real cost, so this page declines rather than doing it quietly. For JPEG the segments can simply be dropped. If you need a clean PNG, running it through the image resizer re-encodes it, and re-encoding discards metadata as a side effect.
Do social networks already strip this?
Most large ones do strip EXIF on upload, and that has been true for years. It does not help with the file itself: what you email, put in a shared folder, attach to a listing, or send in a chat that keeps the original is the file as it came off the camera. The upload is the one case that is usually handled.
What is a camera serial number doing in my photo?
Many cameras write the body and lens serial numbers into every file. On its own it identifies nothing, but it links photographs to each other: two pictures with the same serial came from the same physical camera, whoever posted them and wherever they were posted. It is one of the more surprising things in the list and one of the reasons to remove metadata before publishing.
Is the location accurate?
Usually to within a few metres outdoors, which is precise enough to identify a house. It comes from the phone's own GPS at the moment of the shot, stored as degrees, minutes and seconds. Indoors, or in a city with tall buildings, it can be out by considerably more, and some cameras record a coarse position on purpose.
Why do the tables sometimes show nothing?
Because the file genuinely has no metadata. Screenshots, images exported from most design tools, and pictures already stripped by a social network all arrive clean. That is a good answer rather than a failure, and the page says so rather than showing an empty table.
What a photograph can carry
Not every file has every field. A phone photograph straight off the device usually has all of the first group; a screenshot has none of it.
| Field | What it tells someone |
|---|---|
| GPS position | Where you were, to within a few metres |
| Camera serial | Links every photo from that body to each other |
| Lens serial | The same, for the lens |
| Artist, Copyright | A name, usually yours |
| Date and time | When, to the second, in local time |
| Make and model | What you own |
| Software | What you edited it with, and often the version |
| Thumbnail | A second, smaller copy of the picture |
| Exposure, aperture, ISO | Nothing about you: this is the interesting part |
The thumbnail is the one worth knowing about. It is a separate small image stored inside the file, and cropping or blurring the main picture in some editors does not update it: the original can survive in the thumbnail of an edited photograph. Removing the metadata removes the thumbnail with it.
Your data stays on your device
Everything above runs inside your browser as WebAssembly compiled from Rust. Nothing you type is uploaded, logged or stored on a server. You can load this page once, go offline, and it still works.
This page makes no requests at all, to anywhere. That is not a promise in the copy: it is a Content-Security-Policy header your browser enforces, and connect-src on it is none. Open the network tab and watch nothing happen.