What “WebP to PNG” actually does
A WebP file is a container plus a coded picture. Lossy WebP behaves like a modern JPEG; lossless WebP is closer to PNG. Either way, your browser can already turn those bits into pixels. WebpUndo asks the browser for that bitmap, draws it onto a canvas, and calls toBlob('image/png').
That means the PNG is a lossless snapshot of whatever the decoder produced — not a re-wrap of the WebP bitstream. If the original WebP was lossy, the softness or banding is already in the pixels. PNG will not invent detail that WebP discarded. It will stop further generations of loss, which is usually the point.
When PNG is the right export
- Logos, icons, and product cutouts that need an alpha channel.
- UI screenshots where type must stay sharp.
- Files headed into design tools that treat JPEG as a last resort.
- Any image you expect to crop or composite again.
Photographs that will only be viewed as photos are often happier asJPG. PNG can get heavy on busy camera images because it refuses to throw away color noise.
Transparency
If the WebP has an alpha channel, the PNG keeps it. Edges stay clean on whatever background you place later. If you also export JPG from the same batch, that copy is flattened onto white — JPG cannot store transparency.
Batch WebP to PNG
Select many files at once. Each row shows the original name, pixel size, and the PNG weight after encode. Download one image or a ZIP namedwebpundo-YYYY-MM-DD.zip. Files that are not WebP appear in a red list and never enter the ZIP.
Limits that are honest
Very large images are limited by your device memory, not by a server quota. Animated WebP becomes a still of the frame the browser decodes first. Color profiles beyond what the browser applies are not remapped. For a deeper comparison of the three formats, seeWebP vs PNG vs JPG.