AVIF Browser Support: Complete Guide for 2026

"Does AVIF work in Safari?" is a question people still ask in 2026. The answer has been yes since 2023. Here's the complete browser-support landscape and what fallback strategy makes sense.

The summary table

In 2026, AVIF is supported by every browser version still receiving security updates.

Caniuse global percentage (2026)

Combined global support across all browsers: 97.8%. The 2.2% missing is:

• Internet Explorer (deprecated since 2022)
• Some industrial-control browsers
• Older feature phones

For practical purposes, you can ship AVIF without a fallback to 98% of your audience.

Should you drop the JPEG fallback?

It depends on your audience.

Drop it if:

• Your audience is mostly Western consumer market (97-99% AVIF support).
• You're shipping a SaaS or content site, not legacy enterprise.
• You have analytics showing < 2% of traffic on browsers without AVIF.

Keep it if:

• You serve government, healthcare, or enterprise. These audiences run older browsers.
• You support APAC markets with high feature-phone penetration.
• The fallback is cheap (you already have JPGs in your image library).

The fallback cost is mostly storage. Encoding once, storing two formats, serving via <picture> with <source>, minimal overhead.

A realistic 2026 fallback strategy

<picture>
  <source srcset="image.avif" type="image/avif">
  <source srcset="image.webp" type="image/webp">
  <img src="image.jpg" alt="..." width="1600" height="900">
</picture>

This serves:

• AVIF to 97.8% of browsers
• WebP to the next 1.5% (mostly slightly-older Firefox / Safari)
• JPEG to the remaining 0.7%

Three formats per image is more storage but covers every case. See How to Use the HTML Picture Element.

What about email?

Email is the legacy world. Stick with JPG in email. Most email clients don't render AVIF. Some don't render WebP. This isn't going to change soon.

What about Microsoft Office?

PowerPoint and Word handle AVIF in 2024+ versions but it's flaky. If you're embedding images in slides or docs that will be opened on older Office installs, use JPG.

What about PDFs?

PDF readers in 2026 mostly handle AVIF, but the spec doesn't require it. Embed PDFs with JPG images for maximum compatibility. OmegaPix's Images to PDF automatically converts AVIF input to JPG for embedding for this reason.

How AVIF support is measured

Several sources track browser support:

1. caniuse.com: probably the most cited. Combines self-reported support and user-agent data.
2. MDN compatibility tables: spec-level support, updated by Mozilla.
3. Google's CrUX: real Chrome user data.
4. Your own analytics: most honest for YOUR audience.

For decisions affecting your specific audience, check your own analytics.

Detection in JavaScript

If you need to feature-detect AVIF support in JS:

async function supportsAvif() {
  const img = new Image();
  img.src = 'data:image/avif;base64,...'; // minimal AVIF test image
  return new Promise(resolve => {
    img.onload = () => resolve(true);
    img.onerror = () => resolve(false);
  });
}

You typically don't need this: <picture> element negotiation handles fallback at the browser level.

Conclusion

AVIF is safe for production in 2026. The "Safari doesn't support it" complaint is three years out of date. Ship AVIF as your primary format, WebP as a defensive fallback, JPG only if you're targeting legacy environments.

Related

• AVIF vs JPEG: Is the Switch Worth It in 2026?
• How to Use the HTML Picture Element for WebP and AVIF
• How to Serve Next-Gen Image Formats in 2026