Does WebP support transparency?
Short answer: yes. WebP carries a full 8-bit alpha channel, so a WebP file can be partly or fully transparent exactly like a PNG. This guide explains how WebP transparency actually works at the format level, how it compares to PNG and AVIF, why a transparent WebP sometimes shows up with a white background in certain tools, and how to convert it without flattening the transparency.
Convert WebP to transparent PNG →Yes — WebP supports transparency
Yes. WebP supports 8-bit alpha transparency in both lossy and lossless modes, so a WebP image can have fully transparent, semi-transparent, and fully opaque pixels — the same per-pixel transparency a PNG provides. If a tool shows a white background instead, the tool is flattening the alpha channel, not the WebP.
How WebP transparency works
WebP stores transparency as an alpha channel: one 8-bit value per pixel, ranging from 0 (fully transparent) to 255 (fully opaque), independent of the red, green, and blue colour values. This is the same model PNG uses, which is why transparency round-trips cleanly between the two formats — every intermediate value, from a hard cut-out edge to a soft feathered shadow, has a direct equivalent. The important detail that surprises people is that lossy WebP can carry alpha too. This is the key difference from old-style JPG: JPEG has no alpha channel at all, so a "transparent JPG" is impossible and any transparent source saved as JPG gets composited onto a solid background. WebP has no such limitation. A lossy WebP compresses the colour (RGB) data with its VP8 lossy coder while storing the alpha channel separately — and that alpha plane can itself be encoded losslessly even when the colour is lossy. So you get a small file that still has clean, exact transparency. Lossless WebP, encoded with the VP8L coder, preserves both colour and alpha exactly, with no compression artefacts anywhere — the direct equivalent of a PNG. In practice, lossless WebP is the right choice for logos, icons, and flat-colour graphics with transparency; lossy WebP with alpha works well for photographic cut-outs where a small amount of colour compression near the edges is acceptable in exchange for a much smaller file.
Transparency support and typical size by format
How the common web formats handle transparency, with representative file sizes for a 1024×1024 transparent logo. Sizes are illustrative examples, not measured benchmarks — actual results depend on the image content and encoder settings.
| Format | Transparency | Alpha depth | Typical size (transparent logo) |
|---|---|---|---|
| WebP | Yes — lossy and lossless | 8-bit alpha channel | ~70 KB (lossy) / ~140 KB (lossless) |
| PNG | Yes — always | 8-bit alpha channel | ~280 KB (optimized) |
| AVIF | Yes — lossy and lossless | 8-bit alpha channel | ~52 KB (lossy) / ~510 KB (lossless) |
| JPG | No — composites onto a solid colour | None | N/A (cannot store transparency) |
When a WebP loses its transparency
A transparent WebP does not lose its alpha channel on its own — the data is in the file. What usually happens is that some tool in the pipeline cannot read WebP alpha and flattens the image onto a solid background, almost always white. The transparency is not corrupted; it is being discarded at the point of import or display. The common culprits are older or non-browser software. A WebP placed into an application that predates WebP support, opened by an image library configured to drop the alpha channel, or passed through a thumbnail generator that composites onto white will all produce the same symptom: your see-through logo suddenly sitting on a white rectangle. The same file dragged into a current version of Chrome, Firefox, Safari, or Edge will show its transparency correctly, because those browsers decode the alpha channel properly. That contrast — transparent in the browser, white background in the other tool — is the tell-tale sign that the WebP is fine and the consuming software is the problem. The reliable fix is to convert the WebP to a PNG. PNG transparency is understood by essentially every piece of imaging software ever written, so a transparent PNG sidesteps the compatibility gap entirely. Because both formats use an identical 8-bit alpha model, the conversion preserves the transparency exactly — there is nothing to lose in the round-trip.
Converting transparent WebP for tools that do not support it
When the destination is a design application, an office document, an email client, a print workflow, or any older CMS, the safe move is to convert the transparent WebP to PNG before handing it over. PNG is the universal lossless format for transparency: it opens everywhere, needs no plugins, and never silently flattens to white. The WebP to transparent PNG converter does exactly this in your browser. It decodes the WebP alpha channel value-for-value and writes it straight into a PNG, so a pixel that is alpha 180 in the WebP stays alpha 180 in the PNG. Nothing is uploaded, nothing is composited, and the transparency you put in is the transparency you get out. If you already know you need a PNG, you can skip the theory and convert directly.
Under the hood
Decoding is handled by libwebp, the reference WebP implementation from Google (github.com/webmproject/libwebp), compiled to WebAssembly. libwebp reads the WebP container, decodes the VP8 (lossy) or VP8L (lossless) colour data, and decodes the alpha plane separately, assembling a single raw RGBA pixel buffer in which every alpha value is an exact integer between 0 and 255. When you convert to PNG, that buffer is passed to oxiPNG (github.com/shssoichiro/oxipng), a Rust PNG encoder also compiled to WebAssembly. oxiPNG applies lossless DEFLATE optimization to shrink the file but never alters a pixel value, so the alpha bytes libwebp produced are copied verbatim into the PNG. Both codecs run inside a Web Worker, keeping the main thread responsive, and the entire pipeline executes on your device. Every conversion in ConvertMyPic is 100% local: no file ever leaves your browser, it is free because there are no servers to run, and after the first load it works offline as an installable PWA.
FAQ
Can WebP be transparent?
Yes. WebP supports an 8-bit alpha channel, so a WebP image can be fully transparent, semi-transparent, or fully opaque on a per-pixel basis — the same kind of transparency a PNG offers. If a transparent WebP appears with a solid background somewhere, the software displaying it is flattening the alpha channel; the transparency is still present in the file.
Does lossy WebP support transparency?
Yes. This is the key difference from JPG. A lossy WebP compresses the colour data with the VP8 coder while storing the alpha channel separately, and the alpha plane can be encoded losslessly even when the colour is lossy. So you can have a small, lossy-compressed WebP that still preserves clean, exact transparency — something a JPEG can never do, because JPEG has no alpha channel at all.
How do I check if a WebP has transparency?
Drag the WebP file into a current Chrome, Firefox, Safari, or Edge tab. If parts of the image show a checkerboard pattern or the page background shows through, the file has an alpha channel and is transparent. If the whole image is opaque with no see-through areas, it has no transparency. You can also open it in an image editor such as Photoshop or GIMP and look at the channels panel for an alpha channel.
Why does my WebP show a white background in a particular app?
Because that app cannot read WebP alpha and is compositing the image onto white when it imports or displays it. The transparency is not lost from the file — the same WebP will show correctly in a modern browser. Older design tools, some thumbnail generators, and image libraries configured to drop alpha all cause this. Converting the WebP to a PNG before using it in that app avoids the problem entirely, since PNG transparency is universally supported.
Is WebP or PNG better for transparent images?
For delivery on a modern website, transparent WebP is usually better: it carries the same 8-bit alpha as PNG at a much smaller file size, and every current browser decodes it. For everything else — design tools, office documents, email, print, older platforms — PNG is the safer choice because its transparency is understood by essentially all imaging software. A practical rule: WebP for the web, PNG when you are handing the file to a tool or a person rather than a browser.
Does converting WebP to PNG lose the transparency?
No. WebP and PNG use an identical 8-bit alpha model, so the alpha channel transfers exactly. libwebp decodes the WebP alpha to precise integer values and oxiPNG writes those same values into the PNG without compositing or rounding. A pixel that is alpha 180 in the WebP stays alpha 180 in the PNG. The whole conversion runs locally in your browser, so the file is never uploaded.
Related conversions
- Convert WebP to transparent PNG — Keep the alpha channel intact when converting a transparent WebP to PNG.
- WebP to PNG converter — Convert any WebP to PNG in your browser, transparent or opaque.
- PNG to WebP converter — Turn a transparent PNG into a smaller WebP that keeps its alpha channel.
- Image transparency guide — How alpha channels work across PNG, WebP, AVIF, and other formats.