Illustration of a PNG image card transforming into a WebP download inside a browser

Image guides

How to Convert PNG to WebP in Your Browser

PNG keeps every pixel exactly and can carry transparency; WebP compresses harder but only if the browser’s encoder is willing to keep the alpha channel intact. This guide covers what happens to both the pixels and the transparency during that re-encode, and when the trade makes sense.

Ready to try the tool this guide describes?

How PNG becomes WebP

  1. The browser decodes the PNG losslessly into a full pixel grid, including its alpha channel if it has one, recovering exactly what was saved originally.
  2. That pixel grid is drawn onto a canvas without any background fill — no white or other color is painted first, so transparent and semi-transparent pixels stay intact going into the next step.
  3. The canvas is encoded as WebP using the browser’s own encoder at your chosen quality setting, which applies WebP’s lossy compression to the color data.
  4. The resulting blob’s MIME type is confirmed as image/webp before the download is offered, so a browser that can’t actually produce WebP won’t hand back a mislabeled file instead.

What changes when you convert

Compression becomes lossy where PNG’s wasn’t. WebP’s encoder makes trade-offs in the color data to shrink the file — even at a high quality setting — so this step is not reversible the way re-saving a PNG is.

Transparency generally survives when the browser’s WebP encoder supports alpha, which current versions do broadly. Unlike JPG output, there’s no white-fill step here — semi-transparent pixels stay semi-transparent rather than blending into a background color.

File size typically shrinks, and WebP is often meaningfully smaller than PNG for photographic content, but that’s not universal — simple graphics with flat colors and few gradients sometimes compress just as well or better under PNG’s lossless scheme.

When WebP is the right choice — and when it isn’t

WebP is worth using for icons, illustrations, and UI graphics with transparency that are headed to a website or app where you want a smaller download — it keeps the alpha channel PNG has while typically compressing further than PNG can.

It’s not the right move if you need to keep editing the image losslessly, since every re-save after converting applies WebP’s lossy compression again. It’s also a weaker choice if the destination doesn’t reliably support WebP — some older software and a handful of platforms still expect PNG specifically.

Limitations and privacy

This conversion depends on the browser actually supporting canvas WebP encoding. Most current browsers do, but when one doesn’t, the tool fails with a clear compatibility message rather than silently saving a different format under a .webp name.

The quality slider (50–100%, default 90%) controls the lossy trade-off; there’s no separate lossless WebP mode in this tool. Everything runs locally — the PNG is decoded, redrawn, and encoded entirely in your browser, with nothing uploaded to a Looty Tools server.

Convert PNG to WebP FAQ

Why doesn’t the WebP output get a white background like some JPG converters use?
WebP supports an alpha channel, so there’s no need to flatten transparency onto a background color the way JPEG requires. The canvas is drawn without any fill, so transparent and semi-transparent PNG pixels carry straight through to the WebP.
Why might a simple graphic not shrink much when converted to WebP?
WebP’s advantage is strongest on photographic, gradient-heavy content. Flat-color graphics like basic icons or logos can already compress efficiently under PNG’s lossless scheme, so the size difference after converting can be small or occasionally reversed.
Is it a problem to keep re-converting the same image to WebP and back?
Each WebP encode is a lossy step, so repeatedly re-saving through WebP will gradually degrade quality, similar to repeatedly re-saving a JPEG. Keep a PNG master if the image needs further editing.
Should I choose WebP or AVIF for a PNG that has transparency?
Both keep alpha channels when the browser supports it, but AVIF encoding support is more limited — it’s currently Chromium-first — while WebP encoding works in a broader range of current browsers. WebP is usually the safer default; AVIF can compress harder if you know your audience’s browsers support it.
Does my PNG leave my device at any point during conversion?
No. Decoding, the alpha-preserving draw step, WebP encoding, and the MIME verification all happen locally in your browser.

Related guides

Open the tool

Jump into PNG to WebP when you are ready to process your files.

← Back to all guides