Image Tools
WebP Compressor
Squeeze already-efficient WebP further — re-encode at the quality your use case needs, savings shown per file.
In short
Compress WebP images online: re-encode at lower quality presets and see per-file savings instantly. Batch support, 100% in your browser.
By NaveenKumar T · Updated
Learn: How to Compress Images for the Web (Without Ruining Them)
- Per-image savings shown
- 3 quality presets or a KB target
- Batch compression
Runs entirely in your browser — nothing you paste or open here is uploaded, logged, or stored.How we handle data →
Learn more
Compressing WebP images, explained
WebP is already an efficient format, so compressing WebP is about right-sizing quality rather than fixing waste: a WebP exported at quality 90 for archival can comfortably drop to 70 for web delivery, often halving again. The encoder is libwebp itself — Google's reference WebP encoder, compiled to WebAssembly — so it works in every browser (including Safari, which can't encode WebP natively) and squeezes harder than canvas-based tools. The preset tabs make the quality decision explicit, and each card's before/after readout shows exactly what the drop bought.
Files that arrive already lean will report small savings or 'optimal' — the never-inflate guarantee means you can run anything through without risk. For maximum compression beyond WebP's reach, AVIF is the next step down the size curve (see Related tools).
Picking a quality for WebP specifically
libwebp's quality scale isn't JPEG's. Its own default for web delivery is 75; 85 is visually transparent for almost all photographs, 70 is where careful viewers begin to notice smoothing in fine texture, and 50 shows banding in soft gradients and skies. Typical results: a 400 KB WebP exported at quality 90 lands at 200–240 KB on Balanced; one already at 75 gains almost nothing at High Quality — the card will say 'already optimized' — and 30–40% at Max. Because most WebPs were produced by a build tool or image CDN, the source's setting decides your headroom, and the per-card readout tells you which case each file is.
The encoder is libwebp compiled to WebAssembly — the SIMD build when the browser supports it — so this works in Safari, whose canvas can't write WebP at all. Transparency is decoded and re-encoded intact; EXIF, XMP and ICC metadata are dropped, and wide-gamut sources are converted to sRGB pixels. Outputs are named name-compressed.webp. One caution on workflow: if a site's WebPs come from a pipeline (next/image, imagemin, a CDN), fix the quality setting there rather than post-compressing every deploy; this page is for the one-off batch and for files you received rather than generated. Keep the original master — the PNG or photo the WebP was made from — not the compressed WebP.
Help
Frequently asked questions
Everything you need to know about the WebP Compressor.
01Why does the WebP compressor work in Safari when the WebP converters do not?
Because it does not use the canvas. The converters rely on the browser's own WebP encoder, which Safari lacks; this page runs libwebp itself, compiled to WebAssembly (the SIMD build where supported), so it encodes in every current browser. Transparency is re-encoded intact; EXIF, XMP and ICC metadata are dropped and wide-gamut sources are written as sRGB.
02My WebP barely compressed — why?
WebP sources are usually already export-optimized, so the remaining headroom depends entirely on how high the original quality setting was. Big gains mean the source was conservative; tiny gains mean it was already tight. The card's numbers tell you which case you have, per file.
03Can I compress animated or lossless WebP files?
Animated WebP: no — the decoder reads only the first frame, so the result would be a single still image; keep those files out of the queue. Lossless WebP (the kind exported from PNG-like sources): yes, but the output is lossy at the chosen quality; it will typically be 3–5× smaller with transparency intact, and you lose the lossless guarantee. If the source must stay pixel-exact, leave it alone or run a PNG version through the PNG compressor instead.
Keep working
Related tools
Learn the format
Related guides
How to Compress Images for the Web (Without Ruining Them)
Practical image compression guide: lossy vs lossless, picking the right quality level, why some files won't shrink, and how to compress in your browser.
4 min readGuide · ImagesJPG vs WebP vs AVIF: Which Image Format Should You Use?
JPG, WebP and AVIF compared honestly: file size at equal quality, browser support, transparency and encode speed — plus a simple rule for choosing.
3 min read