Convert WebP to PNG
One WebP in, one lossless PNG out at the same pixel dimensions, with the see-through parts still see-through.
Format settings
WebP to PNG
Convert a different pairWebP · up to 20 MB
Your image never leaves your device — the work happens here, in this browser tab. No account, no watermark.
PNG is the format to turn a WebP into when part of the picture has to stay see-through and whatever you are handing it to will not accept a WebP at all. On Resizo the converter is fixed at WebP in and PNG out: add the .webp file, press Convert to PNG, and what comes back holds the decoded pixels exactly, alpha channel and all, at the width and height it already had. Both halves run on your own device, on a decoder and an encoder the page downloads from this site, so the file never leaves the machine it is sitting on.
Accepts WebP. Saves PNG.
What this changes
- Stores the decoded pixels exactly, with no quality number applied and no colours dropped.
- Preserves the cut-out: a see-through background stays see-through instead of being filled in.
- Produces a heavier file than the WebP was, often several times heavier on a photograph.
What stays the same
- The smoothing a lossy WebP encoder already applied is copied faithfully, not cleaned up or reversed.
- Resizing belongs to a different tool, so the pixel count is left exactly where the WebP had it.
How to convert a WebP to PNG
- Add the WebP. Drag the .webp file onto the panel above, or use the browse button, up to 20 MB. Both format boxes are already filled in on this page, and anything that is not a WebP is turned away before it is read.
- Press Convert to PNG. The picture is decoded and those exact pixels are stored in a PNG. The alpha channel travels with them, so a cut-out arrives still cut out rather than sitting on a black rectangle.
- Look at the two byte counts. The panel prints what went in beside what came out. On a photograph the second number is normally several times the first, which is what exactness costs.
- Download the PNG. It arrives at the width and height the WebP had, so nothing further down the line needs re-measuring or re-cropping.
The transparency is the reason to choose PNG
One question settles which format you want: is any part of this picture see-through? Plenty of WebP files have an alpha channel — stickers out of a chat app, a logo lifted off a site, a product shot with the background already knocked out — and PNG is the escape format that has one too. Clear pixels arrive clear, and the half-clear pixels along a soft edge keep the exact amount of transparency they had.
Take the same file to WebP to JPG and every empty area is filled in with black instead, because JPEG has nowhere to store it. That page is the right one when the image is a plain rectangle — a photograph, a screenshot — where the JPG will be a fraction of the weight and just as widely accepted. See-through, and you want this page. Solid, and you want that one.
A PNG copies the picture. It does not clean it up
The encoder loaded into this page is lossless and has no settings at all: no quality number, no colour reduction, nothing to get wrong. Whatever the WebP decoded to is what the PNG stores, pixel for pixel. From then on you can open the file and save it as often as you like and it will not shift.
Which is a floor, not a repair. Most WebP files on the web were written in the lossy mode, and the smoothing their encoder applied — softened texture, a gradient stepped slightly flat — belongs to the picture now and is copied faithfully along with everything else. A WebP that happened to be written losslessly is the happier case: there the PNG is a genuine duplicate of the original, in a format far more software can read.
Expect a considerably heavier file
WebP is useful because it is small. PNG is useful because it is exact. Trading the first property for the second is the whole transaction here, and it is not a gentle one: a 300 KB WebP photograph can come back well past a megabyte, because photographic texture is close to random and lossless compression has almost nothing to grip.
Flat artwork behaves far better. A logo built from a handful of colours, a chart, an interface screenshot — these are the images PNG was designed around, and the increase is usually modest. If the weight turns out to be a problem and the destination would have accepted a WebP after all, the original file is still the better thing to send.
What comes through, and what does not
| Part of the file | Result | Notes |
|---|---|---|
| Transparency | Kept | Fully and partly transparent pixels both survive. |
| Width and height | Unchanged | Nothing is scaled or trimmed on the way through. |
| Colour | Exact | Full colour, with no palette and no quantising. |
| Compression already applied | Baked in | A lossy WebP cannot be un-compressed by copying it. |
| Animation | First frame only | A single still image is written from the opening frame. |
| EXIF and GPS fields | Not carried | The output is rebuilt from raw pixels, so it has none. |
Where a PNG is what you are asked for
- Design tools and slide decks, where a mark has to sit on a coloured background rather than inside a white box.
- Storefront and marketplace listings that want the product floating on a clear background, and take PNG or JPG and nothing else.
- Icon and favicon tooling, which is written almost entirely around PNG.
- Forms and document uploads whose accepted-formats line names PNG, with WebP absent from it.
- Anything you are about to edit. Starting from an exact file means one lossy step at the very end rather than one on every save.
Limits
- There is no batch mode on this page, so a set of stickers or logos has to be fed through one file at a time, each under 20 MB.
- A full-size lossless encode is real work, and a device without room for the decoded frame and the PNG together is refused before it is attempted.
- Nothing here writes an animated PNG, so a moving WebP arrives as its opening frame and the sequence stays in the original file.
Other conversions
- A photograph saved as a PNG, many times heavier than it needs to be — PNG to JPG
- Something downstream demands a PNG and will not take the JPG you have — JPG to PNG
- Photos going onto a web page, where 30 percent off every file is the whole point — JPG to WebP
- A transparent graphic that has to get smaller and stay transparent — PNG to WebP
- You saved an image from a web page and now nothing on your computer will open it — WebP to JPG
Frequently asked questions
Does a transparent background survive the conversion?
Yes, and so does everything in between. PNG carries a full alpha channel, so a pixel that was completely clear in the WebP is completely clear in the PNG, and the partly clear pixels around a soft shadow or an anti-aliased curve hold their exact degree of transparency. That is the whole reason to send a cut-out here rather than to the JPG page.
Why is the PNG so much larger than the WebP?
The two formats are built for opposite jobs. WebP discards detail in order to get small; PNG writes down every pixel of whatever is left, texture and all. For a photograph a fivefold increase is unremarkable. For flat artwork the gap is much narrower, because large areas of a single colour are exactly what PNG compresses well.
Will converting to PNG make the image look better?
No, and nothing downstream can. If the WebP was written lossily, the softening happened when that file was made and there is no record of what used to be there. What you do gain is a stopping point: from the PNG onwards, opening the file and saving it again costs nothing at all.
What happens to an animated WebP?
You get the opening frame and nothing after it. The PNG written here is a single still image, so the first frame becomes the file and the rest of the sequence stays behind in the original. Hold on to the WebP if the movement is the part that mattered.
Should I convert my WebP to PNG or to JPG?
Check for transparency first, because it decides the answer on its own. If any part of the image needs to be see-through, PNG is the only one of the two that can hold it and you are on the right page. If the image is a solid rectangle and the file size matters, JPG is the better choice: much lighter, equally well accepted, and nothing is lost that the picture had.
Can I convert WebP to PNG without uploading the file?
Yes, because there is nowhere for it to be sent. The WebP decoder and the PNG encoder are ordinary code the page fetches from this site, and once they have loaded, your own device reads the file, converts it and writes the result. That is worth having here in particular: a cut-out that is not public yet, a client mark, artwork still under wraps — none of it travels. The PNG that comes out carries no EXIF or GPS data either.
What to do next
- Need exact pixel dimensions too? Resize it Resize Image
- Converted and still too big? Compress it Compress Image
- Trim the frame before converting — crop it Crop Image
- Converting an iPhone photo? Use the HEIC tool Convert HEIC
- Converting to share it? Remove the camera data as well Remove Image Metadata
- Need a document instead of an image? Combine the photos into a PDF JPG to PDF
- Ended up with two PDFs and need one? Combine them Merge PDF
- Crop, size and compress a scanned signature for an online form. Signature Resizer
- Set the print resolution a JPEG or PNG claims, without re-encoding it. Change Image DPI
You are on the Convert Format tool.