AVIF to PNG

Drop AVIF images and get PNG copies back in this tab. Your browser decodes the AVIF — no library, no upload — and the PNG is written from those decoded pixels, so nothing is compressed a second time. PNG keeps the alpha channel, which is the whole difference from a JPG: a transparent AVIF comes out transparent, not painted onto a white card.

Drop AVIF images here

or choose files · up to 30 at a time · still or animated · 8-bit, 10-bit or tiled

AVIF in, PNG out · still, animated, tiled or 10-bit AVIF · up to 30 files per batch · alpha kept · no upload · no account · no watermark

AVIF to PNG: What You Buy Is Predictability, Not Quality

The PNG this page writes is not a better picture than the AVIF. It is the same picture, frozen. On a 1600 × 1200 photo, the AVIF going in was 204,487 bytes and the PNG coming out was 3,179,872 — 15.5 times larger — and when both files were decoded side by side, 0 of 1,920,000 pixels differed and the alpha channel matched on 100% of them. Nothing was improved. Nothing was lost either, which is the part that matters: the PNG is exact with respect to what the decoder produced, and it will stay exact no matter how many times a different program opens and re-saves it.

That is a real thing to pay 15 times the bytes for, and it is the only thing this page is selling. If you wanted a smaller file, the conversion you want runs the other way — AVIF to WebP is the size-oriented direction, and its measurement says plainly that WebP usually loses that fight against AVIF.

A PNG decides nothing, it records

AVIF is a codec with choices: it can throw away detail it thinks you will not see, and different encoders make different choices. PNG is a container with almost no choices — eight bits per channel, a deflate stream, and the pixels you handed it. Converting from one to the other fixes the image at whatever the decoder decided.

The test above is the check: decode the source AVIF, decode the output PNG, compare pixel by pixel. The maximum difference on opaque pixels was 0, on all 1,920,000 of them. On the 600 × 400 file with an alpha channel, the alpha comparison came back exact on every one of the 240,000 pixels as well. So the honest description is "the same pixels in a container that cannot drift" — not "higher quality", and not "restored detail".

Why the file is 15 times bigger

A photograph is mostly noise from an encoder's point of view, and AVIF spends its bits on the parts a viewer notices. PNG spends bytes on the parts deflate cannot predict, which for photographic detail is nearly everything. 204,487 bytes became 3,179,872; the ratio near 15.5 is what you get when a lossy codec meets a lossless one on the same photograph, and it is not a defect of this page.

Two smaller files behaved the same way: the 2,257-byte AVIF with transparency became a 30,263-byte PNG (13.4×), and a 400-byte 10-bit gradient became 9,518 bytes (23.8×). Flat areas compress well in both formats, so the ratio moves around — what does not move is the direction.

The alpha channel is why this page exists

The 600 × 400 test file had 116,186 fully transparent pixels out of 240,000 — 48% of the image. All 116,186 were still transparent after conversion, and the file reports 58% of sampled pixels carrying partial alpha. A JPG cannot do that at all: it has no alpha channel, so the same conversion on the AVIF to JPG page has to paint those pixels onto a matte colour you choose.

This is the test to run before choosing an output format. If the picture has soft edges, a transparent background or a cut-out subject, PNG keeps all of it and JPG throws it away by design. If the picture is a rectangle of photograph, PNG keeps something you will never look at.

10-bit in, 8-bit out

The gradient test file's container reports a 10-bit source (bits: 10 in the panel), and this page writes 8 bits per channel — that is what a canvas gives back to any browser tool, and what the PNG that comes out contains. The visible consequence is banding on very smooth gradients: 1,024 levels per channel became 256.

It is worth knowing what this is not. It is not the AVIF being damaged, and the PNG is not "worse than the file you gave it" in the way a re-compression would be — it is a precision ceiling that PNG-in-a-browser has, applied once, exactly. If you need 16-bit PNG, this page is not the route; a desktop converter that writes 16-bit output is.

What survives and what does not

The panel reads each file's container before converting, so the card tells you what was inside: brand, bit depth, frame count, tiled (grid) AVIF, Exif present. What comes out is only ever the pixels of the first frame — an animated AVIF (the 480 × 270 test file carries 42 frames) becomes one still PNG, and the card says so. Exif stays in the original file; a canvas has no way to write it back, so the PNG carries no capture date, camera model or GPS position.

How to convert AVIF to PNG here

1. Add the AVIFs. Drop them on the box above or choose files — up to 30 at a time, 100 MB and 100 megapixels each.
2. Wait for the cards. Each file converts as it is added; the card shows the pixel size, the ratio, and in → out with the percentage.
3. Download. Each card has its own link; the button under the panel packs the whole batch into a ZIP built in this tab.

What each control does

There are none, and that is deliberate. PNG has no quality setting, so a quality dial would be theatre; alpha is kept rather than flattened, so a matte picker would be a lie. The two things you can set are which files go in and how many, and the note under the panel says what the output is: 8 bits per channel, same dimensions as the source, alpha kept as alpha.

Why this page doesn't upload your AVIF

The AVIF decoder ships with the browser — no library, no WASM, no server. A round trip would produce the same pixels, because PNG has no encoder settings to apply on the far side; all it would add is a copy of your file on someone else's disk and a queue in front of your download.

Open DevTools (F12), switch to the Network tab, convert a file: no request carries it. Disconnect the network and convert again — the same PNG comes out.

Questions that come up

Does converting AVIF to PNG make the photo look better? No. The pixels are what the AVIF decoder produced: on the 1600 × 1200 test photo, 0 of 1,920,000 differed between the decoded AVIF and the decoded PNG. What changes is the container — PNG cannot re-decide anything, so the picture stops moving.

Why is the PNG so much bigger than the AVIF? Because AVIF is allowed to approximate and PNG is not. The 204,487-byte AVIF became 3,179,872 bytes, 15.5 times larger; the transparent 2,257-byte file became 30,263 bytes. If size is what you need, convert to WebP instead, and expect it to be larger than the AVIF too at any quality above 60.

Is the transparency really preserved? Yes, as 8-bit alpha. On the 600 × 400 file, all 116,186 fully transparent pixels were still fully transparent, and the alpha channel was identical on 100% of pixels. What PNG cannot give you is more than 8 bits of alpha, which is also what the AVIF carried here.

What happens to a 10-bit AVIF? The container is read as 10-bit and reported on the card, but the canvas this tool draws through is 8 bits per channel, so the PNG is 8-bit. On the 1024 × 320 gradient that is 1,024 levels per channel collapsing to 256, which is where banding would show.

Can I get every frame of an animated AVIF? Not on this page: the first frame is what becomes the PNG, and the card tells you how many frames were in the file. Animated AVIF is rare in the wild; if you have one, the frames have to be stepped out by a tool that opens the container's tracks.

Where did the capture date go? It stayed in the AVIF. Exif lives in a container box, and a canvas exposes pixels only, so the PNG has no date, no camera model and no GPS. The card flags files that carried Exif, so you know which originals to keep.

For the size-minded direction on the same file, AVIF to WebP is the measured comparison; for the same picture with no alpha channel and a much smaller footprint, AVIF to JPG paints transparency onto a matte and encodes at a quality you pick. If the file you have is HEIC from an iPhone rather than AVIF, HEIC to PNG is the same idea through a different decoder.