Breezo

Compress WebP

Already the efficient format — squeeze it further.

Nothing is uploaded

Drop files here, or click to choose

Accepts WebP. No size limit, no sign-up.

    WebP is already more efficient than JPEG or PNG, but files exported at a high quality setting still have plenty of room. This compresses them further, on your own machine, with the alpha channel intact.

    Transparency survives, which is the point

    Compressing a transparent image usually means choosing between keeping the alpha channel and getting a small file. WebP is the format where you do not have to choose: it carries alpha in both its lossy and lossless modes.

    The alpha channel is compressed losslessly even when the colour data is compressed hard, so cut-out edges stay clean while the file still shrinks meaningfully. That is why WebP displaced PNG for so many logos, icons and product images on the web.

    Where the savings are largest

    WebP's advantage over older formats grows as quality rises and as the image gets flatter. Measured against JPEG on the same content: on a photograph WebP was 32% smaller at quality 70, while on a flat-colour graphic it was 63% smaller at quality 90.

    That means a WebP exported at a high quality setting from a design tool is often carrying far more data than it needs. Bringing it down to somewhere in the high seventies typically removes a large share of the file with no visible change.

    It is still a re-encode

    If your WebP was created in lossy mode, recompressing it discards detail a second time. The same rule as JPEG applies: do it once, at the lowest quality you find acceptable, rather than repeatedly shaving the slider down.

    If your WebP was created in lossless mode, this tool converts it to lossy WebP. That is usually the intent when someone asks to compress a WebP, but it is worth knowing that the result is no longer pixel-exact.

    No upload, therefore no ceiling

    Your browser decodes WebP natively, and the encoder is a WebAssembly build of the reference implementation. Both run in this tab.

    There is no size limit, no queue, no hourly quota, no watermark and no account, because your conversions consume none of our resources. Verify it in the DevTools Network tab while compressing.

    Measured: flat-colour graphic, 1600×1000

    Few colours, hard edges, transparent background.

    QualityJPEGWebPWebP vs JPEG
    4023.9 KB21.2 KB-11%
    5026.7 KB22.1 KB-17%
    6029.7 KB22.9 KB-23%
    7033.8 KB23.8 KB-30%
    7536.8 KB24.2 KB-34%
    8041.1 KB25.7 KB-38%
    8546.0 KB27.5 KB-40%
    9083.0 KB30.4 KB-63%
    95106.2 KB36.6 KB-66%
    Source PNG46.2 KB
    Optimised PNG (lossless)40.6 KB

    Measured in Chromium with the same WebAssembly encoders this site ships. Your results will differ with your own images — the point is the shape of the curve, not the exact bytes. Measured: 2026-08-08

    Frequently asked questions

    Does compressing keep the transparent background?

    Yes. WebP supports an alpha channel in lossy mode, and the alpha data itself is compressed losslessly, so cut-out edges stay clean.

    What quality should I use?

    The default 78 works well for most images. WebP holds up better at lower settings than JPEG does, so you can often go further down than you would expect.

    My WebP was lossless. What happens?

    It is re-encoded as lossy WebP, so the result is no longer pixel-exact. That is usually what is wanted, but it is worth knowing before you replace the original.

    Can I compress the same file repeatedly?

    You can, but each pass discards more detail. Compress once at the lowest quality you find acceptable.

    Is the file uploaded?

    No. Decoding and encoding both happen inside your browser tab.

    Other tools