Image Metadata Remover
Pick what to strip, download the clean copy, and read a receipt that only lists what a second scan of the exported file could confirm.
- EXIF, GPS, device tags
- Clean: Strippable
- XMP and PNG text chunks
- Clean: Strippable
- Content Credentials (C2PA)
- Clean: Strippable
- Pixel watermarks
- Unknown: Not locally removable
- Verification
- Re-scan of the exported file
- Uploaded
- 0 bytes of your file
How the export works
PNG output is rebuilt chunk by chunk, which keeps the pixels bit-for-bit identical while dropping the text, timestamp and metadata chunks. JPEG, WebP and AVIF have to be re-encoded, so the receipt says so rather than implying the file survived untouched.
Either way the exported file is scanned again before the receipt is written. A category only appears under REMOVED if that second scan confirms it is gone.
GPS is the one people forget
A photo taken on a phone and sent straight from the camera roll can carry the coordinates of the place it was taken. Some platforms strip that on upload and some do not, and the ones that do are inconsistent about it. Stripping locally, before the file leaves your machine, is the only version of this that is under your control.
What the receipt will not say
It will not say the picture is now anonymous. Stripping metadata changes the file, not the pixels. A pixel watermark, if one is present, is still present, and the NOT REMOVED column says so every time.
FAQ
EXIF including camera, GPS and timestamps; XMP including AI DigitalSourceType; PNG tEXt and iTXt chunks including Stable Diffusion prompts; and C2PA Content Credentials manifests.
Pixel-level watermarks, anything embedded in the image content itself, and the visual style of the image. This tool changes the file, not the pixels.
No. Rendering is unchanged. For PNG the pixels are preserved exactly; other formats are re-encoded, and the receipt says which path was used.
Some do, inconsistently. Most strip EXIF, and C2PA is often preserved. Stripping locally is the only way to be sure before the file leaves your device.
No. The file is read as a local Blob and the cleaned copy is generated in the same tab.
Every check runs in your browser: how it works. The limits are written down too: what DetectMark cannot remove.