100% local · no uploads · free

WebP Compressor

Compressing WebP is not the same job as compressing any other format, because WebP stores its data differently. Understanding what the encoder is actually doing is the difference between hitting a size target cleanly and mangling an image.

A WebP compressor has a choice the others do not, because WebP offers both modes properly. Lossy WebP typically produces files around thirty percent smaller than JPG at matching visual quality, and lossless WebP usually beats PNG by twenty to thirty percent while preserving every pixel exactly.

That makes the choice of mode the important decision rather than an afterthought. Photographs belong in lossy mode. Screenshots, logos and anything with flat colour or sharp text belong in lossless, where JPG-style artefacts around edges would otherwise be visible.

WebP also carries a full alpha channel in both modes, so transparency survives compression. This is the main practical reason to prefer it over JPG for logos and interface assets that need to sit on a coloured background.

Everything runs in this browser tab. Add one file or several hundred, set a target size or a quality level, and the results come back without anything being uploaded.

Open the WebP compressor →

Files never leave your device
No size limits
Free, no sign-up

Frequently asked questions

How much can a WebP file realistically shrink?

It depends heavily on content and starting quality. Photographs saved at high quality often halve. Images already compressed hard have much less left to give, and pushing further shows visible artefacts.

Will compressing degrade my WebP images?

At sensible quality settings the difference is not visible at normal viewing size. Pushing towards very small targets does show, particularly on flat colour and around text, which is why the result is shown before you save it.

Can I compress a whole folder at once?

Yes. Add as many files as you like and each is compressed independently to the same setting, then returned as a single ZIP. Processing happens on your device, so there is no upload queue and no file count limit.

Are my images uploaded anywhere?

No. The encoder runs in your browser as WebAssembly and the images never leave your device. You can confirm this in the Network tab of your developer tools while a batch is running.