Why compress a WebP you already have
WebP is efficient, but efficient is not the same as optimized. A WebP exported from a design tool, a camera app, or a bulk converter is often saved at quality 90 or higher — safe, but heavier than it needs to be. If those files are going onto a web page, into an email, or through an app with an upload cap, there is usually room to cut them down further with no visible cost.
The lever is simple: quality. A WebP saved at 90 and one saved at 75 look the same to a human eye on most photos, but the second can be a third smaller. Compressing means re-encoding at a setting that fits where the image is actually going, instead of the conservative default it came with.
This is different from converting. You are not changing the format — the file stays WebP, so it keeps WebP's transparency support and its modern compression. You are just asking it to do that compression harder. If instead you need a different format for compatibility, look at WebP to PNG or WebP to JPG.
Compress WebP in three steps
- Drop your WebP files inOne or a whole folder. They load instantly — no upload, so nothing sits in a queue.
- Lower the qualityKeep WebP as the output and drag the slider down. Watch the saved-size number update as you go, and stop where the preview still looks right.
- Download the smaller filesTake one, or export the batch as a ZIP. Filenames stay the same.
What changes, what doesn't
| Before | After compressing | |
|---|---|---|
| Format | WebP | Still WebP |
| Transparency | Preserved | Preserved |
| File size | Heavier | Often 30–60% smaller |
| Visible quality | — | Unchanged at 70–80 |
The format, the transparency, and the way the image looks all stay put. The only thing that moves is the number of bytes — which is the whole point.
Compressed on your device
Every file is re-encoded in your browser with the libwebp encoder compiled to WebAssembly. Nothing is uploaded, so there is no server holding a copy and nothing that can be exposed later. It's the right default for client work and unreleased assets, and it means the only limit on how many files you push through is your own machine — not somebody else's bandwidth.
More tools
Questions
How do I make a WebP smaller?
Re-encode it at a lower quality. Keep the format as WebP and drag the quality slider down — 90 to 75 often cuts size sharply with no visible change.
Does compressing hurt quality?
Lossy compression trades a little detail for a smaller file. At 70–80 it's invisible for most images. Use lossless mode when nothing can be lost.
Can I do a whole batch?
Yes. Drop the set and download a ZIP. The free tier handles 20 files at once; Pro removes the limit.
Is anything uploaded?
No. Compression runs in your browser via WebAssembly. Your files never leave your device.