Need a WebP as a PNG — with the transparent background kept intact? Convert one image, or a whole batch, losslessly in seconds.
Multiple files welcome — converted locally, never uploaded
Choose PNG when the image has transparency (logos, stickers, product cut-outs, UI graphics) or sharp edges and text that JPG compression would smudge. PNG is lossless and keeps the alpha channel exactly as it was in the WebP, while JPG flattens transparency onto a background colour and adds compression artefacts around hard edges. The trade-off is file size: a photographic PNG can be several times larger than the WebP it came from, so for plain photos JPG is usually the better destination.
PNG is the format design and development workflows are built around. If the WebP you saved is a logo, icon, sticker, product cut-out, app screenshot or UI element, it almost certainly needs to end up as a PNG: design tools, app stores, game engines and content management systems all expect PNG for graphics with transparency, and many will reject WebP outright. The same goes for screenshots containing text — release notes, documentation, bug reports — where JPG's compression visibly fringes letters and makes small text harder to read. If the image will be edited again later, PNG is also the safer working format, because every JPG re-save discards a little more quality, while PNG can be opened and re-saved indefinitely with no further loss.
And when is PNG the wrong choice? For ordinary photographs with no transparency, almost always. A full-size photo converted to PNG can be five to ten times larger than its JPG equivalent, with no visible benefit — the extra bytes store a precision your eyes cannot use. For photos, use the WebP to JPG converter on this site instead.
1. Drag your WebP files onto the box above, or click to choose them. Multiple files at once are welcome.
2. Each image is decoded and re-encoded as PNG on your own device — a second or two per file, with no upload and no queue.
3. Download each PNG from its row. Names are kept, with the extension changed to .png.
Your browser decodes each WebP image and re-encodes it as PNG entirely on your device — no server upload, no queue, no watermark. Because PNG encoding here is lossless, the pixels and transparency in the downloaded file match the decoded WebP exactly.
That local processing matters most for exactly the files people convert to PNG: unreleased product shots, client logos, screenshots of private dashboards, artwork that has not been published yet. On an upload-based converter those files sit on a stranger's server for at least a few minutes. Here they never leave the tab they were dropped into — switch to airplane mode after the page loads and the tool still works, which is the simplest proof there is.
WebP and PNG both support an alpha channel, including partial transparency — the soft edges of a drop shadow, a fade, or anti-aliased text. This converter carries those values across untouched, so a graphic composited over a coloured background in your design tool will blend exactly as the WebP did. If a converted PNG shows a white or black box around your graphic in some viewer, the viewer — not the file — is usually at fault: a few older programs display transparency against white and are showing you the transparent area, not a filled one. Opening the file in a modern editor confirms the alpha is still there.
Is transparency really kept? Yes. Unlike the JPG converter, nothing is flattened — transparent and semi-transparent pixels are preserved in the PNG.
Will the PNG be larger than the WebP? Almost always, especially for photos. That is normal: PNG trades size for lossless quality and transparency. If the PNG is too big, run it through the Exact-KB compressor afterwards.
What about animated WebP files? They convert to a PNG of the first frame — PNG is a still-image format. Keep the original WebP if you need the animation.
Is there a file limit? No account and no daily cap. Very large batches are limited only by your device's memory.
Are my images uploaded anywhere? No. Conversion runs entirely in your browser; your files are never sent to a server.