How to Convert WebP to PNG — Why You Need To and Every Free Method

WebP is the right format for serving images on websites. But the moment you try to use a WebP file outside a browser — in Adobe Lightroom, as an email attachment, as an og:image tag, on an iPhone, in Microsoft Word — you hit a wall. WebP compatibility outside browsers is still surprisingly limited in 2026.

The good news: converting WebP to PNG is completely lossless. PNG stores every pixel with zero loss. If the source WebP was lossless, you get a perfect copy. If the source was lossy, you get the same lossy pixels stored in a larger but higher-compatibility container — no additional quality degradation. This guide covers every reason to convert and every free method.

Why Convert WebP Back to PNG? Real-World Compatibility Problems

WebP was designed for web delivery. It was never designed to be a universal image exchange format. Here are the most common scenarios where WebP fails and PNG is required:

The Lossless Upsizing Truth: WebP to PNG Never Degrades Quality

A common misconception is that converting an image "back" to a different format degrades quality. This is only true when the destination format is lossy (like JPG). PNG is lossless — it stores exactly the pixels it receives.

When you convert WebP to PNG:

• The WebP file is decoded to raw pixels (the same process that happens when a browser displays the image).
• Those raw pixels are written to a PNG file using lossless DEFLATE compression.
• The output PNG is a perfect pixel-for-pixel copy of what the WebP decoded to.

If the source WebP was lossless: the PNG is identical to whatever was originally converted to WebP. Zero generation loss.

If the source WebP was lossy: the PNG stores those lossy pixels without adding any new artifacts. The compression artifacts that the lossy encoder introduced are baked into the pixel values, but the PNG conversion does not make them worse.

File Size Reality: PNG Is Larger Than WebP

When you convert WebP to PNG, the file gets bigger. Sometimes much bigger. This is expected and unavoidable:

Lossy WebP files balloon massively when converted to PNG because PNG has to losslessly store all those decoded pixels without the benefit of lossy compression. A 180 KB lossy WebP might decode to 5 MB of raw pixel data, which PNG then compresses (losslessly) to 650 KB. The WebP was only 180 KB because lossy encoding threw away data — PNG cannot do that.

If file size matters for the destination use case (email, downloads), consider converting to JPG instead of PNG — JPG is smaller than PNG for photographic content.

Method 1: Convertlo — Free, Browser-Based, No Upload

Method 2: dwebp CLI — Google's Official WebP Decoder

# Convert single WebP to PNG
dwebp input.webp -o output.png

# Batch: convert all WebP in current folder (Linux/macOS)
for f in *.webp; do
  dwebp "$f" -o "${f%.webp}.png"
done

# Using ImageMagick (alternative, widely available)
convert input.webp output.png

# ImageMagick batch
mogrify -format png *.webp

Method 3: Windows — Built-in Paint or Photos App

Method 4: macOS — Preview App

When to Convert to JPG Instead of PNG

PNG is the right choice for WebP conversion in most cases, but sometimes JPG is better for the destination use:

Frequently Asked Questions