PNG is the format to reach for when a WebP has to go into an editor or workflow that does not read WebP and you do not want to lose the transparent background. The PNG keeps the alpha channel and is lossless from here on. It cannot bring back detail the WebP already discarded, and it will be a lot bigger.
or use the button below to add files
Drag & drop a file here
or use the button below to choose a file
File selected
Accepts WEBP · up to 20 MB each
Processing your file…
This usually only takes a moment.
Your file is ready
·
Your file is processed on our server and deleted automatically afterward — see the privacy note below.
Overview
About WebP to PNG
What carries over
For an opaque WebP, the decoded pixels are written to the PNG exactly: we compared our output with an independent decoder and found no differences. The alpha channel is kept too. In our test, a fully transparent pixel in a WebP logo stayed fully transparent in the PNG, and partly transparent values moved by at most one level out of 255. Width and height do not change. EXIF data and embedded colour profiles are not copied. Only static WebP images work: animated WebP files made with two different encoders (Pillow and ffmpeg) were rejected in our local tests.
Is the conversion really lossless?
The step from decoded pixels to PNG adds no compression loss: in our tests a lossless opaque WebP came back from the PNG pixel for pixel, and transparent images differed only by that one-level alpha shift. But a WebP is usually lossy to begin with, and whatever it lost when it was created is gone for good. So the PNG is a faithful copy of what the WebP looks like, not of the original image behind it.
Why the PNG is so much bigger
| Test image (generated for this test) | WebP | PNG |
|---|---|---|
| 1200 × 800, gradients and noise | 286 KB | 2.20 MB |
| 600 × 600 logo with a soft transparent edge | 17.6 KB | 123 KB |
| 1280 × 720 screenshot, flat colours with small hard-edged text | 27.4 KB | 85.1 KB |
The gradient image and the logo grew about seven times, the flat screenshot a little over three times. PNG has to store every pixel without loss, while a lossy WebP stores an approximation. These figures come from images we generated and converted locally with this tool. They are examples only: not a benchmark, not a typical customer result and not a guaranteed ratio.
PNG or JPG as the target?
Pick PNG when you need transparency or a lossless working copy, such as for an editor or a graphics tool. If the image is a photo with no transparency, WebP to JPG will give you a far smaller file.
When WebP is the better file
For a website, WebP is normally the better choice, because it is smaller and current browsers display it. Keep the WebP, and make a PNG only for the places that need one. The JPG vs PNG vs WebP guide explains the trade-offs in more detail.
Compatibility
Supported Formats
Accepts static WebP (.webp), including WebP files with transparency. Output is PNG. Limits: 20 MB per file, 12,000 px per side and 40 megapixels.
Guide
How to Use WebP to PNG
- Choose a static WebP file (up to 20 MB).
- Click "Convert WebP to PNG".
- Download the PNG. Expect it to be noticeably larger than the WebP.
Highlights
Features
- Transparency kept The alpha channel carries over to the PNG instead of being flattened.
- Lossless PNG output The decoded pixels are written without further compression loss, apart from a one-level alpha shift in transparent images. Loss already in the WebP is not undone.
Applications
Use Cases
- Opening a WebP graphic with transparency in software that only reads PNG
- Getting a lossless working copy of a WebP asset before editing it
- Meeting an upload or template requirement that specifies PNG
Good to Know
Limitations
Animated WebP files are not supported. The PNG cannot restore detail a lossy WebP discarded, and it is usually much larger than the source. EXIF data and embedded colour profiles are not written to the PNG, and no colour conversion is applied before the profile is dropped, so an image in a wide-gamut space such as Adobe RGB or Display P3 can look different afterwards.
Files are processed on our servers and are not shared with third parties. Files are deleted as soon as processing or download finishes. Any leftover temporary file is removed automatically by our cleanup process within the configured retention period (60 minutes). See our Privacy Policy for full details.
Support
Frequently Asked Questions
Will the transparent background of my WebP survive the conversion?
Yes. The alpha channel carries over. In our test, a fully transparent pixel stayed fully transparent in the PNG, and partly transparent values moved by at most one level out of 255.
Why is the PNG so much larger than the WebP?
PNG stores every pixel without loss, while a lossy WebP stores an approximation. In our local tests a generated 286 KB WebP became a 2.20 MB PNG.
Is WebP to PNG truly lossless?
The conversion step itself adds no compression loss, but a lossy WebP has already lost detail that no PNG can restore. The PNG is a faithful copy of what you see, not of the original image.
Should I choose PNG or JPG for my WebP?
PNG if you need transparency or a lossless editing copy. JPG if it is a photo with no transparency and you want a much smaller file.
Can I convert an animated WebP to PNG?
No. Only static WebP images are supported. In our local tests, animated WebP files from two different encoders were rejected rather than converted.
Keep Going
Related Tools
- WebP to JPG Convert a static WebP to JPG for apps and sites that refuse WebP. Transparency becomes white.
- PNG to WebP Convert a PNG to lossy WebP at quality 85 while keeping transparency.
- PNG Compressor Lossless PNG re-save that keeps every visible pixel and transparency. It helps with uncompressed PNGs and often will not shrink others.
- JPEG XL to JPG / PNG Convert a still JPEG XL (.jxl) image to JPG or PNG at the same pixel size, with a WebAssembly decoder that runs in your browser. Animated or damaged files are refused clearly.