In this article:

• What AVIF actually is, who built it, what problem it solves

• Why the same image is ~50% smaller than JPEG and ~20% smaller than WebP at equivalent quality

• When AVIF is the right call — and when it isn't

• 2026 browser support: is it finally safe to use everywhere?

Let me start with one number. The same 1920×1080 photo, encoded at the quality where the human eye can't tell them apart:

• JPEG at q75: 263 KB

• WebP at q75: 168 KB

• AVIF at q50: 102 KB

Three formats. Same image. Same perceived quality. The AVIF version is less than 40% the size of JPEG.

That single number is why we're having this conversation in 2026. But "use AVIF" is the easy answer. The harder, more useful one is when to use it — and when not to. That's what this guide covers.

What Is AVIF, Briefly

AVIF stands for AV1 Image File Format. It was released in 2019 by the Alliance for Open Media, a consortium of companies that wanted a royalty-free, open-source image compression standard. The roster includes Google, Mozilla, Cisco, Apple, Netflix, Amazon — basically the companies that pay the most in bandwidth costs and care the most about open standards.

Why a new format at all? The image format landscape in 2019 looked like this:

• JPEG (1992): Still everywhere. Still 34 years old.

• PNG (1996): Lossless, but huge for photos.

• HEIC (2015): Apple-developed, used by iPhones. Patent-encumbered, expensive to license.

• WebP (2010): Google's attempt to replace JPEG. Got stuck because Safari took a decade to support it.

The opening: a modern, royalty-free format that actually used the latest compression research. AVIF is built on top of the AV1 video codec — the same codec YouTube and Netflix use for HD/4K streaming. AVIF is essentially "one frame of AV1 video, saved as an image."

The result: the full power of modern video compression, applied to a single still image.

How It Actually Works

You can skip this section if you don't care about the technical details — but understanding the basics helps you make better calls about when AVIF helps and when it doesn't.

AVIF compresses an image by breaking it into blocks (anywhere from 8×8 to 128×128 pixels). For each block, the encoder predicts what it should look like based on neighboring blocks, then stores only the difference between the prediction and the actual content.

Imagine you're encoding a photo of a sky. You've got 10 nearly-identical blocks of blue. AVIF says "look at the first block, the next 9 are basically the same with tiny corrections." That's intra-frame prediction, and JPEG doesn't have it. JPEG compresses every block independently. That's why JPEG creates visible banding in gradients — skies, sunsets, blurry backgrounds.

Two other technical wins worth mentioning:

Wider color depth. JPEG is locked to 8-bit per channel (256 shades). AVIF supports 10 and 12-bit (1024 and 4096 shades). This matters for HDR photos — JPEG literally can't store HDR information; AVIF can.

Alpha channel. Transparency, like PNG. AVIF supports it, JPEG doesn't, and AVIF transparent images are typically 60-80% smaller than equivalent PNGs.

AVIF vs WebP vs JPEG — Real Numbers

I tested the same 1920×1080 photo across all three formats, calibrating quality settings so the perceptual quality (measured with DSSIM) was identical:

Three takeaways:

1. AVIF wins on file size by a wide margin. Same visible quality, 60-75% less storage. The bandwidth savings are massive, especially for mobile users.

2. Encoding is slow. JPEG encodes in 50ms, AVIF can take 1.5 seconds for the same image. This isn't a user-facing problem (you only encode once), but it matters for batch jobs. AVIF uses significantly more server CPU.

3. Browser support is 94%. That means 6% of your visitors can't see AVIF. This is why fallback strategy still matters (more on that below).

When to Use AVIF (and When Not)

Switching every image to AVIF tomorrow is not the right move. Some use cases make sense, some don't. Here's how I think about it:

✅ Use AVIF

• Web hero images — Page speed is critical, bandwidth matters, 6% fallback is acceptable

• Photography portfolios — High resolution, lots of files, storage costs add up

• E-commerce product images — Page load impacts conversion, milliseconds count

• Blog cover images — Core Web Vitals affect SEO rankings

• HDR photos — JPEG can't preserve HDR; AVIF can

• Transparent backgrounds — Replace PNG, get 80% smaller files

❌ Don't Use AVIF (yet)

• Email content — Many email clients still don't render AVIF (Outlook 2019 doesn't)

• Legacy systems — Enterprise B2B tools, government portals

• Print pipeline — If it's going to PDF/PSD eventually, use JPEG/PNG

• Older Photoshop workflows — Pre-2022 versions can't open AVIF directly

• Internal admin panels where speed doesn't matter

🟡 The Hybrid Approach (What I Actually Do)

In practice, I generate three versions of every image:

• AVIF (modern browsers)

• WebP (older Chrome/Firefox)

• JPEG (universal fallback)

Then let the browser pick using the <picture> element:

`<picture>
  <source srcset="hero.avif" type="image/avif">
  <source srcset="hero.webp" type="image/webp">
  <img src="hero.jpg" alt="...">
</picture>
`

The browser checks in order: Does it support AVIF? Yes → load AVIF. No? WebP? Also no? Load the JPEG. Every visitor gets the smallest file their browser can handle.

This triples your storage cost (three copies of each image), but bandwidth savings usually make up for it. If you're paying for a CDN, the numbers work out fast.

Browser Support in 2026

Last time I checked caniuse.com (early 2026), AVIF support looks like:

• Chrome — Since August 2020 (5+ years)

• Firefox — Since October 2021 (4+ years)

• Safari — Since March 2023 (Safari 16.4+)

• Edge — Since January 2024 (version 121+)

• iOS Safari — Since March 2023

Total global coverage: ~94%.

What this means: Using AVIF in 2024 was an "early adopter" move. In 2026, it's a standard choice. You still need to think about the 6% fallback — that's what <picture> solves.

If your audience skews corporate (Internet Explorer might still be alive in some IT departments!) or is heavy on older Asian Samsung devices, that 94% might be lower for you. Check your actual analytics before assuming.

*Converting to AVIF with *SwapFile.io

This is exactly the problem SwapFile.io was built for. You want to convert old JPEGs to AVIF, but you don't have Photoshop, you don't know ImageMagick from the command line, and you definitely don't want to upload your family photos to some random cloud service.

Our JPEG to AVIF converter handles this directly:

• Drop the file in the browser (under 1 second)

• Conversion happens on our server

• Files auto-delete after 1 hour — we never see them, no third party has access

• No cloud storage. No account required (up to 15MB without signup)

We also support PNG, HEIC, WebP, GIF, and a few others — all convertible to AVIF. The full tools page lists every supported conversion.

Frequently Asked Questions

Why can't I see AVIF thumbnails in Windows Explorer?

Windows 11 doesn't ship with AVIF support by default. Install the AV1 Video Extension from the Microsoft Store (it's free). Once installed, File Explorer will show thumbnails automatically.

Photoshop won't open my AVIF file.

Photoshop CC 2022 (version 23.2) and later support AVIF natively. If you're on an older version, either upgrade or convert AVIF back to JPEG first.

Is AVIF quality worse than JPEG?

At the same file size, AVIF is better. At the same quality, AVIF is smaller. So: JPEG at quality 80 looks the same as AVIF at quality 50, but the AVIF is half the size. At very low quality settings (q20 or below), both formats produce visible artifacts, but AVIF generally degrades more gracefully.

Will AVIF preserve HDR from my iPhone photos?

Yes. AVIF supports 10-bit and 12-bit HDR. JPEG can't store HDR information (8-bit limit). If you've shot HDR on an iPhone Pro and want to preserve it when moving to a PC, AVIF is the right format.

Should I convert PNG files with transparency to AVIF?

Usually yes. PNG-to-AVIF conversion typically saves 60-80% on file size while preserving the alpha channel. The exception: tiny icons (16×16, 32×32) — at that size PNG is already small, and AVIF's encoding overhead negates the savings.

Does AVIF hurt mobile performance?

Decoding AVIF is 2-3x slower than JPEG, but on modern mobile devices the difference is measured in milliseconds. The smaller file size = faster network download more than compensates. Net effect: faster page loads on mobile.

Does using AVIF help SEO?

Not directly. But it improves Core Web Vitals (specifically LCP — Largest Contentful Paint), which is a Google ranking factor. Switching to AVIF typically drops LCP by 200-500ms. So: indirectly, yes.

The Bottom Line

One sentence: AVIF should be your default web image format in 2026, paired with a fallback strategy.

Exceptions: email, print pipelines, legacy systems. In those, stick with JPEG/PNG.

If you're currently serving JPEG and care about page speed (e-commerce, blog, portfolio), switching to AVIF typically pays back in bandwidth savings within 1-3 months. Encoding time is a one-time cost. Storage costs increase slightly. Bandwidth savings are continuous.

Your next step:

• Convert 5 different photo types using our AVIF converter (portrait, landscape, product shot, screenshot, HDR)

• Compare side by side — same quality? Yes → look at the file size difference

• Convert the 10 most-used images on your site/blog to AVIF

• Add <picture> tag fallback to your HTML

• Re-run PageSpeed Insights — watch LCP drop

Related Reading:

• WebP vs JPEG: A 2026 Comparison

• What Is HEIC? Why Windows Can't Open iPhone Photos

• Lossy vs Lossless: Which Image Compression Should You Use?

Originally published on SwapFile.io. I'm building SwapFile.io in public — a privacy-first image converter (HEIC, AVIF, WebP, JPG, PNG, BMP, TIFF, PDF). Files auto-delete in 1 hour, no Google Analytics, free for the first 6 months. Try it: swapfile.io. Feedback welcome.