Decoded input
The browser reads the actual WebP dimensions and file bytes. A filename alone is not treated as evidence.
Local batch converter
Choose one file or a batch, optionally resize it, then compare the decoded dimensions and measured file sizes before downloading. Files stay in this browser.
WebP to PNG
Each row reports source dimensions, output dimensions, source size, output size, and a direct download.
What is measured
The browser reads the actual WebP dimensions and file bytes. A filename alone is not treated as evidence.
The image is drawn to a canvas at the requested dimensions and encoded as PNG by default โ or as JPG at your chosen quality when you select that format.
The report uses the generated PNG blob, so the displayed size is the size of the file available for download.
Format decision
Troubleshooting
This is normal for photographic WebP files. PNG uses lossless compression and prioritizes exact decoded pixels, transparency, and broad editor compatibility rather than minimum web-delivery size.
Some viewers display transparent pixels against black. Open the PNG in an editor with a checkerboard preview or place it over a colored background before concluding that alpha was lost.
This browser tool exports the decoded still frame. It does not create animated PNG files. Keep the original WebP when animation is required.
Very large images require multiple in-memory canvases. Convert fewer files at once or resize the output. The 20 MB input limit reduces, but does not eliminate, device-specific memory limits.
Questions
Normal conversion happens locally in this browser. The tool reads selected files with browser APIs and does not need to send them to a conversion server.
No. PNG avoids adding another lossy compression stage, but it cannot reconstruct detail that is missing from the source WebP.
Yes. One width or height can be applied to the whole batch. With ratio lock enabled, each file keeps its own aspect ratio during conversion.
Yes. Choose JPG in the output format panel and set a quality level. Transparent pixels are filled with white because JPG has no alpha channel.
A conversion is not a repair. WebP is usually stored lossily: the encoder already decided which frequencies mattered and discarded the rest. Converting that file to PNG changes the container, not the contents โ the pixels you get in the PNG are exactly the pixels WebP decoded to.
Two consequences:
The file gets much larger. PNG stores the decoded pixels losslessly, so it has to describe detail the WebP encoder had already thrown away โ as well as detail it kept. On our published corpus the PNG output was 7.3x to 18.2x the size of the source WebP, depending on image type; a photograph went from 60.7 KB to 1,106.8 KB.
The image does not get better. Nothing recovers the discarded frequencies. If the source WebP looked good, the PNG looks identical and five to twenty times larger.
So the honest question is not "is PNG higher quality" but "does my destination accept WebP". That single fact decides most conversions.
Many tools and platforms still reject WebP โ older desktop editors, some content management systems, print workflows, and plenty of upload forms. When a destination accepts WebP, keeping it saves most of the file size. Convert when something requires PNG, or when you need an exact, lossless copy of the decoded image for further editing.
PNG carries an alpha channel with full 8-bit precision per pixel, and our tests found the conversion preserved every transparent pixel exactly โ 229,211 fully transparent pixels in the logo test image and 1,056,057 in the product cutout came out identical, with no pixel differing by more than 1/255.
Two caveats sit either side of that:
An animated WebP holds a sequence of frames. Pillow, browsers' canvas APIs and most converters expose only the first frame, so an animation converted by a still-image pipeline becomes a single static image. That is not a bug in the converter; it is a different file format being asked for a frame.
If the animation matters, check whether the destination accepts animated WebP or APNG before converting. If it must be a static image, choose the frame deliberately rather than accepting frame one.
| Symptom | Likely cause | What to try |
|---|---|---|
| "Unsupported file" on a WebP you did not create | The file is an animated WebP, or is truncated | Open it in a browser first; if it animates, treat it as an animation |
| Conversion succeeds, output looks washed out | Source had a colour profile browsers ignore | Compare in two browsers; the profile is the difference |
| Very large output, unexpected for the content | Source was a photograph; lossless storage of decoded pixels is expensive | Ask whether the destination needs PNG at all; if yes, resize before converting |
| Output is blank or partly grey | Decode failed part-way (corrupt or truncated download) | Re-download the source; browsers are stricter than desktop viewers |
| Colours shift after conversion, edges look noisy | The WebP was recompressed multiple times before you got it | Nothing to fix in conversion โ the damage predates it |
WebP decoding is effectively universal in current browsers, but encoding is not symmetric across platforms, and phone workflows differ in where the conversion happens:
Because the conversion on this site runs in your browser rather than on a server, the result does not depend on a queue, an account, or a file-size limit imposed by an upload form โ and your file never leaves the device.
Converting a folder is mostly a naming problem:
Source: file-size multipliers measured on 22 October 2026 with Pillow 11.0.0; raw CSV and the test corpus are published at ./assets/bench/.
Batch-convert WebP files to PNG or JPG in your browser โ measured, private, and free.
Open the converter