Is the WebP optimizer free?
Yes. The WebP Optimizer is completely free and runs entirely in your browser with no sign-up or upload.
Does my file leave the browser?
No. Optimization runs locally in your browser, so the WebP stays on your device and is never uploaded to a server.
Does it work on animated WebP too?
Yes. The optimizer accepts both still and animated WebP files and exports a lighter WebP result locally.
Should I use this instead of the quality recompressor?
Usually yes. This page is for fast preset-driven optimization. The WebP Quality Recompressor is for still WebP when you want tighter manual quality control.
Does it work on mobile?
Yes. The optimizer runs in the browser, so you can compress WebP files on a phone or tablet with the file staying on your device.
How do I compress a WebP file?
Open it here and export. For a still image the tool runs a quality-first recompression; for an animated WebP you also get an FPS cap and a color count hint, because animation size is dominated by frames, not by pixels.
How do I compress an animated WebP?
Cap the frame rate first. Animated WebP stores every frame, so bringing a 30 fps capture down to 12 or 20 fps removes a large share of the file and is hard to see on a UI recording. Only then reduce the color count, and only if the animation is flat-color.
Is WebP smaller than PNG and JPG?
Usually, yes, and it keeps a real alpha channel, which JPG cannot. That combination, transparency plus small files, is the reason to stay in WebP rather than converting to JPG for size.
Should I use this or the WebP Quality Recompressor?
Use this one to make a file smaller with sensible presets, including animation. Use the Quality Recompressor when you want to set the exact quality value yourself and compare the result.
Does optimizing a WebP twice make it smaller?
It makes it worse. WebP is lossy, so a second pass costs quality for very little size. Always go back to the original source rather than re-compressing an export.