WebP to PNG converter
Get PNG copies of WebP images with every transparent pixel exactly where it was.
- Processed on your device. Your photos are never uploaded. How we know
- Free, no sign-up, no watermark
Drop WebP images to convert to PNG
Drop files, paste with Ctrl+V, or choose them from your device.
PixWrench’s code runs on your device. We don’t receive your files, file names or their contents.
PixWrench’s code runs on your device. We don’t receive your files, file names or their contents. What happens to your files
How to convert WebP to PNG
WebP is common on websites, but stickers, logos, product cut-outs and design assets are often needed as PNG: slide decks, editors and print shops know PNG well, and it carries transparency just like WebP does. Converting to JPG would paint over those clear areas. Converting to PNG keeps them.
The PNG this page writes is lossless, so what you get is exactly what the WebP decodes to, pixel for pixel. How that compares with the original artwork depends on which kind of WebP you started with, as the example shows.
- 1
Choose your WebP files
Drop them on the panel or browse for them. The tool checks the bytes inside each file, not just the .webp ending.
- 2
Decide on metadata
Remove all metadata, or remove only the location and keep details like the date. There is no quality setting, because PNG output is lossless.
- 3
Save the PNGs
Download each image, or all of them in one zip. Transparent backgrounds stay transparent.
What this tool does
- Lossless PNG output
- Alpha channel preserved, soft edges included
- Accepts lossy and lossless WebP
- JPG, PNG, AVIF and HEIC accepted as well
- OxiPNG keeps the PNG compact
- Convert a batch and download a zip
- Metadata: drop it all or only GPS
Worked example: lossless and lossy WebP sources
We measured two cases with the codecs this tool runs (libwebp for decoding, OxiPNG for the PNG), in Node.
A lossless WebP graphic. We encoded our 640 × 480 flat-color test graphic, with 53.8% of its pixels transparent, as a lossless WebP of 944 bytes. Converted back, the PNG was 1,246 bytes. We then compared every red, green, blue and alpha value with the original artwork: all identical, transparency included.
A lossy WebP photo. Our 1200 × 800 test photo, a lossy WebP of 113,156 bytes, became a PNG of 694,058 bytes, about 6.1 times larger. The PNG faithfully preserves what the WebP shows, including any softness from lossy compression, but it cannot recover the detail the WebP encoder discarded. (1 KB = 1,000 bytes.)
How the conversion keeps every pixel
libwebp, compiled to WebAssembly, decodes the WebP inside a Web Worker into four channels per pixel: red, green, blue and alpha. Nothing is blended or flattened. Those values are written straight into a PNG, a format the W3C specification defines as lossless, and OxiPNG then searches for the most compact way to store them.
Because no step in that chain throws information away, the PNG decodes to the same pixels the WebP did. Any embedded color profile is copied along with them.
Lossless WebP vs lossy WebP sources
WebP comes in two flavors. Lossless WebP stores pixels exactly, like PNG; Google reports such files as about 26% smaller than the equivalent PNG, which matches the direction of our test above. Lossy WebP works more like JPG and drops detail to save space; Google says it can carry transparency too.
From a lossless source, the PNG is a perfect copy of the original artwork. From a lossy source, the PNG is a perfect copy of an approximation. Either way, the PNG is a safe base for editing, because saving it again costs nothing. If you only need a picture to share, WebP to JPG gives a much smaller file. Our format comparison guide covers the trade-offs in depth.
Soft shadows and anti-aliased edges
Transparency is not just on or off. Drop shadows, glows and smooth outlines use partial opacity, and PNG stores each pixel’s exact level of opacity. That is why a cut-out converted here still sits cleanly on any background, with no white or black halo, unless the halo was already baked into the WebP.
Good to know
- Photos get much bigger as PNG. Our lossy test photo grew about sixfold.
- No lost detail returns. A lossy WebP stays exactly as soft or blocky as it was.
- Animated WebP isn’t accepted; only still images can be converted.
- Optimization takes a moment on large images, especially on phones; small graphics finish almost instantly.
- Image size is capped at 50 megapixels on computers and 24 on phones, with a resize to 6000 px offered.
What happens to your files
Processed on your device. Your photos are never uploaded. PixWrench’s code runs on your device. We don’t receive your files, file names or their contents.
Logos and design assets are often unreleased work, so it matters that they stay put. The WebP files you add are converted inside this browser tab and the PNGs are saved by your browser directly. Your artwork, its file names and its contents are never sent to us.
Related tools and guides
Questions people ask
Does WebP to PNG keep the transparent background?
Yes. The alpha channel is copied unchanged, including partly transparent edges and shadows.
Is the conversion lossless?
Yes. The PNG holds exactly the pixels the WebP decodes to. If the WebP itself was lossy, its earlier losses remain.
Why is the PNG bigger than the WebP?
WebP generally compresses tighter than PNG, and lossy WebP is far smaller than any lossless format. A photo can grow several times over.
How do I know if my WebP is lossy or lossless?
The file name won’t tell you, and this tool handles both the same way. If in doubt, assume a WebP photo was lossy: the PNG will still match exactly what you see on screen.
Can I turn the PNG into a favicon?
Yes. The favicon generator takes a PNG and builds every icon size a website needs.
Can I go back to WebP later?
Yes. The WebP converter has a lossless mode that keeps transparency.
Sources and review
Page reviewed by the PixWrench team · How it works · Changelog · Report a problem