Convert WebP to PNG

People arrive at WebP to JPG because something refused to open their file. They arrive here on purpose, and usually for one of two reasons: the image has a transparent background, or it is going into a design tool and needs to survive being edited.

Transparency is the clear-cut case. WebP has a real alpha channel and so does PNG, so a cut-out product shot, a logo with no background or an interface icon converts with its transparency completely intact. There is no fill colour to choose and nothing to check afterwards.

Converting the same file to JPG would flatten those areas onto a solid colour — usually white — and a white logo on transparency simply disappears. If there is any transparency in the image at all, PNG is the answer and JPG is not.

PNG is lossless, so once the picture is decoded it can be cropped, adjusted, exported and re-saved as many times as you like without accumulating any further damage. A JPG loses a little on every save, which is invisible once and obvious after ten rounds. If the image is going to be worked on rather than simply looked at, start from a PNG.

One thing this cannot do, and the word invites the misunderstanding: it does not improve the image. The WebP discarded detail when it was created, and nothing recovers that. What PNG guarantees is that no further detail is lost from here on.

If the original exists somewhere in a better form — the photograph off the camera, the vector file the logo was exported from — converting that is always better than converting the WebP.

Sometimes a lot. WebP is efficient and PNG is not, particularly for photographs, where PNG can easily be five times the size. For flat graphics and icons the gap is much smaller, because that is the kind of image PNG was designed around.

If the image is a photograph with no transparency and you simply need it to open in something, JPG will serve you better and at a fraction of the size. The conversion runs in your browser either way, so a folder of images converts as fast as your machine manages and nothing is uploaded.

WebP comes in two kinds and the file does not announce which one you have. A lossless WebP converts to PNG with every pixel intact — nothing is lost in either direction, and converting back would give you the same image again.

A lossy WebP is the common case for photographs, and there the PNG faithfully preserves a picture that has already been reduced. Both give you a correct PNG. Only one of them gives you a PNG worth what it costs in size.

Flat colour, sharp edges and text are exactly what PNG compression was designed around, and it is where the size penalty largely disappears. A screenshot saved as WebP and converted to PNG often grows by a fifth rather than fivefold.

It is also where the conversion is most clearly worth doing, because these are the images that end up in documentation, tickets and design files — places that read PNG without argument and WebP sometimes not at all.

Midjourney and most image generators hand back WebP from their web apps, because it is what a browser serves most cheaply. That is fine until the picture has to go anywhere else: upscalers, retouching software, print services and stock platforms frequently will not take the format, and the file that took an hour of prompting is stuck.

PNG is the right destination when the image is going to be worked on rather than just looked at. A generated picture is usually the start of a pipeline — upscale, retouch, composite, print — and each lossy re-encode along that path compounds. Converting to PNG once, losslessly, means the pixels the generator produced are the pixels every later step receives.

Drop up to 100 files at once. They convert one after another and come back together as a ZIP, in the order you gave them.

Watch the total size with this pair in particular. Two hundred photographs that took 40 MB as WebP can be several hundred megabytes as PNG, and all of that is being assembled in your browser. On an older machine, batches of fifty are the safer way round.

Open the PNG over a background that is not white. Most viewers show a checkerboard behind transparent areas; a white rectangle where you expected a checkerboard means the transparency was flattened somewhere upstream, not here.

This is worth the thirty seconds when the image is a logo going into a document. A white box around a logo is the kind of thing nobody notices until it has been printed.