## Why compress a format that is already small
WebP’s reputation is “smaller than JPEG,” so people export once and stop. Exports are not automatically good. A lossless WebP of a photograph can be huge. A quality-95 WebP of a 5000-pixel banner is still a lot of bytes. Compress WebP means: decode, encode again with a more aggressive (usually lossy) setting, same format. You keep the pipeline—every
![]()
that already points at .webp still works—and you pick up the savings you thought you had on the first export.
The risk is the same as any lossy recompress. If the WebP was already quality 70, another pass will show it. Always keep the PNG/JPEG/TIFF master and compress from the best parent when you can. Use this tool when the WebP is what you were given.
## Lossy versus lossless WebP
WebP has both modes. Lossless is for UI and some graphics; it will not crush a photo. Lossy is for photographs and rich illustrations. If compression “does nothing,” you may be in lossless mode on a busy image, or the file is already tiny. Try a lower quality, or resize. If a logo suddenly grows mosquito noise, you needed lossless or a PNG.
Alpha should remain for transparent WebP. Check the matte. Animation is a separate profile; this compressor is aimed at stills. An animated WebP may flatten or fail—keep a copy.
## WebP is not the end of the line
If you still need more savings on a photographic hero and you control the HTML, AVIF may beat a third WebP pass. If a destination does not accept WebP, you are in the wrong tool—convert to JPEG. Compression does not change compatibility.
## ToolPin details
Processing is local. Campaign assets stay on the device. 250 MB limit. No signup, no watermark. Metadata is typically stripped on re-encode. That is usually what you want on the public web. Orientation and color go through the canvas: sRGB, 8-bit.
Phones can struggle with large lossless WebP decode. Use desktop for 4K. If encode fails, the browser’s WebP encoder may refuse an unusual profile (stacked, animated, or 10-bit). Re-export a simple still WebP from the source.
## A budget-minded workflow
Set a per-image budget (for example 150 KB for a hero on 3G). Resize to 2× display width. Compress WebP until you meet the budget or quality falls apart. If you cannot meet it, crop, or switch that one asset to AVIF with a WebP fallback. Do not compress every tiny icon—overhead and quality loss are not worth 200 bytes.