Convert WebP to PNG
Drop a WebP file below and get a PNG back. The conversion happens on your own machine, so nothing is uploaded and there is no size or quantity limit beyond what your browser can hold in memory.
Drop images here
Ctrl/⌘ VPaste a screenshot or copied image
Accepts WebP
Lower means a smaller file. 75 is a good default for photos.
100% in your browser Files are never uploaded.
Why convert WebP to PNG?
Plenty of websites, content management systems and older desktop programs reject WebP uploads outright. PNG is accepted just about everywhere, and that alone accounts for most of these conversions.
Expect the PNG file to come out larger than the WebP you started with. That is the price of the broader compatibility and simpler decoding PNG gives you.
PNG is lossless, so the conversion adds no new compression artefacts. Whatever detail survives in the WebP file is carried across exactly.
PNG is the format most image editors and design tools expect, which makes it the practical choice when the file is headed for further editing rather than straight onto a web page.
Save an image from almost any modern website and you get a .webp file. Google built the format to make pages load faster and it does that well, but a lot of software never caught up: older Photoshop versions, some upload forms, various Office and printing workflows will simply refuse it. Converting to PNG is not about making the picture better — it is about handing it to a program that will accept it.
Before you convert
The file gets bigger, typically by 20 to 55 percent
PNG is lossless: it stores every pixel exactly. Most WebP files on the web are lossy. Going from one to the other means giving up the compression that made the file small in the first place, so growth is expected, not a bug. Photographs grow the most; flat-colour graphics and screenshots grow least, because that is the kind of content PNG was built for.
The picture will not look better than it already does
This is the part people get wrong most often. Lossless does not mean restored. Whatever detail the lossy WebP encoder discarded is gone, and PNG will faithfully preserve what remains — including the compression artefacts. You are paying file size for compatibility, and that is the entire transaction.
Animated WebP gives you one frame
WebP can hold an animation; PNG as handled here holds a single still image. If the source moves, you will get its first frame and nothing else. What you actually want in that case is a video or GIF conversion, which is a different kind of tool.
What carries over
- Transparency — PNG has a real alpha channel
- Pixel dimensions
- Every pixel from here on, losslessly
What does not
- The small file size
- Animation, if the source had any
- Detail the lossy encoder already discarded
WebP vs PNG at a glance
| Property | WebP | PNG |
|---|---|---|
| Compression | Lossy | Lossless |
| Transparency | Yes | Yes |
| Typical file size | 65-75% of an equivalent JPEG | 300-500% of an equivalent JPEG |
| Compatibility | Supported by all current browsers and most apps | Opens everywhere, including decades-old software |
| Usually comes from | Websites optimising page weight | Screenshots, logos and graphics |
Frequently asked questions
Are my WebP files uploaded anywhere?
No. The decoder and encoder are WebAssembly modules that run inside this page. The network tab may show a codec downloading the first time you use a format, but no request contains your file. On supported browsers, a codec that has already been used is cached so the same conversion can work offline.
Is there a file size or quantity limit?
There is no limit imposed by us. The practical ceiling is your device’s memory, since the image has to be held uncompressed while converting. On a typical laptop, images up to around 100 megapixels convert without trouble.
Will converting to PNG lose quality?
The original WebP is already lossy, so some detail was discarded when it was first created. Converting to PNG preserves whatever is in the WebP file exactly, but it cannot recover what was lost earlier.
Does it work on a phone?
Yes. The same WebAssembly modules run on mobile browsers. Conversion is slower than on a desktop because phone CPUs are weaker, and very large images are more likely to hit memory limits.
Why did I end up with a WebP file?
Most websites now serve WebP because it is smaller than JPEG, so saving an image from a web page usually hands you one. Browsers support it well, desktop software noticeably less so — which is why converting it away is such a common need.
Why is the PNG bigger than the original?
PNG is lossless, so it stores every pixel exactly instead of approximating them. For photographs that usually means a file several times larger than a lossy original. PNG earns its keep with screenshots, logos, line art and anything needing transparency — not with photos.