HEIC to JPG: Why iPhone Photos Won't Open, and How to Fix It

If you have ever emailed a photo from an iPhone to someone on Windows and been told the file will not open, you have met HEIC. Since iOS 11, iPhones have saved photos in the High Efficiency Image Container by default rather than as JPEG, and the .heic file that results is invisible to a lot of software that predates it or never added support.

The format itself is not the problem. HEIC uses modern video-derived compression to store a photograph at roughly half the size of an equivalent JPEG, with support for higher bit depth, transparency and multiple images in one file — which is how Live Photos and depth data travel. On an iPhone or a Mac it is strictly better.

The friction is entirely about compatibility. Windows needs an extension to view HEIC natively, many web upload forms reject the extension outright, older versions of Office and Photoshop cannot open it, and a good deal of print and photo-lab software has never heard of it. Converting to JPEG solves all of that at the cost of some file size, and it is worth understanding what you gain and lose before deciding whether to convert one photo or change the setting on your phone.

HEIC is a container — the High Efficiency Image Container — holding image data compressed with HEVC, the same codec used for H.265 video. Compressing a still photograph with a video codec sounds odd but works well, because modern video compression is extremely good at predicting one region of an image from another, and that is just as true within a single frame as between frames.

The container part matters as much as the codec. One .heic file can hold several images, which is how a Live Photo carries its short video, how a burst keeps its frames together, and how portrait mode stores the depth map alongside the picture. It also carries the edits you have made non-destructively, so the original is recoverable on the device.

This is why conversion is more of a decision than it looks. A JPEG holds exactly one image with no depth information and no edit history. Converting flattens all of that into the single frame you see, and the extra data is not recoverable from the JPEG afterwards.

HEVC is patent-encumbered, and its licensing terms have made vendors reluctant to ship decoders by default. Windows can display HEIC but requires an extension from the Microsoft Store, which many users have never installed. Android added support but inconsistently across versions and manufacturers. Plenty of desktop applications simply never added it.

Web upload forms are the most common practical obstacle, and they fail in a particularly unhelpful way. A form that filters by file extension rejects .heic before anything is uploaded, usually with a message about the file type being invalid rather than anything mentioning HEIC. Government portals, job application systems and older content management systems are all frequent offenders.

Email is the other regular source of confusion, made worse by the fact that Apple sometimes converts on send and sometimes does not, depending on how the photo is attached and which app is doing it. That inconsistency is why the same person can successfully email a photo one day and not the next.

Converting HEIC to JPEG is a lossy-to-lossy transition, so the output is decoded from the HEIC and re-encoded as JPEG. Doing this once at high quality costs very little that anyone could see; doing it repeatedly, or at a low quality setting, visibly degrades the picture.

Two things protect the result. Convert from the original file off the phone rather than from a copy that has already been through a messaging app — apps like WhatsApp re-encode aggressively, and converting their output means stacking two lossy passes. And set quality at 90 or above, which keeps the conversion itself effectively invisible; you can always compress the JPEG afterwards as a separate, deliberate step.

Orientation is the other thing to watch. A HEIC carries its rotation as metadata, and software that ignores that metadata displays portrait shots sideways. A conversion that bakes the rotation into the pixels avoids the problem permanently, which is what Zyff's converter does.

The still image survives conversion faithfully. Everything else in the container does not.

A Live Photo becomes a single frame — the video component has nowhere to go in a JPEG. Depth data from portrait mode is discarded, so you cannot re-adjust the background blur afterwards. Burst sequences become one image each rather than a group. Non-destructive edits are flattened into the pixels, so the unedited original is no longer recoverable from that file. And HEIC's higher bit depth is reduced to JPEG's 8 bits per channel, which is invisible on most photographs but can introduce banding in a smooth gradient.

None of that is a reason to avoid converting, but it is a reason to keep the originals. Convert copies for the thing that needs JPEG and leave the HEIC files in your photo library where the extra data is still useful.

If you hit this constantly, the setting is worth changing. In Settings, open Camera, then Formats, and choose Most Compatible instead of High Efficiency. New photos are then saved as JPEG and the problem does not arise.

The trade-off is real: files roughly double in size, so your storage fills faster, and you lose the higher bit depth. Existing HEIC photos are unaffected — the setting applies to new captures only, so anything already in your library still needs converting.

For most people who mainly share photos rather than edit them, Most Compatible is the better default. For anyone who edits seriously or is short on iCloud storage, keeping High Efficiency and converting on demand is the better trade.