AVIF to PNG Converter
Convert AVIF images to PNG right in your browser. Batch, private, no uploads, and a dropped folder adds up to 3,000 files at a time.
- Free, no account
- No watermark
- No usage limit
About the AVIF to PNG Converter
An AVIF becomes a PNG here, inside the browser tab you already have open, and the PNG comes back several times larger than the file you fed in. That catches almost everyone out, so it goes first. A 1,366 by 900 screenshot went in as a 50.9 KB AVIF and came out a 417.4 KB PNG. Eight times the size, and nothing went wrong at either end.
There are real reasons to pay that. PNG is lossless, so nothing gets discarded on the way out, and it keeps a transparent background instead of painting white behind it. It also opens in software that has never heard of AVIF, which is a lot of desktop software. If none of that applies to you, an ordinary photo is better off as a JPG and you keep the megabytes.
Nothing is uploaded, and that one is checkable rather than decorative. Neither the converter nor the image engine behind it ever sends your file anywhere, so it is read, converted and handed back without leaving the machine you are sitting at, with no account to make and no queue to stand in.
How to use
- Drop AVIF files on the box, click it to browse, or paste one straight from the clipboard. A whole folder works too, and it takes the first 3,000 files it finds in there.
- If the shot is sideways or mirrored, set rotate or flip before you convert. There is no quality slider to fret over, because PNG has nothing to trade away.
- Press Convert. A batch runs files side by side, one job per file up to the number of processor cores your machine reports, so four files run four at a time.
- Download each PNG on its own, or take the batch as a single ZIP. Files that share a name come out as photo.png, photo (1).png and photo (2).png instead of quietly overwriting each other.
Why the PNG comes out so much bigger
AVIF is built on the AV1 video codec and is about as good as still-image compression currently gets, and the AVIFs you find on the web are almost all lossy. PNG cannot make guesses of that kind at all. It writes the picture out the long honest way, which is both why it never loses anything and why the file is so much larger. The size jump is both formats doing exactly their job.
Four real conversions through this page, so you can see the shape of it:
| What went in | AVIF in | PNG out | Times bigger |
|---|---|---|---|
| 1,366 x 900 page screenshot | 50.9 KB | 417.4 KB | 8.2 |
| 750 x 2,780 phone screenshot | 20.5 KB | 220.4 KB | 10.7 |
| 2,560 x 1,800 page with artwork | 66.2 KB | 907.6 KB | 13.7 |
| 3,840 x 2,400 photograph | 10.4 KB | 601.6 KB | 58.0 |
The photograph is the extreme case. A smooth photograph is exactly what AVIF was built for, so it came down to a tenth of a megabyte, and that same smoothness leaves PNG with nothing much to work with. The multiplier is a property of the picture rather than of our converter, and you cannot predict it from the AVIF's size alone, which is why we do not print an estimate before you press the button.
If you are converting a photo and all you actually need is a file something will open, the AVIF to JPG converter is the better page. Come here when you need lossless, or transparency, or a file you are going to keep editing.
Nothing about the picture changes on the way through
Lossless is easy to claim, so it got measured. Each AVIF was decoded, converted to PNG through this page, and then the PNG was decoded again and compared against the decode of the original, value by value.
Across five files that is 17,400,544 pixels and 69,602,176 color values. Number that came back different: none. The largest gap on any single channel was zero.
The honest limit sits on the other side of that. This page can only give you what the AVIF is already holding, and most AVIFs on the web were saved lossy, so whatever detail was thrown away when the AVIF was first made is gone before your file ever reaches us. So the PNG is an exact copy of an AVIF that had already lost something. No converter anywhere fixes that, and any that says otherwise is selling something.
Most of the wait is the converter making your PNG smaller
Reading the AVIF is quick. Writing the PNG is where the time actually goes, and it goes there on purpose.
| Picture | Megapixels | Read the AVIF | Write the PNG | PNG we write | A plain PNG write |
|---|---|---|---|---|---|
| 512 x 512 logo | 0.26 | 9 ms | 58 ms | 4,333 B | 14,908 B |
| 1,366 x 900 screenshot | 1.23 | 50 ms | 651 ms | 427,464 B | 713,199 B |
| 750 x 2,780 screenshot | 2.08 | 55 ms | 795 ms | 225,693 B | 420,616 B |
| 2,560 x 1,800 artwork | 4.61 | 135 ms | 1,916 ms | 929,404 B | 1,852,962 B |
| 3,840 x 2,400 photo | 9.22 | 252 ms | 4,767 ms | 616,047 B | 2,127,797 B |
This page does not just write a PNG, it compresses it properly before handing it over, and on those five files the result came out between 40 and 71 percent smaller than a straight write of the identical pixels. The 9 megapixel photo went from 2,127,797 bytes to 616,047. Given that the whole complaint about PNG is its size, that is the part of the job worth spending time on.
That compression costs the time. The plain write of that photo took 54 ms and the compressed one took 4,767, so you are paying roughly eighty eight times as long to save 71 percent of it. On a desktop, anything under two megapixels finishes inside a second and a 9 megapixel photo takes about five, and a phone will be slower than that. That is the trade, stated plainly, and it is the reason a big batch is not instant.
What actually ends up in the file you download
A PNG is a short list of labeled blocks and you can read the list back. Four of the five files above came out carrying exactly three: the header, the picture, and the end marker, and nothing else was in any of them. No location block, no camera model, no timestamp, no color profile, because none of them are ever written in the first place. The camera data is not stripped out of your file as a favor, it simply has nowhere to go.
The logo was the exception and came back with two extra blocks, a color table and its transparency table, because everything in it fits inside a 256 color table and saying so made the file 4,333 bytes instead of 14,908.
The other place a converter can quietly keep something is your browser's own storage, so that got watched too. On a fresh load the page wrote nothing. Adding files wrote nothing. Pressing rotate wrote one entry with eight fields in it, quality, width, height, keep ratio, target size, rotate, flip horizontal and flip vertical, which is your control panel and not your picture. The file name is not in there and neither is a single pixel.
Frequently asked questions
Will a transparent background survive?
Yes. Tested on a 512 by 512 logo with 143,195 fully transparent pixels in it. After the round trip, 140,894 were still fully transparent and 4,889 had gone partly transparent around the edge of the shape, and every one of those matched the AVIF exactly. So the softening happened when the AVIF was made, not on the way out. If the AVIF carries an alpha channel, the PNG gets it, and the converter picks the smaller of a full color file and a palette with a transparency table.
One file in my batch failed. Did I lose the others?
No. Four files went in, one of them deliberately half downloaded. Three converted normally and the broken one came back on its own line, named: "half-downloaded.avif could not be read as AVIF (Decoding error). The file may be truncated, or it may carry the wrong extension for what is inside it." The other three downloaded as usual. A bad file costs you that file.
Does it work with the internet disconnected?
It does not work offline, and I would rather tell you than let you find out mid task. The page loads quickly because the part that knows how to read AVIF is only fetched the first time you press Convert, and checking the built page confirms it is not among the scripts that arrive with it. Pull the plug before that first conversion and you get an error instead of a PNG.
What is still true is that your picture never travels. The page fetches a piece of itself from our server the first time you convert, and your file stays exactly where it is. That is the claim worth having, and it is a different claim from the offline one.
How big a file will it take, and how many at once?
We set no size cap, so the real ceiling is how much memory your device has to hold the decoded picture, and an old phone will hit that long before a laptop does. The timing table above is your guide to how long any of it takes. There is one hard limit and it lands on folders: drop a folder of 3,500 images and it adds 3,000 of them and tells you so, with "That folder holds more than 3000 files, so only the first 3000 were added. Drop the rest in a second batch." The button then reads "Convert 3000 images", so the count you are about to run is never a guess.
It said it skipped some of my files. What happened?
The box takes images and turns everything else away, out loud. Hand it five files where one is an AVIF and four are documents and you get "Skipped 4 files that are not images: notes.txt, budget.csv, readme.md, and 1 more." with the button reading "Convert 1 image". Nothing is discarded in silence, which matters most when you have dragged in a folder and cannot see what was in it.