C
Chaudify
Searching...
No tools found

Convert PNG to AVIF Free

Convert PNG to AVIF in your browser — nothing is uploaded. AVIF is usually far smaller than WebP, and this tool hands back whichever file is smaller.

Runs in your browser — nothing is uploaded. Verify it

About the Convert PNG to AVIF Free

Convert PNG to AVIF in your browser, with the encoder running on your own machine — nothing is uploaded. AVIF is the smallest format the web has: measured in Chrome on this page, an 800×600 photographic PNG of 2,528,652 bytes became 10,715 bytes of AVIF at quality 50, while the same image as WebP at quality 90 was 119,860 bytes. The tool also checks the result against your original, because AVIF does not always win — a flat 200×200 PNG of 329 bytes encoded to 336 bytes, larger than the file it came from, and that row says so instead of claiming a saving.

AVIF is what the next generation of the web is served in, and it is the one modern format the rest of this site cannot reach: the canvas API writes PNG, JPEG and WebP only, so producing AVIF needs a WebAssembly build of the libavif encoder running in the page. The gain is real but it is not uniform, and the difference between a 91% saving and a small loss is entirely the file in front of you. A photograph with gradients and noise is where AVIF earns its place; a small flat graphic that PNG deflate already compresses well can come out larger, because AVIF has container overhead that a 329-byte PNG does not pay. That is why every row reports a measured number rather than a promised percentage, and why the default is to hand you whichever of the two files is smaller.

How to use the Convert PNG to AVIF Free

  1. Select one or more PNG images, or drag them onto the page.
  2. Leave the quality at Balanced — 50 unless you have a reason to move it; 35 is for thumbnails and 65 or 80 for an image that is the product.
  3. Leave the fallback on "Give me the smaller file" so a PNG that AVIF cannot beat is handed back untouched, or switch it to "Give me AVIF anyway" when a site requires the format.
  4. Read the before-and-after size on each row, then download the files individually or as a ZIP.

Frequently asked questions

Is AVIF actually smaller than WebP?

Usually, and by a lot — but the size of the win depends on the setting, which is what makes it worth measuring. On an 800×600 photographic PNG of 2,528,652 bytes: AVIF at quality 50 came out at 10,715 bytes, while WebP at quality 90 came out at 119,860 bytes, so AVIF was 91% smaller than WebP. Push AVIF to quality 90 on the same image and it grows to 178,643 bytes, which is larger than the WebP. Quality 50 in libavif is roughly where a JPEG at 80 sits, and it is what most of the web actually ships, which is why it is the default here.

Why did I get my PNG back instead of an AVIF?

Because the AVIF was not smaller. AVIF is efficient on photographs but it is not free: it carries container overhead that a tiny PNG does not pay, and a PNG that is already small can beat it. Measured on this tool, a flat 200×200 PNG of 329 bytes encoded to 336 bytes of AVIF, and a 900×600 flat-colour graphic of 5,004 bytes came down to 634 bytes. The first is a loss, the second a 87% win, and nothing about the file name tells you which you have. When the AVIF loses, the row says "PNG is smaller" and hands the original back unchanged rather than quietly making your page slower. Switch the fallback setting to "Give me AVIF anyway" if you need the format regardless of the size.

Does AVIF keep transparency?

Yes, and unlike the JPEG path nothing is flattened. AVIF carries a full alpha channel, so a transparent PNG stays transparent with no white background behind it. AVIF has two separate quality settings, one for the colour and one for the alpha, and this tool leaves the alpha at the encoder default so transparency is preserved at the highest setting.

What quality should I choose?

Balanced — 50 for almost everything. Measured on the same 800×600 photographic PNG: quality 35 gives 3,616 bytes, 50 gives 10,715 bytes, 65 gives 23,656 bytes, 75 gives 63,051 bytes and 90 gives 178,643 bytes. Note how steeply the last two climb — past about 65 the extra bytes buy very little visible detail, which is why 50 is the default and 35 is the sensible choice for a thumbnail or a long article where the image is decoration.

Does converting change the image dimensions?

No. The pixel dimensions are copied through untouched, so an 800×600 PNG produces an 800×600 AVIF. A format conversion and a resize are different jobs, and this tool only does the first. If you need a smaller pixel count as well, resize first and then convert.

Are my images uploaded to a server?

No, and that is the reason the tool can exist at all. The AVIF encoder is a WebAssembly build of libavif that runs inside the page, so the pixels are read from your own machine, encoded in your own browser and handed straight back to you. You can disconnect from the internet after the page loads and it will still work. Most AVIF converters that rank for this query send the file to a server, which for a client logo or an unpublished design is the part that matters.

Will the AVIF open everywhere?

In every current browser. AVIF shipped in Chrome 85, Firefox 93 and Safari 16, and it is now supported by all of them on desktop and mobile, so a plain <img> tag is enough. The one place it still needs care is older software outside a browser — some desktop editors, print tools and older CMS uploaders do not read AVIF yet, in which case keep the PNG as well.

Is there a size limit?

Images up to 40 megapixels, which is well beyond any phone or consumer camera. The limit exists because the encoder runs on the main thread and libavif needs several bytes per pixel on top of the decoded bitmap the browser is already holding; past that a tab starts running out of memory rather than failing cleanly. If you hit it, resize the image below 40 megapixels first and then convert.

Guides

More Image tools