Skip to content
Initurn

Convert PNG to AVIF

Files never leave your device. All processing happens in your browser.

Lower means a smaller file. Above 90 the file grows fast for little visible gain.

Pixels. Leave empty to keep the original dimensions.

How to convert PNG to AVIF

  1. 1

    Add your PNG files. A 3.5 MB encoder downloads on first use, then is cached.

  2. 2

    Choose a quality level — 50 suits photographs, 65 or above suits graphics.

  3. 3

    Let the encoder finish, then download the AVIF files.

A PNG carrying a photograph is the single most wasteful thing on most web pages, and this conversion is the most aggressive fix for it. Size reductions of 90–98% are routine, transparency survives intact, and the result still looks right. If a designer handed you a folder of PNG exports and your pages are slow, start here.

Transparency is fully preserved

AVIF stores a complete alpha channel, so everything PNG could express — soft shadows, feathered cut-outs, semi-transparent overlays — comes across unchanged. Unlike JPEG, you are not forced to choose between transparency and small files. Unlike GIF, the transparency is not reduced to a hard on/off mask with a jagged edge.

The lossy trade you are making

PNG is lossless. AVIF here is lossy. That is where the enormous saving comes from, and it means this is a one-way door: keep your PNG as the master and treat the AVIF as a delivery copy. Never let an AVIF become your only copy of artwork you may need to edit later, and never run the AVIF back through another lossy conversion.

Quality settings by content type

  • Photographs and photographic composites: 45–55 is ample. AVIF quality numbers sit much lower than PNG or JPEG intuitions suggest.
  • Logos, icons and flat illustrations: use 65–80. Hard edges and large flat areas are where lossy compression is most visible, and these files are small anyway.
  • Screenshots with fine text: 70 or above, and check the smallest text at full size before committing.
  • Anything you will edit again: do not convert it. Keep the PNG.

Expect it to take a while

AVIF encoding is slow — several seconds per image is normal, more for large ones. The first conversion on this page also downloads a 3.5 MB WebAssembly encoder, since browsers can display AVIF but none can create it. That download is cached afterwards, and it is deliberately not loaded on any page that does not produce AVIF, so the other converters here stay light.

A caveat for very small graphics

AVIF has a fixed container overhead of a few hundred bytes. For a tiny icon — say a 32×32 PNG of a few hundred bytes — the AVIF can genuinely come out larger. The size is shown before you download, so check rather than assume. For assets that small, keeping the PNG or inlining it as base64 is usually better.

The whole process runs on your own device in a background thread. Nothing is uploaded, which means unreleased designs and client artwork stay entirely local.

Questions about PNG to AVIF

Does AVIF keep the transparent background?

Yes, completely. AVIF stores a full 8-bit alpha channel, so soft edges, shadows and semi-transparent areas all survive. It is one of the main advantages AVIF has over JPEG for web graphics.

How much smaller will the file be?

For photographic PNGs, commonly 90 to 98 percent smaller. For flat logos and icons the saving is much less dramatic, and for very small images the AVIF can occasionally be larger because of its container overhead.

Is this conversion lossless like PNG?

No. AVIF is used lossily here, which is where the size reduction comes from. Keep the PNG as your master — the AVIF is a delivery copy and should not be your only version of anything you may edit.

Why is my tiny icon larger as an AVIF?

AVIF files carry a few hundred bytes of container structure regardless of image size. For icons of a few hundred bytes, that overhead outweighs any compression gain. Keep the PNG for assets that small.

What quality should I use for a logo?

Higher than you would for a photograph — around 65 to 80. Lossy compression is most visible on hard edges and flat colour, which is exactly what logos are made of, and the files are small enough that the extra bytes cost little.

Why does the first conversion take so long?

Two reasons: a 3.5 MB encoder downloads on first use because browsers cannot create AVIF natively, and AVIF encoding is inherently slow. Subsequent files skip the download and start immediately.

Related converters