Why does my HEIC open on my phone but not on my computer?

Because the phone and the computer have different codec support. iPhone and macOS include an HEVC decoder; many desktop programs and browsers do not. The file is intact, and converting it to JPG for the computer is usually the quickest fix.

My file ends in .heic but nothing recognises it. What now?

Check what the file actually contains rather than trusting the name. It may have been renamed from PNG or JPEG, or exported with the wrong extension. A file info tool that reads the container brand will identify the real format so you can pick the right tool.

Can a HEIC become corrupt during transfer?

Yes. A transfer that is interrupted, or a card or cable disconnected while a file is being written, can leave the file structurally incomplete. Partial files often decode at the start and fail at the end, which is why they may open and then error partway through.

Does renaming a HEIC to JPG make it open?

No. The extension is only a label, and the bytes inside are still HEVC. Browsers act on the content type from the server, and image editors inspect the content, so renaming tends to produce a less clear failure rather than a working file.

How do I tell a damaged file from an unsupported one?

Try the file in two independent decoders and run a health check. If capable tools report that they cannot decode the image data, the file is damaged; if they read the structure but not the codec or a feature, the file is valid but unsupported by that tool.

Will converting a damaged HEIC make it worse?

Converting a copy is safe and often the only way to see how much of the image survived. Overwriting the original is what causes harm, because it removes the evidence a later, better tool might be able to read. Work on a copy and keep the source.

Can't open a HEIC file

On this page

Start with the symptom
1. Check whether the software supports HEIC
2. Check whether the file is really a HEIC
3. Check for cloud placeholders and permissions
4. Check whether the file is damaged
Where the file opens, and where it does not
What to do next, by outcome
Do not rename the file to force it open
What we will not tell you

Start with the symptom

'Cannot open' covers several different failures. A broken image icon in a browser, a generic file icon in Explorer, an error from a photo app, a picture that opens but shows the wrong colours, and a file that opens on one device but not another are not the same problem.

The symptom narrows the cause before you change anything. Note where it fails and where it works, then work through the possibilities in order of likelihood, starting with the cheapest to check. If the only symptom is a plain icon instead of a picture in File Explorer, see HEIC thumbnails not showing in Windows.

1. Check whether the software supports HEIC

This is the most common cause. Many websites and desktop programs do not implement HEVC. If the same file opens on an iPhone or Mac but not elsewhere, the file is fine and the software is the limitation. A website that refuses the file at upload is the same problem; see HEIC upload not supported. If a print service or an email recipient cannot use it, see printing or emailing HEIC photos; if a phone's gallery will not show it, see HEIC not showing in Gallery.

Test that theory before doing anything else: open another HEIC you know to be good in the same app. If that fails as well, the app is the problem rather than the file.

Convert it to JPG for those destinations. That is the whole problem solved, and it costs nothing but a little quality. On Windows, the Windows guide explains the two Store extensions, and HEIF extension installed but not working covers what to check when they are installed and HEIC still fails; on a Mac, Preview and Photos open HEIC directly; on Android, see HEIC on Android; on Linux, HEIC on Linux explains the missing HEVC decoder; and for Photoshop, Lightroom or GIMP, see HEIC in Photoshop, Lightroom and GIMP.

2. Check whether the file is really a HEIC

A file ending in .heic is not necessarily HEIC. It may have been renamed from another format, or exported by an app that used the wrong extension. The Health Check reads the file's real signature and will tell you what it actually is — for example "this is actually a JPEG" — and the repair tool can save it under the correct name.

This matters because the fix differs. A PNG that was renamed to .heic will not be helped by a HEVC decoder; it needs its extension corrected, or a tool that reads content rather than names.

Some files are also valid HEIF but use a codec other than HEVC, or a feature the tool does not implement. Those report as unsupported rather than broken, which is a different outcome with a different response.

3. Check for cloud placeholders and permissions

On Windows and macOS, files from OneDrive, iCloud Drive and similar services can appear in a folder without being present on the disk. The entry looks normal, but reading it fetches the content, and if that fetch fails the file opens as nothing.

Check the reported file size and whether the item is marked as cloud-only. Opening it in the provider's app, or downloading it explicitly, often resolves the issue without any conversion at all.

Permissions and protected folders are rarer but worth a glance. A file copied from a locked-down location can be unreadable to the account you are using, which produces an error that looks like corruption.

4. Check whether the file is damaged

If the file is genuinely HEIC and a capable viewer still fails, the file may be truncated or corrupted, for example by a transfer that stopped early or a partial download. The health check decodes the image and reports whether the container, the image data and the metadata are intact.

Be careful with cloud-sync placeholders here too: a file that has not actually downloaded can look present but be unreadable.

A damaged file is a different situation from an unsupported one, and the response differs. Unsupported means convert; damaged means recover what you can and keep the original untouched.

Where the file opens, and where it does not

Dividing the evidence this way is the fastest diagnostic. If the file opens on a phone and not on a desktop, the format is supported somewhere and the desktop is the limitation. If it opens nowhere, the file is the more likely suspect.

It helps to try two tools with different decoding engines, such as a phone app and a browser-based viewer. Two failures from independent decoders point strongly at the file.

One success is enough to establish that the file is valid. From that point the task is finding a way to read it on the machine you are using, not repairing anything.

What to do next, by outcome

Writing down which outcome you got is worth the minute it takes. It prevents repeating the same attempt and makes it obvious when a tool is guessing rather than reading the file.

Opens elsewhere but fails here: convert to JPG, or use a viewer that decodes locally.
Reports as not a HEIC: correct the extension or identify the real format.
Reports as unsupported feature: try a different decoder, or accept that the file uses something this tool does not implement.
Reports as partially readable: convert what decodes, and keep the original.
Reports as damaged: try the thumbnail, and treat the original as evidence rather than something to overwrite.
Marked as cloud-only: download it first, then try again.

Do not rename the file to force it open

Changing the extension does not change the contents. Renaming a HEIC to .jpg can make a program attempt a decode it cannot complete, producing a worse error than the original, and some programs will write a corrupted output file rather than fail cleanly.

There is one related point worth knowing: renaming does not affect whether a browser downloads or displays a file, because that decision comes from the server's content type. Renaming a local file achieves nothing.

If a tool needs a particular extension, let a proper conversion produce the new file. That way the bytes and the name agree.

What we will not tell you

We will not call a file repaired unless a real recovery step succeeded. Diagnosis and recovery are different things, and it is more useful to know that a file is damaged than to be told it was fixed.

We will not tell you a file is beyond help when we have only failed to decode it once. Different tools implement different parts of the standard, and a second opinion from another decoder is cheap.

And we will not ask you to upload a private photograph to find out what is wrong with it. The checks here run on your device.