WebP to PNG Converter

Convert WebP images to PNG while keeping transparency intact.

This tool runs entirely in your browser. Your data is never uploaded, never stored, and never leaves your device.

Saves a WebP as a PNG that any editor, print shop or upload form will accept, keeping the transparent areas transparent. PNG is lossless, so nothing further is lost on the way out — but it also cannot undo the compression the WebP already applied.

How to use it

1Choose the WebP; its name, byte size and pixel dimensions appear.
2Press Convert to PNG. There is no quality slider here, because PNG records every pixel exactly.
3Check the size comparison and download — the file keeps its original name with a .png extension.

Example

Input: A 400 × 400 WebP logo with a transparent background, 6.6 KB
Output: A 25.0 KB PNG — 281% larger, transparent corner still fully transparent

Expect it to grow, sometimes dramatically: a 24.4 KB photographic WebP came out as a 1.01 MB PNG, and a 38.9 KB screenshot as 276.1 KB. That is not a fault. PNG has to store, losslessly, every artefact the lossy WebP already baked in, so what you get is a perfect copy of an imperfect image — no detail is recovered by coming here. If the only problem is that something refuses to open .webp files and there is no transparency worth protecting, WebP to JPG gives you a far smaller file. Dimensions are unchanged, and one file is handled at a time.

What happens to your data

This tool runs entirely in your browser. Your input is never uploaded to a server, never stored, and never logged. Your browser's built-in WebP decoder reads the file, a canvas holds the pixels and the browser's PNG encoder writes them back out. Because that hand-off carries pixels and nothing else, none of the original's embedded metadata survives into the PNG you download.

Last updated August 2026

Save a picture from a web page and what lands in your downloads folder is often a .webp. Sites serve that format because it makes the page lighter, which is a decision taken for the page rather than for you, and the bill arrives later: the upload form lists JPG and PNG and nothing else, the editor shrugs at the file, and the person you emailed it to says that double-clicking does nothing.

PNG is the right answer when part of the picture is transparent, because JPEG — the other place a WebP usually goes — has no alpha channel at all and has to fill those areas with a solid colour. What you pay for that is size, and it is not a small amount: an 85.4 KB photo left here as a 1.42 MB PNG. That is PNG doing what it is for rather than the conversion going wrong.\n\nTo convert WebP to PNG is the right move when transparency matters or the image is flat graphic work \u2014 a logo, an icon, a screenshot of an interface. The WebP PNG pairing suits that case exactly: PNG is lossless, so nothing degrades on the way through, and it is WebP to PNG free here with no account. Where the picture is a photograph, WebP to JPG usually gives a far smaller file for the same apparent quality, so the WebP-PNG pairing is not always the right one.

How it works

Toolvore hands the file to your browser's own WebP decoder, draws the decoded image onto a canvas at its natural width and height, and asks the canvas for a PNG. There is no quality setting, because PNG has nothing to trade away: measured against the same WebP decoded in the same browser, not one of a 1400 × 900 photo's 5,040,000 samples differed, and the same held for every file tried here, transparency included. That route also explains the weight. What comes back is 8-bit RGBA and nothing else — no palette, no metadata, no colour profile — so a Display P3 photo is converted into the canvas's sRGB space on the way in and arrives untagged, and the encoder is tuned for speed rather than size: one 384.4 KB result, re-encoded from the identical pixels with per-row filtering and maximum compression effort, came to 209.1 KB. No server is involved at any point; with the network switched off, the same photo produced the same 1,490,273-byte file.

Common use cases

Getting a picture that downloaded as .webp into a form that only accepts JPG or PNG
Converting a logo to PNG with its transparent background intact, for a slide or a document
Opening an image in an editor or a viewer that was written before WebP existed
Sending a file to someone whose computer does nothing when they double-click a .webp
Taking a lossless copy of a WebP before you edit it, so the picture is not compressed a second time

Frequently asked questions

How do I convert a WebP to PNG?＋

Choose the .webp file and press Convert to PNG. There is nothing to set, because PNG records every pixel exactly. The download keeps the original name and dimensions, so a 512 × 512 logo.webp comes back as a 512 × 512 logo.png. It takes one file per run, and picking the next one clears the previous result on its own, so there is no reloading in between. No signup and no watermark.

Will a transparent background still be transparent in the PNG?＋

Yes, and so are the partly transparent pixels at the edge of a shape — the part that usually goes wrong elsewhere. The PNG stores exactly what the WebP decodes to, alpha channel included: a 512 × 512 logo came back with all 262,144 of its transparency values unchanged from the file it was made from, the 1,376 partly opaque pixels along its edges among them, spread over 15 different levels. That soft edge is what stops a logo showing a hard white or black fringe against a coloured background. If you want the opposite, WebP to JPG fills transparent areas with a colour you choose.

Why is the PNG so much bigger than the WebP?＋

Two reasons, and only one of them is the format. A lossy WebP got small by throwing detail away, and PNG has to store the result exactly as it now is, artefacts and all — measured here, 6.3 KB became 37.0 KB for a logo, 27.2 KB became 225.7 KB for a screenshot and 85.4 KB became 1.42 MB for a photo. The second reason is your browser's encoder. A 172.2 KB lossless WebP came back as a 384.4 KB PNG, and the identical pixels re-encoded with more effort fit into 209.1 KB, so most of that particular growth is the browser choosing speed over size and there is no setting here to change it. If size rather than format is the real problem, put the PNG through the image compressor afterwards.

Should I convert a WebP to PNG or to JPG?＋

If any part of the image is transparent, PNG — JPEG cannot store transparency at all, so the alternative is picking a colour to fill it with. If none of it is transparent, JPG is far lighter for the same picture: the photo above came out at 1.42 MB as a PNG and 183.9 KB as a JPEG at the default quality of 90. The exception is a screenshot, a chart or anything with sharp text, where JPEG smears hard edges and the heavier PNG earns its weight.

What happens to an animated WebP?＋

You get a still of the first frame, and nothing on the page warns you that the rest has gone. A three-frame animation converted here produced a single 300 × 300 PNG of frame one, byte for byte the same whether it was converted immediately or five seconds in. Nothing on this site turns an animated WebP back into an animated file, so if the movement matters, this is not the tool for it.

Is my image uploaded to convert it?＋

No. Your browser decodes the WebP, draws it and writes the PNG; the file never leaves the tab, and nothing carrying it is sent anywhere. Switching the network off after the page had loaded and converting the same photo produced the identical 1,490,273-byte file.