Is transparency preserved?

Yes. Both WebP and PNG support a full alpha channel, so transparent and semi-transparent areas convert cleanly. This is the main reason to choose PNG over JPG as a destination.

Does the conversion lose any quality?

The PNG step loses nothing. It cannot recover what the WebP already discarded, so you get a perfect copy of the decoded image rather than a perfect copy of the original.

When should I choose PNG over JPG here?

When the image has transparency, when it contains text or sharp graphic edges, or when you are going to edit it and want no further generational loss. For an ordinary photograph headed for email, JPG is the better trade.

Is the PNG optimised?

Yes. Every PNG produced here goes through oxipng, which rewrites the compression losslessly — identical pixels, smaller file.

Is my image uploaded?

No. Decoding and encoding both run in this browser tab. The Uploaded readout beside the result measures the page's outbound traffic, so a successful conversion reads 0 B.

Is there a file size limit?

None imposed. Because PNG output is large, memory becomes the practical constraint sooner here than on other converters.

Can I convert several files at once?

Yes, though modest batches are wise. Each PNG is many times larger than its source, and several in memory at once adds up quickly on a phone.

Will there be a watermark?

No. Nothing is added and nothing is paywalled.

Why did a website give me a WebP instead of a PNG?

Because WebP is far smaller, so serving it saves bandwidth. Saving an image from a modern web page often produces a WebP even when the original was a PNG.

Convert WebP to PNG

A lossless PNG copy with transparency intact, made on your own machine. Nothing is uploaded.

ReadyWEBP → PNG

Uploaded0 B

What next

How do I convert WebP to PNG?

To convert a WebP to PNG, drop the file onto this page and download the PNG it returns. The conversion runs in your browser, nothing is uploaded, and transparency is preserved. PNG is lossless, so nothing further is discarded — but the file will be far larger, roughly eighteen times larger on our test image.

How to do it

Open the converter. Open this page in any modern browser. Nothing needs installing.
Add your WebP files. Drag them onto the panel or click to choose. Any alpha channel in the source is carried through.
Let it encode. Each PNG is written losslessly and then optimised with oxipng, which shrinks the file without changing a single pixel.
Download the PNG. The result opens in essentially any image editor, including ones that reject WebP outright.

At a glance

Converts	WebP to PNG
Transparency	Preserved
Compression	Lossless encode, but detail already lost by WebP cannot come back
Where it runs	In this browser tab. The file is not uploaded
File size limit	None imposed — your device memory is the ceiling
Cost	Free
Account needed	No
Watermark	None
Works offline	Usually after first use, but not guaranteed — there is no offline app

What it actually produces

Measured, not estimated. A procedurally generated 2400×1600 (3.8 MP) test image built to carry photographic entropy: value noise across nine octaves down to near-pixel scale, a dense field of small high-contrast features, a smooth gradient, hard edges and light grain. It is not a photograph — it is reproducible, which a photograph is not. Each figure below comes from running that image through this page.

Input	Output	Change
247 KB	2.61 MB	10.9× larger

Your own files will differ — a photograph, a screenshot and a diagram compress very differently. The point of a fixed image is that the formats can be compared with each other, not that your result will match.

Why convert WebP to PNG?

Two reasons, and they are different from each other.

The first is compatibility. WebP is a web format; plenty of desktop editors, print workflows and upload forms still reject it. PNG is accepted essentially everywhere.

The second is transparency. If the image has a transparent background, PNG is the format that keeps it while remaining universally readable. Converting to JPG would flatten it to white.

Why is the PNG so much bigger?

Considerably bigger. On the fixed test image used for every measurement on this site, a 247 KB WebP became a 2.61 MB PNG — around eleven times larger.

The mechanism is the same one that makes any lossy-to-lossless conversion expand. WebP achieved its size by discarding fine detail and introducing subtle compression noise. PNG has to store whatever remains, exactly, and fine noise is the hardest thing for lossless compression to squeeze.

Every PNG here is run through oxipng afterwards, which recovers some of that size without altering a single pixel. It cannot change the underlying arithmetic.

Is this a lossless conversion?

The PNG step is lossless. The overall result is not a lossless copy of the original image, because the WebP already discarded detail before you got here.

Put plainly: you get a perfect copy of a lossy image. That is genuinely useful — it means further edits and saves will not compound the damage — but it is not restoration.

PNG or JPG as the destination?

PNG when the image has transparency, contains text or sharp graphics, or is about to be edited.
JPG for ordinary photographs, where the file will be a fraction of the size and the quality difference is invisible.

Questions

Is transparency preserved?: Yes. Both WebP and PNG support a full alpha channel, so transparent and semi-transparent areas convert cleanly. This is the main reason to choose PNG over JPG as a destination.
Why is the PNG so much bigger?: On the fixed test image here, a 247 KB WebP became a 2.61 MB PNG — roughly eleven times larger. WebP achieves its size by discarding detail; PNG stores every remaining pixel exactly, including the compression artefacts WebP introduced. Those artefacts are fine detail, which lossless compression handles worst.
Does the conversion lose any quality?: The PNG step loses nothing. It cannot recover what the WebP already discarded, so you get a perfect copy of the decoded image rather than a perfect copy of the original.
When should I choose PNG over JPG here?: When the image has transparency, when it contains text or sharp graphic edges, or when you are going to edit it and want no further generational loss. For an ordinary photograph headed for email, JPG is the better trade.
Is the PNG optimised?: Yes. Every PNG produced here goes through oxipng, which rewrites the compression losslessly — identical pixels, smaller file.
Is my image uploaded?: No. Decoding and encoding both run in this browser tab. The Uploaded readout beside the result measures the page's outbound traffic, so a successful conversion reads 0 B.
Is there a file size limit?: None imposed. Because PNG output is large, memory becomes the practical constraint sooner here than on other converters.
Can I convert several files at once?: Yes, though modest batches are wise. Each PNG is many times larger than its source, and several in memory at once adds up quickly on a phone.
Will there be a watermark?: No. Nothing is added and nothing is paywalled.
Why did a website give me a WebP instead of a PNG?: Because WebP is far smaller, so serving it saves bandwidth. Saving an image from a modern web page often produces a WebP even when the original was a PNG.

About these formats

Sources

Portable Network Graphics (PNG) Specification, Third Edition — W3C
WebP — an image format for the web — Google
oxipng, the lossless PNG optimiser used here — oxipng contributors