AVIF to PNG Converter
The route to take when the .avif has a cut-out in it, or when a second round of compression is not something you can accept.
JPEG has no transparency, so transparent areas are filled with this color.
Everything runs locally in your browser. Nothing is uploaded to any server — close the tab and your files are gone.
How to convert AVIF to PNG
Add the .avif files
PNG is preselected as the output, so nothing needs setting before you start. One file or a folder full of them behaves the same way, and every row reports its own size before and after.
Look at whether the image has a cut-out
AVIF stores transparency, and images pulled off a modern site often use it. That is the reason to choose PNG rather than JPG here: the alpha channel is decoded and written straight into the PNG, with no background colour to pick and nothing composited underneath.
Decide whether this is a working file or a delivered one
The answer changes what you should pick. A file you are about to open in an editor wants PNG, because nothing further is lost each time you save. A file that is simply going onto a page is better served by WebP, which keeps the transparency at a fraction of the weight — the format picker switches without reloading anything.
Use the resize control as your only size lever
A lossless output has no quality setting to lean on, which leaves the dimensions. The longest edge can be fitted to 4096, 2048 or 1024 px before the PNG is written, and anything already under the target is left exactly as it is.
Hand the PNG to whatever refused the AVIF
Download the rows individually, or together as a ZIP once several have finished. The pixel dimensions and the colours are unchanged, so what arrives in the other program is the same picture in a format it has read for decades.
Why PNG is the cautious way out of AVIF
The cut-out survives the trip
This is the real difference between sending an AVIF to PNG and sending it to JPEG. JPEG has no alpha channel, so transparent pixels must be painted onto a solid colour before it can encode them at all. PNG keeps the alpha channel: fully transparent, semi-transparent and opaque pixels all arrive as they were, which is what a logo, an icon or a product shot on no background actually needs.
Nothing is compressed a second time
The AVIF came out of a lossy encoder and whatever it dropped is long gone, but the conversion itself adds nothing on top. The decoded pixels go into the PNG untouched, so what you look at afterwards is exactly what the AVIF decoded to. Send the same picture to JPEG or WebP instead and a fresh round of loss lands on top of the old one.
Eight bits per channel, whatever the AVIF was holding
AVIF can store 10 or 12 bits per channel and carry HDR signalling; the pipeline here moves every image through an 8-bit-per-channel buffer between the decoder and the encoder, so that extra precision is not represented in the PNG. On ordinary web images nobody will see the difference. On a graded master or a wide-gamut export, banding can appear in long gradients — export from the original file in that case rather than converting a delivery copy.
This is the format to be in before editing starts
If the picture is going to be opened, adjusted, cropped and saved a few times, the question is not which format is smallest but which one stops decaying. PNG is that format: every save writes the same pixels again. Do the editing on the PNG and publish a WebP or an AVIF from the finished result, rather than re-saving a lossy file over and over.
A much larger file is the expected result
AVIF is one of the most efficient formats in use and PNG does not compress photographic content in that sense at all, so the PNG is normally several times the size — more again for a big photograph. Each row labels its own result with the real number. When size is the point rather than compatibility, the AVIF you already have is the better file to keep. Making a fresh AVIF from the PNG afterwards costs minutes rather than seconds, which our AVIF speed measurements puts numbers to.
AVIF to PNG — frequently asked questions
Does the transparency in my AVIF survive as a PNG?
Yes. The alpha channel is read out of the AVIF and written into the PNG unchanged, so soft edges and semi-transparent pixels look the same afterwards. No background colour is applied, and no swatch appears — that control only exists for JPEG output.
Should I convert my AVIF to PNG or to JPG?
PNG when the image has transparency, or when it is going to be edited and re-saved: it is lossless, so nothing is added on top of what the AVIF already lost. JPG when the file has to be small or the destination takes nothing else. There is a page for that route as well, and the format picker above the queue switches between them at any time.
What happens to a 10-bit or HDR AVIF?
It comes through at 8 bits per channel. Every image on this site passes through an 8-bit-per-channel pixel buffer between the decoder and the encoder, so extra precision an AVIF may carry is not represented in the PNG. On ordinary web images this is invisible; for graded or wide-gamut masters, export from the original file instead.
Why can my browser show the AVIF when nothing else can?
Browsers took the format on well ahead of everything around them. Desktop editors, older operating-system previews, print workflows and upload forms with a fixed extension list all trail behind, which is how a file that displays perfectly in a tab opens nowhere else on the same machine.
Can I turn the PNG back into an AVIF afterwards?
You can — AVIF is in the format picker — but understand what you would get. It would be a fresh lossy encode of pixels that an AVIF encoder had already been through once, not the file you started with. If you still have the original .avif, keep using that; the round trip only costs you.
Will an animated AVIF come through as an animation?
No. This page writes a single still PNG and there is no animated-PNG output, so a frame is the most you get. If the movement matters, keep the AVIF or go back to whatever it was made from.
Is there a size limit on the images I can convert?
No fixed one, but there is a practical ceiling: an image has to exist in memory as raw pixels while it is being worked on, which costs roughly four bytes per pixel regardless of how small the AVIF was on disk. A very large photograph can therefore fail with an out-of-memory error on a modest device, and resizing on the way through is the way around it.
Does the AVIF get sent to a server to be decoded?
No. The AVIF decoder and the PNG encoder are both WebAssembly modules running inside this tab. The page reads the file from your disk and nothing is transmitted, so there is no server-side copy to worry about afterwards.