Skip to content
Este site está disponível em português →
Toolbench

Convert WebP to PNG

NOTHING IS UPLOADED — IT RUNS IN YOUR BROWSER

The conversion for when transparency matters

There are two ways out of a WebP file, and which one you want depends on a single question: is any part of the image see-through? For a photograph the answer is no, and converting to JPG gives you a smaller file that opens everywhere. For a logo, an icon, a sticker or anything cut out against a transparent background, JPG would flatten every see-through pixel to white — and this page exists so that does not happen to you.

PNG carries a full alpha channel, exactly like WebP does. Soft shadows, rounded corners and anti-aliased edges come through the conversion pixel for pixel.

Why you have a WebP you cannot use

Nearly every website now serves WebP to browsers, because the format is 25 to 35 percent smaller than the equivalents and pages load faster. Saving an image gives you what the site sent. The catch is everything outside the browser: older Photoshop versions, many print services, plenty of office software and a surprising number of upload forms still reject WebP outright. PNG has been understood by essentially everything for nearly thirty years.

The file will get larger — here is why

PNG is lossless: it stores every pixel exactly. The WebP you start from almost certainly is not — it stored a close approximation in very little space. Re-encoding that approximation exactly takes far more room, so a three-fold size increase is normal, and a photograph saved as PNG can grow much more than that. Nothing is wrong when that happens; it is what lossless storage costs.

Worth being straight about the reverse, too: converting to a lossless format does not recover quality. Detail the WebP encoder discarded is gone, and the PNG preserves the image exactly as it is now — artefacts included.

When JPG is the better destination

If the image is a photograph with nothing transparent in it, PNG buys you nothing except a heavier file. WebP to JPG produces something a third of the size that every program opens. The rule of thumb: graphics and transparency go to PNG, photographs go to JPG.

Batches, and where your files go

Drop in as many WebP files as you like — an icon set, an export folder — and take the results back one by one or as a single zip. Everything is decoded and re-encoded by your own browser: nothing is uploaded, there is no size limit and no queue, and the page keeps working with the connection switched off.

Animated WebP

WebP can hold animation, much like a GIF. PNG as produced here is a still format, so only the first frame survives. That is a limit of the destination rather than a fault in the conversion — if you need the motion kept, the video and GIF tools are the right drawer.

Frequently asked questions

Does transparency survive the conversion?

Yes, completely. Both formats carry a full alpha channel, so soft shadows, rounded corners and anti-aliased edges come through exactly as they were. This is the reason to pick PNG over JPG as the destination — converting the same WebP to JPG would flatten every transparent pixel to white.

Why is the PNG so much larger than the WebP?

Because PNG is lossless and WebP usually is not. The WebP stored an approximation of the image in very little space; PNG stores every pixel exactly. A three-fold size increase is normal, and for a photograph it can be far more. The size is the price of a format that everything opens and nothing recompresses.

Do I get quality back by converting to a lossless format?

No. Detail the WebP encoder discarded is gone permanently. The PNG is a perfect copy of the WebP as it is now — including any compression artefacts already baked in. Converting recovers compatibility, never quality.

What happens with an animated WebP?

Only the first frame converts. PNG as produced here is a still format, so the animation has nowhere to go. That is a limit of the destination format rather than a fault of the conversion.

Can I convert a whole folder at once?

Yes. Drop in as many files as you like and take the results individually or as a single zip. Everything is decoded and re-encoded in your own browser, so the only ceiling is your device memory.