When to re-encode instead of strip
- The file cannot be cleaned losslessly. Animated images, HDR gain maps and unusual chunks block the lossless path; a fresh encode sidesteps all of them.
- You want new pixels. A 3% shrink at quality 92 changes every pixel value slightly while looking identical. Hash-based matching and C2PA bindings no longer line up.
- You want a different format. Turn a 12 MB PNG into a 900 KB WebP or JPEG for faster uploads.
- You want the rotation baked in. Re-encoding writes upright pixels, so no orientation flag is needed and nothing can misread it.
Choosing a format
Scroll sideways to see all columns →
| Format | Best for | Transparency | Notes |
|---|---|---|---|
| JPEG | Photos, universal compatibility | No, becomes white | Quality 90 to 95 is visually lossless |
| WebP | Smaller files, web and social uploads | Yes | Encoded in the browser; older Safari cannot encode it |
| PNG | Graphics, screenshots, exact colors | Yes | Lossless and larger; quality slider is ignored |
Resize presets
Keep size writes the same dimensions. Shrink 3% is the gentle default: a 4000 pixel photo becomes 3880 pixels, invisible in a feed but enough to produce different pixel data. Fit 2048 and Fit 1080 cap the longest side, which matches what Instagram and most feeds display anyway and keeps uploads quick.
What changes in a re-encoded file
- Colors are converted to sRGB. Wide-gamut originals lose their ICC profile but display the same in browsers.
- Transparency is preserved for WebP and PNG output and flattened onto white for JPEG.
- Lossy formats add a small amount of compression noise. At quality 92 it is not visible at normal viewing sizes.
- The output is inspected again and must show no metadata before the download appears.
Your images are processed inside your browser, with no upload endpoint and no account. Checking, cleaning and converting all happen on your device. Read how your privacy is protected.
Questions people ask
Does a 3% resize remove invisible watermarks?
Usually not. Watermarks such as SynthID are designed to survive resizing and re-compression. Resizing defeats exact hash matching and invalidates C2PA bindings; it is not a watermark remover.
Which quality should I pick?
92 is a safe default for photos. Go to 95 for fine texture, or down to 80 for much smaller files when the image will only be viewed on a phone.
Why is WebP unavailable in my browser?
Encoding happens with the browser’s own canvas encoder. Chrome, Edge and Firefox support WebP output; some Safari versions do not. Pick JPEG or PNG in that case.
Can I convert HEIC files?
Not yet. The parser handles JPEG, PNG and WebP. Export HEIC to JPEG on your phone first, then convert here.