The converter above turns WebP images into PNG files entirely inside this page. Drop your files on the drop zone or pick them with the Choose WebP files button, and the tool works through them one at a time in the order you added them. Each finished image gets its own download button, so nothing reaches your downloads folder until you ask for it.
This page exists for the moment something refuses to open a .webp file. Saving a picture from a website often hands you one, and plenty of desktop programs, document templates, and upload forms still expect PNG. PNG is the right target when the image has a transparent background, because that transparency survives the conversion instead of being flattened onto white.
How the WebP to PNG converter works
Your browser already knows how to read WebP, so the tool hands each file to that built in decoder rather than fetching a separate library. The decoded image is drawn onto a canvas at its full pixel size, and that canvas is what gets encoded as a PNG.
The encoding step uses the canvas toBlob method. MDN documents that browsers are required to support image/png and that the quality argument applies only to formats with lossy compression such as JPEG and WebP. PNG has no quality dial to turn down, so the output is a full lossless copy of what the browser decoded.
Each finished PNG is held in memory as a blob, and its download button points at an object URL created for it. MDN describes createObjectURL as returning a blob URL for the object you pass it, and notes that you release one by calling revokeObjectURL, which is what Clear all does when it empties the list.
None of this needs a server. There are no uploads and no network calls carrying your image, so the file never leaves the device you are reading this on. The list holds up to 20 files at a time, each file at 40 MB, and each decoded image at 40 megapixels, limits that come from browser memory rather than a server quota.
How to read your results
A file that finishes and offers a Download button converted cleanly, and the PNG should look identical to the WebP because it was written from the same pixels the browser just decoded.
Expect the PNG to be larger than the WebP you started with, sometimes several times larger. That is the format working as designed. The W3C specification describes PNG as lossless storage for raster images, and Google reports lossless WebP as 26 percent smaller than the same image stored as a PNG.
Transparency is preserved, so a logo or a cut out product shot still drops cleanly onto a colored slide. If you care more about file size than the transparent background, the JPG converter is the better tool, since it flattens transparency onto white.
Files the tool cannot accept are listed as skipped with a plain reason, and the rest of the batch still converts, so read that line before retrying. A batch that slows to a crawl on one very large picture is a different signal, and it points at browser memory rather than a broken file.
If a file fails to convert
Start with the message beside the file, since the tool states why it refused. A file over 40 MB or one that is not a WebP at all is set aside as skipped before conversion is attempted, and the other files carry on. An image over 40 megapixels is different, since it is admitted and decoded first, then fails with a message under its name, because that cap applies to the decoded size. If the image is simply too big, shrink it rather than fight the limit, and How to Crop and Rotate Images in Windows Photos covers cropping or scaling it down before you come back.
A file that will not decode at all is often not the WebP it claims to be, since downloads sometimes arrive truncated or carry a .webp extension over data the browser cannot read. Opening it in a desktop editor confirms whether the file is intact and lets you re-save it, and Best Free Photo Editors lists free options worth trying.
If nothing happens when you add files, or the page stalls partway through a batch, treat it as a browser problem rather than a file problem. Extensions, a wedged tab, or a browser that needs restarting can all interrupt work that runs entirely inside the page, and How to Fix Chrome When It Is Not Working walks through the usual repairs.
A PNG that converts here but still shows as an empty placeholder inside a document is a separate problem on the document side. Word can fail to render a picture it has already accepted, and How to Fix This Image Cannot Currently Be Displayed in Word covers the display settings and file paths behind that message.
Where WebP files come from
WebP is Google's image format for the web. Google's developer documentation describes lossy WebP as using predictive coding, the same method used by the VP8 video codec, and lossless WebP as reusing image fragments it has already seen in order to reconstruct new pixels exactly.
The point of the format is weight. Google reports lossy WebP as 25 to 34 percent smaller than comparable JPEG images at an equivalent quality index, and lossless WebP as 26 percent smaller than PNG. Transparency is supported in both modes, costing about 22 percent additional bytes in lossless WebP.
MDN fills in the detail behind those numbers. Lossy WebP stores the image in 8 bit Y'CbCr 4:2:0 color, while lossless WebP uses 8 bit ARGB at 32 bits per pixel, which is what carries a full alpha channel. PNG reaches the same result its own way, with the W3C specification allowing an optional alpha channel alongside indexed color, greyscale, and truecolor images.
You keep meeting WebP because sites serve it to save bandwidth, so a right click and Save image often produces a .webp file whether you wanted one or not. The compatibility gap is not in browsers, where support is broad, but in the desktop and document software built around the older formats.
Where WebP and PNG are supported
Browsers are the easy part. Google states that WebP is natively supported in Google Chrome, Safari, Firefox, Edge, and the Opera browser, and MDN lists both WebP and PNG as supported across current versions of Chrome, Edge, Firefox, Opera, and Safari. If you only ever view the image in a browser, you do not need to convert it.
On Android, Google's supported media formats documentation lists WebP decoding from Android 4.0, transparency and lossless WebP decoding from Android 4.2.1, and lossless WebP encoding on Android 10 at a quality of 100. PNG encoding and decoding are listed across Android versions.
On a Mac, Apple documents the formats Preview can export to as HEIC, JPEG, JPEG 2000, OpenEXR, PDF, PNG, and TIFF. PNG is on that list, and WebP is not among the documented export choices.
Documents are where the gap bites hardest. Microsoft's list of graphic file types you can insert into Office documents includes PNG and does not include WebP, which is why an image saved straight from a browser often refuses to go into a Word file while the converted PNG drops in without complaint.
Common questions
Does converting to PNG lose quality
No. PNG is lossless by specification, and the canvas encoder has no quality setting to lower, so the PNG stores exactly the pixels the browser decoded. What no converter can undo is compression that already happened, so if the source was a lossy WebP, the detail that encoder discarded was gone before the file reached this page.
Why is the PNG bigger than the WebP
Because a lossless file carries more data. Google measures lossless WebP as 26 percent smaller than the same image stored as a PNG, so the file should be expected to grow in this direction. If size matters more than the transparent background, converting to JPG produces a much smaller file with white behind anything that used to be transparent.
Are my files uploaded anywhere
No. The decode, the canvas redraw, and the PNG encode all run in this page on your own device, and each download button points at an in browser object URL rather than a file on a server. Nothing is uploaded and nothing is stored. Because the PNG is written from the redrawn pixels, the copy carries the picture itself rather than the original file's metadata.
Official references
- Google overview of the WebP format
- MDN image file type and format guide
- MDN reference for HTMLCanvasElement.toBlob
- MDN reference for URL.createObjectURL
- W3C Portable Network Graphics (PNG) Specification
- Android supported media formats reference
- Apple guide to converting image file types in Preview
- Microsoft list of graphic file types you can insert

