Convert AVIF to PNG online, free

To be honest, most AVIFs in the wild are ordinary photos with no transparency at all. For those, PNG is overkill. The transparency argument only earns its keep when the alpha channel is actually doing something, which is exactly when JPG would quietly ruin the image.

Lossless: why PNG adds no new loss

PNG is a lossless format. It does not throw away detail to save space the way JPG and AVIF do, it records every pixel exactly. So when the browser decodes your AVIF into raw pixels and encodes those pixels as PNG, nothing is discarded in that step. The PNG is a perfect copy of whatever the AVIF decoded to.

That has a clear and reassuring consequence: an AVIF to PNG conversion is as faithful as the AVIF itself. The only compression that ever touched the picture happened when the AVIF was first created, by whoever exported it. Converting to PNG does not stack a second round of loss on top, which is what makes a JPG to JPG round trip slowly degrade an image but a PNG round trip never does.

Because of this, there is no quality slider for AVIF to PNG, and there should not be. There is no detail to trade away, so there is no knob to turn. If you have ever seen a converter ask you to pick a PNG quality, it was either compressing colours behind your back or secretly handing you a different format.

Lossless also means crisp edges survive. JPG smears hard boundaries, the kind you find in logos, line art, and text on a screenshot, into faint halos. PNG keeps every edge razor sharp. So if your AVIF is a diagram, an icon, or a UI capture full of small type, PNG is not just compatible, it is genuinely the higher-fidelity result.

The honest cost: PNG files are big

Here is the trade, stated plainly. PNG is one of the least space-efficient image formats, and AVIF is one of the most efficient. So the PNG you get out is usually a lot larger than the AVIF you put in. For a photograph the difference is often three to ten times. A 200 KB AVIF photo can balloon past a megabyte as PNG.

That is not a flaw in the tool, it is the nature of lossless. PNG stores every pixel, and photographs have millions of subtly different pixels, so there is little for PNG's compression to grip. Flat graphics are a different story: a logo with a handful of solid colours compresses very well as PNG, so the size penalty there is small. PNG was designed for exactly that kind of image.

This is the single most important reason to think before you convert. If your AVIF is a normal photo with no transparency, PNG is the wrong target, you would pay a big size penalty for a lossless copy you do not need. In that case convert it to JPG instead, which is far smaller and opens just as widely.

If you do need PNG but the file comes out heavier than you would like, you can shrink it afterward. Compress the PNG to strip metadata and re-pack the pixels without any visible loss, or if you need to hit a hard upload limit, run it through the compress-to-size tool to land under a specific KB target.

Where AVIF refuses to open

Operating systems were slow to support AVIF. Windows does not preview it out of the box without an add-on from the Microsoft Store, and File Explorer often shows a blank thumbnail where the picture should be. macOS only learned to read AVIF in Ventura, so anyone on an older Mac is stuck with a file that will not even open.

Desktop and creative apps lag further behind. Plenty of image editors, layout tools, presentation software, and older versions of the big design suites simply do not list AVIF as a format they can import. You drag the file in and the app shrugs or throws an unsupported-format error, with no hint that a quick conversion would fix it.

Upload forms are the most common wall, and here the transparency angle bites hardest. A design portal, a print-on-demand storefront, or an asset library may demand PNG specifically because it needs the transparent background your AVIF has. Those forms were built before AVIF and accept PNG, JPG, or JPEG only. A perfectly good transparent AVIF is rejected at the door.

PNG has the opposite reputation. It has been a web and desktop staple since the 1990s, and there is essentially no editor, viewer, or form that cannot read it, transparency and all. Converting AVIF to PNG trades the new format's efficiency for that universal reach while keeping the one thing JPG would have destroyed.

When PNG is the right call, and when JPG wins

Choose PNG when transparency matters. A logo, an icon, a product cut-out, a sticker, anything meant to float over a coloured background needs its alpha channel, and PNG is the lossless, universally-readable way to keep it. If a form or app explicitly asks for a PNG, that is also your answer with no further thought required.

Choose PNG when crisp edges matter. Screenshots, diagrams with text, line art, UI mockups, and flat illustrations all have hard boundaries that JPG softens. PNG keeps them sharp, and because these images use limited colours, the file size stays reasonable. For this kind of content PNG is both the compatible and the higher-quality choice.

Choose JPG when the image is an ordinary photo with no transparency. This is the honest counterweight to the whole page: photos have no alpha to protect and no hard edges to preserve, so the only thing PNG buys you there is a much bigger file. Convert that photo to JPG instead, which is three to ten times smaller and opens everywhere PNG does.

The rule of thumb: PNG for transparency, logos, icons, screenshots, and anything a form names by extension. JPG for photographs. If you are not sure whether your AVIF has transparency, opening it on a checkered background or simply trying the PNG output will tell you quickly, the see-through areas will show.

When you should keep the AVIF instead

If the file is bound for a modern website you control, keep it as AVIF. Current browsers decode it natively, it loads far faster than a PNG of the same picture, and converting to PNG would only make your pages heavier. Serving AVIF with a PNG or WebP fallback is the standard modern pattern, not converting everything up front.

If you need transparency on the web but want it smaller than PNG, WebP is the middle path. It keeps the alpha channel like PNG but compresses much harder, so a transparent WebP is a fraction of the size of the equivalent PNG. Reach for PNG only when the destination cannot read WebP, which is rare on modern browsers but common in older desktop software.

If you are going the other direction, building AVIFs from existing transparent assets, you do not need this page at all. Convert your PNGs to AVIF instead to shrink them dramatically while keeping the alpha channel, which is the efficient choice for anything web-bound.

The honest summary: AVIF is the better format to keep for the modern web, and PNG is the format you reach for the moment a real app or a real form has to read a transparent image and cannot handle anything newer.

Converting a folder of AVIF files to PNG at once

Design systems, icon sets, and asset exports rarely come as a single file, so the tool is built for the batch. Drop a whole folder of AVIFs and every file is decoded and re-encoded to PNG in parallel using a worker pool in your browser, with the alpha channel preserved on each one, then bundled into a single ZIP with the original names kept and the new .png extension applied.

Up to 100 files at 50 MB each go in one batch. A set of transparent icons converts almost instantly because flat graphics decode and encode fast. Photographic AVIFs take a little longer and produce much larger PNGs, but the work spreads across your machine's cores rather than queuing one file at a time.

Because nothing uploads, batch size is bounded only by your device's memory, not by a server quota or a paid tier. There is no per-file fee, no watermark, and no cap on how many batches you run. Just bear in mind that PNGs are heavy, so a folder of large photos will produce a sizeable ZIP, one more reason to send true photos to JPG instead.

If you have a mixed folder of formats, not just AVIF, the bulk image converter handles the whole drop and lets you pick one output for everything. And if the resulting PNGs need to fit a specific limit, the compress-to-size tool iterates until each file lands under your target.