Convert WebP to transparent PNG — alpha channel preserved
Not every WebP is a photograph. Logos, icons, UI sprites, and product cutouts carry an alpha channel that defines exactly which pixels are transparent. Drop a transparent WebP here and every semi-transparent edge, soft shadow, and fully invisible pixel survives intact in the output PNG — no flattening, no white fill, no quality loss on the alpha data.
Convert to PNG →Why convert WebP to transparent PNG?
Transparent WebP files are ideal for the web — compact, widely supported in modern browsers, and capable of carrying a full alpha channel. The trouble starts the moment you need to use that asset anywhere else. Commercial printers reject WebP. Print-on-demand services have never heard of it. Figma, Sketch, Affinity Designer, and Adobe Illustrator all accept PNG natively and handle its alpha channel without any configuration. Enterprise DAM systems, headless CMS platforms, and email marketing tools are in the same camp: they expect PNG for transparent assets and either reject WebP or silently flatten the transparency to white. A transparent PNG is also the most portable archival format for graphics with alpha — every operating system can thumbnail it, every image editor can open it, and every file manager can preview it correctly. Converting your transparent WebP to PNG gives the asset a passport that works everywhere, not just in a browser tab.
What you lose and what you gain — transparency edition
PNG is a lossless format, which means every pixel value in the output — including every alpha channel value — is a bit-for-bit copy of what the WebP decoder produced. A pixel that is 73% opaque in the source WebP will be exactly 73% opaque in the PNG. Feathered edges, gradual drop-shadows, and partially transparent gradients all survive without rounding or thresholding. What you do not recover is any detail that the original WebP encoder discarded if the source was a lossy WebP. Most transparent WebP assets — logos, icons, vector exports — started as lossless WebP (the VP8L variant), so the round-trip is mathematically perfect in those cases. The cost is file size: PNG's DEFLATE compression is less efficient than WebP's algorithms, so a 78 KB transparent WebP logo typically becomes 210–280 KB as an optimized PNG. That's a real trade-off. For transparent assets served over the web, it matters. For transparent assets going to print, a design tool, or an archive, it is irrelevant — you want the alpha fidelity, and PNG gives it to you unconditionally.
How to convert WebP to transparent PNG
The entire conversion runs locally inside your browser using WebAssembly. Your transparent WebP never leaves the device — no upload, no account, no waiting for a server:
- Click "Convert to PNG →" above, or drag your transparent WebP directly onto the drop zone on the homepage. Both paths route to the same in-browser engine.
- The tool decodes your WebP using libwebp — Google's reference WebP decoder, compiled to WebAssembly via Emscripten. libwebp unpacks both the color channels and the alpha channel into a raw RGBA pixel buffer. Every transparent and semi-transparent pixel is decoded exactly as the WebP specification defines it.
- The RGBA buffer — alpha channel completely intact — is handed to oxiPNG, a Rust-based PNG encoder and lossless optimizer also compiled to WebAssembly. oxiPNG writes a standard RGBA PNG file, preserving every alpha value without any compositing, flattening, or threshold cutoff.
- Click the download button. Your transparent PNG saves to the Downloads folder with the original filename and a .png extension. Open it in any PNG-capable application — Figma, Photoshop, a browser tab — and the transparent regions will render as transparent.
- Need tighter compression without sacrificing any alpha fidelity? Open /convert directly and raise the oxiPNG optimization level toward 6. The alpha channel is losslessly preserved at every optimization level; higher levels only adjust DEFLATE parameters to shrink the file further.
File size comparison: transparent WebP vs transparent PNG
Measurements from two common transparent-asset scenarios. WebP sources were encoded at quality 90 using cwebp with alpha compression enabled. PNG output used oxiPNG at optimization level 6.
| Source | Format | Mode | File size |
|---|---|---|---|
| 1024×1024 transparent logo | WebP q90 | Lossy color + alpha channel | ~78 KB |
| 1024×1024 transparent logo | PNG (unoptimized) | Lossless RGBA | ~280 KB |
| 1024×1024 transparent logo | PNG (oxiPNG level 6) | Lossless RGBA, optimized | ~210 KB |
| 1920×1080 transparent overlay | WebP q90 | Lossy color + alpha channel | ~290 KB |
| 1920×1080 transparent overlay | PNG (oxiPNG level 6) | Lossless RGBA, optimized | ~1.4 MB |
When transparent WebP is the right choice — and when PNG wins
Transparent WebP is a genuinely better format for the open web. A 78 KB transparent WebP served to Chrome and Safari users is meaningfully faster than a 210 KB PNG, and both browsers have supported WebP alpha since 2014. If you control the full delivery pipeline — a modern website, a mobile app, a CDN that serves correct MIME types — and your analytics confirm you have negligible traffic on browsers that predate WebP support, staying on transparent WebP is the right call for page-speed reasons. PNG is the right choice in every other context. Print workflows universally accept PNG and frequently reject WebP. Design collaboration is another clear case: Figma, Sketch, Photoshop, and Illustrator all handle PNG alpha channels with zero friction, while WebP support in those tools ranges from partial to nonexistent. Legacy CMS and DAM integrations are a third case: many older systems store assets as uploaded and serve them unchanged, so a WebP that looks fine in Chrome may arrive broken for visitors on Firefox 60 or Internet Explorer. Email is perhaps the strongest case: transparent PNGs render correctly in every email client that supports HTML email, while WebP in email is effectively unsupported across Gmail, Outlook, Apple Mail, and most mobile clients. The transparent alpha channel itself is never the deciding factor — both formats carry it equally well. The deciding factor is always the destination: choose transparent WebP for the web, transparent PNG for everything else.
Under the hood: which codecs handle the alpha channel
WebP decoding uses libwebp, the reference implementation of the WebP standard developed at Google. The WASM build originates from chromium.googlesource.com/webm/libwebp. libwebp handles all three WebP variants: VP8 lossy (no alpha), VP8L lossless (alpha encoded in the lossless stream), and VP8X extended format (lossy color data plus a separately compressed alpha plane). The separately compressed alpha plane in VP8X is the most common form for transparent WebP files in the wild — logos and icons are typically encoded as lossy-color-plus-alpha. libwebp decodes the alpha plane fully, producing an exact integer alpha value for every pixel in the RGBA output buffer. PNG encoding uses oxiPNG, a Rust rewrite of OptiPNG, maintained at github.com/shssoichiro/oxipng. oxiPNG applies DEFLATE-level tuning — filter-type selection, Zopfli compression — to reduce file size without changing a single pixel value. The alpha channel byte sequence written to the PNG file is identical to the alpha data libwebp placed in the RGBA buffer. The pipeline: libwebp → raw RGBA pixel buffer → oxiPNG → transparent PNG file. Both run in a Web Worker so the browser UI stays responsive during large conversions.
FAQ
Will my transparent WebP really stay transparent as a PNG?
Yes. The alpha channel is decoded by libwebp and passed into oxiPNG without any compositing, white-fill, or flattening step. Every pixel that was transparent in the WebP — whether fully transparent at alpha 0 or partially transparent at any value from 1 to 254 — will be represented with the same alpha value in the output PNG. Open the result in a browser tab or any tool that renders alpha as a checkerboard; the transparent regions will appear transparent.
Are semi-transparent (partial alpha) pixels preserved?
Yes, completely. PNG stores alpha as an 8-bit channel (values 0–255), identical to WebP's RGBA representation. A pixel with alpha 128 (roughly 50% opaque) in the WebP will have alpha 128 in the PNG. Soft drop-shadows, feathered selection edges, smooth gradients from opaque to transparent, and anti-aliased text all survive without rounding or clipping. The conversion is bit-for-bit faithful on the alpha channel.
Does the conversion preserve the full alpha channel?
Yes. oxiPNG encodes the alpha channel losslessly — the optimization pass only adjusts DEFLATE compression parameters and filter types. It does not quantize, threshold, or otherwise modify pixel values. The alpha channel in the output PNG is an exact copy of what libwebp decoded from the WebP source.
Will the alpha channel be preserved on a lossless WebP?
Absolutely, and the round-trip is mathematically perfect in that case. Lossless WebP (VP8L) stores color and alpha data without any lossy compression. When libwebp decodes a VP8L file, the RGBA pixel buffer it produces is exactly the original image data. oxiPNG then encodes that buffer to PNG losslessly. The resulting PNG is pixel-for-pixel identical to the original image — including every alpha value.
Do my files get uploaded anywhere?
No. The entire conversion runs in your browser using WebAssembly. You can verify this yourself: open your browser's Network tab, start a conversion, and watch the requests. You will see zero outbound requests beyond the initial page load. There is no upload server — the compute happens entirely on your CPU, using the same libwebp and oxiPNG WASM modules served once from a CDN on first visit.
Is this free? What is the catch?
There is no catch. The tool operates no servers — your browser does all the work. Hosting cost is a static file CDN, which is essentially zero. There is no business model that requires charging users or monetizing file data, so the tool is free with no file-count limits, no watermarks, and no signup wall.
Can I convert multiple transparent WebP files at once?
The current one-file-at-a-time flow works best for individual assets. For batch transparent WebP conversion today, open /convert in multiple browser tabs and process files in parallel — each tab runs an independent WASM instance. True batch processing with a queue is on the roadmap.
Does this work offline?
Yes. After the first page load, the service worker caches the app shell and both WASM modules (libwebp and oxiPNG). Subsequent visits work with no network connection at all. The PWA is installable on desktop and mobile, which makes it available from your dock or home screen — useful for workflows where you frequently need to convert transparent WebP assets.
Why is the transparent PNG so much larger than the transparent WebP?
WebP uses more sophisticated compression than PNG's DEFLATE. For transparent content, WebP can represent the same pixels in roughly one-quarter to one-third the bytes a PNG needs. oxiPNG level 6 compresses as tightly as the PNG format allows, but it cannot close that gap — PNG's design predates WebP's compression research by about 15 years. The file size increase is a real cost. For transparent assets delivered over the web, it matters. For assets going to print, a design tool, or a CMS, it does not — those destinations care about compatibility and alpha fidelity, not byte count.
How do I know if my WebP has an alpha channel at all?
Drag the WebP into a browser tab (Chrome or Firefox). If you see a checkerboard pattern behind parts of the image, the file is transparent and has an alpha channel. If the background renders as solid white or a solid color, the WebP is opaque — it may still be worth converting to PNG for compatibility, but the alpha-channel preservation question does not apply. The converter handles both cases: opaque WebPs produce opaque PNGs, transparent WebPs produce transparent PNGs.