WebP to PNG Converter
Turn a WebP into a PNG that older software will actually open — written losslessly, transparency intact, never uploaded.
JPEG has no transparency, so transparent areas are filled with this color.
Everything runs locally in your browser. Nothing is uploaded to any server — close the tab and your files are gone.
How to convert WebP to PNG
Drop the WebP files in
The output format on this page is already set to PNG. One file or a batch — each gets its own row with the size before and after, and the row that finishes first can be downloaded while the others are still running.
Notice that the quality slider is gone
It hides itself whenever PNG is the output, because there is nothing to trade away. The PNG path is lossless, so there is no quality dial to set in the first place — and no background colour to choose either, since PNG keeps the alpha channel.
Resize if the PNG has to be smaller
Compression cannot do much for a lossless file, which makes dimensions the lever you actually have. Fitting the longest edge to 2048 or 1024 px is the effective way to bring the size down, and it happens before the PNG is written rather than as a second save afterwards.
Download, and expect a bigger file
Most rows will show a “+x% larger” label. That is the expected outcome of this conversion rather than a failure — the reason is below.
What to expect from a WebP → PNG conversion
The file will almost always get bigger
WebP files are usually lossy: detail was thrown away to make them small. PNG is lossless and has to store every pixel it is handed, artifacts included. The output is then run through oxipng at level 2, which squeezes out what it can without altering a single pixel — but no amount of that closes a gap between two different kinds of format. A PNG several times the size of the WebP is normal.
Bigger does not mean better
Converting to PNG freezes the picture exactly as the WebP already was: softness, banding and blocky edges come along too. Nothing is recovered — a lossless container around lossy pixels still holds lossy pixels. If the original PNG or camera file still exists somewhere, that is the better source to work from.
Lossless here means faithful to the WebP, not to the original
It is worth being precise about what the guarantee covers. The PNG will match the WebP pixel for pixel; it makes no claim about the photograph or artwork the WebP was made from. The one case where those two are the same thing is a WebP that was saved in the format’s own lossless mode — those exist, and this page reads them the same way, so the PNG then really is the original pixels.
A cut-out arrives as a cut-out
Both formats carry an alpha channel, so transparent and semi-transparent pixels move across untouched and no fill colour is applied anywhere. Do check the edges of the subject in the compare view, though: if the WebP was compressed hard, the soft boundary around a cut-out may already carry a faint fringe, and the PNG will preserve that fringe as carefully as it preserves everything else.
Where it is worth doing anyway
Compatibility, and only compatibility. Older desktop applications, layout and print workflows, some office software and plenty of internal tools still refuse a .webp outright, and PNG is the format that always opens. When the choice is between a file nothing will place and a file five times larger that everything will, the larger file wins. Picking a delivery format rather than a fallback is the opposite problem, and the WebP, AVIF and JPEG guide is where that one is worked out.
WebP to PNG — frequently asked questions
Why is my PNG several times larger than the WebP?
Because PNG is lossless. The WebP got small by discarding detail, while PNG stores every pixel it receives, so the size climbs back up — often steeply. That is the price of a format everything can open.
Does converting to PNG improve the image quality?
No. Detail the WebP encoder already dropped is gone, and no format can put it back. The PNG is a faithful copy of the WebP as it stands today, nothing more.
Is the transparency preserved?
Yes. The alpha channel comes across unchanged, so cut-outs, soft edges and semi-transparent pixels look the same in the PNG as they did in the WebP.
My WebP was saved losslessly — is the PNG then identical to the original?
Pixel for pixel, yes. A lossless WebP holds exact pixels, and the PNG path here is lossless as well, so nothing is approximated anywhere in the chain. What still will not travel is anything stored outside the pixels, such as metadata.
Can I convert an animated WebP this way?
Not as an animation. What comes out is a single still image — there is no animated-PNG output here. If you need the motion, keep the WebP or go back to the original GIF.
Is there a quality setting for the PNG?
No, and that is deliberate. The PNG encoder is lossless, so there is nothing to trade and the slider hides itself when PNG is selected. Compression happens through oxipng, which reorganizes the file without touching the image.
Will the PNG place correctly in Illustrator, InDesign or Word?
That is the usual reason people are on this page, and yes — PNG has been readable by layout, office and print software for decades, transparency included. The pixel dimensions are unchanged by the conversion, so the image places at the same physical size it would have.
What if I need something smaller than the PNG?
Resize it. With a lossless format the dimensions are the only real lever — or, if whatever you are feeding will accept it, switch the output back to WebP or JPEG, where a quality setting exists.
Does this work on a phone?
It does, with one worker instead of three, so a batch takes longer than it would on a laptop. Very large images are the real limit: everything is decoded in memory, and a row can come back with an out-of-memory error on a small device where the same file converts fine on a desktop.