PNGToolbox

Local batch converter

Convert PNG to WebP โ€” the reverse trip, with transparency intact

Last reviewed: 7 November 2026

Our main converter turns WebP into PNG; this page runs the route in the other direction, for the moment you decide the destination actually accepts WebP. Unlike the JPG trip, nothing has to be sacrificed: WebP keeps the alpha channel, so cutouts stay cutouts. The conversion is native browser encoding, the quality is yours to set, and every output size is measured.

PNG to WebP

Convert and verify

Conversion reportMeasured in your browser
0 files
WEBP

Your measured results appear here

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

Measured sizes

PNG to WebP at quality 80: measured on the same corpus

Same six test images, both formats, from our published benchmark. WebP at quality 80 against the PNG source:

Test image PNG source WebP at q80 Change Verdict
Product cutout1,713.1 KB20.5 KBโˆ’98.8%83.6x smaller, transparency kept
Photograph3,167.5 KB54.5 KBโˆ’98.3%58.1x smaller
UI screenshot1,082.3 KB152.8 KBโˆ’85.9%7.1x smaller
Flat artwork16.1 KB23.7 KB+47.2%WebP is larger
Logo6.3 KB8.9 KB+41.3%WebP is larger
Gradient6.9 KB9.7 KB+40.6%WebP is larger

Source: measured on 22 October 2026 with Pillow 11.0.0; raw CSV published at ./assets/bench/study-a-format.csv. WebP encodes lossily by default, so the three bottom rows are not a codec failure โ€” they are the lossless PNG format being unbeatable on exactly the content it was designed for. The honest rule: convert photos, cutouts, and screenshots to WebP; keep logos, flat art, and gradients as PNG. Our WebP vs PNG comparison works through the full trade-off, and the format decision table covers acceptance across platforms.

Settings

Choosing the quality value

WebP's quality slider behaves like JPEG's in shape but buys more per point. Between roughly 75 and 85 the file stays small while artefacts stay out of sight for photographic content; pushing toward 95 multiplies the file for changes that are hard to see at normal viewing sizes. For cutouts with soft edges, inspect the result at 100% zoom after converting โ€” the semi-transparent edge pixels are where a low quality setting shows first.

Unlike the PNG-to-JPG route, nothing is flattened here: WebP stores an alpha channel, so the queue rows still report EXIF absence and the output keeps every transparent pixel. If a browser cannot encode WebP at all, the affected rows say so and fall back to PNG rather than pretending.

Questions

PNG to WebP FAQ

Does WebP keep transparency?

Yes. WebP supports a full alpha channel, so a converted cutout remains a cutout โ€” no fill colour is involved. This is the main advantage over the PNG-to-JPG route.

Why did my logo get larger?

WebP encodes lossily by default, spending bytes to describe pixels it could have stored exactly. On flat-colour graphics a lossless PNG is already near-optimal, so the re-encode adds overhead. Keep graphics as PNG.

Does conversion improve quality?

No. Conversion changes the container and the compression; it cannot reconstruct detail. The value is in the size reduction, not in any quality gain.

Are my images uploaded?

No. Conversion runs locally in this browser with the canvas API โ€” your files are never transmitted to a server.

Which browsers accept WebP files?

Every current browser renders WebP, but upload forms, CMS builds, and desktop applications still reject it in many places. Convert for the destinations that accept it, and keep the PNG as the master copy.

Ready to convert?

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

Open the converter