Remove EXIF from JPEG, PNG, and WebP on this device.

A measured JPEG, 26 October 2026

On 26 October 2026 this site built one synthetic JPEG with Pillow 10.2.0 at quality 90, 960 by 640 pixels. ExifTool 12.76 then wrote Make CreatorPrivacyKit, Model SyntheticFixture, LensModel FixtureLens, DateTimeOriginal 2026:10:26 12:00:00, Artist CPK Fixture, ImageDescription 2026-10-26 strip fixture, Copyright Fixture only, GPS 35 deg 0' 0.00" N and 139 deg 0' 0.00" E, altitude 12 m above sea level, XMP-dc:Description "synthetic fixture, not a residence", and IPTC Keywords fixture. The coordinates were typed. They are not a residence and they did not come from a GPS receiver. The file was not uploaded.

Four copies of that 157,107-byte file were then processed. ExifTool 12.76 used -overwrite_original -gps:all= on one copy and -overwrite_original -all= on another. mat2 0.13.4 used --inplace on a third copy. The fourth copy was opened in headless Chrome 154.0.8037.92, launched with --no-sandbox and --disable-dev-shm-usage. That run called createImageBitmap, drew the bitmap to a canvas with getContext("2d", { alpha: true }), and saved canvas.toBlob("image/jpeg", 0.95). Those are the JPEG steps in sanitizeImage in metadata-cleaner.js. The bundled function was not called, and the button on this page was not clicked.

Pillow 10.2.0 decoded every file to 960 by 640 RGB, 1,843,200 bytes. The source, the -gps:all= copy, and the -all= copy share decoded-pixel SHA-256 49e03beeb23cf101e13471821cabbd1c8c711f8fb295e41856347279c9fd1c2e. mat2 differs: e0152c412262edc0dcfc31158439b2a2a17f0ba54c7019db126d11e888e4898e. The canvas file differs: 6fdc3430801fe6ffdd0831f4c8f59120d45d73bbacfc4e11b8072c8716ae09cc.

On this file, -gps:all= removed GPS latitude, longitude, altitude, and Composite GPSPosition, and left Make, Model, the date, the XMP description, and the IPTC keyword. -all= left no EXIF, GPS, XMP, IPTC, JFIF, or ICC group in the ExifTool listing. File type and the 960 by 640 size remained, and the decoded pixels still matched the source. The file shrank from 157,107 bytes to 153,592. mat2 also cleared EXIF, GPS, XMP, IPTC, and ICC, left JFIF 1.01, changed the pixels, and shrank the file to 92,212 bytes.

The canvas file grew to 160,408 bytes. Quality 0.95 on a Pillow quality-90 source can do that. EXIF, GPS, XMP, and IPTC were gone. Chrome inserted an sRGB ICC profile whose copyright line reads Google Inc. 2016. The source JPEG had no ICC profile. A claim that this canvas path drops ICC does not hold for this Chrome build.

metadataremover.ai, as read on 26 October 2026, shows one synthetic JPEG: GPS 46.655000, 11.158889 removed, camera Travel Camera MR-1 removed, and time 2026:07:31 06:42:18 removed. The page says Privacy Safe cleanup was checked with that tool and ExifTool, that decoded pixels matched, and that the check date was 2026-10-23. It also describes a 19 September 2026 test of four synthetic 80 by 48 PNGs with ExifTool 13.59. Its FAQ says Privacy Safe and Custom normally remove containers without changing compressed pixels, and that those modes preserve ICC profiles, while Normalize & Strip re-encodes. This page’s cleaner re-encodes JPEG and WebP at quality 0.95. The table above is the measurement those pages do not publish: bytes, file hashes, decoded-pixel hashes, and which tag groups survived four methods. This site did not re-run metadataremover.ai. ExifStrip was not installed, so its output was not re-tested.

metadataremover.ai