PNG to AVIF Converter

PNG to AVIF, entirely in your browser, with no upload of any kind. Most people reaching for this conversion are developers, designers, and site owners trying to cut page weight: a folder of transparent UI graphics, logos, screenshots, or product shots on transparent backgrounds that bloat PNGs and drag down Core Web Vitals and LCP. The catch with cloud converters is that your branded or confidential assets ride across someone else's server, often behind daily limits, file-size caps, and watermarks. This tool encodes AVIF locally so the source bytes never leave the page.

What this conversion actually does (and does NOT do)

AVIF preserves PNG's full alpha channel, so transparent logos, icons, and cutouts stay transparent with no white flattening like you would get converting to JPG (or jpeg). This page writes lossy AVIF at the slider quality, and on a photographic or gradient-heavy PNG the result is commonly 50-90% smaller. The AVIF format also has a lossless mode, but this converter does not offer it; at 90-95 the output is near-lossless. The savings depend heavily on content, not a fixed ratio. A flat-color logo of roughly 15 KB might only drop to about 10 KB, whereas a transparent product photo can fall from around 3 MB as PNG to roughly 80 KB as AVIF. The AVIF format can carry higher bit depth and HDR, but this encoder writes 8 bits per channel, so a 16-bit PNG is reduced to 8-bit, just as it would be for JPG. What it does NOT do: it does not carry animation. An animated PNG (APNG) is converted from its first frame only, so the result is always a still AVIF. It is also not an editing master. AVIF is intended for final web delivery, so keep the original PNG if you plan to re-edit, since lossy re-encodes degrade and AVIF is not a universal editing format. Expect encoding to take a few seconds: AVIF uses the AV1 codec and is 5-10x slower than JPEG or WebP, which is the real tradeoff for much smaller files.

When to choose PNG to AVIF vs the alternative

Pick the quality by content, not habit. Use 90-95 for flat-color logos, icons, UI sprites, screenshots with text, and pixel art, where hard edges matter (or keep them as PNG if every pixel must match). Use 75-85 for photos-with-transparency and gradient-heavy illustrations where smooth tones dominate the byte cost. If you need the very widest compatibility today, AVIF sits at roughly 92-95% browser support in 2026 (Chrome 85+, Firefox 93+, Safari 16+ and iOS 16+, Edge 121+), so the recommended deployment is AVIF primary with a fallback via the <picture> element. If a target audience or pipeline still chokes on AVIF, converting PNG to WebP is the safer, faster-encoding intermediate that still keeps transparency. For broad, no-transparency compatibility, plain PNG to JPG remains the fallback floor.

How to convert

1. Drop one or many PNG images into the box; they are read locally and never uploaded.
2. The output format is pre-selected to AVIF; the quality slider applies (90-95 for near-lossless, 75-85 for the web sweet spot).
3. Because AVIF keeps alpha, transparency is preserved automatically: no flattening, no background color to pick.
4. Click Convert. A single file downloads directly; multiple files download as a ZIP with no count cap.

No upload. It runs on your device.

The encoder is Rust compiled to WebAssembly and runs inside your browser tab. Your PNGs are processed in memory, with zero network requests for the file itself, so the bytes of your internal logos and unreleased brand assets never touch a server or a queue. After the page loads once it works offline, even in airplane mode. There is nothing to delete afterward because nothing was ever uploaded, and you can verify all of this yourself: open the DevTools Network tab while converting and you will see no upload request for your image.

No limits

Unlimited batch conversion, no file-size cap, no file-count cap, no watermark, no sign-up, and no ads. Because encoding runs on your own CPU instead of a shared server, heavy AVIF jobs are not throttled or rate-limited.

Frequently asked questions

Does converting PNG to AVIF keep transparency?

Yes. AVIF preserves PNG's full alpha channel, so transparent logos, icons, and cutouts stay transparent with no white flattening.

Is PNG to AVIF lossless, or will I lose quality?

It is lossy. The AVIF format has a lossless mode, but this converter always encodes lossy AVIF at the slider quality: 90-95 is near-lossless and 75-85 is the usual web sweet spot. Keep the original PNG if you need a pixel-identical copy.

How much smaller is AVIF than PNG?

It depends entirely on content rather than a fixed ratio. A flat-color logo near 15 KB might only drop to about 10 KB, whereas a transparent product photo can fall from roughly 3 MB to about 80 KB, with lossy savings on photographic or gradient PNGs commonly landing in the 50-90% range.

What quality should I use when converting a PNG to AVIF?

Use 90-95 for flat-color logos, icons, UI sprites, screenshots with text, and pixel art where hard edges matter. Use 75-85 for photos-with-transparency and gradient-heavy illustrations where smooth tones dominate the file size.

Are my PNG files uploaded to a server when I convert to AVIF?

No. The conversion runs entirely in your browser through Rust compiled to WebAssembly, so the image bytes never leave your device. You can confirm there is no upload request in your browser's DevTools Network tab while converting.

Can I convert PNG to AVIF offline or without internet?

Yes. Once the page has loaded, the WebAssembly encoder works with no network connection, even in airplane mode. Nothing is sent out and nothing needs to be deleted afterward because nothing was ever uploaded.

Is there a file size or daily limit for converting PNG to AVIF?

No. There is no file-size cap, no file-count cap, and no daily limit. Because encoding uses your own CPU instead of a shared server, large AVIF jobs are not queued, throttled, or rate-limited.

Can I batch convert many PNGs to AVIF at once?

Yes. Drop dozens or hundreds of PNGs at once; a single image downloads directly while multiple images download together as a ZIP. There is no count cap on a batch.

Do all browsers support AVIF in 2026?

Nearly all do, at roughly 92-95% support (Chrome 85+, Firefox 93+, Safari 16+ and iOS 16+, Edge 121+). For the remaining holdouts, serve AVIF as the primary source with a WebP or PNG fallback through the HTML <picture> element.

Why is PNG to AVIF conversion slower than other formats?

AVIF uses the AV1 codec, which is roughly 5-10x slower to encode than JPEG or WebP. A local converter trades those few seconds of CPU time for substantially smaller files, which is the tradeoff to expect.

Should I replace my PNGs with AVIF or keep both?

Use AVIF for final web delivery but keep the original PNG if you may re-edit the image. AVIF is not a universal editing master, and repeated lossy re-encodes degrade quality over time.

Does PNG to AVIF preserve 16-bit color and HDR?

No. The AVIF format supports higher bit depth and HDR, but this encoder writes 8 bits per channel, so a 16-bit PNG is reduced to 8-bit, much as it would be for JPG. Keep the original PNG if you need the extra depth.

Related tools: go the other way with AVIF to PNG, batch-shrink existing files with image compression, or browse the full image tools hub.