Opening HEIC on Windows: The Extensions, the Settings and the Permanent Fix

Windows 10 and 11 gained HEIF/HEIC support as an installable extension. Open the Microsoft Store and search 'HEIF image extensions' — the current builds offer it free (older Windows 10 versions sold a paid 'HEVC Video Extensions' variant; the modern package is the free one). Once installed, double-clicking a .heic opens it in Photos, thumbnails render in Explorer, and Mail attachments preview normally.

The honest limitations of that fix: it makes HEIC displayable, not universal — apps that read images through their own pipelines (an old website editor, a print shop's upload form, a workplace viewer locked to JPEG/PNG) still see an unsupported format. And it only helps your machine; the person you email the original HEIC has not installed anything.

Two settings fix this at the source, and they are worth five minutes once per device. Settings → Photos → scroll to the bottom → Transfer to Mac or PC: set to Automatic, and any copy to a computer via cable rewrites HEIC to JPEG on the fly — your library stays efficient on the phone, your PC folder is universally readable.

Settings → Camera → Formats → Most Compatible stops the problem even earlier: new photos are captured as JPEG directly. You lose the roughly 50% size advantage of HEIC in your library, which on a 256 GB phone with a big photo habit is a real cost — the usual recommendation is keeping HEIC capture and using the transfer rewrite or per-share conversion.

And the setting nobody mentions: the share sheet. Tapping the share button and sending via Mail, Messages (in most configurations) or third-party apps re-encodes to JPEG at that moment. The HEIC that confuses your PC is a library file, not the form the photo takes when you share it normally.

For folders of photos you already have on the PC — a library copied years ago, a family's camera roll dumped to a drive — conversion is the right move, and the upload-based converters most people find first carry a specific problem: iPhone photos embed GPS coordinates in their EXIF, so a bulk 'convert my holiday album' upload is sending locations and timestamps along with the pixels.

A browser HEIC converter handles up to 20 files per batch: select them all, quality 90, download the JPGs. The WebAssembly decoder runs in the tab; the Network tab shows nothing leaving (and the HEIC format guide covers why the format exists at all). For a whole library (hundreds to thousands), a desktop script with a HEIC-capable ImageMagick build runs unattended overnight — the browser batch is for the folder, the script is for the archive.

Two real edge cases. A file that is not actually HEIC — some apps write HEVC-encoded images into .heic wrappers that the phone's own decoder handles but a generic converter does not; if the browser's converter rejects a file the Photos app opens, that is usually it, and the workaround is the share-sheet copy on the phone. And live photos: the .heic you see is the still frame of a paired asset, and converting it loses the motion half — the full Live Photo needs the phone's own share route to become a video or GIF.

Also worth knowing: a converted JPEG is a one-way door. The HEIC had better tonal range (it is 16-bit internally where JPEG is 8-bit), so the conversion discards a little fidelity permanently — invisible on screen, present in heavy re-editing. Keep the original library somewhere and treat the JPGs as sharing copies.

The permanent fix is rarely technical and mostly habitual: cloud photos services (iCloud, Google Photos) deliver JPEG-compatible versions on the web to anyone you share with, the share sheet converts on send, and the PC gets JPEGs via the Automatic transfer setting. With those three in place, HEIC stops ever appearing at a compatibility boundary — it stays what Apple intended it to be, an efficient storage format nobody outside the phone's library ever sees.