WebP to PNG Converter

Converts WebP images to PNG with the transparency kept and every decoded pixel stored exactly, so the file opens in any editor and loses nothing more when it is saved again. Expect it to grow: our 227 KB WebP test photo became a 1.9 MB PNG, about eight times larger. Runs in your browser, five files at a time.

Last updated

Target Format
webp ➔ png
Up to 5 images per batch

How to convert WebP to PNG

01

Drop in up to five WebP files

Drag them onto the panel or tap it to choose. Files are identified by their contents rather than their names, so a .webp that is really a JPEG is still read correctly.

Tip: Saved the image from a website? That is the most common reason people need this, and it converts like any other WebP.
02

Untick anything you want to skip

Every file arrives ticked. There is no quality setting, because PNG is lossless: the only decision is which files to convert.

Tip: Only need to view or email a photo? WebP to JPG gives a far smaller file that opens just as widely.
03

Process and download

A single file downloads on its own; several arrive as one ZIP, each keeping its original name with a .png extension.

Tip: Check the size before sending it anywhere with a limit. A PNG of a photograph often runs to several megabytes.

Why convert WebP to PNG here

Transparency carried across exactly

WebP and PNG both store an 8-bit alpha channel, so soft shadows, rounded corners and cut-outs arrive in the PNG with the same transparency they had, pixel for pixel, with no fringe around the edges.

Lossless from here on

The PNG holds exactly the pixels the WebP decoded to. Open it, edit it and save it again as often as you need, and it will not lose anything more along the way.

Runs in your browser

Decoding and encoding both happen on your device in a Web Worker. Nothing is uploaded, and the converter keeps working with your connection switched off once the page has loaded.

Checked by content, not extension

Files are identified from their first bytes. A mislabelled file is converted as what it really is, and something that is not an image at all is turned away before it reaches the encoder.

Colour applied, metadata dropped

The browser applies any embedded colour profile while decoding, so colours look as they did on screen, and the PNG is written in standard sRGB. EXIF data, including any location, is not copied across.

Five files per batch

Each image is fully decoded into memory before it is written out, at about four bytes per pixel. Five at a time keeps that within what a phone browser will allow without closing the tab.

Frequently Asked Questions

Will the PNG be better quality than the WebP?+
No. It will be identical to what the WebP decodes to, which is the point: nothing further is lost. Detail the WebP discarded when it was first saved cannot be recovered by any converter, because that information is no longer in the file.
Why is the PNG so much bigger than the WebP?+
Because PNG is lossless and most WebP files are not. A photograph stored without loss needs far more bytes: our 227 KB WebP test photo came out as a 1.9 MB PNG, about eight times that size. Flat graphics such as logos and icons grow much less, and sometimes hardly at all.

If file size matters more than editability, convert to JPG instead.

What happens to an animated WebP?+
Only the first frame is kept. For an animated file the browser hands the converter a single still image, so the result is an ordinary still PNG. Keep the original WebP if you need the animation.
Does a transparent background survive the conversion?+
Yes. Both formats store transparency for every pixel with the same precision, so a cut-out or a logo on a transparent background converts with its edges exactly as they were, including the partly transparent ones.
Is my image uploaded anywhere?+
No. The WebP is decoded and the PNG written inside your browser. You can confirm it: open your browser's developer tools, watch the Network tab while you convert, and no request will carry your file.
Can I turn the PNG back into a WebP later?+
Yes, and for a website that is usually the right final step. The PNG to WebP converter on our home page turns it back into a small file with the transparency kept, so you can edit in PNG and publish in WebP.

Format Comparison

Feature SpecificationWebP to PNG conversionAlternative
CompressionLossless onlyLossy or lossless
Our 1200 × 900 test photo1.9 MB227 KB
Transparency8-bit alpha8-bit alpha
Opens inEssentially everythingCurrent browsers and most current editors
AnimationNot in this toolSupported by the format

Technical Overview & Specifications

Deep dive into WebP to PNG conversion architecture and processing.

Show Details

Platform Overview

WebP is a good format to receive a website in and an awkward one to receive a file in. Right-click an image on most large sites and choose Save, and what lands in your downloads folder is often a .webp, even when the page called it a photo. Then the trouble starts: an older image editor will not open it, a print shop's upload form rejects it, a slide deck shows an empty box where the picture should be. PNG has none of those problems. It is understood by essentially everything, and because it is lossless it is the safe format to edit from: open it, change it and save it as many times as you like, and it does not degrade further.

This page decodes the WebP with your browser's own decoder and writes the pixels into a PNG, losslessly, inside a Web Worker. Transparency comes across exactly, because both formats store a full 8-bit alpha channel. What cannot come across is detail the WebP already threw away. Most photographs on the web are saved as lossy WebP, and converting one to PNG freezes it in its current state rather than restoring the original. That is usually exactly what you want; it is just worth knowing that a PNG made from a WebP is a more compatible and more editable image, not a sharper one. Up to five files per batch, each up to 25 MB and 8192 pixels on its longest side, and nothing is uploaded.

From WebP to PNG, step by step

WebP comes in two kinds that share one container. Lossy WebP is built on the VP8 video codec: the image is split into blocks, each block is predicted from neighbours that have already been decoded, and only the difference is stored, coarsely. Lossless WebP uses a different method altogether, closer to PNG in spirit but with better prediction and a cache of recently seen colours. Either kind can carry an alpha channel. The browser's decoder handles all of them, which is why this page accepts any WebP without asking which kind it is.

Inside a Web Worker the file is decoded with createImageBitmap, drawn onto an OffscreenCanvas at its original dimensions and handed to the canvas PNG encoder. PNG then does what it always does: it filters each row of pixels to make it more predictable and compresses the result with DEFLATE, the algorithm behind ZIP files. DEFLATE is good at flat colour and repeated patterns and poor at photographic grain, which is the whole reason a PNG of a photo is several times the size of the WebP it came from. Nothing in this pipeline guesses or smooths; every pixel the decoder produced is written out unchanged.