What this tool removes
The browser inspects supported JPEG, PNG, and WebP structures for recognized EXIF/GPS, XMP, IPTC, and descriptive text groups. It reports what it recognized before generating a new image.
Why the image is re-encoded
The clean copy is produced from decoded pixels rather than by copying the original metadata container. This prevents recognized metadata from being carried over, but it can change compression and embedded color-profile behavior. Keep the original when exact archival bytes matter.
Privacy and limits
Inspection and re-encoding happen locally. Unsupported or incompletely inspected structures fail instead of being reported as clean. The result is checked again for recognized metadata before its download button is shown.
This version supports standard static JPEG, PNG and WebP containers. It scans JPEG through all scans to the end marker, checks PNG chunk checksums through IEND, and checks WebP container lengths and padding. Unknown application segments or chunks, trailing bytes and incomplete containers are rejected. PNG text chunks, including compressed text, are removed as whole containers; their private field values are not displayed.
Displayed EXIF orientation is applied before re-encoding. JPEG and WebP may lose quality. PNG retains transparency; JPEG uses a white background. Embedded color profiles and higher bit-depth color may change, so keep the original when color fidelity matters.
Choose the output format before export. Browsers without WebP encoding support can still read a WebP input and create a cleaned PNG or JPEG. Native encoders may add metadata of their own; recognized metadata containers are stripped from that encoded result before the final check.