Core tool
Compress a WebP
Efficient, and still shrinkable.
Squeeze more out of a WebP that was exported at a higher quality than it needed.
Compression
How did this tool do?
Good to know
There is usually still room in a WebP
WebP is already an efficient format — that is normally why a file is in it. Google's own figures put lossy WebP at roughly 25 to 35% smaller than a JPG of comparable quality, which is the reason it became the default export from so many tools. So a WebP that is too large is rarely a format problem; it is a settings problem.
The usual cause is an export preset. Design tools, CMS plugins and "convert to WebP" utilities tend to encode at a quality of 90 or above, well past the point where anyone could see the difference. Bringing that to 75 or 80 commonly takes another third off a file that was already smaller than the JPG it replaced.
Lossy WebP behaves like JPG in the one way that matters here: re-encoding discards detail, and doing it repeatedly compounds the loss. Compress from the best copy you have rather than from a file that has already been through two or three conversion steps, and you will get a visibly better result at the same file size.
WebP also has a lossless mode, which is what most PNG-to-WebP conversions produce. A losslessly encoded WebP full of flat colour and text will not shrink much further without switching it to lossy — worth knowing before you conclude the file is already as small as it goes. If the image is a screenshot or a diagram, try it and use Compare; sharp edges are where lossy encoding shows first.
If you want to go further still, AVIF is typically smaller again at the same visual quality, at the cost of slower encoding and slightly narrower support in older software. For images on a web page that is usually a good trade; for a file you are sending to someone else, WebP remains the safer choice.
Where you'll meet it
Images exported at 90+ quality
The common case — a preset chose a quality nobody can see.
Web pages that are still slow
Converting to WebP was step one; tuning the quality is step two.
Hitting a CMS upload limit
Switch to Target size and type the number it allows.
Related tools
Guide
How to use it
- 01Drop your WebP files, or paste one with Ctrl+V.
- 02Leave the output on WebP and pick a quality — Medium is a good starting point for an over-exported file.
- 03Tap Compress and use Compare, paying attention to edges and text.
- 04Download one file, or all of them as a zip.
Good to know
Questions, answered
Can a WebP be compressed further?
Usually yes, if it was exported at a high quality — which most automatic converters do. If it was encoded losslessly, as PNG-to-WebP conversions generally are, the only way to go much smaller is to switch it to lossy.
Does compressing a WebP lose quality?
Lossy WebP does lose detail when re-encoded, and repeating it compounds the loss. Lossless WebP does not, but also does not shrink much. Compare before downloading and look at edges and lettering first — that is where it shows.
Should I use AVIF instead?
AVIF is typically smaller again at the same visual quality and every current browser reads it, so for images on your own site it is usually a good trade. Encoding is slower, and support outside browsers is patchier, so WebP is safer for files you send to other people.
Will transparency be kept?
Yes. WebP supports full alpha transparency, so a transparent background survives compression. Choosing JPG instead would fill it with white.
Is anything uploaded?
No. The file is decoded and re-encoded in your browser, so it never leaves your device.