HEIC (High Efficiency Image Container — also called HEIF) is the format Apple has used for iPhone photos by default since iOS 11 (2017). It's roughly half the size of an equivalent JPG at the same visual quality, supports HDR and wide colour gamuts, and can store multiple images per file (live photos, burst shots).
The format's compression is based on HEVC (H.265 video). HEVC is patented, which means most non-Apple platforms either don't support HEIC natively or require licensed decoders. This is why HEIC photos shared from iPhones often appear as 'can't open this file' on Android, Windows, and most web platforms.
The practical answer is conversion: if you're sharing or publishing iPhone photos, convert HEIC to JPG before sending. The tools linked below do this entirely in your browser, with no upload. If you're staying in the Apple ecosystem, HEIC is the better format — keep it. If you're sharing widely, JPG is still the universal standard.
History — introduced 2015
By: MPEG (ISO/IEC standardised) — adopted by Apple in 2017
HEIF was standardised by MPEG in 2015 as a still-image format using HEVC video compression. Apple adopted HEIF (using the .heic extension) as the default iPhone photo format with iOS 11 in 2017. Despite the technical merits, broader adoption has been slow because the underlying HEVC compression is heavily patented and requires licensed decoders.
How it works
HEIC uses HEVC (H.265) intra-frame compression — the same video codec used in 4K Blu-ray and many streaming services. Each image is encoded as a single video frame in a HEIF container (ISOBMFF, the same container format as MP4). The container supports multiple images per file, which is how Apple stores live photos and burst sequences.
Because HEVC requires patent licensing for both encoding and decoding, HEIC support is not universal — most desktop browsers, most CMSes, and many image editors can't render HEIC without an additional licensed decoder.
Strengths and weaknesses
Strengths
- Roughly half the size of an equivalent JPG at the same visual quality.
- Supports HDR and 16-bit colour depth — full dynamic range capture from modern iPhone cameras.
- Stores multiple images per file (live photos, burst shots, depth maps).
- Excellent integration in the Apple ecosystem — Photos, Mail, Messages all handle HEIC natively.
Weaknesses
- Effectively unsupported outside Apple — most browsers, CMSes, social platforms and image editors can't render HEIC without conversion.
- Patented compression (HEVC) limits adoption by open-source software.
- Editing tools outside Apple's ecosystem rarely have native HEIC support.
- Sharing iPhone HEIC photos to non-Apple recipients usually means converting first.
When to use it
- iPhone photo storage in iCloud (efficient, native, supports all camera features)
- Within the Apple ecosystem — Mac, iPad, iPhone, Apple TV all handle HEIC natively
- Local backups of iPhone photo libraries
- Print workflows that integrate with the Apple ecosystem (Photos app, Apple Print)
When NOT to use it
- Anywhere you're sharing photos with non-Apple users — convert to JPG first.
- Web publishing — virtually no browser other than Safari renders HEIC.
- Image editing outside the Apple ecosystem — convert to a more universally-supported format.
- Social platforms — most platforms accept HEIC uploads but convert them server-side, so you might as well convert client-side to control quality.
Browser support
Global coverage: 5%
| Browser | Support |
|---|---|
| Chrome | Not supported (no native decoder) |
| Firefox | Not supported |
| Safari | 17+ (2023) on macOS / iOS — works |
| Edge | Not supported |
| Legacy / notes | Effectively Apple-only. On other platforms, HEIC needs converting to JPG or PNG before display. |
Performance considerations
- HEIC decoding on Apple hardware is hardware-accelerated and fast.
- On non-Apple platforms with licensed decoders, decoding is slower than JPG.
- HEIC files are dramatically smaller than JPG — iPhone photo libraries take ~half the storage when kept in HEIC.
SEO considerations
- HEIC is not a web format. Search engines index image alt text and surrounding content, not HEIC file contents directly.
- If you're publishing iPhone photos to the web, convert HEIC → JPG or WebP before upload. Always include descriptive alt text.
Common mistakes
- Uploading HEIC files directly to a website — most users won't see them.
- Emailing HEIC photos to non-Apple recipients without converting first.
- Editing HEIC in tools that secretly convert to JPG with loss before saving — check the editor's behaviour or convert intentionally first.
- Assuming 'HEIF' and 'HEIC' are different. They're effectively the same — HEIC is HEIF using HEVC compression.
Frequently asked questions
- Why won't my computer open HEIC files?
- HEIC uses patented HEVC compression. Most platforms outside the Apple ecosystem need a licensed decoder. Windows 11 supports HEIC via a paid Microsoft Store extension; many Linux setups and most websites won't render HEIC at all. The cleanest fix is converting to JPG.
- Should I change my iPhone to take JPG instead of HEIC?
- If you mostly share photos with non-Apple recipients, yes — Settings → Camera → Formats → 'Most Compatible' switches your iPhone to JPG. You'll trade roughly 2× the storage for universal compatibility. If you stay in the Apple ecosystem, HEIC is better.
- Does HEIC support transparency?
- Yes — the format supports alpha transparency. In practice it's rarely used for iPhone photos (which don't have alpha) but the spec supports it.
- How do I convert HEIC to JPG?
- Use the HEIC to JPG converter linked below — it runs entirely in your browser, with no upload. The conversion is lossy (any re-encoding step is), but quality loss is invisible at q90 and the result is universally readable.
- Will HEIC strip metadata or GPS data?
- No — HEIC carries EXIF metadata including GPS, just like JPG. If you're sharing iPhone photos and don't want to include the GPS coordinates of where they were taken, strip metadata before sharing.