What happens when you compress a WebP file
WebP was designed by Google to replace both JPG and PNG on the web, and it does that job well: a WebP image is usually smaller than an equivalent JPG, and it supports transparency, which JPG does not. The catch is that WebP is not a format most people create on purpose — it arrives from a download, an exporter, or a site that converted your upload behind the scenes.
Compressing a WebP here means re-encoding it at a lower quality setting, and reducing its pixel dimensions when the file has to meet a size limit. It stays a WebP, so browsers keep the smaller-file advantage.
How to compress WebP images
- Add the files. Drag them onto the box or pick them with the file chooser. 20 per batch, up to 20 MB each.
- Choose the target. Automatic makes the file smaller while keeping it visually clean. Pick a fixed size when a form or a platform imposes one.
- Download. Each row shows before, after and the percentage saved — single files or the whole batch as a ZIP.
WebP, JPG and PNG: which should you end up with
| Your goal | Format to use |
|---|---|
| Smallest file for a photo on a web page | WebP, with JPG as the fallback for very old software |
| Maximum compatibility — email, Word documents, printing | JPG |
| Transparency, sharp edges, screenshots of text | PNG or WebP, never JPG |
| An upload form that lists “JPG or PNG only” | Convert away from WebP; the form will reject it |
That last row is the most common reason people arrive here looking for a WebP compressor in the first place. Plenty of portals still validate file extensions, and a perfectly good 80 KB WebP will be refused where a 300 KB JPG is accepted.
This compressor keeps the output as WebP when the input is WebP, because silently changing the format is the kind of surprise that breaks a workflow. If the destination demands JPG, use the JPEG compressor on a converted copy instead, so you can see the result before you send it.
What you gain, and what you do not
A WebP that was already optimised by the site that served it has little left to give. A WebP exported from a design tool at a high quality setting often has a lot to give. The measured percentage in each row is the honest answer for your file, and it will not be the same for the next one.
Two things worth knowing before you replace anything:
- Animation. An animated WebP is treated as a still image by canvas-based compressors, so only the first frame survives. Do not compress animated files here.
- Transparency. WebP supports it, and it is preserved when the output stays WebP. If you convert to JPG elsewhere, transparent areas become white.
No upload, no queue
The file is decoded and re-encoded inside your browser tab. Nothing is sent to a server, which also means no waiting for a 10 MB file to travel and come back, and no daily cap on how many images you can process.
Frequently asked questions
Does compressing WebP reduce quality?
Yes, if the quality setting is lowered or the dimensions are reduced. The row for each file tells you the size before and after; check the downloaded copy before deleting the original.
Will the file stay WebP?
Yes. WebP input produces WebP output, so the browser compatibility and size advantages stay intact.
Can I convert WebP to JPG here?
Not on this page — it keeps the format. Use a converter for that, then compress the JPG if it is still too large.
Are animated WebP files supported?
No. Animation is not preserved, so only the first frame would survive. Keep animated files out of the batch.
How many files per batch?
20 files, up to 20 MB each, with no daily limit.