Skip to content

Convert AVIF to PNG

The newest format on the web, decoded to the oldest safe one: a lossless PNG with transparency intact, which every editor, app and upload form has read for twenty-five years. Nothing stored.

  • Never stored
  • No queue, no waiting
  • No signup, no watermark

How it works

1

Add your AVIF files

Drop any number of .avif files.

2

Convert

Each is decoded to its exact pixels and written as a PNG — there is no quality setting, because nothing is lost.

3

Download

One by one, or all as a ZIP.

What a lossless target does and does not give you

Lossless means lossless from here on, not retroactively. The AVIF's compression — AV1 intra-frame coding, usually with chroma stored at quarter resolution — was applied when the file was made, and the decoder hands over the result of it. The PNG preserves that result exactly, including the soft gradients AV1 is good at and the slight smearing of fine texture it is prone to. The gain is that every edit and every save after this costs nothing further.

The alpha channel is the real reason to pick PNG over JPG here. AVIF stores transparency as a separate plane and PNG stores it per pixel; both are full 8-bit, so a soft shadow or a feathered edge survives with its gradient intact rather than being flattened onto a colour. A picture with no transparency gets an opaque PNG and the alpha channel is simply omitted.

Bit depth is where something is lost. AVIF can carry 10- or 12-bit colour and a wide gamut; the PNG written here is 8-bit sRGB, so an HDR image is tone-mapped down — a sunset that glowed on an HDR display comes out flat and no editing recovers it. Images that were 8-bit sRGB to begin with, which is nearly all of them on the web, come across without change.

When you want something else

avifdec in.avif out.png is the reference decoder and the right tool for a folder; it can also keep 16-bit output for HDR sources, which nothing in a browser canvas can. If the destination can read AVIF at all, do not convert: the original is smaller, higher quality and carries the colour the PNG cannot.

A PNG straight out of a decoder is not a small PNG. If the file is going on a website, run it through oxipng or zopflipng afterwards — they recompress without touching a pixel and routinely save a fifth of the size — or consider whether WebP lossless would serve the same purpose at half the bytes.

Frequently asked questions

When is PNG the right target, and when is JPG?

PNG when the picture has transparency, flat colour, text or line art, or when you are about to edit it and want nothing further lost. JPG when it is a photograph that only needs to be opened somewhere — the PNG of a photo is far larger. The AVIF to JPG page is the other half of this one.

Is transparency kept?

Yes. AVIF carries an alpha channel and PNG does too, so a transparent AVIF becomes a transparent PNG with the same edges.

Is anything lost?

Nothing beyond what the AVIF had already lost when it was made. PNG is lossless, so the file holds exactly the pixels the decoder produced, including any AVIF compression artefacts — which are now pixels, not artefacts.

Why is the PNG so large?

Because AVIF is around half the size of a JPEG, and PNG is several times larger than a JPEG for a photograph. A 150 KB AVIF of a photo becoming a 3 MB PNG is normal. For artwork and screenshots the gap is small.

Are my files stored anywhere?

No — nothing is stored at any point.

What about HDR and animated AVIF?

HDR is tone-mapped to standard 8-bit colour, which PNG can hold; the wide gamut does not survive. An animated AVIF converts as its first frame.

Good to know: HDR AVIF is tone-mapped to standard colour. Animated AVIF converts as its first frame. The PNG is written without a colour profile.

Put this tool on your website

Free for any blog, class page or help article. Paste one snippet and your visitors can use it right on your page.