EXIF Remover: Strip Metadata and GPS from a Photo

Cleaning a photo means emptying three separate metadata standards out of the same file, and this tool empties all of them in one pass rather than offering a checklist nobody wants to work through.

EXIF goes first. That covers the device make and model, the specific lens on a multi camera phone, the firmware and software versions, the capture date and time down to the second, orientation, exposure settings, and the GPS block holding latitude, longitude, and sometimes altitude and heading. The embedded thumbnail goes with it, which matters because an old thumbnail occasionally shows an uncropped version of the picture.

IPTC goes next. These are the descriptive fields: captions, keywords, credit lines, copyright notices, and the location names an editing tool may have written in alongside the coordinates.

XMP goes last. Editing software uses it as a scratchpad, so it can hold edit history, software identifiers, ratings, and internal document IDs that link one export to every other export made from the same original.

One block stays, on purpose. The ICC colour profile describes how the numbers in the image should be turned into colours on screen. Strip it and a photo shot in a wide colour space can come back visibly flat or oversaturated, depending on the viewer. The profile says nothing about who took the photo, where, or when, so keeping it costs no privacy and saves the picture from looking wrong.

The result reports how many fields were removed and confirms separately when location data was among them. For an ordinary phone photo that count is usually higher than people expect.

A photo taken at home carries the home. That is the whole problem in one sentence, and it is why the GPS block deserves more attention than the rest of the metadata combined.

The situations where it bites are ordinary ones. An item photographed on the kitchen table for a marketplace listing. A picture of a broken appliance sent to a repair service for a quote. A photo posted to a forum to make a point about something entirely unrelated. In each case the visible image is harmless and the file is not, because anyone who downloads it rather than viewing it in a browser has coordinates accurate to a few metres and a timestamp saying when someone was standing there.

The common counterargument is that platforms handle this. Some do. Many strip metadata when they process an upload, partly for privacy and partly because it saves them storage. Others do not, image hosts in particular often serve the original file byte for byte, and behaviour differs between a service's website and its app, and between this year and last year.

Even where stripping does happen, it only covers the copy that platform serves. The file in the chat thread, the email attachment, the shared album, and the copy on the memory card all still carry everything. Platform behaviour protects one copy of a photo, not the photo.

Cleaning the file before it leaves your device is the only step that applies to every copy that comes after. If you want to see what is in there first, the metadata viewer reads the same file without changing it.

The claim that removing metadata costs no quality sounds like marketing until you look at how a JPEG file is actually built.

A JPEG is a sequence of segments, each introduced by a two byte marker. Some segments carry the information a decoder needs, such as the quantisation tables and the Huffman tables. Others are application segments, numbered APP0 through APP15, which hold data that has nothing to do with decoding. APP1 is where EXIF and XMP live. APP13 is where IPTC lives. APP2 is where the colour profile lives. After all the segments comes a marker called start of scan, and everything from there to the end of the file is the compressed image itself.

Cleaning the file means walking that sequence, copying every segment except APP1 and APP13, and then copying the entire block after the start of scan marker without touching a byte of it. The compressed image data is never decoded and never re-encoded, so there is no second round of lossy compression and nothing to argue about: the pixels that come out are the pixels that went in.

That is what makes the difference between removing metadata and re-saving a photo. A tool that opens the image, decodes it to pixels, and saves it again produces a visually similar file with fresh compression artefacts baked in. Doing that repeatedly is how a photo slowly degrades across a chain of edits.

Formats other than JPEG cannot be edited in place this way, so they are redrawn and saved as PNG. PNG compression is lossless, so no pixel changes, but the file is genuinely rewritten and the result says so instead of implying otherwise.

The outcome depends on what the file is, and the tool tells you which of the two paths it took.

JPEG takes the fast path. The metadata segments come out, everything else is copied untouched, and the file stays a JPEG with the same name plus a suffix marking it as the clean copy. Quality is not a question here, because no image data was decoded.

PNG, WebP, and anything else the browser can decode take the second path. The image is drawn to a canvas and saved as a PNG, which loses no pixels because PNG compression is lossless, but does produce a genuinely new file. The extension changes accordingly. The result notes that the copy was re-encoded rather than stripped, so nobody is left thinking it came out identical.

HEIC files from recent phones are a special case, because browsers vary in whether they can decode them at all. Converting to JPEG first with the HEIC conversion tool gives a file that takes the lossless path, and it is worth knowing that the conversion carries the original metadata across, so the clean step is still needed afterwards.

File size moves in either direction. A phone photo carrying a full colour profile and an embedded thumbnail can lose tens of kilobytes to the strip alone. A small PNG redrawn from a heavily compressed source can come out larger, since PNG is not competing with JPEG on size. When size is the actual goal rather than a side effect, the image compressor is the tool for that, and the resizing tool handles dimensions.

Advice about metadata usually fails for the same reason as advice about backups: it asks for vigilance instead of a routine. A routine that works has three parts and takes less thought than deciding what to post.

Look once, not every time. Open a single photo from your phone in the metadata viewer and read what is actually in it. Doing that once tells you what your specific device writes, which is more useful than any general claim, and it is the step that makes the rest feel worth doing.

Clean the copy that goes out. Not the copy you keep. This distinction is the part most guides get wrong by telling people to strip everything. Capture dates are what make a personal photo library sortable, camera and lens data is what lets a photographer learn from their own archive, and once those fields are gone they are gone. Strip the version being published and leave the original alone.

Keep originals somewhere that is not being shared. A folder, an external drive, a private album. The metadata that is a liability in public is genuinely useful at home, and treating the two copies differently costs nothing.

For anything published in volume, the same order applies: inspect one file to learn the pattern, clean everything that goes out, keep the originals. Photos taken on the same device carry the same field set, so a single look answers the question for the whole batch.