Pixshrink

Compress WebP Online — 95% Smaller, No Upload

Re-encode or recompress WebP files with libwebp. At the same visible quality, a WebP is typically 25–35% smaller than the equivalent JPEG — and you can push further with a higher-effort encode.

Compress a WebP now How it works
25–35%smaller than same-quality JPEG
libwebpreference encoder
Lossy & losslessmodes supported

Why WebP, and why compress it again?

WebP is Google's modern image format, supported by every major browser since 2020 and now near-universal. It supports lossy (VP8-based), lossless (VP8L), and animation, plus an alpha channel in all modes. Most websites that serve WebP saw a 25–35% bandwidth drop versus serving JPEG, with no measurable change in user-perceived quality.

But not all WebPs are equal. A photo exported from Photoshop with default settings is meaningfully larger than the same photo re-encoded through libwebp at the same SSIM. Pixshrink lets you feed in any WebP — including the bloated ones from image editors — and re-encode it with a configurable quality slider and a higher-effort /pass setting that trades CPU for bytes.

Lossy vs lossless WebP

Lossy WebP uses VP8-style intra-frame prediction and a custom quantizer, which is why it beats JPEG at the same quality. The quality slider runs 0–100; values around 75–80 are visually indistinguishable from the source for most photographs. Lossless WebP (the lossless checkbox) uses predictive transforms plus entropy coding, and is the right choice for screenshots, UI assets, and images with transparency that cannot tolerate any color shift.

For animated WebP, Pixshrink supports a per-frame quality control. Most animations can be cut by 30–50% just by switching the encoder from the default 4 to method 6.

Will it work in every browser?

Yes — Chrome, Edge, Firefox, Safari 14+, and every mobile browser released in the last few years. If you need maximum compatibility (for example, for an email newsletter), the same input can be re-encoded to JPEG or PNG from the same page.

Consider AVIF for even smaller files

WebP is the safe modern default. If you control the destination and the audience, AVIF delivers another 20–30% on top at the same perceptual quality, at the cost of older-browser support. GIF animation is now outperformed by animated WebP on every metric that matters.

Frequently asked questions

Should I use lossy or lossless mode?

Lossy for photos, lossless for screenshots, line art, and assets that other tools will re-encode. The mode is one click away; try both and keep the smaller file that still looks right.

How does WebP compare to JPEG at the same quality?

WebP lossy at the same SSIM2 score is typically 25–35% smaller. For example, a 350 KB JPEG at quality 80 often becomes a 230 KB WebP at quality 80 with no visible difference.

Can I keep transparency?

Yes. Both lossy and lossless WebP support an 8-bit alpha channel, and Pixshrink passes the alpha plane through unchanged. 32-bit RGBA PNGs convert to WebP without compositing artifacts.

Does compression run in the browser?

Yes — libwebp is compiled to WebAssembly. The file is read, encoded, and downloaded with zero network calls. You can confirm this in DevTools → Network.