Convert WebP to PNG
Need to edit a downloaded WebP in a tool that doesn't speak WebP? Converting to PNG gives you a lossless copy with full transparency — perfect for Photoshop, GIMP, Figma imports, or PowerPoint slides.
To convert WebP to PNG, drop the WebP above and download the resulting PNG. The browser decodes the WebP (including its alpha channel) and re-encodes it as a lossless PNG that opens in every editor and design tool. Use this when a downstream app — Photoshop 22 and earlier, PowerPoint templates, old CMSs, screen printers — refuses WebP but accepts PNG. Nothing is uploaded and no quality is lost beyond the WebP's own lossy encode. Because PNG is lossless, this conversion adds no new artefacts — whatever the WebP already discarded stays discarded, but nothing further is lost, which makes PNG the right target when the file will be edited or annotated afterwards. Expect the PNG to be substantially larger, often two to four times, since it stores every pixel exactly. An animated WebP yields only its first frame, as PNG has no animation format in common use. Transparency is preserved throughout, so logos and UI assets convert cleanly.
Drop a WebP here, or click to upload
Output: PNG
What happens when you convert WebP to PNG?
PNG is a lossless raster format standardised as ISO/IEC 15948, with full 8-bit alpha and universal compatibility from 1996 onwards. Converting from WebP is a pure decode-and-re-encode: every pixel emerging from the browser's WebP decoder is copied verbatim into the PNG. If the WebP source was lossy, the PNG will preserve those already-decoded pixels exactly — it cannot magically add detail back. The output is often 2–5× larger than the WebP because PNG's DEFLATE compression is less aggressive than VP8 or WebP-Lossless.
Common mistakes and limitations when going from WebP to PNG
PNG cannot be smaller than a well-compressed WebP for photographic content; expect a substantial size increase. Animated WebP loses its animation — only the first frame is exported. PNG also has no built-in color-profile handling beyond an optional sRGB tag, so wide-gamut WebP images may look flatter in browsers that ignore embedded ICC profiles. For pixel-art or line-drawn work where absolute fidelity matters, PNG is ideal; for hero photography going straight to the web, keep the WebP.
Choosing the right settings for WebP to PNG
This is the lossless direction, so nothing further is discarded — the PNG stores exactly what the WebP decoded to, including the full alpha channel. That makes it the correct choice when the WebP has transparency and the destination cannot read WebP. File size will grow, usually substantially. PNG's compression is far less efficient than WebP's, and a 200 KB WebP commonly becomes a 600 KB to 1 MB PNG. There is no setting to change this; it is inherent to the format. If the source WebP was lossy, the conversion preserves its artefacts exactly. PNG is lossless with respect to its input, not with respect to the original photograph — so a lossy WebP converted to PNG gives you a large file containing compression artefacts, which is the worst of both. Where the goal is an editable master, go back to the original source image if one exists. The common practical use is design work: pulling a WebP asset into an editor that does not import the format, or preparing an image for a workflow that expects PNG. After converting, check the alpha channel renders as expected in the destination application, since a few older tools read PNG transparency inconsistently. If the WebP is animated, only the first frame converts. Animated WebP is increasingly common as a replacement for GIF, and it is easy to convert one expecting a still image and not notice the motion has gone until later. Check the source in a browser first if you are unsure whether it animates, because most desktop viewers display a single frame and will not tell you that motion was present in the file.
WebP to PNG conversion FAQ
Will transparency be preserved?
- Yes. Both WebP and PNG support 8-bit alpha, so transparent and semi-transparent pixels are copied through unchanged.
Is there any quality loss?
- No new loss. PNG is lossless, so the pixels the WebP decoder produced are stored exactly. If the WebP was lossy, that earlier loss remains.
Why is the PNG so much bigger?
- PNG's DEFLATE compression is optimised for lossless flat graphics, while WebP was designed for aggressive photographic compression. Expect a 2–5× size jump.
Does the PNG work in old software?
- PNG has been universally supported since 1996 — it opens in every browser, editor, phone gallery and word processor without a plugin.
Can I open a PNG in Photoshop CS6?
- Yes. PNG has been a native Photoshop format since Photoshop 4 (1996).
What about animated WebPs?
- Only the first frame is decoded and exported. PNG does not support motion (APNG exists but is rarely used).
Should I use lossless WebP instead?
- Lossless WebP is roughly 25% smaller than PNG at identical visual fidelity, but PNG has better legacy tool support.
Does the file's color profile survive?
- The sRGB tag is preserved. Wide-gamut ICC profiles may not survive canvas re-encoding — reassign the profile in a color-managed editor if this matters.
WebP vs PNG at a glance
| Property | WebP source | PNG output |
|---|---|---|
| Compression | Lossy VP8 or lossless | Lossless DEFLATE |
| Alpha channel | Yes (8-bit) | Yes (8-bit, preserved) |
| Typical size vs WebP | Baseline | 2–5× larger |
| Animation support | Yes | No (first frame only) |
| Best used for | Web delivery | Editing, PowerPoint, print |
Last updated:
References: ISO/IEC 15948 (PNG), Google WebP decoder specification, MDN documentation on canvas Image encoding.