Compress WEBP — lighter web images, you choose the quality
Drop a WEBP below, adjust the quality slider, and download a lighter version. Everything runs in your browser — no upload, no signup.
Your file is processed entirely in your browser. Nothing is uploaded.
WEBP is already the most efficient image format on the modern web, but that does not mean every WEBP file is as small as it could be. Cameras and tools sometimes export WEBP at quality 90 or above, which is overkill for most web destinations. A website banner at quality 90 might weigh 800 KB; at quality 75, the same banner weighs 300 KB with a quality difference most users cannot detect. Re-encoding at a lower quality is the simplest way to cut the file size and improve page load speed, especially when the WEBP came from a source that defaulted to a higher quality than needed.
This tool uses the HTML5 Canvas API to decode your WEBP and re-encode it at the quality level you choose with the slider. The result is a new WEBP with the same pixel dimensions but fewer bytes. At quality 80, the visual difference from a high-quality original is imperceptible on photographs. At quality 65, some softness appears on sharp edges. At quality 50, artifacts are noticeable but the file is very small. The quality slider lets you experiment in real time, and the result panel shows the exact size savings before you decide to download.
How to compress a WEBP in 4 steps
- 1
Select your WEBP file
Drop the file into the dropzone or click to browse.
- 2
Adjust the quality slider
The default is 85. Lower it for more compression, raise it to preserve detail. The re-encoding runs on slider release.
- 3
Compare the sizes
The result panel shows original size, compressed size, and percentage saved.
- 4
Download the compressed WEBP
Save the lighter WEBP. The original is untouched.
How WEBP quality affects file size
WEBP’s lossy mode uses a compression scheme derived from VP8 video coding. At quality 100, it retains nearly all original detail but produces large files. At quality 80, it discards high-frequency information the eye barely detects, typically producing a file 40 to 60 percent smaller than quality 100. At quality 60, further savings come at the cost of visible softening on text and sharp edges. WEBP’s compression is generally more efficient than JPG at equivalent quality levels, so even a WEBP at quality 80 is typically sharper and smaller than a JPG at quality 80. For web images, quality 75 to 85 is the ideal range.
When should you compress a WEBP?
Reducing hero image weight for Core Web Vitals
A WEBP banner re-encoded from quality 95 to 80 can drop from 800 KB to 250 KB, directly improving LCP.
Shrinking CDN bandwidth on high-traffic sites
Every KB saved on a popular image multiplies across millions of requests. WEBP compression at scale is pure bandwidth savings.
Preparing images for a PWA offline cache
Offline-first apps need lightweight assets. WEBP at quality 75 gives you the best ratio for cache budgets.
Batch-optimizing an image folder before upload
Running each WEBP through this tool at quality 80 before uploading to a CMS can save gigabytes of bandwidth over time.
Frequently asked questions
- What quality should I choose?
- For web use, 75 to 85 is the sweet spot. At 85, quality loss is invisible. At 75, sharp edges may soften slightly. For thumbnails, 60-65 is fine. For high-fidelity archival, stay at 90+.
- Does it preserve transparency?
- No — the Canvas toBlob WEBP encoder in most browsers does not support lossy WEBP with alpha. If your WEBP has transparency, the background may be filled white. For transparent WEBPs, convert to PNG instead.
- Can re-encoding a WEBP make it larger?
- Only if you encode at a higher quality than the source. If the source is quality 80 and you encode at 90, the file grows. At the same or lower quality, it will be the same size or smaller.
- Does it strip EXIF metadata?
- Yes. Canvas re-encoding removes all metadata, including EXIF, ICC profiles, and XMP. If metadata matters, use a metadata-preserving tool.
- Is my WEBP uploaded?
- No. The Canvas API handles everything locally. No file leaves your browser.