Image · 55 tools · nothing uploads

WebP to PNG

Store a WebP as a lossless PNG. The transparency survives, so do the details WebP already discarded, and the file grows several times over.

Input

WebP to PNG keeps the transparency intact, which the JPG route cannot do at all. What PNG will not do is put back detail a lossy WebP already dropped, so what you get is exact storage of inexact pixels in a much bigger file. This page has no quality box, because the PNG encoder ignores one.

Questions

Does converting to PNG bring back lost detail?

No. PNG is lossless once it starts, but decoding a lossy WebP and writing the result as PNG only locks in whatever the WebP encoder kept. Nothing WebP discarded on the way in returns.

What survives?

The alpha channel survives, since both formats support full transparency. What does not change is the loss WebP already applied; PNG stores those pixels exactly, artifacts included, with no further loss added.

Which engine handles this?

jSquash decodes the WebP and encodes the PNG, both through WebAssembly, running the same way in Node, on the command line, through MCP and in the browser.

How much bigger does the file get?

Often several times bigger, since PNG has no lossy shortcut and stores every remaining pixel. A WebP saved small at a low quality can still grow substantially once it becomes PNG, since file size there was never tied to pixel count alone.

What is the reverse page?

PNG to WebP runs the opposite direction, writing a lossy WebP at quality 80 by default rather than a lossless one.

Related Image tools