WebP to PNG

Drop WebP images here and get PNG copies back in this tab. The pixels are copied once and stored losslessly, transparency is kept, and the files never leave your device.

Drop WebP images here

or choose files · up to 30 at a time · batch or single

WebP in, PNG out · up to 30 files per batch · transparency kept or flattened · no upload · no account · no watermark

WebP to PNG: What Actually Changes (and What Doesn't)

Converting a WebP to PNG does not cost quality, and it does not add any. The browser decodes the WebP into the exact pixels it stores, and the PNG keeps them, losslessly.

What changes is the file around those pixels: the PNG is usually several times larger, transparency is preserved, animation is usually lost, and a wide-gamut image can come out with slightly different colors.

That is the whole trade. Below is what happens inside the tab, the numbers from real files, and how to check a conversion before you send it anywhere.

What the converter actually does

A WebP file is compressed data. To turn it into a PNG, the browser's own decoder unpacks it into a grid of pixels with four channels each: red, green, blue and alpha. That grid is drawn onto a canvas, and the canvas is encoded as PNG.

Two consequences follow. First, there is no second lossy step: the pixels you get are the pixels the WebP stored, not a re-compressed copy of them.

Second, nothing can be recovered that the WebP already threw away. If the source was saved at low quality, the PNG will faithfully preserve those compression artifacts, at a much larger size.

Transparency survives; soft edges do not improve

PNG supports alpha, and so does WebP, so transparent areas stay transparent. A logo with a cut-out background keeps its cut-out.

What does not happen is any smoothing. If a soft shadow or a glow already looked stepped in the WebP, it will look stepped in the PNG for the same number of pixels. The converter copies; it does not repair.

When you need the transparency gone — for a print shop, an upload form that rejects alpha, or a JPEG-only pipeline — flatten it onto white instead of deleting the alpha channel by hand.

Animated WebP: expect a still image

A canvas draws one frame. Convert an animated WebP here and you get its first frame as a PNG, not an animated PNG. That is fine for a thumbnail or a still, and wrong for anything that is supposed to move.

If the motion matters, keep the WebP, or convert to an animated format with a tool that handles frame sequences and timing. Nothing is lost from the file you still have: this page never modifies the original.

The color shift to check for

Browsers draw images into an sRGB canvas. If the WebP carries a wide-gamut profile — a Display P3 photo exported from a phone, for example — those colors are mapped into sRGB on the way in, and the PNG that comes out carries no color profile of its own.

For most screenshots and web graphics this is invisible. For a saturated photo, it can mean the PNG looks slightly duller than the WebP did in a color-managed viewer. If exact color matters, compare the two side by side at 100% before you delete the original.

Why the PNG is so much bigger

PNG is lossless, so it cannot use the shortcuts that make WebP small on photos. Transparency, sharp edges and flat color compress well; photographic detail does not.

These are real conversions run in Chrome on this machine, using the same page you see above:

File	Pixels	WebP	PNG	Growth
Photo, 12 MP	4000×3000	463 KB	11.70 MB	25.9×
Photo	1024×772	173 KB	1.50 MB	8.9×
Photo	550×404	59.2 KB	550 KB	9.3×
Photo	550×368	29.6 KB	362 KB	12.2×
Transparent graphic	400×301	17.7 KB	129 KB	7.3×
Transparent graphic	386×395	13.8 KB	86.7 KB	6.3×
Lossless WebP	400×301	79.9 KB	141 KB	1.8×

The pattern is sharp: a lossy WebP becomes a PNG many times its size, while a WebP that was already saved losslessly barely grows. A 12 MP photo that weighed under half a megabyte lands at 11.7 MB — fine as a master file, far too heavy to put on a web page.

That is the moment to ask what the PNG is for. Editing, printing, uploading to a service that rejects WebP, or keeping a lossless master: convert.

Publishing on the web: keep the WebP, or use a JPG for photos. Our image resizer and image compressor exist for that second case.

How to check a conversion in under a minute

1. Dimensions. The PNG must report the same width and height as the WebP. If they differ, something resized the image, and the file is not a straight conversion.
2. Transparency. Put the PNG over a dark background. Transparent regions should show that background, not a white or black box.
3. Detail at 100%. Zoom to one image pixel per screen pixel and compare an edge. A correct conversion shows the same edge, including its artifacts. A softer edge means the file went through a resize or a lossy re-encode.
4. The header, if you want proof. Every PNG starts with the bytes 89 50 4E 47 0D 0A 1A 0A. A file that begins with RIFF is still a WebP, whatever its name says.

That last point cuts both ways. WebP files are sometimes served with a .jpg or .png extension by mistake.

This page reads the first bytes of each file instead of trusting the name, so a mislabeled WebP still converts, and a real JPEG dropped in by accident is refused with a note instead of being silently turned into a huge PNG.

When the WebP should stay a WebP

Every current major browser renders WebP — Chrome, Firefox and Edge have for years, and Safari since version 14 in 2020. A WebP on a web page is smaller and just as sharp, so converting it for the web is usually a step backwards.

Convert when the next stop is not a browser: a desktop editor that does not read WebP, a print workflow, a CMS upload that rejects the format, or an archive where you want a lossless master. Convert the copies you need, and keep the original.

Batch, ZIP, and the limits of a tab

This page accepts up to 30 files at once and converts them one after another, so memory stays flat instead of holding 30 decoded photos at the same time.

Each result can be downloaded on its own, or all of them as a ZIP that is assembled in the page — no second service, no upload queue.

The guard rail is 100 megapixels per image. A canvas needs four bytes for every pixel, so a 12 MP photo occupies about 46 MB before the PNG encoder runs. Larger images are refused with a message rather than left to freeze the tab.

You can confirm the local-only claim yourself: open the browser's Network panel, convert a file, and watch that no request carries the image. Or load the page, disconnect from the internet, and convert again — it still works.

Quick answers

Does converting WebP to PNG reduce quality? No. The pixels are copied once and stored losslessly. Quality can only go down if the file is resized or re-encoded as a lossy format.

Will the PNG be bigger? Almost always, and often by a lot: 6× to 26× in the conversions measured above. A WebP that was saved losslessly grows far less.

Is my file uploaded? No. The decoding, drawing and encoding all happen in your browser tab. Nothing is sent to a server.

Can I convert several files at once? Yes, up to 30 per batch, with individual downloads or one ZIP.

What happens to an animated WebP? You get the first frame as a still PNG. Animation is not carried over.

Does transparency survive? Yes. Choose "White (flatten)" only when a destination requires an opaque image.

Can I use this on a phone? Yes. The page works in mobile browsers; the file picker opens your photo library.

What if my file is named .jpg but is really a WebP? It will still convert, because the tool checks the file header rather than the extension.

Is there a file size limit? 80 MB per file and 100 megapixels per image. Anything larger is refused before it can stall the tab.