How to Convert WebP to PNG (4 Free Methods)

You saved an image from a website and got a .webp file. Now Photoshop won't open it. Your email client rejects the attachment. The print shop says they need a PNG. This is the reality of browsing in 2026 — Chrome, Firefox, Safari, and Edge all save images as WebP by default because websites serve WebP to save bandwidth. Your browser is happy. Everything else is not.

The fix is straightforward: convert WebP to PNG and move on with your life. Here are four free methods, from a two-second drag-and-drop to a one-liner that converts an entire folder.

Why Convert WebP to PNG?

WebP is a great format for serving images on the web — smaller files, decent quality, transparency support. But it falls apart the moment you leave the browser:

• Software compatibility. Older versions of Photoshop (pre-2022), Illustrator, InDesign, GIMP 2.8, and many Windows applications still reject .webp files. Print-oriented tools rarely support it.
• Print workflows. Print shops want PNG, TIFF, or PDF. WebP is a web format — sending it to a printer is like handing someone a Spotify link when they asked for a vinyl record.
• Archival reliability. PNG has been universally supported since 1996. WebP depends on Google's continued stewardship. For long-term archival, PNG is the safer bet.
• Editing flexibility. PNG is lossless with full alpha channel support, making it ideal for layered editing workflows. Converting a lossy WebP to PNG freezes the image at its current quality — no further degradation from re-encoding.
• Email and documents. Gmail, Outlook, and most document editors (Word, Google Docs, Canva) handle PNG natively. WebP support in these tools is inconsistent.

If you just need to view a WebP file without converting, check out how to open WebP files for quick options. But if you need to edit, print, share, or archive — conversion to PNG is the right call.

Method 1 — Pixotter Online Converter

Best for: Quick, one-off conversions with no installs. Works on any device with a browser.

Pixotter's WebP to PNG converter runs entirely in your browser. Your image never leaves your device — all processing happens client-side via WebAssembly. No upload, no server, no privacy concerns.

Steps:

1. Open pixotter.com/convert-webp-to-png/.
2. Drag your .webp file onto the drop zone (or click to browse).
3. The PNG appears instantly. Click Download.

That's it. No account, no watermark, no file size limit imposed by a server. Because the conversion runs in your browser's WASM engine, it works offline once the page loads.

Transparency handling: If your WebP has an alpha channel, Pixotter preserves it in the output PNG automatically. No checkbox, no "enable transparency" toggle — it just works.

Batch support: Need to convert multiple files? Pixotter's conversion tools accept multiple files at once. Drop a batch, download a batch.

Method 2 — dwebp CLI (Google's libwebp)

Best for: Developers and terminal users who want fast, scriptable conversion.

dwebp is the official WebP decoder from Google, part of the libwebp library. It decodes WebP and writes PNG (or other formats) with zero quality loss for lossless WebP files. License: BSD 3-Clause.

Install libwebp 1.4:

# macOS (Homebrew)
brew install webp

# Ubuntu / Debian
sudo apt install webp

# Fedora
sudo dnf install libwebp-tools

# Windows (Chocolatey)
choco install webp

Convert a single file:

dwebp input.webp -o output.png

Verify the output:

file output.png
# output.png: PNG image data, 1920 x 1080, 8-bit/color RGBA, non-interlaced

Key flags:

dwebp is the simplest option for CLI conversion — single-purpose, no configuration, no surprises. If your WebP is lossless, the PNG output is bit-for-bit identical to the original pixel data.

Method 3 — ImageMagick

Best for: Users who already have ImageMagick installed, or who need conversion as part of a larger image processing pipeline.

ImageMagick (version 7.1+) handles WebP natively when compiled with libwebp support — which it is in every major package manager's build. License: Apache 2.0 (derived from an ImageMagick license, which is Apache-2.0-compatible).

Install ImageMagick 7.1:

# macOS (Homebrew)
brew install imagemagick

# Ubuntu / Debian
sudo apt install imagemagick

# Fedora
sudo dnf install ImageMagick

# Windows (Chocolatey)
choco install imagemagick

Convert a single file:

magick input.webp output.png

Note: ImageMagick 7 uses the magick command. If you are on ImageMagick 6 (legacy), the command is convert input.webp output.png — but version 6 is end-of-life. Upgrade to 7.1+.

Check that WebP support is compiled in:

magick identify -list format | grep -i webp

You should see WEBP* rw- in the output — the rw- means ImageMagick can both read and write WebP.

Control output quality and bit depth:

# Force 8-bit RGBA output
magick input.webp -depth 8 output.png

# Strip metadata (EXIF, XMP) from the output
magick input.webp -strip output.png

# Resize during conversion
magick input.webp -resize 800x600 output.png

ImageMagick's strength here is chaining operations. If you need to convert AND resize AND strip metadata in one command, ImageMagick handles that without intermediate files. For conversion alone, dwebp is leaner.

Method 4 — macOS Preview / Windows Paint

Best for: Non-technical users who want zero installs.

Both macOS and Windows ship with built-in tools that can open WebP and re-save as PNG. No terminal, no downloads.

macOS — Preview

macOS Preview has supported WebP since macOS Monterey (12.0, released 2021).

1. Double-click the .webp file. It opens in Preview.
2. Click File > Export.
3. Set the Format dropdown to PNG.
4. Choose your save location. Click Save.

Preview preserves the alpha channel. If the WebP has transparency, the exported PNG will too.

Windows — Paint

Windows Paint has supported WebP since the September 2023 update to Windows 11.

1. Right-click the .webp file > Open with > Paint.
2. Click File > Save as > PNG image.
3. Choose your save location. Click Save.

Limitation: Paint flattens transparency. If your WebP has an alpha channel, Paint replaces transparent pixels with white. For WebP files with transparency on Windows, use Pixotter, dwebp, or ImageMagick instead.

Windows — Paint.NET (Free, MIT License)

If you need transparency preserved on Windows without the command line, Paint.NET (version 5.0+, MIT License) handles WebP-to-PNG with full alpha support:

1. Open the .webp file in Paint.NET.
2. File > Save As > change type to PNG.
3. Click Save.

WebP vs PNG — When to Keep Each

Not every WebP needs to become a PNG. Here is when to convert and when to leave the file as-is:

For a deeper comparison of these formats — file sizes, compression ratios, browser support data — read PNG vs WebP: Which Should You Actually Use?.

Batch Conversion

Converting one file is fine. Converting a folder of 200 WebP screenshots is a different problem. Here are batch approaches for each method.

Pixotter Batch Conversion

Pixotter's conversion tools accept multiple file selections. Select all your .webp files at once, convert, and download the batch. Runs client-side, so speed scales with your machine — not a server queue.

dwebp Batch (Bash Loop)

# Convert all .webp files in the current directory to .png
for f in *.webp; do
  dwebp "$f" -o "${f%.webp}.png"
done

This preserves the original filenames — hero.webp becomes hero.png. Add -mt for multi-threaded decoding on large files.

ImageMagick Batch (mogrify)

# Convert all .webp files in-place (creates .png alongside originals)
magick mogrify -format png *.webp

mogrify is ImageMagick's batch tool. It processes every matching file and writes the output with the new extension. The original .webp files are untouched.

PowerShell Batch (Windows, using dwebp)

Get-ChildItem *.webp | ForEach-Object {
  dwebp $_.FullName -o ($_.FullName -replace '\.webp$', '.png')
}

Performance Comparison

For a folder of 50 WebP files (average 2MB each), expect roughly:

Times vary with hardware. The point: all methods handle batch conversion in seconds, not minutes.

FAQ

Does converting WebP to PNG reduce quality?

No — if the WebP is lossless. The conversion decodes the pixels and re-encodes them as PNG (also lossless), so the output is pixel-identical.

If the WebP is lossy (which most web-served images are), the conversion captures the already-decoded pixels. You are not losing additional quality — but you also cannot recover detail that lossy compression already removed. The PNG will be larger than the WebP because PNG does not discard data. Think of it as freezing the image at its current state.

Why are all my saved images WebP?

Browsers save images in the format the server delivers. Most websites in 2026 serve WebP via content negotiation — the server detects your browser supports WebP and sends that instead of JPEG or PNG. When you right-click and "Save image as," you get the WebP file the server sent.

Some browsers (notably Chrome) even convert clipboard pastes to WebP internally. This is a server-side and browser-side behavior, not something you did wrong.

Can I convert WebP to PNG without losing transparency?

Yes — with all four methods listed here except Windows Paint. Paint flattens the alpha channel to a white background. Pixotter, dwebp, ImageMagick, macOS Preview, and Paint.NET all preserve full alpha transparency during conversion.

Is PNG better than WebP?

Neither is universally better — they solve different problems. WebP produces smaller files for web delivery. PNG offers universal compatibility, lossless quality, and broader software support. For a detailed breakdown with file size data, see Best Image Format for Web.

Use WebP when file size matters (websites, apps). Use PNG when compatibility matters (print, email, archival, editing). The best approach for web projects is often both: serve WebP to browsers and keep PNG as a fallback.

How do I convert WebP to PNG on iPhone or iPad?

The simplest approach: open pixotter.com/convert-webp-to-png/ in Safari, tap the upload area, select the WebP from your Photos or Files app, and download the converted PNG. No app install needed.

Alternatively, the iOS Shortcuts app can automate this: create a shortcut using the "Convert Image" action, set the output format to PNG, and add it to your share sheet.

What is the file size difference between WebP and PNG?

PNG files are typically 25-35% larger than equivalent WebP lossless files. For lossy WebP converted to PNG, the size increase can be 2-5x because PNG stores every pixel without compression shortcuts. A 200KB lossy WebP might become a 600KB-1MB PNG.

If file size is a concern after conversion, run the PNG through Pixotter's PNG compressor to reduce it without visible quality loss.

Can I batch convert hundreds of WebP files at once?

Yes. All four methods support batch conversion. The CLI tools (dwebp, ImageMagick) handle any number of files through shell loops or GNU Parallel. Pixotter's browser tool accepts multiple files per drop. See the Batch Conversion section above for specific commands.

Wrapping Up

WebP is a solid web format stuck in a world where most desktop software still speaks PNG. Until every application catches up — and that is happening slowly — converting WebP to PNG is a necessary step in most workflows.

Pick the method that fits how you work: Pixotter for quick browser-based conversion, dwebp for terminal scripting, ImageMagick for pipeline integration, or your OS's built-in tools when you just need to re-save one file.

The conversion is lossless from lossless sources and non-destructive from lossy sources. Your images come out clean. Go fix that email attachment.