PNG to AVIF Converter
Convert PNG images to AVIF 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 PNG to AVIF Converter
AVIF is the biggest size cut you can wring out of a PNG, routinely 70 to 90 percent, and that is exactly why so many free converters make you jump through hoops to get it. Encoding AVIF is genuinely slow and compute-hungry work, so those sites run it on their own servers. Which means you upload your PNG first, and then they cap you at a handful of files, stamp a watermark on the output, or push a sign-up to cover the cost. When the PNG in question is a private screenshot or an unreleased design asset, handing it to some stranger's server is the last thing you want.
This converter does the whole encode on your own machine instead. Your PNG never leaves the browser tab, nothing is uploaded or stored, there is no file cap, and it never adds a watermark or asks you to sign up. Drop one image or select a few hundred at once, and it spreads the work across your browser so a batch converts in parallel rather than one slow file at a time. When it finishes you grab each AVIF on its own or the whole set as a single ZIP. It does not work offline from a cold start, and that is the one flattering thing this page will not tell you. The AVIF encoder is enormous by the standards of anything else here, two builds of 3,534,665 and 3,485,872 bytes, and it is fetched on your first press of Convert rather than shipped with the page. The 181,088-byte PNG reader comes down with it. Both stay in your browser afterward, so a batch you start online finishes fine on a train.
How to use
- Drag your PNGs onto the drop zone, or click to browse and pick files from your device. You can also paste an image straight from the clipboard, which is handy for a screenshot you just grabbed.
- Set the quality if you want to. Higher keeps more detail at a slightly larger file, lower squeezes harder. The default of 80 is a solid start for most images, you can always redo it if the result looks off.
- Click Convert. Everything runs on your device, so there is no upload wait and nothing about your image goes anywhere.
- Download each AVIF, or hit Download all (ZIP) when you converted a batch. The panel shows the before and after size per file and the total percent you saved.
No account or email is needed, and there is no watermark on the output.
Why AVIF gets a PNG so much smaller
PNG the format is lossless. It stores every pixel exactly as it was, which is perfect for a master copy and terrible for file size, because it can never throw away the detail your eye would never miss. AVIF, with a real lossy mode borrowed from the AV1 video codec, is free to drop exactly that, and it holds full transparency the whole time. That gap is why a detailed PNG running several megabytes often lands well under a megabyte as AVIF with no visible difference.
On a web page this is one of the highest-value swaps you can make, because images are almost always the heaviest thing loading. Trading big PNGs for AVIF can cut your total image weight enormously, which shows up directly in faster loads and better PageSpeed and Core Web Vitals scores. Your bandwidth bill drops right along with it. App icons and game textures win the same way, they ship smaller without going soft.
Getting the cleanest result
The quality slider is the one setting worth thinking about. For photographs and busy, detailed images, the default of 80 is already indistinguishable from the source and comes out tiny. For a logo, an icon, or a screenshot full of sharp text, nudge it up toward 90, hard edges are the first place aggressive compression shows itself as a faint fuzz. Because the panel reports the exact savings per file, you can push the quality down, glance at the numbers, and dial it back if a file shrank more than it needed to.
Transparency carries over on its own. A transparent PNG stays transparent as AVIF, soft anti-aliased edges and partial see-through areas included, so you never flatten it or pick a fill color first. That is the real reason to reach for AVIF over JPG on anything with a transparent background, since JPG cannot do transparency at all and would jam a solid color into those pixels.
One more quiet benefit: the conversion strips embedded metadata. Any location or camera information that can ride along inside an image is dropped, so a screenshot or exported graphic does not carry hidden details out into the world when you publish it. Nothing is uploaded either, so nothing but the image itself leaves your machine.
A note on browser support
AVIF displays in every current browser, Chrome, Firefox, Edge, and Safari 16 and up, which covers the large majority of people online. The one thing to plan for is a genuinely ancient browser that cannot render it yet. If your audience might include those, serve AVIF with a PNG fallback using the HTML picture element and keep the original PNG on hand. For a modern site or app, AVIF-only is completely fine and it loads noticeably faster.
Frequently asked questions
Why did my AVIF come out bigger than the PNG?
It happens with small, flat graphics. A simple icon or a tiny logo that was already a well-optimized PNG has so little data that AVIF's container overhead can outweigh what it saves, especially at a high quality setting. For those, the original PNG or a WebP is often the smaller choice, and since the tool shows you the before and after size you will spot it immediately. AVIF's edge grows with the size and complexity of the image, so it wins big on photos and detailed graphics and can lose on a 2 KB icon.
Is there a truly lossless AVIF option?
The quality slider tops out at near-lossless, not perfectly lossless. At the highest setting the result is visually identical to the PNG for any normal use, but if you need a byte-exact master for archiving or further editing, keep the original PNG and treat the AVIF as your lightweight delivery copy.
Does transparency survive a low quality setting?
Yes. The alpha channel is encoded separately from the color, so turning the quality slider down compresses the visible picture harder without punching holes in the transparent areas or adding a halo around a cut-out edge. What can soften at very low quality is the color right at a hard edge, so an icon sitting on a transparent background might pick up a faint fuzz there before the transparency itself is ever touched. Keep quality in the mid range for anything with cut-out edges and you will not notice it.
How big a batch can I convert?
None that we impose on the files you pass in yourself, and no daily quota waiting behind them. The ceiling there is your own device, since all the work happens locally, so a few hundred images is no trouble on a normal laptop and a very large batch simply takes a little longer or uses more memory. Drag a whole folder instead of the files and a real number turns up, because the tool reads it down to the first 3,000 images and then tells you on screen that it stopped, so the rest go through on a second drop. If you are throwing thousands at it in one go, split it into a couple of groups so your browser tab has room to breathe.
AVIF or WebP, which should I pick?
For most photos and detailed images, AVIF encodes smaller than WebP at the same visual quality, sometimes by a real margin. WebP has slightly wider support on older setups and encodes faster. So if maximum size savings for a modern audience is the goal, go AVIF. If you want the widest possible reach with still-strong compression, WebP is the safer bet. We have converters for both, so run the same file through each and compare the numbers.
Will it run on my phone?
It will. The conversion happens in your mobile browser the same way it does on a desktop, on the phone itself, with nothing uploaded. A large batch is slower on a phone than a laptop because there is less processing power to go around, but for a handful of images it is quick.