MetaRinse guide

JPEG, PNG, and WebP metadata compared

The three containers store pixels and metadata differently. Browser re-encoding can remove readable fields, but it can also change compression, color handling, and file size.

JS YOO · 8 min · Published 2026-07-12 · last reviewed 2026-07-12 · reviewed by JS YOO

Containers are not interchangeable

JPEG commonly carries EXIF APP segments, XMP, IPTC-style data, and ICC profiles. PNG uses chunks, including textual and color-related chunks. WebP uses a RIFF container that can include EXIF, XMP, and ICC chunks. “EXIF remover” is therefore too narrow a description for a multi-format cleaner.

MetaRinse support matrix

Format	Inspect	Clean	Pixel encoding
JPEG/JPG	Yes	Yes	Lossy output at the selected quality
PNG	Yes	Yes	PNG output; browser processing can still change bytes/profile behavior
WebP	Feature-detected	Feature-detected	Lossy output at the selected quality
GIF/HEIC/AVIF/TIFF	No	No	Rejected rather than silently converted

Why file size changes

The original encoder may have used different quantization, filtering, chroma subsampling, lossless parameters, or optimization. Canvas encoding is browser-controlled. Removing metadata can reduce size while re-encoding can increase it; either outcome is possible, and size is not a verification signal.

Dated browser test note

Date	Automated environment	Coverage
2026-07-12	Chromium 149.0.7827.55 · Playwright 1.61.1 · Windows 11 10.0.26200	Fixture upload, inspection, cleaning, download, output re-parse, accessibility, and no-upload checks
2026-07-12	Firefox 151.0 · Playwright 1.61.1 · Windows 11 10.0.26200	Fixture upload, inspection, cleaning, download, output re-parse, accessibility, and no-upload checks
2026-07-12	WebKit 26.5 · Playwright 1.61.1 · Windows 11 10.0.26200	Fixture upload, inspection, cleaning, download, output re-parse, accessibility, and no-upload checks
2026-07-12	Mobile Chromium 149.0.7827.55 · Pixel 7 emulation · Playwright 1.61.1 · Windows 11 10.0.26200	Fixture upload, inspection, cleaning, download, output re-parse, accessibility, and no-upload checks
Required before launch	Current stable Safari, Chrome, Edge, Firefox, and assistive technology	Manual real-device results are not yet recorded and must be completed on the production domain

These are Playwright-bundled browser engines, not recorded manual results from installed stable Safari, Chrome, or Edge.

Color and transparency limits

PNG and WebP transparency is kept by using an alpha-capable canvas. JPEG has no alpha channel. Embedded color profiles may not survive browser decode and re-encode, so color-managed workflows should compare the output visually and retain the original.

Practical takeaway

Use the same output format, compare dimensions and orientation, inspect the result, and expect binary bytes and file size to change.

Sources

Related guides

Ready to inspect your own file?

Your image never leaves your device.

Clean images