Browsers and CDNs have quietly standardised on WebP, the format Google pushed for cutting image weight, so most screenshots, downloads, and website exports now land on disk as .webp files. The problem appears at the next handoff: a school form asks for a PNG, an older editing app lists WebP as unsupported, a printing vendor returns the file with a polite error, and a couple of government portals accept JPEG and PNG only. This tool bridges that gap without a server round-trip. You pick the WebP file, the picture is redrawn at full resolution inside your browser, and the download is a lossless PNG that opens anywhere.
What WebP is, and why some destinations only open PNG
WebP is a modern container that can store both lossy and lossless pictures, plus transparency, at smaller file weights than JPEG or PNG. It is a smart format for the web and a stubborn one everywhere else, because software written before 2015 simply never learned its codec. PNG has no such problem: it is three decades old, lossless by design, and supported by every image tool, form, and printer driver still in use. Converting one WebP image to PNG changes nothing about what the picture shows and makes the file universally openable.
Why the PNG usually weighs more than the WebP
Expect the output file to be larger, sometimes two to four times the original. That is not a mistake; it is the price of lossless storage. A lossy WebP throws away the detail your eye cannot resolve to shrink the file, while a PNG writes every pixel exactly as the decoder produced it. The tool prints both weights next to the download button so you are never surprised. If a destination also imposes a size ceiling and the PNG lands above it, your options are to start from a smaller WebP or, when transparency is not required, convert to JPG instead and accept the mild quality trade.
How the conversion works on this page
Your file never leaves the device. The browser decodes the WebP into raw pixels, redraws those pixels onto a canvas at the original width and height, and encodes the canvas as PNG. No upload step exists, there is no account, no watermark, and no queue, which also means the page keeps working when you are offline after the first load. Transparent regions inside the WebP come out transparent in the PNG, and colour stays where it was, because no resampling happens unless the source itself is scaled.
Choosing between PNG and JPG for the destination
Use the PNG output when the file will be edited again, when it contains cut-out products, logos, or screenshots with transparency, or when the form lists PNG among the accepted types. Use a JPG instead when the picture is a plain photograph with no transparency and the size ceiling matters more than perfect fidelity. For print shops, PNG is the safer pick whenever the file fits the ceiling. After downloading, check the reported weight before uploading, and keep the original WebP as your master copy since the conversion is one-way in terms of file size.
Frequently asked questions
Does the conversion change the picture?
n
No. The conversion is lossless: the same pixels at the same resolution, repacked into a container that PNG readers open. Text stays sharp, edges stay clean, and a WebP with transparent areas comes out as a PNG with the same transparent areas.
n
What is the maximum file size?
n
25 MB per file. Screenshots and web exports fit well under that. If the source is a large scanned picture, the PNG output can be bigger than the source, so check the reported weight before uploading to a portal with a ceiling.
n
Which browsers run this tool?
n
All modern browsers decode WebP: Safari 14 and later, current Chrome, Edge, and Firefox. If the page says the file is not a WebP, the file is more likely misnamed or partially downloaded than unsupported.
n
I got a WebP that will not open. Now what?
n
Re-save the file from its original source. A WebP that arrived through a slow connection or a third-party resaver can be truncated, and a truncated file decodes as garbage. The original download is the clean copy.
n
Is the image uploaded to a server?
n
No. Decoding and re-encoding both happen in your browser, and the download is the only copy that leaves the device.
n