FreeTinyPNG

WebP to PNG

Convert WebP to PNG losslessly, preserving transparency, in your browser.

A WebP file icon on the left and a PNG file icon on the right, with a preserved-transparency symbol in the middle

How to convert WebP to PNG

  1. Drop your WebP files into the upload box, or click to select.
  2. Wait a moment while each file re-encodes as PNG in your browser.
  3. Download each PNG individually or use Download all for the batch.

Files never leave your device. Everything runs via the browser’s native decoders and encoders.

Why convert WebP to PNG?

WebP is a better format for most modern web delivery, but there are specific situations where PNG is what you need:

  • Editing pipelines that only accept PNG, like certain older versions of photo editors, some specialized graphics tools, or legacy print workflows.
  • Preserving transparency for use in a tool that doesn’t support WebP alpha.
  • Archiving a lossless copy when the source WebP was lossless and you want to hand it to a system that won’t accept WebP.
  • Compatibility with operating systems or software that predate widespread WebP support (Windows 7, older Photoshop, ancient mail clients).

Unlike WebP to JPG, this conversion preserves transparency. Transparent pixels in the source WebP remain transparent in the PNG, so this is the right choice when alpha matters.

What you’ll give up

PNG is a less efficient format than WebP for most content types:

  • Larger files. Expect the PNG output to be roughly 3–5× the size of the source WebP.
  • No faster delivery. If the destination is the web, shipping PNG instead of WebP measurably slows page loads.

The trade-off is compatibility with tools that don’t accept WebP. If your destination accepts WebP, keep the WebP.

Lossy WebP vs lossless WebP

The source WebP’s compression mode affects the conversion:

  • Lossless WebP → PNG: truly lossless round trip. Every pixel is preserved bit-for-bit.
  • Lossy WebP → PNG: preserves the lossy WebP’s already-compressed pixel data in a lossless PNG container. You don’t recover any detail WebP threw away. You just stop losing more.

If you need to preserve maximum quality for later edits, use a source WebP that was itself lossless.

Transparency handling

This tool preserves the full 8-bit alpha channel from the source WebP. Transparent pixels remain transparent, semi-transparent pixels remain semi-transparent. Nothing gets flattened.

For the same reason, PNG files produced from transparent WebPs can be significantly larger than ones produced from opaque WebPs, because transparency data doesn’t compress as aggressively as opaque photography in PNG’s DEFLATE scheme.

How the conversion works

Your browser:

  1. Decodes the WebP into a pixel buffer including its alpha channel.
  2. Paints it onto a canvas preserving transparency.
  3. Re-encodes the canvas as a PNG using the platform’s native PNG encoder.
  4. Delivers the PNG as an in-browser download.

No server. You can verify with DevTools → Network tab. Zero outbound requests carrying your image data.

File size expectations

For a 1600×1200 image:

  • Source WebP (lossy, quality 80): 80–150 KB.
  • Source WebP (lossless): 200–500 KB.
  • Converted PNG: 500 KB – 2 MB.

PNG just isn’t as compact as WebP for photographic content. If file size matters, keep the WebP.

When you probably shouldn’t convert

In 2026, most modern software handles WebP:

  • Adobe Photoshop and Lightroom since late 2022.
  • Affinity Photo since version 2.
  • macOS Preview, Finder, and Quick Look since macOS 11.
  • Windows Photos app since Windows 11.
  • Firefox, Chrome, Safari, Edge — all modern browsers.

If your target tool is modern, try opening the WebP directly first. Conversion may not be needed.

Metadata stripping

Canvas re-encoding drops metadata — EXIF, color profile, and anything else. For most web uses this is fine. If you need to preserve metadata, use a desktop conversion tool that supports metadata passthrough (like cwebp’s -metadata flag or ImageMagick).

For metadata-only stripping that keeps the WebP format, see our EXIF stripper.

Common mistakes

  • Converting WebP to PNG and expecting a smaller file. PNG is larger.
  • Using PNG for web delivery when WebP was serving you fine. You’re making your pages slower for no reason.
  • Expecting quality to improve. PNG is lossless, but it can’t recover detail the source WebP already threw away.

Frequently asked questions

Is this free?
Yes, no signup, no watermark, no rate limits.
Will transparency be preserved?
Yes. The alpha channel from your WebP is carried into the PNG unchanged.
Does the tool upload my files?
No. Everything happens in your browser.
Why is the PNG larger than the WebP?
PNG's lossless compression is less efficient than WebP's on photographic content. Expect 3–5× the file size.
Can I convert a lossy WebP to truly lossless?
The PNG will be lossless from that point forward, but it can't recover detail the source WebP already discarded during its lossy encoding.