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.
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 | O | O | Lossy output at the selected quality |
| PNG | O | O | PNG output; browser processing can still change bytes/profile behavior |
| WebP | Feature-detected | Feature-detected | Lossy output at the selected quality |
| HEIC/HEIF | O | O | Decoded locally and cleaned to JPEG |
| GIF/AVIF/TIFF | X | X | Rejected rather than silently converted |
Recorded results from MetaRinse test fixtures
These are results from small, project-owned files generated for MetaRinse rather than estimates or examples copied from another service. The fixtures are intentionally tiny so the full inspect, clean, download, and re-inspect flow can run repeatedly in automated browser tests.
| Fixture | Original scan | Cleaned-file check | Pixel property checked |
|---|---|---|---|
| JPEG · 32 × 24 · 1,175 bytes | 21 readable fields; 14 private or descriptive fields, including 7 location and 4 device fields | 0 private or descriptive fields detected | 32 × 24 output; displayed orientation preserved |
| PNG · 24 × 18 · 1,121 bytes | 9 readable fields; Author and Comment were the 2 private or descriptive fields | 0 private or descriptive fields detected | 24 × 18 output; translucent and opaque alpha samples preserved |
| WebP · 4 × 3 · 468 bytes | 5 private or descriptive fields: 2 device, 1 creator, and 2 description fields | 0 private or descriptive fields detected when the browser supports WebP encoding | 4 × 3 output; sampled alpha preserved |
Evidence reviewed 2026-07-26. Input byte counts are fixed fixture properties; output byte counts are intentionally omitted because browser encoders can differ.
A zero in the cleaned-file column means the configured scanner found no supported private or descriptive field. It is not a forensic guarantee.
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-26 | 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-26 | 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-26 | 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-26 | 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 |
The results above use Playwright-bundled browser engines. Behavior can differ in installed stable browsers, real devices, and assistive technologies.
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
Your image never leaves your device.