PNG to AVIF Converter

Turn heavyweight PNGs into small AVIF files with transparency intact — HEIC-class compression or better, in a format the web actually reads. Encoding runs on your device, typically a few seconds per image, and every row shows the measured percent saved.

Convert PNG files to AVIF

Drop .png files, pick a quality, and download verified AVIFs — alpha preserved, real before/after sizes shown. Expect a few seconds of on-device encoding per image.

or drag and drop .png files here

Up to 40 files · 100 MB each · 300 MB per selection

    Why PNGs are big — and where AVIF fits

    PNG is lossless: every pixel you put in comes back exactly, and the format pays for that guarantee in file size, especially for photos and busy screenshots. AVIF makes the opposite trade — modern lossy compression from the AV1 video codec — while keeping the one thing that usually chains images to PNG: real alpha transparency. A logo with soft shadows, a cut-out product shot, a UI screenshot with rounded corners — all of them stay transparent in AVIF at a fraction of the bytes. The conversion is worth it for delivery: web pages, chat, docs. It is not an archival move; keep the PNG master.

    The honest details

    • Transparency preserved: AVIF carries a full alpha channel; nothing is flattened. (Tested — a transparent PNG round-trips with its alpha intact.)
    • Measured, not promised: every row shows real input bytes, real output bytes, and the computed percent change — including "larger — keep your original" when a small, flat-color PNG beats the encoder.
    • Lossy by design: the quality slider (default 50) trades fidelity for bytes. Pixel-exact work should stay in PNG.
    • A few seconds per image, on your device: AV1 encoding is CPU-heavy; the fast preset is deliberate, the row reports the actual encode time, and no target-size mode is offered because eight search probes at seconds each would be dishonest UX.
    • Encoded by libavif + aom locally:libavif with theaom AV1 encoder (BSD-2-Clause, under the AOM patent grant — royalty-free, unlike HEVC/HEIC), compiled from pinned upstream source to WebAssembly, self-hosted, and running in a bounded worker only in your browser. Details on themethodology page.
    • Verified output: every AVIF is re-sniffed and re-decoded before its download button appears.

    Photos living as JPGs go through JPG to AVIF. Need broad compatibility instead of minimum bytes? PNG to WebP also keeps transparency with wider legacy support, and PNG to JPG is the universal (flattened) fallback. Coming back from AVIF,AVIF to PNG restores a lossless, editable file.

    Frequently asked questions

    Does transparency survive the conversion?

    Yes. AVIF carries a full 8-bit alpha channel, so soft shadows, anti-aliased edges, and partial transparency all come through — nothing is flattened onto a background. This is the big practical difference from converting PNG to JPG.

    How much smaller will the AVIF be?

    For screenshots, graphics, and photos stored as PNG, the drop is usually dramatic — PNG is lossless and pays for it in bytes. But the honest answer depends on your image, which is why every row shows the measured percent from real byte counts instead of a banner promise. Flat-color graphics with few colors are the one case where a well-optimized PNG can compete.

    Is AVIF lossy? Will my image change?

    At this page’s settings, yes, mildly: AVIF here is lossy compression, tuned by the quality slider (default 50). For photos and screenshots the difference is very hard to see. Pixel-exact needs — archival masters, images you will keep editing — should stay PNG.

    How long does encoding take?

    Typically a few seconds per image, done entirely on your device. AV1 encoding is CPU-heavy; the page uses a fast preset on purpose and each row reports the actual time it took. Alpha channels add a little extra work.

    Why is there no target-file-size mode on this page?

    Measured encode times. The binary-search approach used on the JPEG tools needs up to eight re-encodes; at several seconds per AVIF encode of a large image, that would run close to a minute per file. The quality slider is the honest control here.

    Is my image uploaded anywhere?

    No. The AVIF encoder (libavif with the aom AV1 encoder, compiled to WebAssembly) is served by this site and runs in your browser tab. The site’s security policy blocks requests to any other origin — verifiable in your network inspector.

    Local processing: your images are converted and verified inside your browser and never transmitted. AVIF encoding bylibavif andaom, BSD-2-Clause, self-hosted and used unmodified — see the methodology page for full attribution and how to verify the no-upload claim yourself.