Convert WebP images to PNG with full transparency preserved. Lossless, batch-capable conversion that runs privately in your browser.
You saved an image from a website, got a .webp, and the program you need to put it into will not take it — a slide deck, an older version of Photoshop, a print template, a product-listing uploader, a company wiki. PNG is the format that everything accepts. More importantly, PNG is the format that keeps transparency, which is the reason to convert to PNG rather than to JPG. If the image is a logo, an icon, a cut-out product shot, or a UI element with soft edges, converting it to JPG will paste a white rectangle behind it. Converting it to PNG will not.
Drop your files on the upload area or click to browse, press Convert All, and download the results. There is nothing to configure, because PNG has nothing to configure: it is a lossless format with no quality dial. Every converted pixel — including every level of partial transparency — is written out exactly as it was decoded.
PNG uses DEFLATE compression, which is entirely reversible: the pixels you put in are bit-for-bit the pixels you get back out. So the WebP → PNG step adds no compression damage at all. That is a real guarantee and it is the main reason to choose this route.
What it does not mean is that a lossy source becomes sharp again. WebP comes in two flavours and they behave very differently here:
| Source | Result in PNG |
|---|---|
| Lossless WebP — typically screenshots, logos, exported graphics, anything with flat colour or text | A genuinely perfect round trip. Every pixel matches the original exactly. Nothing has ever been thrown away, and nothing is thrown away now. |
| Lossy WebP — typically photographs and most images served by websites for speed | Every pixel of the decoded image is preserved exactly, including whatever compression artifacts the WebP encoder already baked in. The PNG is a faithful copy of a damaged image. It cannot be undamaged. |
This is the single most common misunderstanding about converting to a lossless format. Converting a compressed photo to PNG freezes it in place at its current quality; it does not restore detail. What it does buy you is that no further generation of loss happens — which is exactly what you want if the file is about to be cropped, colour-corrected, composited, and re-saved several times.
Convert the file and look at the size change the tool reports next to each result. A lossless WebP of a screenshot usually grows modestly as a PNG, because both formats are doing similar work on the same kind of content. A lossy WebP photo often balloons several times over, because you are taking an image that was compressed with a photographic codec and re-encoding it with a compressor designed for flat colour. A very large jump is a strong signal your source was lossy and photographic — and a signal that PNG may be the wrong destination for it.
WebP supports an 8-bit alpha channel, and so does PNG. Both can represent 256 levels of transparency per pixel, which is what gives you smooth anti-aliased edges on a logo instead of a jagged staircase. This tool preserves that channel: the image is drawn onto a canvas that keeps transparency and written out as a 32-bit RGBA PNG. A logo with a transparent background goes in transparent and comes out transparent, with the soft edge pixels — the ones that are 40% or 70% opaque — still soft.
Two honest caveats about the browser canvas the conversion runs through:
For every ordinary use — a logo for a document, an icon for a deck, a cut-out for a mockup, a UI asset for a designer — the transparency comes through exactly as you would expect.
PNG is not universally better; it is better for a specific class of image. Choose by what is in the picture, not by habit.
| What you are converting | PNG? | Why |
|---|---|---|
| Logo or icon with a transparent background | Yes | Nothing else in wide use keeps the alpha channel. |
| Screenshot of an app, a terminal, an error dialog | Yes | Sharp text and flat colour are exactly what PNG's compression is good at — and what lossy compression smears. |
| Chart, diagram, line art, or an image with text in it | Yes | Crisp edges stay crisp. No ringing halos around the letterforms. |
| Asset you will edit and re-save repeatedly | Yes | Every save is lossless, so ten rounds of editing cost nothing in quality. |
| Photograph you just want to email or upload | Usually no | The PNG can be several times the size for no visible gain. A JPG at high quality is the sensible answer. |
| Image going onto a web page you care about the speed of | Only if it needs transparency | You would be undoing the reason the site served WebP in the first place. |
Lossless compression cannot beat lossy compression on photographic content, and no amount of clever encoding changes that. So expect PNG output to be larger — sometimes much larger — than the WebP that went in. You are buying two specific things with those bytes: an alpha channel, and immunity from further generation loss. If you need neither, you are paying for nothing, and a high-quality JPG is a better destination.
If you do need PNG but the file is uncomfortably large, the fix is to reduce what the image contains rather than to compress it harder. Resize it to the dimensions it will actually be displayed at — halving both dimensions removes three-quarters of the pixels. For flat-colour graphics, running the result through a palette reducer that maps it to 256 colours can shrink it dramatically with no visible change. This tool does neither; it converts, and does it exactly.
.webp. Anything else is ignored.hero-image.webp becomes hero-image.png.Failures are per-file: one bad image marks itself with an error and the rest of the batch carries on. The usual causes are a truncated download (right-click-saved images from a page that was still loading are a classic), a file that has been renamed to .webp but is really something else, or an incomplete cloud sync. Re-download the original and try again. A quick sanity check: a real WebP file starts with the ASCII bytes RIFF, then four size bytes, then WEBP. If a hex viewer shows something else at the front, the extension is lying.
The conversion happens entirely in your browser. Each file is read from disk by the page, decoded by the browser's own WebP decoder, drawn to an in-memory canvas, and encoded to PNG by the browser's encoder. No image data is sent to this site or anywhere else, and there is no server-side copy to expire, leak, or be retained.
You can confirm it rather than take it on trust: open developer tools, watch the Network tab while you convert, and you will see no upload. Once the page has loaded, the tool keeps working with the network disconnected — which is a decent proof in itself. There is no account, no queue, no daily cap, and no watermark, because there is no server doing the work that would need to charge you for it.
This is the difference that matters if the images are internal screenshots, unreleased design assets, client artwork, or anything covered by an NDA. The common alternative — a converter that uploads to a processing server — means handing that material to a third party and trusting a deletion policy. Here there is no transfer to trust.
WebP exists to make pages load faster: it compresses better than both JPEG and PNG for most content, and it can do transparency and animation, which JPEG cannot. Browser support is now effectively universal, so sites serve it by default, which is why a right-click save so often produces a file your desktop software refuses. The format is doing its job; the mismatch is between what browsers accept and what the rest of the software world accepts. Converting to PNG is the reliable way across that gap when the image has an alpha channel worth keeping.