What your camera writes that you never asked for
The first time I dropped a phone photo into a metadata viewer, the punchline was a pair of coordinates that resolved to my apartment block, five decimal places deep. The photo was a bowl of soup. Nobody needs to know where soup was eaten, but there it was - written by the camera the instant the shutter moved, along with the phone model, the lens, the exposure, and a timestamp accurate to the second.
That block of information is EXIF, and it is not a bug. It is useful for sorting libraries and for forensic work. It becomes a problem the moment the photo leaves your hands: posted to a forum, attached to a marketplace listing, sent in a reply to a stranger. Most platforms strip it on upload, but "most" is doing heavy lifting in that sentence, and forwarded originals travel as-is.
I built this gate because the tools I found fell into two camps. Fast ones delete the metadata and say nothing about what was in it. Careful-looking ones upload your photo to a server to show you a report - which misses the point so completely it loops back around to funny.
What gets read out, and what gets wiped
Drop a JPG in and the scanner reads the EXIF block directly from the file structure: camera make and model, the original timestamp, lens and serial fields when present, and GPS coordinates converted from degrees-minutes-seconds to decimal degrees. The list is shown on the card before anything is removed - you see what the photo was leaking while it is still leaking it.
The wipe is a re-encode. The pixels are painted onto a fresh canvas and a new file is generated from them, which means everything that was not pixels - EXIF, GPS, IPTC, XMP - simply has nowhere to exist in the output. After encoding, the tool re-scans the finished file at the structure level, looking for any EXIF or XMP block. Only a clean scan turns the card green.
The sideways-photo trap, handled
Here is the detail most removers get wrong. Phones do not rotate portrait photos when you take them; they store landscape pixels plus an orientation flag in EXIF, and viewers rotate on display. Delete the metadata and the flag goes with it - the photo falls over sideways. Anyone who has batch-stripped a camera dump has seen a folder of lying-down sunsets.
This tool reads the orientation flag first, physically rotates the pixels onto the canvas in that direction, and then encodes. Upright goes in, upright comes out, no flag needed. The eight standard orientations are all covered.
Screenshots, PNG, and honest "nothing to do"
Screenshots contain no EXIF - a screen capture never passes through a camera, so there is no camera to write anything. The tool tells you that plainly instead of performing a fake cleanup: a file with nothing to strip gets a "no metadata, ship it" card, not a suspicious progress bar.
PNG and WebP rarely carry EXIF for the same reason of specification: PNG's spec does not include it and WebP support is uncommon. The rare file that does embed a block gets it removed like any JPG would. The format that actually matters is JPG, because that is what cameras and phones shoot by default.
Quality: why the slider starts at 92
Re-encoding a JPG regenerates the image at the pixel level, and that costs a sliver of quality - claiming otherwise would be lying. The default here is 92, above the common 85, because the whole point of this tool is that you post the output directly; at 92 the loss is invisible in normal viewing. If the output is going into another editing pass and must stay pixel-perfect, switch to PNG, which is lossless and metadata-free by construction, at the cost of a larger file.
One honest limit: this tool cleans what is inside the file. It cannot stop a platform from re-compressing your photo or reading pixels for its own features - no local tool can promise that, and you should distrust any that does.