9314JIUsi
Privacy tool · inspect before you post

Put your photos through inspection before they leave

Every photo a camera writes carries a passenger list: the model of the phone, the moment it was taken, sometimes GPS coordinates precise to five decimal places. Drop photos into the gate below. The list gets read out first, the metadata gets wiped, and the output gets scanned again - zero residue, then it ships. Nothing ever leaves this device's browser.

INSPECTION GATE Belt slots free: 20 / 20
Photos go in the tray

Drag, click to browse, or paste with Ctrl+V. JPG / PNG / WebP, up to 50MB each, 20 per batch. List first, wipe second, re-scan last.

Photos are read and re-encoded in this device's browser only: nothing is uploaded to a server and nothing is written to local storage. Your output format and quality preferences are kept in this browser and disappear when you switch devices or clear site data. Use "Clear my data" in the footer to remove them.

The belt is idle. Drop photos in and watch each card: scan and list, wipe, re-scan. You see exactly what privacy got taken out.

Three steps through the gate

  1. InspectPhotos land in the tray. Each one gets scanned: model, timestamp, GPS coordinates, orientation flag. What is there gets listed; what is not does not get invented.
  2. WipePixels are rotated upright according to the EXIF orientation, then re-encoded into a fresh file that contains nothing but pixels. JPG defaults to quality 92; pick PNG for lossless.
  3. Re-scanThe finished file gets a structure-level check for EXIF or XMP blocks. Zero residue and the card turns green. Download one by one or grab the ZIP.

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.

Facts and limits

InputJPG (where EXIF lives) / PNG / WebP (usually no EXIF - shown honestly as "nothing to clean"; embedded EXIF/XMP blocks get wiped all the same). HEIC and GIF are not supported
OutputPNG (lossless pixels, no metadata by construction, larger) / JPG (small, slight re-encode loss). Output names gain a -clean suffix and the right extension; duplicates get numbered
DefaultsJPG quality defaults to 92 (slider 1-100; PNG is lossless so the slider disables itself). Nothing else to configure - the wipe is total, not per-field
ProcessingLocal Canvas re-encoding in your browser (pixels rotated per EXIF Orientation 1-8 first, then regenerated as a pixels-only file). EXIF/GPS/camera info/IPTC/XMP all go; output is re-scanned at file-structure level. No uploads, no account; preferences live in this device's localStorage, photos are never stored
Limits50MB per file; 20 files per batch; files process one by one so a failure never blocks the batch; results pack into a stored (uncompressed) ZIP
Known limitsJPG output carries slight re-encode loss (invisible at quality 92; use PNG to avoid it entirely). Removed metadata cannot be restored - back up originals you care about. This tool cleans what is embedded in the file; it cannot change what platforms do after upload

FAQ

Will my photos end up sideways after cleaning?

No. Portrait photos shot on a phone stay upright because of an orientation flag inside EXIF. Most tools delete the flag along with the metadata, and the photo falls over. This tool physically rotates the pixels according to that flag before re-encoding, so the new file is upright and carries no metadata at all.

Are screenshots dangerous to share?

Screenshots have no EXIF. EXIF is written by cameras; a screenshot is captured from the screen and never touches a camera, so there is usually no location or device data in it. Two things still deserve caution: original photos picked from your camera roll (especially ones with location on), and photos someone sent you that you are about to forward - you cannot know what they carry. Drop them in here first; if the list comes back empty, share away.

Can the removed metadata be recovered?

No. The cleanup here is a re-encode: only the pixels survive, inside a brand-new file that was never given any metadata. The original EXIF is not hidden or masked - it simply does not exist in the new file. Keep a backup of the original if you need it; a cleaned photo cannot be un-cleaned.

Do PNG or WebP images need cleaning?

Usually not. The PNG specification does not include EXIF and WebP support for it is rare, so this tool tells you plainly when a file has nothing to clean instead of pretending to work. The format to watch is JPG: cameras and phones shoot JPG by default, and that is where EXIF lives. Files that do embed an EXIF or XMP block get it removed all the same.

How many at once, and is quality lost?

Up to 20 files per batch, each up to 50MB. Re-encoding regenerates the image at the pixel level, so JPG output takes a slight quality hit - that is why the quality slider defaults to 92, higher than the usual 85, and stays visually clean. For pixel-perfect output pick PNG, which is lossless but larger. Every result card states how many items were removed and whether the re-scan found any residue.

Are my photos uploaded to a server?

No. Reading metadata, re-encoding and the re-scan all happen inside this device's browser - no network request carries the image, and photos are never written to local storage. Only your output format and quality preferences are kept in this browser so the page opens the way you left it. The Clear my data link in the footer removes them.

Related tools