WebP → PNG

Convert WebP files to universally supported PNG. Free, no upload. 1 GB max · Up to 1 GB · Processed locally, never sent to a server.

You right-clicked an image in your browser, chose "Save image as", and ended up with a file in .webp. It displays perfectly in the tab it came from, and refuses to open in a good share of the software installed on your machine. It is not a damaged file: it is a format that sites serve to make their pages lighter, and that desktop applications adopted several years late.

This tool reads the WebP with the decoder built into your browser, redraws the image at its original dimensions in a canvas, then re-encodes it as PNG. The PNG produced is lossless: every decoded pixel is written as it stands, alpha channel included. You can drop several .webp files at once; they are handled one after another, with the name of the current file shown in the progress bar, and collected separately or in a ZIP archive.

There is no setting to adjust, and that is deliberate: a PNG has no quality slider. The only decision left to you is taken beforehand, and consists of knowing whether PNG is the right destination for your image.

How to use it

  1. Drop your WebP files The picker offers .webp only. You can add several, reorder the list with the ↑ and ↓ arrows, or remove a file with the ✕ button.
  2. Check the list before converting Each line shows the name and the size of the source file. No options panel appears, since a PNG has no quality level to set.
  3. Click Run The progress bar names the file being handled and advances as each image finishes. The total time is shown at the end.
  4. Check the resolution announced Each result gives the size of the PNG and its dimensions in pixels, for example 1280 × 720 px. It should match that of the original WebP.
  5. Download one by one or as a ZIP A button sits beside each PNG. Past a single file, the ↓ Download all (ZIP) button groups everything into one archive.

Where the .webp files nobody can open come from

WebP was created by Google in 2010 to reduce the weight of pages. Content platforms, online shops, Google Images and most publishing systems now convert the visuals handed to them. When you save an image from Chrome, Edge or Firefox, you get what the server sent, and not the JPEG the author uploaded. WhatsApp stickers also use this format.

The gap shows on the side of installed software. Older versions of Windows Explorer and of the Photos app do not display .webp files until an extension has been added from the Microsoft Store. Photoshop only opens them natively in its recent versions; before that, the WebPShop plug-in was needed. Above all, plenty of online submission forms, shop back offices and print shops list nothing but .jpg, .png and sometimes .gif.

Why aim for PNG rather than JPG

JPEG has no alpha channel. A WebP with a transparent background, a logo, a pictogram or a cut-out visual, loses its transparency as soon as it is exported to JPEG: the empty areas are filled with an opaque block of colour. PNG keeps the transparency value of each pixel, which is what this tool does, since the canvas works in red-green-blue-alpha and the export writes all four channels.

The second reason lies in the nature of the two compression schemes. JPEG cuts the image into blocks and rounds off the high frequencies; on crisp text, thin lines or areas of flat colour, that rounding leaves a halo around the edges. PNG encodes pixels without approximating them and keeps the borders clean. On top of that comes a generation effect: most of the WebP files on the web are already compressed with loss, and re-encoding them to JPEG would stack a second loss on the first.

What the conversion cannot do

The PNG obtained will almost always be heavier than the WebP it came from: the starting file was compressed with loss, the destination file keeps every pixel. If your aim was to make the image lighter, this is not the right route. Nor does the conversion restore anything, and the PNG faithfully records the artefacts left by the original compression.

An animated WebP yields only a still image, the canvas capturing a single frame. That same trip through the canvas explains why the PNG contains nothing but pixels: the EXIF blocks a WebP can carry are not copied over.

When this tool is not the right choice

If your .webp is a photograph with no transparency and you only want to open it in software that ignores the format, JPG is often a better destination: on photographic material the visible gap with PNG is nil and the file weighs a fraction as much. The Compress an image tool accepts WebP as input and offers JPG as output, with a quality slider and the MozJPEG codec.

Nor should you make PNG a staging post before another compression. If your image is going to end up published on a site, the WebP you already hold remains the best suited.

Frequently asked questions

Why is my PNG heavier than the original WebP?

Because it throws nothing away. A WebP served by a site is almost always compressed with loss, whereas the PNG records every decoded pixel without approximation. The gap can be large on a photograph.

Does the conversion improve the sharpness of the image?

No. The PNG copies what the WebP decoder produced, including the blocks and the smoothing left by the original compression. No lossless format rebuilds information that has already been discarded.

My animated WebP gives only a still image, is that normal?

Yes. The image is drawn in a canvas, which holds a single frame, and the PNG produced is static. To keep the movement, keep the WebP as it stands.

Can I drop an AVIF or a JFIF into this zone?

The picker filters on .webp, but drag and drop does not: if your browser can display the file, a PNG will come out of it. Otherwise a message says the file is not an image your browser can read.

Is the metadata carried over into the PNG?

No. The image passes through a canvas, which carries nothing but pixel values. The PNG delivered holds no date, no camera, no coordinates and no colour profile.

Does the conversion need a connection?

WebP decoding and PNG writing rely on functions built into the browser, with no component to download. Only the ↓ Download all (ZIP) button fetches the JSZip library, which the site hosts itself, at the moment you click.

Does a WebP with a transparent background keep its transparency as a PNG?

Yes. The image is drawn in a canvas that works in red-green-blue-alpha, and the export writes all four channels, so the transparency value of every pixel is carried over intact. That is the main reason to aim for PNG rather than JPG, which has no alpha channel and fills the empty areas with an opaque block of colour.

How many WebP files can I convert at once?

There is no cap on the number and no account or quota, because nothing is uploaded: each image is decoded and re-encoded inside the tab, one after another, with the name of the current file shown in the progress bar. Past a single file, the ↓ Download all (ZIP) button groups the results into one archive. Individual files are accepted up to 1 GB, with a warning past 400 MB, and the real ceiling is the memory of the device, since each image is decoded at full size before being written out.

The image I saved from a website is a .webp that nothing on my PC will open. What do I do with it?

Drop it into this page: the browser that displayed the file can decode it, and the PNG that comes out is accepted by Windows Photos, by Photoshop and by submission forms that list nothing but .jpg, .png and sometimes .gif. The file is not damaged: sites serve WebP to make their pages lighter, and desktop software adopted the format several years late. If the image is a photograph with no transparency, the Compress an image tool takes WebP in and gives JPG out, for a fraction of the weight.

Similar tools

Discover other tools

Categories