anytools
Image · 55 tools · nothing uploads

PNG to WebP

Re-encode a PNG as WebP. The alpha channel survives and the losslessness does not, because quality defaults to 80 and text edges are redrawn.

Input

Options

PNG to WebP keeps every pixel's transparency, which is why a logo or a screenshot with a see-through background survives the trip. What does not survive is the PNG's exactness. At the default quality of 80 this encoder is lossy, thin text edges soften first, and no setting here writes a lossless WebP.

Questions

Does the picture stay lossless?

No, not at the default settings. This tool writes the WebP at quality 80, its lossy mode, trading PNG losslessness for a smaller file.

What survives and what does not?

The alpha channel survives, since WebP supports transparency the same way PNG does. Exact pixel fidelity does not survive at quality 80; fine text edges and flat color boundaries come out slightly softer than the source. Metadata is dropped in the decode and re-encode pipeline.

Which engine runs this, and where?

jSquash decodes the PNG and encodes the WebP, both through WebAssembly, running identically in Node, on the command line, through MCP and in the browser. Raising the quality option toward 100 gets closer to the source without ever becoming truly lossless.

What size should I expect?

Usually smaller, since PNG stores every pixel exactly and lossy WebP throws some of that away on purpose at quality 80. A screenshot full of flat color and text can stay close in size, since that content compresses worst under a lossy codec.

What is the reverse page?

WebP to PNG runs the opposite direction and produces a lossless file again, though it cannot bring back anything the quality setting on this page discarded.

Related Image tools

n→nHEIC to JPGTurn an iPhone HEIC photo into a JPG for Windows and for upload forms. There is no way back: nothing here writes HEIC, and no encoder exists.Runs on each file you dropn→nPNG to JPGFlatten a PNG into a JPG. Transparency has nowhere to go and arrives as a solid block, and hard edges are the exact thing JPEG rings around.Runs on each file you dropn→nJPG to PNGRewrite a JPG as a lossless PNG. Every block edge and ring the JPEG already baked in is copied across exactly, in a much larger file.Runs on each file you dropn→nWebP to JPGTurn a WebP into a JPG. Any alpha is flattened onto a background nobody picked, and a lossy WebP is put through a second lossy encoder.Runs on each file you dropn→nJPG to WebPRe-encode a JPG as WebP. The old compression artefacts are picture now, so the WebP encoder spends bits keeping them rather than clearing them.Runs on each file you dropn→nWebP to PNGStore a WebP as a lossless PNG. The transparency survives, so do the details WebP already discarded, and the file grows several times over.Runs on each file you dropn→nAVIF to JPGOpen an AVIF as a JPG. The same picture costs several times more bytes here, because JPEG needs them to look the way the AVIF looked.Runs on each file you dropn→nAVIF to PNGSave an AVIF as a PNG. Decoding lands on 8-bit RGBA first, so a 10-bit AVIF is flattened before PNG stores the result losslessly.Runs on each file you drop