What is AVIF? The Next-Gen Image Format Explained (2026)

If you've poked around image-tool settings recently you've probably seen "AVIF" listed alongside JPEG, PNG, and WebP. It's the newest mainstream image format, and in 2026 it's finally crossed the line into being a reasonable default for the web — but the choice between AVIF, WebP, and JPEG still depends on what you're using the image for.

This guide explains what AVIF is, how it compares to other formats, where it's supported, and when picking AVIF actually pays off.

What AVIF actually is

AVIF (AV1 Image File Format) is a still-image container that uses the same compression technology as AV1 video. AV1 is the royalty-free video codec developed by the Alliance for Open Media (Google, Netflix, Amazon, Microsoft, Mozilla, Apple, and others) to replace the proprietary HEVC/H.265 used in 4K streaming.

When you save a single frame of AV1 with image metadata, you get AVIF. The format was finalised in 2019, and as of early 2026 every major browser supports it. Adoption is still growing.

In practical terms, AVIF gives you:

• Significantly smaller file sizes than JPEG (~50% reduction at the same visual quality is typical).
• Full transparency (alpha channel), like PNG and WebP — no need to use a different format for cutouts.
• HDR support with 10-bit and 12-bit colour, useful for photos and high-end displays.
• Lossless mode for graphics where exact pixel accuracy matters.
• A wide colour gamut including BT.2020 (the colour space modern HDR TVs use).

How AVIF compares to JPEG, PNG, and WebP

Here's the quick comparison, calibrated for typical photo content:

The compression gap matters most at "good but not perfect" quality settings (roughly 70–85 on a JPEG quality scale). At quality 95+, all formats start to converge — the differences get smaller as you ask for near-perfect output.

Where AVIF is supported today (2026)

Fully supported:

• Chrome (since v85, August 2020)
• Firefox (since v93, October 2021)
• Safari (since v16, September 2022)
• Edge (since v121, January 2024)
• Opera, Brave, and other Chromium-based browsers
• All iOS 16+ and Android 12+ devices
• macOS Preview, Quick Look (since macOS Ventura)
• Most image-management apps (Photoshop, Affinity Photo, Lightroom)

Patchy support:

• Older Windows photo viewers — Windows 11 supports AVIF natively, Windows 10 needs the AV1 Video Extension from the Microsoft Store.
• Some older email clients render AVIF inline only if forwarded through a modern client.
• Most CMS plugins now upload AVIF, but a few older builds reject the extension.

Largely unsupported:

• IE11 (long retired but still in some enterprise environments)
• Email clients on older mobile platforms

The practical takeaway: in 2026 you can serve AVIF to most users with a JPEG/WebP fallback for the ~5% of browsers that don't support it.

When to use AVIF

Use AVIF when:

• You're serving images on the web and care about Core Web Vitals / page-speed scores. AVIF's file-size win directly improves Largest Contentful Paint.
• You're storing photos for archival use and have the disk space to re-encode existing JPEGs (the compression win adds up over a large library).
• You need transparency on a photographic image without the file-size penalty of PNG. (Product cutouts on white backgrounds are the canonical example.)
• You're working with HDR content and want to preserve the 10-bit colour pipeline.

Stick with JPEG when:

• You're sending the image to someone whose tools you don't control (email attachments, customer support, some print labs).
• You need maximum compatibility with older systems.
• The encoder you have access to doesn't support AVIF (some older mobile apps still don't).

Stick with WebP when:

• You need broad support but want better-than-JPEG compression. WebP's support is universal at this point and its compression is close enough to AVIF for most use cases.
• Your CDN or image-processing pipeline charges per format and AVIF re-encoding is more expensive.

Stick with PNG when:

• You're working with graphics, icons, logos, or screenshots where you need lossless precision and the file size is already small (PNG's overhead matters less on small images).
• You need single-bit transparency for crisp edges (text, line art, UI elements).

A note on AVIF encoding speed

AVIF's one real downside vs. JPEG and WebP is encoding time. AV1 is computationally expensive, and producing an AVIF image takes 5–20× longer than producing the equivalent JPEG. For one-off image saves this doesn't matter — but for batch pipelines processing thousands of images, the cost adds up.

In 2026 this is mostly mitigated by:

• GPU-accelerated AVIF encoders (libaom and SVT-AV1) that bring encoding cost closer to WebP levels on modern hardware.
• Tiered encoding at CDNs — store a JPEG/WebP for fast initial serving, generate AVIF lazily in the background.
• Pre-encoding at build time rather than on-demand.

For end-user tools like ImageSuite's converter, encoding speed is invisible — a single 5MB photo encodes in 2–4 seconds in the browser.

When AVIF gets weird

A few specific cases where AVIF doesn't behave the way you might expect:

• Some Cog-based AI model containers can't decode AVIF. They decode images by file extension using OpenCV, which doesn't bundle AVIF support. If you upload AVIF to an AI image tool and it crashes with "NoneType has no attribute 'shape'", that's the issue — convert to JPEG first. (ImageSuite's Pro AI tools auto-convert AVIF inputs to avoid this.)
• Animation support exists but is limited. AVIF supports animated images like WebP and APNG, but tooling around animated AVIF (editors, viewers) is sparser. For animated content, WebP and APNG are more practical.
• Metadata handling varies. EXIF and XMP metadata can be embedded in AVIF, but some converters strip it silently. If you need to preserve photographer credit or copyright info, verify it survived the conversion.

Should you re-encode your existing JPEGs to AVIF?

Probably not, unless:

1. You have a specific reason to care about disk space at scale (image hosting, archival, CDN bandwidth).
2. You're willing to keep both formats around for backward compatibility.

For personal use, the file-size win is usually not worth the workflow disruption. For a website serving the public, an AVIF-first pipeline with WebP and JPEG fallbacks is the right modern setup, and most CDNs (Cloudflare, Fastly, AWS) automate that for you.

Try AVIF conversion

If you want to see how AVIF performs on your own images, ImageSuite's free image converter supports AVIF output (and accepts AVIF input). Drop in a JPEG, convert to AVIF, and compare the file sizes side by side. Everything runs in your browser — your photos never leave your device.

For more on choosing between formats, see JPG vs PNG vs WebP vs AVIF — the 2026 guide.