Skip to content
ImageConverter

Secure server conversion

Compress WebP

Reduce the file size of a WebP image, free and without an account. Transparency is preserved, and the saving is shown as soon as each file is processed. Worth reading the note below first, though — a WebP is often already compressed well, and this is one conversion that is sometimes not worth doing.

Deleted automatically Uploads removed within 30 minutes

Drag and drop your WEBP images here

Add several at once. Each file is processed and then deleted from our server.

Up to 20 MB per file Batch ready

75
Smaller file More detail
Presets:

Higher keeps more detail; lower makes a smaller file. Applies to images you add after changing it.

Step by step

How to compress WEBP images in 4 steps

  1. Add your WebP files

    Drag them in or click to browse.

  2. Set the quality

    75 is the default. Raise it for graphics and logos, lower it for photographs where size matters more.

  3. Compare the sizes

    Each file reports how much it changed — including when it got larger, which is a useful signal.

  4. Download the ones that actually improved

Good to know

How WEBP compression works

WebP is unusual among image formats in having two entirely separate compression modes, and which one your file uses changes what this tool can do for it.

Lossy WebP works like JPEG but more efficiently, discarding detail to save space. Most WebP images served by websites are lossy.

Lossless WebP preserves every pixel exactly, like PNG, and is typically 20–30% smaller than the equivalent PNG. It is commonly used for logos, icons and screenshots exported from design tools.

This tool re-encodes as lossy WebP, which has two consequences worth knowing:

  • A lossless WebP will usually shrink a lot — you are trading exactness for size, and the trade is often very favourable.
  • An already-lossy WebP may barely shrink, or even grow. It has already had detail removed, and re-encoding cannot remove the same detail twice.

The second case is the one worth being straight about: if a file comes out larger, the honest answer is that it was already well compressed and you should keep the original. A tool that quietly hands you a bigger file and calls it "compressed" is not doing you a favour.

Transparency survives. WebP keeps its alpha channel through lossy compression — a combination no other widely supported format offers — so there is no background colour to choose and no risk of a transparent logo coming back with a white box around it.

Quality

Choosing a compression level

WebP's quality scale behaves differently from JPEG's, and the difference matters most at the top and bottom of the range:

  • 90–95 — Very close to the original. Worth it for logos, icons, screenshots and anything with text or hard edges, which WebP's lossy mode treats less kindly than photographs.
  • 70–89 — The general range. 75 is the default and handles photographs well.
  • 50–69 — Distinctly smaller. Fine for large background images and thumbnails.
  • Below 50 — Flat colour areas start to blotch and soft gradients band into visible steps. Semi-transparent pixels suffer first, so a soft drop shadow is usually the first thing to look wrong.

If your source was lossless, be more generous than you would be with a photograph. Lossless WebP is usually chosen precisely because the image is a graphic, and graphics are what lossy compression handles worst.

If the file will not shrink, reducing the dimensions is the more effective lever. Halving the width and height leaves a quarter of the pixels, which almost always beats pushing the quality down into the range where the image visibly degrades — see the resize tool.

When compressing a WebP is worth doing

  • The file came from a design tool. Exports are frequently lossless or near-lossless, and are far larger than they need to be for the web.
  • You are publishing a lot of images and every kilobyte multiplies across page loads and bandwidth.
  • The image is decorative — a background, a hero image, a card thumbnail — where nobody will inspect it closely.
  • You are hitting an upload limit on a system that accepts WebP.

When to leave it alone

If the WebP was downloaded from a website, it has almost certainly been compressed already — that is why the site was serving WebP. Re-compressing gains little and costs quality.

If the image is a logo, an icon or a screenshot that needs to stay crisp, and it is currently lossless, think carefully. The size saving is real, but so is the softening around edges. Try 90 or above first and compare.

And if you need the file to open in older desktop software rather than a browser, compression is not your problem — converting to JPG or PNG is.

Reading the size change

Each file shows its result as a percentage. Three outcomes, each meaning something different:

  • A large saving — the original was lossless or lightly compressed. This is the case where the tool earns its keep.
  • A small saving — the original was already lossy at a similar quality. Weigh whether a few percent is worth another generation of loss.
  • An increase — the original was compressed harder than the setting you chose. Keep the original; nothing has been gained.

Compressing a batch

Add as many files as you like; each is processed independently with its own download and its own size report. Each file can be up to the size shown on the upload area.

Privacy

What happens to your file

This tool runs on our server, so it works the same on every phone and computer. Your file is uploaded, and this is exactly what happens to it:

  • Stored outside the public web root under a random name, never under your file's name.
  • Processed, with the original upload deleted immediately — whether it succeeded or failed.
  • The result sits behind a signed link that only you receive, which stops working after 20 minutes, and the file is deleted the moment you download it.
  • Anything never collected is deleted automatically within 30 minutes.
  • The image itself is never logged or kept. If a conversion fails, we record the formats involved and the error — not the file.
  • Camera metadata, including any GPS coordinates recording where a photo was taken, is removed from the result. Only the rotation needed to show the image the right way up is kept.

Questions & answers

Compress WebP: frequently asked questions

Does compressing a WebP keep transparency?

Yes. WebP keeps its alpha channel even through lossy compression — a combination no other widely supported format offers. There is no background colour to choose and no risk of a transparent logo coming back inside a white box.

Why did my WebP get bigger instead of smaller?

The original was compressed harder than the quality you selected. Re-encoding cannot remove the same detail twice, so you get a larger file containing a slightly worse picture. Keep the original — that outcome means it was already well compressed.

My WebP came from a website. Is compressing it worth it?

Usually not. Sites serve WebP precisely because it is already compressed, so a second pass gains little and costs quality. Compression is most worthwhile on lossless exports from design tools, which are often far larger than they need to be.

What quality should I use for a logo or screenshot?

90 or above. Lossy compression struggles with flat colour and hard edges, which is exactly what logos, icons and screenshots are made of. The default of 75 is tuned for photographs and will soften graphics noticeably.

Should I compress or resize?

Resize first if the image is larger than it needs to be. File size scales with pixel count, so halving the width and height leaves a quarter of the data — usually a bigger saving than the quality slider, and with no visible cost at the size the image is actually shown.

Are my files uploaded?

Yes. Compression runs on our server so that it works the same on every device. Your upload is deleted the moment the smaller copy is made, that copy is deleted as soon as you download it, and no one looks at your images.

Keep going

View all tools