A container-aware WebP cleanup
WebP uses a RIFF container with chunks for image data, metadata and optional animation or color profiles. Removing a chunk means the total container size and extended header flags must also be updated.
The cleaner removes XMP, C2PA/JUMBF and other non-display chunks. It keeps supported image, alpha, animation and ICC data. In Privacy clean, EXIF becomes a minimal orientation record when needed; Keep camera EXIF preserves it.
What the verification compares
The verification compares retained media and display data before and after cleanup. Metadata-presence flags are normalized for that comparison because those flags must change when metadata is removed.
Matching hashes establish that this encoded media payload is unchanged. They do not establish that the file has no AI origin, no embedded watermark or no retained EXIF fields in camera mode.
Use the downloaded copy
- Inspect the WebP file and review its removable metadata containers.
- Clean the file and check the matching hashes.
- Download the -clean.webp output and preview it in the intended viewer.
- For animated WebP, check playback as well as the first frame before replacing the source asset.
Common questions
Does this turn WebP into JPEG?
No. The output remains WebP.
Does animated WebP work?
Supported animation chunks are retained. The tool does not re-encode individual frames.
Why are HEIC and AVIF rejected?
They use different container structures. This release does not implement their safe metadata editing and does not silently convert them.
Sources & further reading
Official references for the platform or format behavior discussed above.
Google: WebP container specificationInspect your own file.
Check the containers in your final export, then choose whether to clean a copy.
Open the cleaner