Convert WebP to PNG
Convert WebP images to PNG free, in your browser.
Change the format. Drop an image, a PDF or a Word document.
- JPG · PNG · WebP · Text · Word
- Word
- PDF · Text
This is free and always will be. Buy me a coffee
Your files are processed by your own browser and never sent to a server.
The reason to choose PNG over JPG for a WebP is transparency. Images saved from web pages are frequently logos, icons, product cut-outs and interface screenshots with see-through backgrounds, and JPG destroys that in a way you only notice once the file is already in a document.
PNG keeps it, exactly, with the same 256 levels of transparency WebP uses, so a soft drop shadow or an anti-aliased curve comes across without a fringe. It also keeps every pixel of the picture itself, which makes this the right conversion when the image is going to be edited rather than just viewed.
The price is size, and how steep it is depends entirely on what the picture is. A logo or a flat graphic converts to a PNG of a comparable size, sometimes smaller. A photograph does not: WebP compresses photographs and PNG barely can, so a 300 KB photo can arrive as a 4 MB PNG. If the image is a photograph and you only need it to open somewhere, WebP to JPG is the smaller, saner file.
How to convert WebP to PNG
- Drop your WebP files onto the box above, or paste them with Ctrl+V.
- Save each file from its tile, or take them all at once.
What changes
Animation is lost
A WebP can hold many frames and a PNG holds one, so you get the first frame as a still image.
WebP and PNG side by side
| WebP | PNG | |
|---|---|---|
| Where it came from | 2010, from Google, built on the VP8 video codec | 1996, designed as a free replacement for GIF |
| Throws detail away | Yes | No, every pixel is kept |
| Transparency | Yes | Yes |
| Where it opens | Every current browser. Some older desktop software and printers still refuse it. | Everywhere, without exception, since the late nineties |
| Best at | Images on a web page, where it is roughly a third smaller than JPG at the same quality | Screenshots, logos, diagrams and anything with text or hard edges in it |
More on choosing between JPG, PNG, WebP and AVIF.
Questions about WebP to PNG
Does the transparency survive?
Yes, completely. PNG and WebP store an alpha channel the same way, with 256 levels rather than a simple on-or-off, so soft shadows, glows and anti-aliased edges arrive intact rather than with a hard fringe around them. This is the whole reason to pick PNG here instead of JPG, and it is worth checking your file actually needs it, because if the background is opaque you are paying for a much larger file and getting nothing.
Why is the PNG so much larger?
Because of what is in the picture rather than anything the conversion did. PNG compresses by spotting repetition, which flat colour and hard edges have in abundance and photographs have almost none of. A logo converts to something comparable in size. A photograph that WebP squeezed into 300 KB can easily land at several megabytes as a PNG, because it is now storing every pixel exactly, including the compression noise the WebP already had.
Is anything lost in the conversion?
Not from the image. If your WebP was lossless, the PNG is pixel-for-pixel identical. If it was lossy, the PNG faithfully preserves what the WebP looked like, artefacts included; it cannot recover the detail the original encoder discarded, and nothing can. Animation is the exception: a multi-frame WebP gives you the first frame only, because PNG as written here holds a single still image.
Should I use PNG or WebP for my own site?
WebP, in almost every case. It does everything PNG does, including transparency, in less space, and every browser reads it. The reason to hold a PNG is that something outside a browser needs to open the file: a desktop editor, a print workflow, an older content system, a colleague on a locked-down machine. That is a real reason and it is why this page exists, but it is not an argument about the web.
Other conversions
WebP also converts to JPG.