Re-optimize WebP files that were saved too large — same format, lower quality setting, much smaller file. Everything runs locally in your browser.
The converter
Drop in one image or a whole batch. Everything is converted on your device — no upload, no wait.
How it works
Re-optimize one WebP or a whole batch without any uploads.
01
Pick a file or drag it straight in — drop in any .webp file, transparent ones included.
02
Slide between smaller and sharper. 80 is a great default for most photos.
03
It saves straight to your device the moment it’s ready — no upload, no waiting.
Why re-optimize
Learn
WebP earned its reputation as the small format, but the format cannot save you from a bad quality setting. Export tools and converters that default to quality 95–100 produce WebP files bigger than a sensible JPG. If a "small" WebP is weighing megabytes, its quality setting is almost certainly the culprit.
Re-encoding at 75–80 restores the size advantage WebP is supposed to deliver — commonly 30–60% smaller than the over-saved original with no visible change.
Keep it WebP when the image lives on the web: every modern browser renders it, and it stays the most efficient widely-supported choice. Convert to JPG or PNG instead when the file needs to open in older software or an upload form that rejects WebP — the switcher above takes you straight there.
FAQ
Many tools export WebP at quality 95+ “to be safe”, which doubles or triples the size for no visible gain. Re-encoding at 75–80 restores the size advantage.
Yes — the alpha channel is preserved through re-encoding.
The first frame is re-encoded as a still. Animated WebP optimization is on the roadmap.
No. Decode and re-encode both happen in your browser via the Canvas API.
Rule of thumb: a full-screen photo should be 100–400 KB as WebP. If yours is over a megabyte at normal dimensions, re-encoding will reclaim most of it.
This tool re-encodes lossily (that is where savings come from). Lossless WebP optimization is a roadmap item alongside the PNG optimizer.
More tools