HEIC / HEIF Format Guide (and Why Windows Can't Open It)
If you've ever AirDropped a photo from an iPhone to a Windows PC and watched it refuse to open, you've met HEIC. It's Apple's default photo format since iOS 11, it saves real storage, and it's also the single most common reason people end up searching "how do I open this file." This guide explains what HEIC/HEIF actually is, why Apple ships it, why Windows often can't read it, and the two ways to fix that.
What is HEIC / HEIF?
HEIF (High Efficiency Image Format) is the container; HEIC is the specific variant Apple uses, where the image data is encoded with HEVC (H.265) intra-frame compression — the same codec family used for video, applied to a single still frame. Files carry a .heic extension. The headline benefit: roughly half the file size of a JPEG at comparable visual quality.
Because it borrows from a modern video codec, HEIF does things JPEG never could. A single .heic file can hold multiple images (think burst shots or the still frame of a Live Photo), an alpha transparency channel, image edits stored non-destructively, depth maps for Portrait mode, and HDR/wide-gamut data with more than 8 bits per channel. JPEG is a flat, single 8-bit image and nothing more.
It's worth separating the layers in your head:
- HEIF — the file format / container (
.heif,.heic). - HEVC — the actual compression codec doing the work inside.
- HEIC — Apple's name for HEIF-wrapped HEVC stills.
This matters on Windows, because the missing piece is usually the codec, not the container.
Why does Apple use HEIC instead of JPEG?
The short answer is storage and capability. At similar perceived quality, HEIC files are roughly half the size of JPEG, so iPhones fit far more photos in the same space and iCloud syncs faster. HEIC also natively carries HDR, wide color, depth, and the still frame of a Live Photo — things JPEG simply can't represent.
For Apple's ecosystem this is close to free: every modern iPhone, iPad, and Mac decodes HEVC in hardware, so the heavier math never costs the user anything noticeable. The friction only appears the moment a file leaves that ecosystem — which is exactly where the Windows problem starts.
Why can't Windows open HEIC files?
Windows doesn't ship the HEVC codec by default for licensing reasons. HEVC carries patent-pool royalties, so Microsoft leaves the decoder out of a clean Windows install. Without it, Photos and File Explorer can't render the image data inside a .heic file, even though they recognize the format.
You'll typically see one of these symptoms:
- Photos opens but shows a gray/blank frame or a codec error.
- File Explorer shows a generic icon with no thumbnail.
- An older app (Photoshop CS6, legacy Office, most web uploaders) rejects the file as unsupported.
The same applies to plenty of Android phones, Linux distros, and older Adobe versions — the format is recognized, the decoder is absent.
Fix option 1: install the HEVC extensions
On Windows 10/11 you can add the missing codec through the Microsoft Store:
| Extension | What it does | Cost |
|---|---|---|
| HEIF Image Extensions | Lets Windows read the HEIF/.heic container | Free |
| HEVC Video Extensions | Provides the HEVC decoder the images actually need | Paid (small fee) — a free OEM build ships on some PCs with supported hardware |
Install both, restart Photos, and .heic files open natively with thumbnails. This is the right call if you receive HEIC constantly and want the OS to just handle it.
The catch: it's per-machine, sometimes costs money, the free OEM version isn't reliably available, and it does nothing for old apps or websites that reject .heic outright. For a one-off conversion, it's often overkill.
Fix option 2: convert to JPG (works on any Windows PC)
If you just need a universally openable file, convert it. You can convert HEIC to JPG right in your browser and download a standard JPEG. Because the decoding and encoding run locally, nothing is uploaded (open DevTools' Network tab and you'll see no file leaving your machine), there's no watermark, and it's free. JPG opens everywhere — every OS, every app, every upload form — so this sidesteps the codec problem entirely instead of patching it.
The honest limitation: in-browser HEIC decoding
One caveat worth stating plainly. Decoding HEIC in a browser leans on either the browser's own HEVC support or a WASM decoder. On Safari and most Macs this is seamless. On some Windows + Chrome setups that lack the HEVC codec, the browser can't natively decode HEIC at all — a real constraint, not a marketing footnote. A good in-browser tool ships a WASM fallback decoder to cover those cases, but if you hit a file that won't preview, that missing system codec is usually why. Converting on a Mac, or installing the extensions above, both resolve it.
HEIC vs JPG: which should you keep?
| Factor | HEIC | JPG |
|---|---|---|
| File size (same quality) | ~50% smaller | Baseline |
| Compatibility | iOS/macOS native; Windows/old apps need a codec | Universal |
| Color depth | 10-bit+, HDR, wide gamut | 8-bit only |
| Transparency | Yes (alpha) | No |
| Multi-image / Live Photo frame | Yes | No |
| Depth map (Portrait) | Yes | No |
| Editing / web upload support | Limited | Excellent |
| Royalty-free | No (HEVC patents) | Effectively yes |
Rule of thumb: keep HEIC as your archive on Apple devices to save space and preserve HDR/depth, but convert to JPG whenever a file needs to travel — into a Windows workflow, an old app, a web upload, or a print service.
Quality considerations when converting
HEIC → JPG is a one-way trip in two senses. First, you re-encode from an already-compressed source, so push the JPEG quality slider high (90+) to avoid stacking visible artifacts. Second — and this is the part people miss — the extras don't survive: HDR tone-mapping collapses to standard dynamic range, 10-bit color drops to 8-bit, transparency is lost, and a depth map or burst stack is discarded. For an ordinary photo you won't notice; for an HDR sunset or a Portrait shot you're flattening real data. If those matter, keep the original HEIC and export a JPG copy rather than replacing it.
A related case: if the file is actually a Live Photo, the .heic is only the still frame — the motion lives in a paired HEVC .mov. To keep the movement, convert the Live Photo to a video or to an animated GIF instead of flattening it to a single JPG. For the full breakdown of how these formats fit together, see the HEIC guide and the Live Photo format reference.
Bottom line
HEIC isn't broken — it's a genuinely better still-image format that Windows just can't decode out of the box. If you live in Windows, install the HEVC/HEIF extensions for native support, or skip the patch entirely and convert your HEIC file to JPG in the browser — no uploads, no watermark, works on any machine. Keep HEIC where it shines (Apple, archiving, HDR) and reach for JPG the moment a file has to leave home.