WebP Compressor
Need to compress WebP images that are still too large? This compressor reduces their size further while keeping them as WebP, with a quality slider tuned to WebP's own compression curve.
Quick answer: Drop in up to 50 WebP files, leave quality at 75 or switch to a target size in KB, and download smaller WebP files one by one or as a ZIP. The output stays WebP, and your browser must be able to create WebP files, which Chrome, Edge and Firefox can.
Drop images here or click to browse
WebP up to 50 MB each
Your images never leave your device
WebP, up to 50 megabytes each Your images never leave your deviceHow to use the WebP Compressor
- Drop in the WebP images you want to shrink.
- Adjust quality, or switch to a target KB.
- Download the smaller WebP file.
Features
- Stays WebP throughout, no format change.
- Quality slider or exact target file size in KB.
- Keeps transparency if the source WebP has it.
- Compress up to 50 WebP files together, then download one ZIP.
Can a WebP file be compressed further?
Yes, especially if it was originally saved at a high quality setting or exported by a tool that did not optimize it well. How much it trims depends on the image and on the quality it started at. The next section has measured figures, 85 percent smaller at this tool's default quality of 75 and 96 percent at quality 50. A WebP that was already saved at a low quality may not shrink at all: when the re-encoded file is not smaller, the tool hands back the original, as it did in Chrome for the same test image saved at quality 50 (36,236 bytes before and after).
Measured with Imagenati: one image as WebP and as JPG
These numbers come from the real WebP Compressor and JPG Compressor pages, run in Chrome 157.0.8103.38 on November 8, 2026, with only the quality slider or the Target size mode changed. The test image is generated, not a camera photo: a 2400 by 1600 pixel scene with a sky gradient, a sun, two hills, a fine line grid and light noise, saved by the browser at quality 92 as a WebP of 886,696 bytes and as a JPG of 899,705 bytes. The WebP encoder is part of the browser, so Firefox or Safari can give somewhat different sizes, and the same drawing saved as a JPG in an earlier session gave 898,991 bytes, about 0.08 percent fewer than here. A real photograph will give its own sizes. The target search tries at most seven qualities and keeps the highest one at or under the target, so the 200 KB row landed at 172 KB. At each tool's default setting the WebP came out at 131,052 bytes and the JPG at 345,977 bytes.
| Tool and setting (quality 1 to 100, or a target size) | Source file size (bytes) | Output size (bytes) | Smaller than the source (percent) |
|---|---|---|---|
| WebP Compressor, quality 75, the tool's default | 886,696 | 131,052 | 85 |
| WebP Compressor, quality 50 | 886,696 | 33,330 | 96 |
| WebP Compressor, target size 200 KB, in the Target size mode | 886,696 | 175,906 | 80 |
| JPG Compressor, quality 90 | 899,705 | 866,794 | 4 |
| JPG Compressor, quality 80, the tool's default | 899,705 | 345,977 | 62 |
| JPG Compressor, quality 70 | 899,705 | 279,850 | 69 |
| JPG Compressor, quality 60 | 899,705 | 172,963 | 81 |
Why is a WebP file already smaller than the same JPG or PNG?
WebP is a newer format built specifically to beat JPEG and PNG at their own jobs: its lossy mode generally produces smaller files than JPEG at an equivalent visible quality, and its lossless mode beats PNG for graphics with flat color and transparency. That head start is exactly why a WebP file that still needs compressing is usually already fairly efficient, so do not expect the same dramatic percentage drop you would see compressing a fresh JPEG straight out of a camera. For one image compared at several settings, the quality guide has a measured JPG example at quality 80, 50 and 20; the WebP figures above follow the same rule, that a lower setting gives a smaller file.
Where does WebP not work well?
A handful of older tools, some email clients and some print workflows still do not accept WebP, which is the main reason to convert back to JPG or PNG rather than a quality reason. Every current browser displays WebP correctly, so this is purely a compatibility question for wherever the file ends up next, not a quality or file size one.
Frequently asked questions
How do I compress a WebP image?
Add the WebP to the box above, then lower the Quality slider or switch the mode to Target size and type the size you need in KB or MB. The results table shows the original size and the new one, and Download saves the compressed WebP, or Download all (ZIP) saves every file you added.
Will this keep transparency in my WebP file?
Yes, the alpha channel is preserved through compression, so transparent areas stay transparent.
How is this different from the general Image Compressor?
This one is locked to WebP in and WebP out, so you cannot accidentally end up with a different format when you specifically need WebP.
Can I target an exact file size?
Yes, switch to target mode and type the KB you need; the tool searches for the highest quality that still fits.
Does compressing a WebP file change it to lossless or lossy?
It stays in lossy mode, the same as most WebP files on the web. The quality slider controls how aggressive that lossy compression is, the same way it does for JPEG.
Will an animated WebP still animate after compressing it?
No, only the first frame is kept. Animated WebP support is a future addition; for now treat this tool as being for static WebP images.
Is there a quality point where WebP stops shrinking further?
Yes, once the quality slider is already low, dropping it further saves less and less file size while losing more visible detail. If a file barely shrinks at a lower setting, its practical floor has likely already been reached.
Last updated .