PNG to WebP — Free

Drop the PNG above and press Convert — the WebP downloads immediately. There is no account, no batch limit and no watermark, and the file is never uploaded, since conversion happens entirely in your browser.

Yes. WebP has a full alpha channel, so transparent areas stay transparent and soft anti-aliased edges keep their partial transparency. This is the main difference from converting a PNG to JPG, where transparency cannot be stored at all and has to be filled with a background colour. Because of that, there is no background colour control on this page — nothing needs filling.

It depends enormously on what the PNG contains. Photographs and screenshots saved as PNG often shrink by 70–90%, because PNG stores every pixel exactly and is a poor fit for photographic detail in the first place. Flat graphics, logos and line art with few colours are already efficient as PNG, so the saving there is much smaller and sometimes near zero. Each file reports its actual before-and-after size, so you can see which case you are in.

Yes, and this is worth being clear about because it runs the opposite way to most conversions. PNG is lossless — it holds the exact pixels. The WebP a browser can produce is lossy, so converting introduces loss where there was none before. At Maximum quality that loss is not visible at normal viewing size, and for a photograph the size saving is well worth it. For a logo with hard edges and flat colour it can be a poor trade, since lossy compression is least flattering to exactly that kind of image.

Not in a browser. WebP does have a genuinely lossless mode, and for graphics it often beats PNG outright — but the canvas API browsers expose only produces the lossy variant, so this tool cannot offer it and does not pretend to. If you need lossless WebP, a desktop encoder such as cwebp with its lossless flag will do it. For photographs the lossy mode is what you want anyway.

Compare before committing. A small PNG logo is often already tiny, and lossy WebP can add faint artefacts around the sharp edges and flat colour that PNG renders perfectly. Convert one and look at it at full size next to the original. For icons and simple shapes, SVG is usually the better answer than either format, since it stays sharp at any size and is often smaller still.

In browsers, effectively yes — Chrome, Edge, Firefox and Safari have all supported it for years, including its transparency, which is why it is safe to serve on a website today. Outside browsers it is patchier: some older desktop applications and photo utilities do not open it. So WebP is right for images going onto the web, and PNG remains safer for files you are handing to someone else.

Yes. Add as many as you like and they all convert with the same quality and resize settings. The whole set downloads as a single ZIP, and each file also has its own download link if you only want one of them.

Yes. Tick "Limit the longest side" and give a pixel value — anything larger is scaled down proportionally, and anything already smaller is left alone. For a website this is often the bigger win, since serving a 3000-pixel screenshot into a 900-pixel slot wastes far more bytes than the format choice does.

No. Every image is decoded and re-encoded entirely inside your browser. Nothing is transmitted. That makes it safe for anything you would not upload to an unknown server — product artwork before launch, client work, screenshots containing personal details. Once the page has loaded it works offline.

No. The output is your image as a WebP, nothing added. There is no watermark, no badge, and no paid tier that removes one.