Free plan: 1 conversion/hour, 1 file at a time
Go Unlimited →

Compress WebP

Free Online WebP Compressor

Indicate your files

*Files deleted after 24 hours

Convert up to 1 GB files free, Pro users can convert up to 100 GB files; Sign up now

Uploading

0%

How to Compress WebP

1 Drop your WebP images into the box above, or pick them from your device — there is nothing to install and no account to create.
2 Choose how hard to squeeze: a quality or bitrate target, and optionally smaller dimensions if size matters more to you than detail.
3 Start the job and let the workers re-pack the file; your original is never modified in place.
4 Compare the new size against the original, then download the compressed WebP file.

Compress WebP FAQ

How does Compress WebP actually make the file smaller?
+
Concretely, the encoder re-runs the DCT quantiser at the quality factor you choose, so the saving comes from coarser coefficients rather than from fewer pixels — the dimensions of the picture never change, and quality 80 is the usual sweet spot. Nothing about it depends on you installing software: the job runs server-side and hands back a finished file.
That is decided by the content, not by the tool. Photographic detail, film grain and sensor noise resist compression; flat colour, large uniform areas, line art and text collapse. Expect a dramatic reduction on a screenshot or a logo and a modest one on a busy photograph.
Very much so. WebP carries both a lossy VP8 mode and a lossless mode plus full alpha, typically landing 25-35% under a JPG of matching visual quality. That determines both the headroom available and whether the saving costs you anything in fidelity.
Yes — the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension. It is worth knowing before you overwrite an original you might need again.
Compressing the same file repeatedly. Each pass on a lossy format is a fresh generation of loss and the savings shrink while the damage accumulates. Go from the original to your target in one step, and keep the original.
A single compressed file per input, at a quality level you choose rather than a fixed default. If the result is still not small enough, reducing the pixel dimensions will do more for it than pushing the quality slider further down.
Anything in the lossy raster family — JPG, JPEG, JFIF and WebP — plus the lossless formats (PNG, BMP, TIFF) if you want to mix them in one batch. The format is read from the file header, not the extension, so a photo saved with the wrong suffix still goes through.
Yes: free accounts process images up to 25 MB each, which covers essentially every camera JPG and phone photo; the work is done by libjpeg-turbo and libwebp, the same libraries a desktop editor links against. Larger files are the one thing the free tier will stop you on, and the limit is per file rather than per batch.
A lossy source is already the result of one quantisation pass, and any operation that has to re-encode adds a second. Where the job can be done without touching the pixel data we do that instead, and where it cannot you choose the quality factor yourself rather than getting a fixed default.
Yes. Drop the whole set into the upload area and they queue in parallel with identical settings — that is the main reason to do this in a browser rather than one file at a time in an editor. Free accounts run one file per batch; a pass lifts that.
Camera EXIF (ISO, shutter, lens, GPS) and the embedded ICC profile are carried across by default, because dropping the profile is what makes colours shift on re-import. Use the privacy option to strip metadata before download if you are about to publish the file.
No. Compress WebP is free with no account, no watermark on the output and no signup wall in front of the download. Uploads are deleted automatically a short time after the job finishes.

Rate this editor

5.0/5 - 0 votes
ns6.com — Free WHOIS privacy, DNS and SSL on every domain.
Or plop your files here