Compress WebP

Yes. Compression runs entirely in your browser on an HTML canvas – the image bytes are never uploaded, cached, or tracked. After the page loads you can disconnect from the network and the tool still works.

Yes, 100% free with no cap on how many images you can compress. No sign-up, no watermark, no hidden file-size limit.

Yes. HTML, CSS, and JavaScript are self-contained. After the first page load you can turn off Wi-Fi and keep recompressing WebPs indefinitely.

WebP is efficient out of the box, but many WebPs are exported at default quality (often 90+) or with suboptimal encoder settings. A recompress at Q75-Q85 frequently shaves 30-60% off the file size with no visible difference on typical viewing sizes.

Yes – the Resize slider scales both axes between 10% and 100% while preserving the aspect ratio. Combined with Quality, one pass can both shrink the pixel count and recompress, which usually beats quality alone.

For web images at 1× viewing, 75-85 is the sweet spot. For large hero images viewed on retina screens, 80-90 is safer. For thumbnails and background decorations, 60-70 is often indistinguishable from the original.

No – this tool accepts WebP only, to keep the UX focused. Use the sibling Compress Image tool for JPG, PNG, or GIF inputs: it has an output-format dropdown that can write WebP.

Yes. Before drawing, the canvas is cleared (not filled), so the alpha channel of your WebP is preserved in the compressed output. Logos, icons, and stickers keep their transparency.

Yes – Chrome, Edge, Firefox, Safari, and Opera have supported WebP for years. Caniuse reports over 97% coverage of global users at the time of writing, so it is production-safe on any modern site.

Lossless re-encode passes 1.0 as the quality to toBlob, telling the browser to skip lossy WebP compression. Some encoders interpret this as a full lossless pass, others as max-quality lossy. Either way, the result is the highest-fidelity WebP the browser can produce from your input.