Unuploaded

Converter · No upload

Convert WEBP to PNG on your device

Convert WEBP images to PNG with their transparency kept.

The sample is a 240×120 WEBP made in this tab, with a translucent stripe. The PNG keeps that stripe translucent, with no background painted in.

Read here — Statusidle Files— OutputPNG Network since file read—

Undecodable WEBPs fail, with browser reasons where available, and so do images too large for the browser’s canvas, which are not shrunk to fit. One PNG per file: an animated WEBP keeps its first frame only, and the row says so. Transparency is kept. The picture is written as 8-bit sRGB pixels, an embedded colour profile is not carried, and EXIF and XMP are removed. Takes .webp.

How this converter works

The File API reads the selected WEBP into memory. A browser with WEBP support decodes its pixels and alpha, and the page draws them onto a transparent canvas. The canvas is encoded as PNG and offered as a download link. The file is processed locally, without an extra decoding library.

The site serves static pages and code and has no server-side converter or database. Its Content-Security-Policy only allows connections to the site’s own origin. The policy limits where requests can go, but it is set by the site and could change in a later version, so the methodology page describes checks you can run yourself on the loaded converter.

The PNG can be larger than the WEBP; how much depends on the image and how the WEBP was encoded. It holds the pixels as the browser decoded them into an 8-bit sRGB canvas, without the source metadata or colour profile, so keep the original WEBP if you need those.

Frequently asked questions
Is my image uploaded anywhere?
No. WEBP decoding, canvas rendering and PNG encoding all run in this browser. The network meter counts resource-timing entries from the first file read onward, which leaves out earlier page and code loads and some network channels. The methodology page explains its limits and the separate checks you can run.
Why do so many images download as WEBP in the first place?
A website can serve WEBP to make its images smaller to download; how much smaller depends on the image and its encoding. The apps and upload forms you send it to may still require another format. PNG keeps transparency and avoids another lossy encode, though the file can be larger, so check the actual size and what the recipient accepts.
Is transparency preserved?
Yes. Transparency is kept, and no white background is added. The colours of faint, nearly transparent pixels can change on the way through the browser’s decoder and canvas.
What happens with an animated WEBP?
You get the first frame as a still PNG, and the result row says so. PNG-based animation exists, but this converter does not write it, so use an animation or video tool for the full sequence.
Does converting lose quality?
Not in the PNG step, which adds no lossy compression to the pixels it is given. The browser’s decoder and canvas can still change colour, bit depth or the precision of faint pixels, so the PNG is not a bit-for-bit copy of the WEBP. Any loss already in a lossy WEBP stays.

Related tools