Why convert WebP to PNG?
WebP is what websites hand you — Google pushed it, every CDN serves it, and it saves bandwidth. It is also the format that breaks things. Photoshop before 2022 refuses it, plenty of desktop apps, print shops and internal upload tools still reject it, and some document pipelines only accept PNG. PNG in exchange is the one format every piece of software on earth reads, transparency included. So this conversion is usually not about quality at all — it is about making a file acceptable to something that will not take WebP.
Opens everywhere
PNG is read by every editor, operating system, printer driver and upload form in existence. No "unsupported file type".
Transparency kept intact
Both formats carry an alpha channel, so logos, cut-outs and icons come through with clean edges — unlike JPG, which flattens them.
Nothing leaves your device
This one is stronger than usual: the page loads no codec and makes no request at all while converting. Open DevTools and watch.
The one thing you should know before converting
PNG is lossless, and that is exactly why your file will get much bigger. Most WebP images on the web are lossy — detail was already thrown away when the image was created. Re-wrapping those pixels in a PNG does not bring any of it back. It only stores the same pixels in an uncompressed container. You get a larger file with identical (not better) picture quality.
Here is what that looks like measured, across three real WebP files of different sizes:
| Source WebP | PNG output | Change |
|---|
| 1600×1068 · 294.6 KB | 2.43 MB | +746% |
| 550×368 · 29.6 KB | 361.6 KB | +1121% |
| 386×395 · 27.0 KB | 63.1 KB | +134% |
The smaller the WebP, the worse the ratio — a highly compressed 30 KB file can land above 360 KB. This is not a bug in this tool; it is what "lossless" means. If the file is going somewhere that needs a small size rather than a PNG specifically, the same source exports far smaller:
| Output from the 294.6 KB WebP | File size | vs source |
|---|
| PNG (lossless) | 2.43 MB | +746% |
| JPG at quality 85 | 271.6 KB | −8% |
| JPG at quality 70 | 178.5 KB | −39% |
| WebP at quality 80 | 187.2 KB | −36% |
So: use PNG when something requires PNG or you need transparency. Use JPG or WebP when you only care about the picture. And if you need PNG but the size is the problem, resize — halving the long edge cuts the file to roughly a quarter, which is by far the biggest lever here.
How to convert WebP to PNG
- Add your files — drag them in, click Choose files, or paste with Ctrl + V. Batches are fine.
- Leave it on PNG if you need a PNG. Flip to JPG or WebP if you would rather have a small file; the toolbar tells you what each does.
- Download individual images, or take the whole batch as a ZIP.
Which WebP files are supported?
Both lossy and lossless WebP, with or without an alpha channel, including animated files — though only the first frame is converted, because a PNG holds a single image. If you need the animation, keep it as WebP or convert to GIF or video instead.
FAQ
Why is the PNG so much bigger than the WebP I started with?
WebP compresses hard and PNG does not compress at all — it stores lossless pixels. Measured on our samples the increase ranged from +134% to +1121%. If size matters more than the container format, export JPG or WebP instead; the same 294.6 KB source becomes a 178.5 KB JPG at quality 70.
Will converting to PNG improve the quality?
No, and any tool that implies otherwise is misleading you. If your WebP is lossy, the detail is already gone. PNG is lossless, which means it will not lose anything further — it cannot recover what was discarded before you got the file. Converting a sharp source to PNG and then editing it is still a good idea, because the lossless container will not degrade each time you save.
Will I lose transparency?
Not on this page — PNG keeps the alpha channel. But be careful if you switch the output to JPG: JPG has no alpha channel at all, so transparent areas come out as a solid colour. If your image has transparency, this page detects it and warns you before you download.
Is this really free? What's the catch?
Free and unlimited, no account, no email, no watermark. There is no server cost to recover because there is no server — your browser does the decoding.
Does it work without an internet connection?
Yes. WebP decoding is built into every browser, so this page needs no codec download. Once the page has loaded you can turn off your network and it will still convert.
Are my images uploaded anywhere?
No. The self-verification panel on this page counts both the number of requests and the total outbound byte size. Convert a batch and it stays at zero — there is nothing to upload.
What is the largest batch I can convert?
No artificial cap. Everything runs on your machine, so the only limit is your own memory. PNG output is large in memory too — a few dozen big images at once will use a lot of RAM.