Convert WebP images to PNG in your browser — alpha channel preserved, optional opaque flattening, no upload.
Drop a WebP to convert it to PNG — locally, with transparency intact
Conversion runs entirely in your browser using canvas. Your image is never uploaded. PNG is lossless, so the output is almost always larger than the WebP source — that is expected, not a bug.
WebP is the better web format: it beats JPEG on size at equal quality and, unlike JPEG, supports a real alpha channel. The problem is everything around the web. Desktop publishing suites, print pipelines, older Office builds, medical and legal document systems, and a long tail of image editors still refuse .webp or import it wrong. That is why “WebP to PNG” is a permanent, high-volume task rather than a one-off migration. PNG is the safe target because it is lossless and universally accepted — but be clear-eyed about the trade: PNG re-encodes every pixel with lossless deflate, so a 200 KB photographic WebP routinely becomes a 2 MB PNG, and a 4K screenshot can grow tenfold. That size increase buys compatibility and repeatable round-trips, not quality — the conversion itself loses nothing. Two options matter in practice: preserving transparency (the default here, correct for logos and UI assets) and flattening onto white (needed when the destination cannot handle alpha and would otherwise render your transparent regions as black).
Alpha is preserved by default; flatten onto white only when the destination cannot handle transparency.
A designer delivers a transparent logo as WebP, but the print vendor's software refuses the format.
To convert WebP to PNG: drop your image in and download the PNG — transparency is preserved by default, with an option to flatten it onto white.
FreeToolHub WebP to PNG is a free browser-based tool that converts WebP images to PNG while preserving the alpha channel, no signup, no upload.
Convert WebP to PNG online free. Transparency preserved by default, optional white flattening for pipelines that cannot handle alpha, and max-edge downscaling. Runs in your browser - no upload, no signup, no watermark.
WebP won the technical argument: it beats JPEG on size at equal quality and, unlike JPEG, supports a real alpha channel. What it did not win is the ecosystem around the web. Desktop publishing suites, print pipelines, older Office builds, medical and legal document systems, and a long tail of image editors still refuse .webp files or import them incorrectly. That gap is why WebP-to-PNG remains a permanent, high-volume task rather than a one-off migration, and why the safe target is PNG rather than another modern format with the same compatibility problem.
PNG re-encodes every pixel with lossless deflate, so file size grows substantially — typically 3x to 10x depending on content. Screenshots and logos with flat colors compress relatively well; photographs do not. Before converting, ask whether the destination actually needs lossless. If it just needs something it can open, a max-edge downscale often matters more than the format: halving the width cuts PNG size roughly fourfold while keeping plenty of detail for screen use.
Preserving alpha is correct whenever the PNG will be placed on a colored or image background — logos, badges, UI captures, product cutouts. Flattening onto white is correct when the destination cannot handle transparency and would otherwise render those regions black, which is common in older print RIPs, some CMS thumbnailers, and document pipelines. The wrong choice is reversible but annoying: a flattened PNG cannot have its transparency reconstructed, so re-convert from the original WebP rather than from the flattened PNG.
Yes, by default. PNG supports a full alpha channel and the conversion preserves it, so logos, icons, and UI exports keep their transparent backgrounds. If your destination cannot handle alpha and would render transparent regions as black, tick "Flatten transparency onto white" to bake in an opaque white background instead.
Because PNG is lossless. A photographic WebP at 200 KB routinely becomes a 2 MB PNG, and a 4K screenshot can grow tenfold. That is the expected trade, not a bug: you are buying universal compatibility and the ability to re-edit without generational loss. To keep the size down, set a max-edge limit before converting.
No — and this is the most common misconception. PNG cannot add detail that the WebP does not contain. If the WebP was saved lossily at low quality, the PNG preserves those artifacts faithfully. What PNG does guarantee is that no further quality is lost in this conversion or in later edits.
This tool outputs a still PNG, so an animated WebP converts using its current decoded frame. Animated WebP is a sequence of frames; PNG is a single still image with no animation support. For motion, keep WebP or convert to GIF or video instead.
No. Decoding and encoding happen in your browser using canvas. The file never leaves your device, which makes this safe for client logos, unreleased assets, and anything under NDA.
What do you call a nosy pepper?
No signups, no data sold. Every tool is free to use — the free tier allows 5 downloads or saves per day, and the optional Pro plan ($7/mo, $59/yr) adds unlimited downloads, batch processing, white-label exports and an ad-free experience.
☕Support me on Ko-fi— support the free tier100% of proceeds go towards hosting & building more free tools.