HEIF: Browser Support, Features, Known Issues

What is HEIF?

HEIF stands for High Efficiency Image File Format. The Moving Picture Experts Group published it as ISO/IEC 23008-12, also known as MPEG-H Part 12. The container stores still images, bursts, image sequences, derived images, depth maps, alpha masks, and metadata in one file. HEIF still images use the .heif extension and image sequences use .heifs, while the HEVC profile (HEIC) uses .heic and .heics. The same container also holds AV1 frames as AVIF and AVC frames as AVCI.

Which browsers does HEIF support?

HEIF works only in Safari. Apple added HEIC rendering to Safari 17 on macOS and iOS, while Chrome, Firefox, Edge, Opera, Samsung Internet, Android Browser, and Internet Explorer still treat HEIF files as unknown.

What are the key features of HEIF?

HEIF combines a flexible ISOBMFF container with modern codec support, multi-image storage, and rich metadata. The features below decide whether HEIF fits a project beyond the iPhone camera.

• Small file size: HEIF stores a photo at about half the size of an equivalent-quality JPEG, because HEVC compresses still frames more aggressively than JPEG's DCT.
• Multiple codec profiles: The same container can carry HEVC (HEIC), AV1 (AVIF), AVC (AVCI), JPEG, JPEG 2000, JPEG XR, and JPEG XS. Apps choose the codec without changing the container.
• Multi-image storage: One HEIF file can hold a burst, a focal stack, a panorama, a Live Photo, or a derived edit alongside the original. The container preserves the relationship between frames.
• Derived images and non-destructive edits: HEIF stores edit instructions, such as crop, rotate, and overlay, as separate metadata so the original pixels stay intact.
• Auxiliary data: The container holds depth maps, alpha masks, and segmentation data, which Portrait mode and Magic Eraser tools read for blur and cutouts.
• Wide color and HDR: HEIF supports 10-bit color, BT.2020 wide gamut, and HDR10 metadata when the codec inside is HEVC or AV1.
• Alpha transparency: HEIF carries an 8-bit alpha channel, which makes it a JPEG replacement for icons and overlays where PNG was the only option.
• ISOBMFF foundation: The container reuses the ISO Base Media File Format that powers MP4 and MOV, so HEIF inherits the same boxing model and parser ecosystem.

How do you enable HEIF in your browser?

There is no flag or setting that turns on HEIF in Chrome, Firefox, Edge, Opera, or Samsung Internet. The only browser path to HEIF is updating to Safari 17 or later. For every other browser, the practical option is to ship a fallback inside a picture element or decode HEIF in JavaScript.

• Safari on macOS: Update to Safari 17 on macOS Sonoma or later. HEIC rendering is built in with no flag to flip.
• Safari on iOS and iPadOS: Update the device to iOS 17 or iPadOS 17 or later. Safari, Safari View Controller, and WKWebView all show HEIC.
• Chrome and Chromium browsers: No native HEIF setting exists. Even on macOS, Chrome does not call into the OS HEIC decoder for img tags. Use a JPEG, WebP, or AVIF fallback.
• Edge on Windows: Install HEIF Image Extensions from the Microsoft Store to view HEIC in File Explorer, Photos, and Paint. The extension does not enable HEIC inside Edge web pages.
• Firefox: No native setting and no plugin. The Mozilla bug for HEIF support is at priority P5 with no shipping plan.
• JavaScript workaround: Use libheif-js or heic2any to decode HEIF in the browser through WebAssembly and convert each frame to a JPEG, PNG, or WebP blob you can paint into an img or canvas.
• Picture element fallback: Serve HEIC inside a picture element with AVIF, WebP, and JPEG sources after it. Browsers that cannot read image/heic skip ahead to the next source.

The picture element pattern below covers Safari 17+, Chrome and Firefox through AVIF and WebP, and ancient browsers through the final JPEG src:

<!-- Picture element fallback chain for HEIC photos.
     Safari 17+ shows the HEIC source. Chrome, Firefox, Edge,
     and Opera fall through to AVIF, WebP, then JPEG. -->
<picture>
  <source type="image/heic" srcset="hero.heic" />
  <source type="image/avif" srcset="hero.avif" />
  <source type="image/webp" srcset="hero.webp" />
  <img
    src="hero.jpg"
    alt="Studio portrait, served as HEIC for Safari and JPEG everywhere else"
    width="1200"
    height="800"
    loading="lazy"
  />
</picture>

What are the known issues with HEIF?

HEIF is the default photo format on the most popular phone in the world, and almost every browser still cannot show it. The mismatch creates real failures across uploads, email, content management, and analytics.

• iPhone-default but web-broken: iPhone Camera saves photos as HEIC by default, yet Chrome, Firefox, Edge, Opera, and Samsung Internet cannot show HEIC images. A user uploading a HEIC selfie to a non-Safari browser sees a broken image icon unless the site decodes the file in JavaScript.
• HEVC patent licensing: HEVC, the codec inside HEIC, has two patent pools, Via LA and Access Advance, with overlapping but separate license fees. The cost and complexity is the main reason Chrome, Firefox, and Edge cite for not adding HEIF support.
• OS-level decoding does not reach the browser: macOS, Windows 11, and Android can decode HEIF at the system level, but Chrome, Edge, and Firefox do not pipe that decoder into their img rendering path. Installing HEIF Image Extensions on Windows fixes File Explorer, not Edge web pages.
• CMS uploads reject .heic files: WordPress, Drupal, and many headless CMSes block .heic uploads by MIME type allowlist, because their renderers cannot show the file. Editors get a rejection error from the upload form.
• Email clients drop HEIC inline previews: Gmail web, Outlook web, and most webmail clients cannot render HEIC inline. The recipient sees the file as a download attachment instead of a preview.
• Server tooling is uneven: Sharp, ImageMagick, and Cloudinary support HEIF only when built with libheif and a paid HEVC license. Default Linux distributions ship without libheif, so a server that worked yesterday can refuse HEIC after a deploy.
• Conversion is the common workaround: Most pipelines transcode HEIC to JPEG, WebP, or AVIF on upload. The conversion adds CPU cost, can lose HDR or depth data, and breaks Live Photos or burst metadata.
• File extension confusion: The same file may be .heif, .heifs, .heic, .heics, .avci, .avcs, or .HIF, depending on the codec inside and the camera that wrote it. Allowlists and analytics dashboards often miss the long tail.
• Internet Explorer never supported it: IE never added HEIF support, and Microsoft has retired the browser. Anyone on IE needs a JPEG or PNG fallback in the picture element.

In my experience, the most surprising failure happens on macOS. The operating system can decode HEIC for Preview and Quick Look without breaking a sweat, yet Chrome and Firefox on the same machine still refuse to render HEIC inside img tags. Engineers assume the OS-level decoder is enough, ship HEIC URLs to production, and only catch the gap when a non-Safari user reports a broken hero image.

Citations

All HEIF version numbers and platform notes in this guide come from these primary sources:

• MDN Web Docs - Image file type and format guide: developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Image_types
• Wikipedia - High Efficiency Image File Format: en.wikipedia.org/wiki/High_Efficiency_Image_File_Format
• ISO/IEC 23008-12 - HEIF standard: iso.org/standard/83650.html
• WebKit - WebKit Features in Safari 17.0: webkit.org/blog/14445/webkit-features-in-safari-17-0
• Apple Support - Using HEIF or HEVC media on Apple devices: support.apple.com/en-us/116944
• Apple Developer - WWDC17 Session 513 on HEIF: developer.apple.com/videos/play/wwdc2017/513
• Microsoft Store - HEIF Image Extensions: apps.microsoft.com/detail/9pmmsr1cgpwg
• Mozilla Bugzilla - Bug 1402293 (HEIF support): bugzilla.mozilla.org/show_bug.cgi?id=1402293
• Nokia Technologies - HEIF specification site: nokiatech.github.io/heif
• Via LA - HEVC patent pool: via-la.com/licensing/hevc