WebP → PNG
Converting locally — nothing is uploaded
Into the editor of your choice — free, and finished on your machine.
Drop your WebPs in the drum
or — nothing leaves this tab
READS JPG · PNG · WEBP · GIF · BMP · SVG · AVIF
CYCLE →
WASH TEMP
OUT OF ORDER — JAM REPORT
The WebP → PNG cycle
A surprising number of desktop editors, scientific tools and older plugins still refuse WebP on import. PNG opens everywhere and loses nothing.
Transparency survives the cycle: both stocks carry a full alpha channel. PNG is lossless, so weight follows content — graphics shrink, photos grow. Either way, re-encoding through the canvas collects EXIF like lint — camera model, GPS coordinates and timestamps are stripped from the folded copy.
Need the other direction? PNG → WebP · Other routes into JPG → PNG, GIF → PNG, BMP → PNG, SVG → PNG.
Questions at the counter
Is WebP to PNG lossless?
Yes. PNG is a lossless container, so the copy preserves the WebP exactly as decoded — no second generation of compression, ever.
Why is the PNG so much larger?
Because it refuses to throw information away. WebP’s clever prediction and arithmetic coding collapse the same pixels far smaller. Treat the PNG as a working copy for editing, not for storage.
Does transparency survive?
Perfectly. Both formats carry full alpha channels, so every soft edge arrives exactly as it left.
Is the conversion really private?
Yes — architecturally. This page is static files; there is no server to receive an upload. Your WebP is decoded and re-encoded inside this tab by your own machine, and you can watch the absence of network traffic in your browser’s developer tools.