WebP to PNG Converter

Lossless PNG output with the alpha channel kept intact.

PNG is the format to convert a WebP into when the image has transparency and the destination will not accept WebP — a logo going into an older design tool, an icon for a desktop application, an asset for software that predates the format. Unlike a JPG conversion, PNG keeps the alpha channel, so a cut-out image stays cut out rather than gaining a white rectangle.

🖼️

Click to select or drag & drop WebP files

Transparency preserved · Multiple files · Nothing uploaded

How it works

1

Select your WebP files

One or many, by clicking or dropping them in.

2

Convert

Each image is decoded and re-encoded as PNG in the page.

3

Files download themselves

Multiple files arrive one after another, a fraction of a second apart.

Why PNG rather than JPG for a WebP

The deciding factor is usually transparency. WebP supports an alpha channel and so does PNG; JPEG does not, and has no way to represent it. Convert a transparent WebP to JPG and every transparent pixel is composited against something — usually white, sometimes black — which turns a logo meant to sit on any background into one that only works on that colour.

The second factor is what the image contains. PNG uses lossless compression, so converting a WebP that was itself losslessly encoded produces a pixel-identical result. For screenshots, diagrams, logos and anything with flat colour and hard edges, that is exactly right, and PNG will often be smaller than a JPG of comparable quality.

For photographs the trade-off reverses. PNG stores photographic detail badly — a converted photo can easily be three to five times the size of the WebP it came from, because lossless compression has little to exploit in continuous-tone image data. If the source is a photograph and the destination accepts JPEG, converting to JPG will produce a far smaller file.

What a conversion can and cannot recover

If the original WebP was saved with lossy compression, its detail is already gone. Re-encoding it as PNG stores the damaged pixels perfectly and faithfully — a large file that looks exactly like the small one it came from. Converting to a lossless format does not restore anything; it only stops further loss from that point on.

Animation is the one thing that does not survive. WebP can hold an animated sequence, and PNG in its ordinary form holds a single frame. An animated WebP converted here yields its first frame, which is usually not what was wanted. APNG exists and can hold animation, but browser encoders do not produce it.

Metadata is also dropped. The conversion draws the image onto a canvas and re-encodes it, and the canvas holds pixels — not EXIF data, not an embedded colour profile, not a copyright field. For a web asset that is often an improvement, since it strips location data and shrinks the file. For an archival copy it is a loss worth knowing about before converting the only version you have.

Frequently Asked Questions

Yes. The canvas is left unfilled before the image is drawn, so transparent areas stay transparent in the PNG. This is the main reason to choose PNG over JPG for a WebP.
Because PNG is lossless and WebP usually is not. The PNG stores every pixel exactly, including detail the WebP compression had already approximated, and for photographs that can mean a file several times the size.
Yes. Select or drop as many as you like and each one downloads separately, staggered slightly so the browser does not block the repeated downloads.
Only the first frame is converted. PNG holds a single image, and the animated variant APNG cannot be produced by browser encoders.
No. Decoding and re-encoding both happen in your browser using the canvas API. The files never leave your device, so there is nothing stored or deleted on a server.