How to Convert WebP to PNG: A Step-by-Step Guide

How do you convert WebP to PNG?

You convert WebP to PNG in one of three ways: an online converter, your computer’s built-in image apps, or a command-line tool, depending on how many files you have and how often you do it. WebP and PNG are both common web image formats, but PNG has broader support in older software and tools (MDN). The quickest option for a single file is an online converter or your operating system’s built-in image viewer; for many files at once, the command line is fastest.

Key Takeaways

• You can convert WebP to PNG online, with built-in apps like Preview (Mac) or Paint (Windows), or via the command line.
• WebP is a Google format that’s often 25 to 34% smaller than JPEG, which is why sites use it (Google).
• PNG is a lossless format with universal support and transparency, making it ideal for editing and compatibility (MDN).
• Converting WebP to PNG usually increases the file size, because PNG is lossless and less compressed.
• For many files, a command-line tool like ImageMagick converts them in one batch (ImageMagick).

This guide walks through each conversion method step by step, then explains what to watch out for and when each format is the right choice. It’s a companion to our wider guide on choosing the right image file type.

What is WebP?

WebP is an image format developed by Google that supports both lossy and lossless compression, transparency, and animation, designed to make web images smaller without losing visible quality (Google). Google’s own figures put lossy WebP at roughly 25 to 34% smaller than comparable JPEG files, and lossless WebP around 26% smaller than PNG.

That size advantage is why WebP became common across the web: smaller images load faster, which improves performance and Core Web Vitals. WebP is now supported in all major browsers, including Chrome, Firefox, Edge, and Safari (MDN). The catch is outside the browser: some older desktop software, editing tools, and systems still don’t open WebP files, which is the usual reason people need to convert one to PNG.

What is PNG?

PNG (Portable Network Graphics) is a lossless raster image format that supports transparency and is universally supported across browsers, operating systems, and editing software (MDN). Being lossless means it preserves every pixel exactly, with no compression artefacts, which makes it the standard for graphics, logos, screenshots, and any image you’ll edit repeatedly.

The trade-off is file size. Because PNG doesn’t discard data the way lossy formats do, PNG files are typically larger than the equivalent WebP or JPEG. That’s a fair price for images where quality and compatibility matter more than download size, which is exactly the situation when you’re converting a WebP for editing or sharing. PNG’s combination of lossless quality, alpha transparency, and support everywhere is why it remains the safe, universal choice.

What’s the difference between WebP and PNG?

The core difference is that WebP is built for small file sizes on the web, while PNG is built for lossless quality and universal compatibility (Google). They overlap in features, both support transparency, but they’re optimised for opposite priorities, which is why each suits different situations.

WebP offers both lossy and lossless modes, supports transparency and animation, and produces noticeably smaller files, around 25 to 34% smaller than JPEG in Google’s figures. That makes it ideal for serving images on a live website where load speed matters. PNG, by contrast, is always lossless, supports transparency through a reliable alpha channel, and opens in essentially every program and platform ever made, but its files are larger. WebP’s weakness is support outside the browser: some desktop software and older systems still can’t open it. PNG’s weakness is size: it’s heavier to download. Put simply, WebP wins on efficiency and PNG wins on compatibility and editing, which is exactly why converting between them is so common. You pick the format that matches the job rather than treating one as universally better.

Why would you convert WebP to PNG?

You’d convert WebP to PNG mainly for compatibility: many editing tools, older systems, and some platforms still don’t fully support WebP, while PNG works almost everywhere (MDN). If you’ve downloaded a WebP image and your software won’t open it, conversion is the fix.

The common reasons are practical:

• Software compatibility. Some image editors and design tools don’t open WebP, but all of them handle PNG.
• Editing. PNG is lossless, so it’s better suited to images you’ll edit and re-save repeatedly without accumulating compression damage.
• Transparency you can rely on. PNG’s alpha transparency is universally supported, which matters for logos and graphics.
• Sharing and uploading. Some older platforms or systems reject WebP uploads but accept PNG.
• Printing and archiving. PNG’s lossless quality and broad support make it a safer choice for long-term storage and print.

In short, you convert when you need compatibility or lossless editing rather than the smallest possible file. For the web itself, WebP is usually the better format to keep.

What are the best tools to convert WebP to PNG?

The best tool depends on volume: online converters and built-in apps suit one or a few files, while command-line tools handle batches (ImageMagick). You almost certainly already have at least one option available without installing anything. The table below summarises the main routes.

Each has its place. Online tools are the fastest for a one-off when you don’t want to install anything, though you should avoid uploading sensitive images to third-party sites. Built-in apps keep the file on your machine and need no setup. Image editors make sense when you’re working on the image anyway. And the command line is unbeatable for converting dozens or hundreds of files in a single step. The sections below cover each method in detail.

How do you convert WebP to PNG online?

To convert WebP to PNG online, upload the file to a browser-based converter such as Squoosh or CloudConvert, choose PNG as the output, and download the result (Google). It’s the quickest route for a single image when you don’t want to install software.

The steps are the same across most online tools:

1. Open the converter in your browser.
2. Upload or drag in your WebP file.
3. Select PNG as the output format.
4. Start the conversion.
5. Download the resulting PNG.

A couple of cautions apply. First, don’t upload confidential or sensitive images to a third-party website, since you’re handing the file to an external service; use a local method for anything private. Second, free online converters sometimes limit file size or the number of conversions, so for many files a built-in or command-line method is more practical. For a quick, one-off public image, though, an online converter is hard to beat for convenience.

How do you convert WebP to PNG on your computer?

You can convert WebP to PNG without any extra software using your operating system’s built-in apps: Preview on macOS or Paint and Photos on Windows (MDN). This keeps the file on your machine, which is the safer choice for anything private.

On macOS, open the WebP file in Preview, choose File then Export, select PNG from the format menu, and save. Preview handles WebP natively on recent macOS versions. On Windows, open the file in Paint, choose File then Save as, and pick PNG; the Photos app offers a similar option. If you use an image editor like GIMP (free) or Photoshop, the process is the same: open the WebP, then export or save as PNG. These methods are ideal when you have one or a few files and want to keep everything local. They’re slower than the command line for large numbers of files, but for everyday conversions they’re more than enough and require nothing extra to install.

How do you convert WebP to PNG with the command line?

For converting many files at once, the command line is fastest, and ImageMagick is the standard tool for the job (ImageMagick). Once installed, a single command converts one file, and a short loop converts an entire folder.

To convert a single file with ImageMagick:

magick input.webp output.png

To convert every WebP file in the current folder to PNG, use a simple loop (this example is for macOS or Linux shells):

for f in *.webp; do magick "$f" "${f%.webp}.png"; done

Google also provides a dedicated WebP decoder called dwebp, which converts a WebP straight to PNG:

dwebp input.webp -o output.png

The command line has a learning curve, but for batch work it’s transformative: converting a hundred images takes the same single command as converting one. It’s also scriptable, so you can build it into an automated workflow. If you regularly handle large numbers of images, learning this one command pays for itself quickly. For occasional single files, though, the built-in apps above are simpler.

How do you convert PNG back to WebP for the web?

Since WebP is the better format for a live website, you’ll often want to go the other way too, converting PNG to WebP, and Google’s cwebp tool does exactly that (Google). The workflow of keeping lossless PNG source files and exporting WebP for the web is common, so it’s worth knowing both directions.

The cwebp command-line tool converts a PNG to WebP:

cwebp -q 80 input.png -o output.webp

The -q 80 sets quality (0 to 100); around 75 to 85 is a good balance of quality and size for most web images. ImageMagick handles it too, with the same syntax pattern as before:

magick input.png output.webp

Most modern image editors and build tools can also export or generate WebP automatically, and many content management systems now create WebP versions of uploaded images for you. The reason to bother is performance: serving WebP instead of PNG cuts the download size, which speeds up your pages and helps your Lighthouse score, as covered in our guide to improving your Lighthouse performance score. Keep PNG for your originals and editing; serve WebP to visitors.

What should you watch out for when converting?

The main thing to expect is that the PNG will usually be larger than the WebP, because PNG is lossless and less compressed (Google). That’s normal and expected, not a sign anything went wrong; you’re trading file size for compatibility and lossless quality.

A few other points are worth checking:

• Transparency. If your WebP has transparent areas, make sure your conversion method preserves the alpha channel; PNG supports transparency, but some converters flatten it.
• Quality. Converting from WebP to PNG won’t recover detail the WebP already lost if it was saved as lossy; PNG preserves what’s there, but it can’t restore what’s gone.
• Animation. Animated WebP files don’t convert cleanly to PNG, which is a static format; you’d need APNG or a GIF for animation.
• Batch consistency. When converting many files, spot-check a few outputs to confirm dimensions, transparency, and quality came through as expected.

None of these is a serious obstacle, but knowing them upfront saves confusion, especially the file-size increase, which surprises people who expect conversion to shrink the file rather than grow it.

What are common WebP-to-PNG problems and how do you fix them?

Most conversion problems come down to a few recurring causes: lost transparency, a tool that won’t open WebP, animation that doesn’t carry over, or confusion about file size (MDN). All of them have straightforward fixes once you know what’s happening.

The table below maps the common symptoms to their solutions.

When a conversion goes wrong, the quickest diagnosis is to open the result and check transparency and dimensions first, since those are the most common casualties. If a batch conversion produced odd results, convert one file manually to confirm the settings, then re-run the batch. And remember that converting can’t improve quality, it can only preserve what’s already in the file, so if the source WebP was low quality, the PNG will match it rather than exceed it.

When should you use WebP versus PNG?

Use WebP for images on the live web where speed matters, and PNG for editing, compatibility, and graphics that need guaranteed lossless quality (web.dev). They’re not rivals so much as tools for different jobs, and most workflows use both. The table below sums up the choice.

The practical pattern is to keep your working and source files as PNG (or another lossless format) for editing, then export to WebP for the live site to get the speed benefit. That smaller payload directly helps page performance, which is why image format is part of the wider work in our guide to improving Core Web Vitals and to picking the right format in image file types explained.

How does AVIF compare to WebP and PNG?

AVIF (AV1 Image File Format) is a newer image format that often compresses smaller than WebP at similar quality, making it the current cutting edge for web images, though its tooling and software support still lag WebP’s slightly (web.dev). If WebP replaced JPEG and PNG for many web images, AVIF is the format increasingly doing the same to WebP.

The practical picture is this. AVIF supports both lossy and lossless compression, transparency, and wide colour and HDR, and it typically produces smaller files than WebP for comparable quality, which is its main draw for performance. It is now supported in all major browsers, including Chrome, Firefox, and Safari (MDN). The trade-offs are that AVIF encoding can be slower, and desktop and editing-software support still trails WebP and PNG, so you would convert an AVIF to PNG for the same compatibility reasons covered above. For the live web, the common pattern now is to serve AVIF with a WebP fallback and a PNG or JPEG fallback beneath that, using the HTML <picture> element so each browser gets the best format it supports. For editing and guaranteed compatibility, PNG remains the safe choice.

How do WordPress and other CMSs generate WebP automatically?

Many modern content management systems can create and serve WebP versions of your images automatically, so you upload a PNG or JPEG and the platform handles the conversion, removing the manual step entirely. WordPress added support for uploading and serving WebP images in version 5.8 (WordPress), while automatic conversion of every upload into WebP is provided by performance plugins rather than turned on in core by default.

In practice that gives a WordPress site two routes. You can upload WebP files directly and use them like any other image, or, more conveniently, install a plugin, such as the official Performance Lab plugin’s Modern Image Formats feature, or popular options like EWWW, Imagify, or ShortPixel, that automatically generates WebP (and increasingly AVIF) versions of everything you upload and serves them to supporting browsers (WordPress). Other platforms work similarly, and many hosts and CDNs convert and serve modern formats on the fly. The upshot for most site owners is that you rarely need to convert images by hand for the web at all, the system keeps a compatible original and serves the optimised format automatically. Manual conversion, the focus of this guide, is mainly for the reverse case: getting a WebP file out of the system and into a tool that needs PNG.

Final thoughts

Converting WebP to PNG is straightforward once you match the method to the job: an online converter or built-in app for a single file, and a command-line tool like ImageMagick for batches. The key thing to expect is that the PNG will be larger, since you’re trading WebP’s compression for PNG’s lossless quality and universal compatibility. That trade is exactly why you convert: for editing, for tools that don’t support WebP, and for reliable transparency. For the live web, though, keep using WebP where you can, because its smaller files load faster. To go deeper on choosing formats and on image performance, see our guides to image file types and improving Core Web Vitals. Match the format to the task, lossless PNG for editing and compatibility, compact WebP for the live web, and conversion becomes a routine step rather than a headache.