Shrink WebP files while keeping them as WebP: smaller pages, faster loads, and no format change to manage. Transparency stays intact; an animated WebP is declined rather than flattened to one frame. Part of the image compressor.
Output format
– / –
Drop images or browse
JPEG · PNG · WEBP · AVIF · HEIC · up to 50 at once · max 30 MB each
A real result from this exact operation: 69.5 KB in, 18.6 KB out. Drop your own file and the meter reports yours.
What a WebP compressor does, and when it has nothing to do
A WebP compressor re-encodes a WebP at a lower quality than it was saved at, keeping the format, the pixels and the transparency, and dropping the bytes the eye does not use. A WebP exported by a design tool at quality 90 or 100 carries far more data than a page needs; one already encoded near quality 80 is close to the floor. That is why the answer is measured per file and printed beside it, and why a file that would grow comes back untouched instead of larger.
Compress a WebP image, measured: every setting on one file
Reference file611.2 KBphoto.webp
Setting
Relative to source
Size
vs original
AutoOur default
212.6 KB
−65%
Quality 80
260 KB
−57%
Quality 60
183.3 KB
−70%
Max file size 100 KB
98.4 KB
−84%
Quality 100 (lossless): the original returnedNo saving
611.2 KB
0%
AVIF, Auto (converted, for comparison)Other format
123.9 KB
−80%
Source: photo.webp, 611.2 KB, our reference photo of an iguana on a branch, saved as WebP at quality 95. Every row is the file the engine wrote from that one WebP.
Every byte count is the size of the actual file our engine produced from the named source, the same bytes you would download, not an estimate. The reference photo is one of our own photographs, an iguana on a branch, and the camera photo is a real one too. Drop your own file into the tool above to rerun any of them. How we measure names the sources and the settings.
The quality-80 knee: one number that saves most mistakes
WebP's quality scale has a knee near 80. Below it the file shrinks fast and the picture holds; above it the bytes climb and the picture does not visibly improve. Measured here: quality 60 is 183.3 KB, quality 80 is 260 KB, and quality 100 asks for lossless, which would inflate a lossy source, so the tool returns the 611.2 KB original. Auto stays near the knee per image, and the compare slider is there so your eyes make the call.
Compress a WebP to a size a form demands
Upload forms do not ask for "quality 80"; they ask for "under 100 KB". Set Max file size in Advanced settings and the encoder searches for the highest quality that fits under the number, never over: 98.4 KB against a 100 KB cap on our reference. The compress image to 100 KB page opens with that cap armed for any format; the tool above does the same for WebP.
Compress the WebP, or convert it to AVIF?
For a site you control, convert: the same file as AVIF is 123.9 KB against 212.6 KB as compressed WebP, and about 95% of browsers render it, with the WebP as the fallback. Compress and stay WebP when a theme, a CMS field or a CDN expects a .webp, or when 97% support is the number you were given. One click either way: WebP to AVIF is the same engine, and the WebP converter has every other exit.
Transparency, animation, and what we refuse to fake
The alpha channel survives compression; a transparent logo comes out transparent, and the compare slider's checkerboard proves it. An animated WebP is a different thing: a re-encode that kept only the first frame would report a huge saving and destroy the animation, so we decline animated files with a clear message instead. For a still, the compressor keeps everything but the bytes you cannot see.
When not to compress a WebP
It is a lossless master or a design export?
Keep it as the source and compress copies. A lossy re-encode is a one-way street.
It is already small?
A WebP encoded near quality 80 has little left to give. If the meter shows a few kilobytes, leave it; our guard returns the original rather than a larger file.
It is animated?
We decline rather than flatten it to one frame. Keep the animation as it is, or compress it in a video tool.
Questions, answered
Short answers specific to this page. The tool above settles most of them in a second.
Q:How much smaller will my WebP get?
It depends on how it was saved. Our 611.2 KB reference WebP, exported at a high quality, came back 212.6 KB at Auto quality, −65%, with no visible change. A WebP that was already encoded near quality 80 gains far less, and one below it may gain nothing; the meter beside each file reports the real number.
Q:Should I compress a WebP or convert it to AVIF?
For the smallest file, convert it: our 611.2 KB reference WebP became a 123.9 KB AVIF at Auto, against 212.6 KB compressed as a WebP. Keep it a WebP when the app, site or person you send it to does not take AVIF yet. The converter does either in one drop.
Q:Does compressing a WebP lose quality?
A lossy re-encode always costs something in theory; at Auto quality the difference is invisible at normal viewing size. The compare slider shows your own file before and after at 100% zoom, with the two sizes pinned to it, so you decide with your eyes rather than a number.
Q:What WebP quality setting should I use?
80 is the knee. Measured on our reference file: quality 60 gave 183.3 KB, quality 80 gave 260 KB, Auto 212.6 KB. Above 80 the bytes climb and the picture does not visibly improve; below 60 the picture starts to give. Auto lands near the knee per image.
Q:Can I compress a WebP losslessly?
Quality 100 asks for the lightest lossy setting WebP has, not lossless WebP, which we do not write. On a lossy-encoded source that grows the file, so the tool hands your original back untouched rather than inflate it: 611.2 KB in, 611.2 KB out on our reference. Real savings come from lossy re-encoding at Auto or a chosen quality.
Q:Does compressing keep transparency?
Yes. The output stays WebP, so the alpha channel is preserved; a transparent logo comes out transparent, which the compare slider shows on its checkerboard. An animated WebP is declined with a clear message rather than silently flattened to its first frame.
Q:How do I get a WebP under a size limit?
Set Max file size in Advanced settings. The encoder searches for the highest quality that fits under the cap and never overshoots: our 611.2 KB reference landed at 98.4 KB against a 100 KB cap. If a cap is impossible at the image's dimensions, the tool says so instead of shipping an oversized file.
Q:Should I compress the WebP or convert it to AVIF?
For a site you control, convert: the same file as AVIF is 123.9 KB against 212.6 KB as compressed WebP, and 95% of browsers render AVIF. Compress and stay WebP when a CMS, a theme or a CDN expects WebP, or when the file must keep its extension.
Q:Can I compress the same WebP twice?
You can, and the second pass gains little. Re-encoding at the same quality changes the file by a few kilobytes at most; each pass at a lower quality costs a little more detail. Keep one original, compress once per destination, and never treat a compressed file as the new master.
Q:Why did my WebP get bigger after compressing elsewhere?
Because the tool asked for a higher quality than the file already had, or switched a lossy file to lossless. Re-encoding a quality-70 WebP at quality 95 inflates it. Here, if a same-format compression would grow your file, we return the original and say so.
Q:Can I compress many WebP files at once?
Yes. Up to 50 files a batch, 30 MB each, one ZIP with the filenames kept, no signup and a 300-image daily allowance. Each row shows its own measured before and after size, so you can spot the file that barely moved.
Q:Is it safe to upload my images here?
Yes. We keep nothing: files are processed and wiped automatically, never archived, never shared, never used to train anything. No account is needed, and metadata is stripped from every output by default.
