Image · 55 tools · nothing uploads

AVIF to PNG

Save 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.

Input

AVIF to PNG hands you eight bits a channel, four bytes to a pixel, whatever depth the AVIF was written at. PNG then keeps what is left exactly, alpha and all, in a file that dwarfs the AVIF. Ten and twelve bit files are flattened by the decoder before PNG is asked to store a thing.

Questions

Does a 10-bit AVIF keep its extra bit depth?

No. Decoding lands on 8-bit RGBA pixels regardless of the source bit depth, so a 10-bit AVIF is flattened to 8 bits before PNG stores anything, the same as every format in this pipeline.

What survives?

The full 8-bit color and alpha channel survive, and PNG stores them losslessly from that point on. Any HDR-specific metadata the AVIF carried does not carry across.

Which engine handles this?

jSquash decodes the AVIF and encodes the PNG, both WebAssembly, running in Node, on the command line, through MCP and in the browser without needing a browser tab specifically.

How much bigger does the file get?

Often several times bigger, since AVIF compresses aggressively and PNG has no lossy shortcut once decoding lands on raw pixels.

What is the reverse page?

There is no dedicated page. Convert image can write AVIF from a PNG source, without a page of its own for that direction.

Related Image tools