PNGToolbox

Local batch converter

Convert WebP to PNG and inspect the real output

Last reviewed: 8 October 2026

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

Convert and verify

Conversion reportMeasured in your browser
0 files
PNG

Your measured results appear here

Each row reports source dimensions, output dimensions, source size, output size, and a direct download.

What is measured

A result you can check, not a promised conversion

01

Decoded input

The browser reads the actual WebP dimensions and file bytes. A filename alone is not treated as evidence.

02

Rendered output

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.

03

Measured output

The report uses the generated PNG blob, so the displayed size is the size of the file available for download.

Format decision

When PNG helps and when it does not

Need transparency in office or design softwarePNG is usually the safer compatibility choice.
Need a smaller photo for a websiteKeep WebP. PNG can be several times larger for photographs.
Need crisp logos, diagrams, or screenshotsPNG preserves the decoded pixels and sharp edges without another lossy pass.
Need to recover detail already lostConversion cannot restore information removed by earlier compression.

Troubleshooting

Why a converted PNG may look or behave differently

PNG is much larger

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.

Transparency looks black

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.

An animated WebP becomes still

This browser tool exports the decoded still frame. It does not create animated PNG files. Keep the original WebP when animation is required.

The browser runs out of memory

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

WebP to PNG FAQ

Are my images uploaded?

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.

Does conversion improve quality?

No. PNG avoids adding another lossy compression stage, but it cannot reconstruct detail that is missing from the source WebP.

Can I resize a batch?

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.

Can I output JPG instead?

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.

What actually changes when a WebP file becomes a PNG

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.

Before you convert, check the destination

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.

Transparency: what survives and what does not

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:

  • If the WebP file itself stored a lossy alpha channel (WebP can compress alpha independently), the alpha you get in the PNG is the alpha WebP decoded to โ€” accurate to the source file, not to the original artwork.
  • JPEG has no alpha channel at all, so exporting a transparent image as JPEG flattens it onto a matte colour. Any transparent region becomes solid, usually white, and semi-transparent edges take on a visible fringe.

Animated WebP is not animated PNG

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.

Why conversions fail, and what to do

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

Device differences worth knowing

WebP decoding is effectively universal in current browsers, but encoding is not symmetric across platforms, and phone workflows differ in where the conversion happens:

  • On Android, the file system and the share sheet often pass WebP through without conversion; the practical route is a browser-based converter rather than an installed app.
  • On iPhone, Safari and Files handle WebP for viewing; saving a WebP to Photos may keep it as-is, and sharing it to an app that expects JPEG triggers a silent conversion with loss.
  • On desktop browsers, converting in a page gives the same encoder across platforms, which makes the output more predictable than asking three different operating systems to save the same file.

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.

Batch conversions, and keeping them tidy

Converting a folder is mostly a naming problem:

  1. Convert in one pass, with output names derived from the input names rather than generic counters.
  2. Keep the originals. A lossless conversion cannot improve the image, but it can change how later tools treat it.
  3. Spot-check the largest two outputs at 100% โ€” the biggest files are where an unexpected colour profile or a stray alpha channel shows up first.
  4. If the destination has a byte limit, resize before converting rather than converting and then compressing: the second compression throws away detail you just paid five times the bytes to keep.
7.3x to 18.2xPNG output vs WebP source
100% of pixelsAlpha preserved
first frame onlyAnimated WebP->PNG
your deviceWhere it runs

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/.

Ready to convert?

Batch-convert WebP files to PNG or JPG in your browser โ€” measured, private, and free.

Open the converter