What Is a HEIC File?

The extension you see, .heic, is Apple's branding of a format properly called HEIF — the High Efficiency Image File Format. Apple's own support documentation is explicit that HEIF and HEVC "offer better compression than JPEG and H.264, so they use less storage space on your devices and iCloud Photos, while preserving the same visual quality." That is the entire pitch: a smaller file, no visible trade-off.

HEIF itself is a general standard, not an Apple invention — it comes out of the same standards process (MPEG) that produced HEVC video, and Apple simply adopted it as the default still-image format starting with iOS 11 in 2017. Android gained native support for the same format two years earlier at the platform level than most people realise: Android 9 in 2018 "adds support for encoding images using the High Efficiency Image File format (HEIF or HEIC)," per Google's own developer documentation — the compatibility problem people experience is less about the format being exotic and more about which specific devices and software versions picked it up, and when.

HEIF is built on the same foundation as several other formats this site's tools already deal with. Nokia's technical documentation for the format states plainly that it "specifies the storage of individual images, image sequences and their metadata into a container file conforming to the ISO Base Media File Format" — the identical box-based structure MP4 video uses, and the same family CR3 and HEIC's own video cousin HEVC files belong to.

Inside that container, a typical HEIC holds:

That EXIF layout is worth pausing on, because it explains a real quirk of conversion. The metadata is not a simple named block the way some formats do it — a decoder has to walk the meta box's item-info and item-location tables to find which numbered item is the Exif data, then read it out. ToolForge's converter does exactly that walk to carry your photo's camera details, date and GPS coordinates into the JPG it produces, and gives up quietly rather than failing the conversion if a particular file's structure does not match what it expects.

The compression itself is the other half of the size story. HEVC's intra-frame coding — the same per-image compression a video codec uses on a single frame — captures fine detail more efficiently than JPEG's older discrete cosine transform approach, which is the mechanism behind the format's real, if unquantified by Apple's own documentation, size advantage.

A detail that surprises people: a single HEIC file is not always one photo. Nokia's HEIF technical documentation lists "Storage of burst photos" and auxiliary images — defined as "an image that complements a master image. For example, an alpha plane or a depth map" — as real, standard features of the container, alongside a thumbnail image stored alongside the full-resolution one.

This is why a HEIC-to-JPG converter needs to handle more than a simple one-in, one-out decode. ToolForge's converter checks for exactly this and, when a single HEIC file contains more than one image, produces multiple numbered JPGs rather than silently keeping only the first and dropping the rest.

Worth being precise about what this does and does not include: it is genuinely separate from a Live Photo's motion, which is not multiple images packed inside the still HEIC at all — it is a different file entirely, and converting the still frame never touches it. What actually happens to a Live Photo when you convert it is worth reading before you assume a conversion has "lost" the motion; it was never in the file you converted.

The honest answer is licensing, not technical difficulty. HEVC is patent-encumbered, and decoding it — which is what reading the image data inside a HEIC ultimately requires — has historically meant a manufacturer or platform paying into a patent pool. That is a real cost that a format like JPEG, developed and standardised decades earlier under different terms, never carried.

The practical effect was a staggered rollout rather than a coordinated one. Apple shipped support across its own ecosystem starting with iOS 11 and macOS High Sierra in 2017. Android's platform gained native HEIF encoding support in Android 9, per Google's own developer documentation, though which individual manufacturer builds actually shipped a decoder varied for years afterward. Windows never had it built in at all — Microsoft's own support documentation for HEIF and HEVC files directs users to install a codec from the Microsoft Store rather than promising native support out of the box.

The upshot for anyone holding a HEIC file today: whether it opens depends on your specific device, its OS version, and in Windows' case whether you have installed anything extra — not on the format itself being unusual or broken. The per-platform fix is more useful here than a general explanation, because the answer genuinely differs by platform.

Four situations, four different articles, because the right move depends on what you are actually trying to achieve.

You need to send or upload the photo somewhere that rejects HEIC. Convert it to JPG — a full decode rather than an extraction trick, done in your browser with nothing uploaded.

You just want to view the files on the computer in front of you. The platform-specific fix — usually a free codec install rather than any conversion at all.

Something about the format is behaving strangely — a Live Photo that lost its motion, a batch where some files fail. What is actually happening and the specific failure modes are both worth a look before assuming something is broken.

You would rather your phone stopped writing HEIC files at all. One setting switches new photos to JPEG going forward — it does nothing to photos already in your library.

One thing genuinely worth deciding before any of the above: whether you want to keep shooting HEIC and convert on the way out, or switch the camera setting and never think about it again. The trade-off between the two formats covers that decision directly.