HEIC explained: why iPhone photos will not open, and how to get a JPG

Two acronyms get used as if they were one thing. HEIF is the container - a box that holds image data plus everything that goes with it, in the same way an MP4 holds video, audio and subtitles together. HEVC, also known as H.265, is the codec that compresses the picture itself. A .heic file is normally HEVC-encoded image data sitting inside a HEIF container. Apple made that combination the camera default in iOS 11.

The motivation was space. JPEG was standardised in the early 1990s and works on eight by eight blocks of pixels. HEVC arrived roughly two decades later, designed for video, and can predict one region of an image from another region of the same image before it encodes anything at all. The practical result is around half the file size at comparable quality, which is a large saving when a phone holds thousands of photos. How large depends on the picture: a plain wall compresses beautifully either way, fine gravel does not.

The container also carries things JPEG has no way to express, which matters later when you convert. A single .heic can hold ten bits per colour channel instead of JPEG's eight, which is why skies band less. It can carry transparency. It can store the depth map from Portrait mode that lets the phone re-adjust background blur after the fact, and it can hold a whole burst of frames as one file rather than forty.

A format is only as portable as its decoder, and the HEVC decoder is genuinely not everywhere. Underneath the patchiness sits patent licensing: HEVC is covered by patents administered through more than one pool, which has made browser vendors and open-source projects cautious about shipping a decoder at all. JPEG's patents expired a long time ago, while JPEG has broad compatibility. Format support still depends on the application.

Forms fail earlier and more bluntly than software does. A typical file input checks the extension against a list before anything examines the image, so the rejection happens without your photo ever being decoded. The error message is generic because at that point the site genuinely does not know what you sent.

Even forms that accept the upload can fail afterwards. Plenty of sites run on server-side image libraries that were built without HEIF support, so the file uploads successfully and then the thumbnail comes out blank, or the processing step errors out some time later. Government portals, university admissions systems and job applications are the usual offenders, and they are exactly the situations where a silent failure costs you the most.

If a form rejects your photo and the message only says invalid file type, look at the extension before you look at anything else. That single check explains the large majority of these cases.

Converting files one at a time treats the symptom. If you keep hitting this, change what the camera writes. On the phone, open Settings, then Camera, then Formats. High Efficiency writes HEIC stills and HEVC video. Most Compatible writes JPEG and H.264 instead.

Two things worth knowing before you switch. It only affects photos taken from that moment onwards, so it does nothing for the thousands already in your camera roll. And it costs storage: expect roughly double the space per photo, which is the whole saving you were getting handed back. A couple of high frame rate video modes require High Efficiency, and the phone will tell you if you try to use them.

There is a second setting that causes most of the arguments about this, because it changes what happens without changing what the camera does. Settings, then Photos, then Transfer to Mac or PC, offers Automatic or Keep Originals. Automatic converts HEIC to JPEG when you connect the phone to a computer. Keep Originals hands over the file exactly as stored. Plenty of people are on Keep Originals without ever having chosen it, which is why the same phone can seem to produce openable photos one week and not the next.

This is the part that makes the problem feel random. The format that reaches the other end depends on the route the photo took off the phone, and none of the routes announce what they did.

For an existing HEIC file, a compatible viewer may open it directly. Convert a copy when the receiving application requires another format. The available decoder depends on the browser, operating system and particular file.

Some browser converters bundle a WebAssembly decoder; others use the browser’s native decoding support or send files to a server. UtilByte uses the browser decoder and does not bundle a HEIC decoder. If the browser cannot decode the source, the tool reports failure rather than uploading it.

Unsupported encoding variants, corrupt input and device memory limits can all cause failure. Try opening the original in a compatible photo application and exporting a JPEG copy. Do not assume that a different extension or a browser update will fix every file.

Exporting JPEG decodes the source and then applies lossy encoding. The amount of visible change depends on the image, decoder and quality setting; source bit depth is not always the same. Retain the HEIC original and inspect color, detail and metadata in the exported copy.

The JPEG can be larger or smaller depending on source encoding, dimensions and selected quality. There is no fixed multiplier. Compare the actual file size, particularly when the receiving application also imposes a byte limit.

Live Photos lose the most. A Live Photo is not one file but a still image paired with a short video clip, shown as a single item in the Photos app. Convert it and you keep the key frame; the motion and its audio do not travel. For a document scan or a receipt that is exactly what you wanted. For a picture of a child mid-run, the frame the phone picked may not be the moment you had in mind.

None of this should stop you converting. A file that will not open has a quality of zero to the person who needs it. Keep the HEIC as your original, export a fresh JPEG from it each time you need one, and never convert a conversion.