WebP to PNG

How to convert WebP to PNG

1. Drag one or more .webp images into the dashed box above, or tap it to choose them from a folder.
2. There is nothing to adjust. PNG is lossless, so there is no quality level to pick, and transparent areas are carried over automatically.
3. Press Convert to PNG and follow the status line as each image is handled in turn.
4. One image comes back as a .png carrying the same name as the original. A batch arrives as editzap-webp-to-png.zip, and names that clash get a number added instead of overwriting each other.

What people use it for

PNG is the format to reach for when an image is going to be worked on rather than just looked at. It keeps every pixel exactly as it is, supports see-through areas and opens in practically every editor ever made, which is precisely where WebP still falls short.

• Opening a logo or an icon taken from a website in an editor or a presentation program that refuses WebP, or quietly flattens its transparency.
• Keeping a product cut-out or a sticker on its transparent background, so it can be laid over another picture or a coloured slide.
• Building a lossless master copy before design or print work, where a file that is recompressed on every save slowly loses detail.
• Adding images to documentation, a wiki or a help-desk article that only accepts PNG, JPG or GIF.
• Keeping diagrams and screenshots crisp, with no compression smudges added around the lettering.

Good to know

The PNG will almost always be bigger than the WebP, sometimes several times bigger, and that is expected rather than a fault. A lossy WebP throws detail away to stay small; PNG records the decoded picture without any lossy step, so it has more to hold. Converting cannot restore what the WebP had already discarded, but from here on nothing further is lost, however many times you edit and save. The page reports the size before and after so there are no surprises. When what you need is a small file rather than an editable one, WebP to JPG is the better route. An animated WebP comes out as one still frame, the first. Metadata such as camera details and an embedded colour profile stays behind, and a picture with more pixels than this browser can hold on a canvas is reduced until it fits; the status line names any file that was.

Your images stay on this device from start to finish. The browser showing this page decodes each WebP and encodes the PNG in its own memory; there is no upload step and no server at the other end waiting for your files, so private screenshots and unreleased artwork are as safe here as they are in your own folders.

Questions people ask

Why is my PNG so much larger than the WebP?

Because the two formats make opposite trade-offs. Lossy WebP accepts small changes to the picture in exchange for a light file; PNG refuses to alter a single pixel, so it has to keep more data. Flat graphics with few colours grow the least and photographs grow the most.

Will a transparent background stay transparent?

Yes. Fully and partly transparent areas are kept in the PNG, and the status line names the images that had them. Soft edges such as drop shadows keep their see-through look, although a partly transparent pixel can shift by a shade on the way through the browser.

Can I make the PNG smaller?

Not without giving something up. If the picture has more pixels than it needs, Resize Image reduces its dimensions, which shrinks a PNG considerably. If transparency does not matter, a JPG will be far lighter still.

Does this work with animated WebP?

Only in part. A PNG made here holds one frame, so an animation is saved as a still of its first frame, and the status line mentions it whenever that happens.