ALL IMAGE TOOLS56
AVIF to PNG
Convert AVIF to PNG Online — Lossless, No Upload
Decode AVIF with your browser and write it back out as a lossless PNG.
About AVIF to PNG
AVIF is the AV1 codec's still-image format, and it compresses hard — often half the bytes of a JPG at comparable quality. The trade is support: plenty of desktop software, older image editors and internal tools still cannot open one. This page decodes the AVIF with your browser's own decoder and writes the pixels out as PNG. That decoder is the whole story on the input side. Nothing about AVIF is implemented here — Chrome 85+, Firefox 93+ and Safari 16.4+ ship AVIF decoding, and on a browser without it the file simply will not open and the page says so rather than producing something wrong. On the output side PNG is lossless, so nothing is discarded twice: the pixels the AVIF decoder produced are the pixels in the file you download, and an alpha channel comes through intact. That is the reason to choose PNG here rather than JPG, which would flatten transparency onto white and add a second generation of compression. The cost is size. PNG has no lossy mode, so the download will usually be several times larger than the AVIF that produced it — that is the price of not re-compressing. If you want a smaller file and can accept another generation of loss, convert to WebP or JPG instead. Batch conversion is supported, and everything runs in this tab; no file is uploaded.
Questions
Does my browser support AVIF?
Almost certainly. AVIF decoding landed in Chrome 85, Firefox 93 and Safari 16.4, which between them covers every browser still receiving updates — so if this page loaded, the decode will almost certainly work. The one way to be sure is to try the file: nothing here guesses from a version string.
Who actually decodes the AVIF — this page or my browser?
Your browser, and that is worth knowing because it decides what happens when something goes wrong. No AVIF decoder is downloaded here; the file is handed to the same image pipeline the browser uses for a page's own images. So a browser that cannot read AVIF cannot be rescued by this tool, and a file that fails here will also fail as an ordinary image on any page.
Why PNG rather than JPG?
Two reasons. PNG is lossless, so nothing further is thrown away after the decode — what you get is exactly what the AVIF decoded to. And AVIF can carry an alpha channel, which PNG can store and JPG cannot; converting to JPG flattens every transparent pixel onto white. If you do not need either property, AVIF to JPG produces a much smaller file.
Why is the PNG so much bigger than the AVIF?
Because you are moving from one of the most efficient lossy formats to a lossless one. AVIF is built on the AV1 video codec and routinely stores a photograph in a fraction of what any lossless format needs; PNG stores every pixel exactly and can only win back what deflate finds. A large increase is the expected outcome, not a fault — the page shows both byte counts so you can see the trade before you save.
Does converting to PNG improve the image?
No. Lossless output preserves what it is given; it cannot recover detail an AVIF encoder already discarded. Whatever softening or blocking is in the AVIF is in the PNG too, now stored exactly rather than compressed further. The value of PNG here is that nothing is added to it — not that anything is taken back.
Is my file uploaded to a server?
No. Transmute processes everything locally in your browser using JavaScript and WebAssembly. Your files never leave your device — there is no server, no upload, no cloud processing.