HEIC Browser Support in 2026: What Works Where

HEIC browser support in 2026 is inconsistent and platform-dependent. Safari has full native support. Chrome supports HEIC on macOS and Android but not reliably on Windows or Linux. Firefox has no HEIC support. Edge depends entirely on operating system codecs.

This fragmented landscape makes HEIC unsuitable for web image delivery. For background on the format itself, see What is HEIC?. For a broader developer perspective, see HEIC for Web Developers.

Complete Browser Support Table

Safari is the only browser with unconditional HEIC support. Every other browser depends on OS-level codec availability, hardware decoding capabilities, or both.

| Browser | Desktop | Mobile | Conditions | | --- | --- | --- | --- | | Safari | Full support (macOS 11+) | Full support (iOS 11+) | Native HEVC decoder in Apple hardware | | Chrome | macOS: Yes. Windows/Linux: OS-dependent | Android 10+: Yes. iOS: Uses Safari engine | Requires OS HEVC codec since v118 (Oct 2023) | | Edge | OS-dependent (Windows needs HEVC extension) | Android: Limited. iOS: Uses Safari engine | Delegates to OS media framework | | Firefox | No support | No support on Android. iOS: Uses Safari engine | No HEVC integration planned | | Opera | Same as Chrome (Chromium-based) | Same as Chrome mobile | Inherits Chromium codec behavior | | Samsung Internet | N/A | OS-dependent on Android | Uses Android system media codecs | | Brave | Same as Chrome (Chromium-based) | Same as Chrome mobile | Inherits Chromium codec behavior |

What the numbers mean

Approximately 30-35% of global browser sessions can display HEIC natively. That figure includes all Safari users plus Chrome users on macOS and Android with working HEVC codecs. Compare this to WebP at 97%+ support and AVIF at 93%+ support.

The remaining 65-70% of browser sessions will display a broken image icon, trigger a download prompt, or show nothing at all. This failure rate makes HEIC unacceptable for production web delivery.

Safari: The Gold Standard

Safari has supported HEIC since 2017. Apple ships hardware HEVC decoders in every Mac, iPhone, and iPad sold since that year. Safari accesses these decoders directly through the operating system.

Safari HEIC support covers:

• macOS Safari 11+ (September 2017)
• iOS Safari 11+ (September 2017)
• iPadOS Safari 13+ (September 2019)

Safari decodes HEIC with zero performance penalty. The hardware decoder handles decompression without burdening the CPU. A 12 MP HEIC image renders in under 50 milliseconds on Apple Silicon Macs.

Safari also supports HEIC in CSS background-image, <img> tags, and the Canvas API. This makes Safari the only browser where HEIC works as a drop-in replacement for JPEG.

Chrome: Platform-Dependent Support

Chrome added HEIC support in version 118, released October 2023. However, Chrome does not bundle its own HEVC decoder. It delegates HEIC decoding to the operating system's media framework.

This creates 3 distinct outcomes:

• macOS: Full HEIC support. Chrome uses Apple's built-in HEVC decoder.
• Android 10+: HEIC support works on most devices. Android includes HEVC decoding in the media framework.
• Windows: HEIC works only if the user has installed the HEVC Video Extensions from the Microsoft Store. The extension costs $0.99 USD. Most Windows users do not have it installed.
• Linux: No HEIC support. Standard Linux distributions do not ship HEVC codecs due to patent concerns.

Chrome on Windows is the most unpredictable scenario. A web developer cannot know whether a Windows Chrome user has the HEVC extension installed. The image either renders or fails silently.

Edge: OS Codec Delegation

Edge inherits the same OS-dependent behavior as Chrome. Both browsers are built on Chromium and use the same media decoding pipeline.

On Windows, Edge has one potential advantage: Microsoft pre-installs the HEIF Image Extensions (not HEVC) on Windows 10 and 11. These extensions enable HEIF container parsing but not HEVC decoding. Users still need the separate HEVC Video Extensions for full HEIC support. The distinction between HEIF and HEVC extensions confuses many users.

Edge on macOS behaves identically to Chrome on macOS -- full HEIC support via Apple's system decoder.

Firefox: No Support

Firefox does not support HEIC on any platform. Mozilla has stated that HEVC patent licensing costs prevent them from adding native HEIC decoding. Firefox uses its own media stack rather than delegating to OS codecs, so platform-level HEVC availability does not help.

Firefox on iOS is an exception. Apple requires all iOS browsers to use WebKit as their rendering engine. Firefox on iOS therefore gains Safari's HEIC support through WebKit, not through Mozilla's codebase.

Firefox holds approximately 3% of global browser market share in 2026. Combined with the Windows and Linux Chrome users who lack HEVC codecs, the total non-HEIC-capable audience is substantial.

Mobile Browser Differences

Mobile HEIC support is stronger than desktop support. Apple controls both the browser engine and hardware on iOS. Android ships HEVC codecs on most modern devices.

iOS (all browsers)

Apple requires every iOS browser to use WebKit. This means Chrome, Firefox, Edge, Opera, and Brave on iOS all inherit Safari's HEIC support. Every browser on iOS can display HEIC images. iOS represents approximately 27% of global mobile browser usage.

Android

Android 10 (September 2019) added HEIF/HEIC support to the platform media framework. Chrome on Android 10+ can decode HEIC images. Samsung Internet and other Chromium-based Android browsers also work.

However, not all Android devices include hardware HEVC decoders. Budget Android phones may lack the necessary hardware. Software HEVC decoding is available but slower and battery-intensive.

The iOS advantage

iOS delivers 100% HEIC browser support. Android delivers approximately 85%. Desktop browsers average roughly 40-50% support, depending on the operating system mix of the audience.

Why HEIC Fails as a Web Format

Three factors disqualify HEIC from serious web use.

1. HEVC patent licensing

HEVC is covered by patents held by 3 major licensing pools: MPEG LA, Access Advance, and individual patent holders. Companies implementing HEVC decoders must negotiate licenses and pay royalties. Mozilla, the Linux kernel project, and many open-source tools refuse to include HEVC support. This is a structural barrier that will not resolve without patent expiration.

2. Inconsistent support creates unpredictable failures

A HEIC image on a webpage works for some users and breaks silently for others. There is no reliable way to predict whether a given browser session can decode HEIC. Silent image failures are worse than using a universally supported format at a slightly larger file size.

3. Superior royalty-free alternatives exist

WebP covers 97%+ of browsers and is royalty-free. AVIF covers 93%+ of browsers and is royalty-free. Both offer compression efficiency comparable to HEIC. There is no technical reason to serve HEIC when these alternatives exist.

Detecting HEIC Support in JavaScript

You can detect HEIC support by testing whether the browser can decode a small HEIC data URI. This is useful for upload workflows where you want to show a preview of HEIC files.

function checkHeicSupport() {
  return new Promise((resolve) => {
    const img = new Image();

    img.onload = () => {
      resolve(img.width > 0 && img.height > 0);
    };

    img.onerror = () => {
      resolve(false);
    };

    // Minimal valid HEIC encoded as base64
    img.src = 'data:image/heic;base64,AAAAGGZ0eXBoZWlj...';
  });
}

A more reliable approach uses the createImageBitmap API with a small HEIC blob:

async function detectHeicSupport() {
  try {
    const response = await fetch('/test.heic');
    const blob = await response.blob();
    const bitmap = await createImageBitmap(blob);
    bitmap.close();
    return true;
  } catch {
    return false;
  }
}

Feature detection is not a substitute for serving compatible formats. Even if you detect HEIC support, you still need fallback images for users whose browsers fail the test.

Fallback Strategies Using the Picture Element

The <picture> element is the standard way to serve multiple image formats with graceful degradation. Browsers select the first <source> they can decode and ignore the rest.

<picture>
  <source srcset="/images/photo.avif" type="image/avif" />
  <source srcset="/images/photo.webp" type="image/webp" />
  <img src="/images/photo.jpg" alt="Description" width="800" height="600" />
</picture>

This serves AVIF to 93%+ of browsers, WebP to the remaining modern browsers, and JPEG to everything else. Do not include a HEIC source in the <picture> element. Adding HEIC would cause Safari to select it over AVIF or WebP, which defeats the purpose of serving optimized web formats.

Content negotiation via Accept headers

Server-side content negotiation reads the browser's Accept header to serve the optimal format from a single URL.

function selectImageFormat(acceptHeader) {
  if (acceptHeader.includes('image/avif')) return 'avif';
  if (acceptHeader.includes('image/webp')) return 'webp';
  return 'jpg';
}

Always include Vary: Accept in response headers when serving different formats from the same URL. This prevents CDN caches from serving AVIF to a browser that only supports JPEG.

Better Web Alternatives to HEIC

Three formats cover the entire browser landscape without HEIC's compatibility problems.

| Format | Browser Support | File Size vs JPEG | Licensing | Best For | | --- | --- | --- | --- | --- | | WebP | 97%+ | 25-35% smaller | Royalty-free | Primary web format for all images | | AVIF | 93%+ | 30-50% smaller | Royalty-free | Maximum compression, HDR content | | JPEG | 100% | Baseline | Royalty-free | Universal fallback |

WebP is the safest default for web images in 2026. It delivers meaningful compression savings over JPEG with near-universal support. AVIF provides stronger compression but has a slightly smaller support footprint. JPEG remains the ultimate fallback.

For a detailed comparison of compression and quality, see HEIC vs WebP and HEIC vs AVIF.

Converting HEIC for the Web

The practical workflow is to keep HEIC originals for storage and convert to web formats for delivery. HEIC files from iPhones and iPads preserve maximum image quality and metadata. Converting to WebP, AVIF, or JPEG at publish time gives you browser compatibility without sacrificing source quality.

HEICify converts HEIC files to JPEG and PNG directly in your browser with no server uploads. Use the HEIC to JPG converter for photographs or the HEIC to PNG converter when you need lossless output. All processing happens client-side using Web Workers and libheif-js.

Key Takeaways

1. Safari is the only browser with full, unconditional HEIC support across both desktop and mobile.
2. Chrome supports HEIC on macOS and Android but depends on OS codecs on Windows and has no support on Linux.
3. Firefox does not support HEIC on any platform except iOS (where WebKit handles rendering).
4. Approximately 30-35% of browser sessions can display HEIC. The remaining 65-70% will see broken images.
5. Do not serve HEIC on websites. Use WebP (97%+ support) as the primary format with JPEG fallback.
6. Use the <picture> element to serve AVIF, WebP, and JPEG in priority order for optimal compression and compatibility.
7. Convert HEIC to web formats at publish time to maintain source quality while ensuring universal browser access.