When HEIC files wont open Windows is failing at one of two different tasks, and most tutorials solve the wrong one. Either the system lacks the codec needed to decode a healthy file, or the file is damaged and no codec helps. The first costs a few clicks; the second needs repair, and converting to JPEG first usually makes it worse.
The fastest test is the file size. A 12 MP HEIC from a recent iPhone runs 1.5 to 3 MB, and a 24 MP HEIF from a mirrorless body runs 3 to 6 MB. A file of a few hundred kilobytes is not the photograph at all.
Two problems, one symptom, and they are not related
The codec problem is a software gap. HEIF is a container, and inside it sits an image coded with HEVC. Windows has shipped a HEIF reader for years, but the HEVC decoder that feeds it is licensed separately, so a clean Windows install can open the container and fail to decode its contents. The symptom is consistent: the file has an icon, the file size is correct, and Photos shows an error or an empty frame.
The corruption problem is a data fault. A damaged HEIC does not open on any platform, including the iPhone that created it. If the same file fails everywhere, stop looking for codecs; no decoder affects a broken container.
That distinction is worth testing before spending money on either path, and it takes two minutes:
- Send the file to a device that natively handles HEIC, such as an iPhone or a Mac, or open it in a viewer that bundles its own HEVC decoder.
- If it opens there, the file is healthy and the problem is local to the Windows machine.
- If it fails everywhere, the file is damaged and repair is the task.
| What you see | Most likely cause | Correct fix |
|---|---|---|
| Correct file size, opens on iPhone, fails in Photos | Missing HEVC codec | Install the codec extensions |
| Correct file size, fails on every device | Container or item damage | Repair, not conversion |
| A few hundred KB, opens but looks soft | Only the thumbnail item survived | Recover from the card, not from the file |
| Opens in some apps, not others | Third-party app bundles its own decoder | Use the working app or install the codec |
| Correct size, shows a gray or black frame | Item payload present, index damaged | Repair the container index |
| Zero bytes or 4 KB | The transfer failed, not the file | Re-copy from the source device |
Checking whether the container is intact
A HEIF file is an ISO Base Media File Format file, the same family as MP4. The first four bytes are the size of the first box and the next four are the box type, which for a still image is one of a small set of four-character codes.
Dump the first bytes from a terminal:
“ xxd -l 32 photo.heic “
The output should read as a size, then ftyp, then a brand such as heic, heix, mif1, msf1, or hevc. Two signatures are diagnostic:
- The first bytes are zeroed or random. The container header is gone, which means the beginning of the file was overwritten or the copy was truncated at the front. Neither is repairable from the file itself.
- The
ftypbox is intact but a later box is damaged. The item index is the suspect, and that is repairable in principle, because image data is referenced by an extent list rather than stored inline.
If the magic bytes are wrong, the same triage used on recovered files that open nowhere applies, and a scan of the card the file came from is likely to produce a better copy than any repair of the damaged one.
Installing the codecs, correctly
The fix for the software case is two items, not one, and installing only the first is why so many people conclude that the fix does not work.
- HEIF Image Extensions lets Windows understand the container. It is free, but by itself it can describe the file without being able to decode it.
- HEVC Video Extensions supplies the decoder. Microsoft sells this in the Store for a small fee; some OEM machines ship with it preinstalled, which is why the same file opens on one PC and not another.
After installing both, restart the Photos app rather than trusting a window that was already open, and confirm the change against a known-good HEIC rather than the suspect one. If a known-good file opens and the suspect one still does not, the two problems are separated cleanly.
One caveat for cameras rather than phones: several mirrorless brands now write HEIF as a still format, and their files may use a brand code that older Windows builds do not recognize even with both extensions installed. Converting those through the manufacturer’s own software, or opening them in a recent build of a mainstream editor, is often the faster path.
Why converting a damaged HEIC to JPEG is the wrong first move
Conversion is a decode followed by an encode. If the decode fails there is nothing to encode, and a converter has only three options: fail loudly, produce a gray image, or fall back to whatever part of the file it can read.
The third option is the dangerous one. A HEIF file routinely contains a small thumbnail item in addition to the full-size item, and a converter that cannot reach the primary item will sometimes write out the thumbnail instead and report success. The output is a JPEG that opens perfectly, is 320 pixels wide, and quietly discards the photograph. Users discover this when the file is printed, often months later.
Two habits prevent that outcome. Check the pixel dimensions of anything you convert before deleting the source, and never delete the original HEIC, because it is the only copy carrying the full payload and the metadata. Conversion also discards the 10-bit color depth some HEIF files carry, so it is a genuine quality loss even when it succeeds.
A related myth is worth disposing of directly: renaming a .heic file to .jpg does nothing at all. Windows does not decode a file based on its name. Renaming can make a file appear to open in one application and fail in another only because applications guess at formats differently.
What repair can and cannot restore
If the file is damaged, the outcome depends on which part failed. The image payload is stored as an item referenced by an extent list in the meta box, which means the payload bytes and the map to those bytes are separate concerns.
| Damaged component | Repairable? | What you get back |
|---|---|---|
ftyp box only | Sometimes | A rewritten header with the payload intact |
meta box and item index | Rarely, with tooling | Payload with no navigation, often unrecoverable |
| Item payload partially overwritten | No | Only the surviving portion, if a decoder accepts it |
| Metadata and EXIF only | Yes | The image, with capture data rebuilt from another file |
| Thumbnail intact, primary item gone | No | A small preview only, not the photograph |
The third row decides whether the effort is worth it, and overwritten data is gone regardless of format. The fifth row is the reason to run a recovery scan on the source card before declaring the photograph lost: if the thumbnail is intact, the full-size item was almost certainly written adjacent to it, and a scan of the raw card can sometimes produce a more complete copy than the damaged file you already have. The photo recovery workflow for memory cards covers that path, and the anatomy of the three still formats explains why HEIF’s single index is the least forgiving arrangement of the three.
If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive. None of that helps a file that is damaged in place, which is why the question to ask first is always whether a better copy still exists on the media.
Once a HEIC file does open, two follow-up steps are worth the time. Check that the copy is the size you expect, following the verification steps for recovered files, and confirm that the capture date and location survived. Metadata often does not come back with the pixels, and the guide to restoring photo metadata covers which tags can be rebuilt reliably and which are better left empty. The structure of EXIF and XMP data is useful background if you want to know what a repair actually changed.
Frequently Asked Questions
Do I need to pay for anything to open HEIC files on Windows?
Usually one item. HEIF Image Extensions handles the container and HEVC Video Extensions supplies the decoder, and the second is a small paid purchase from the Microsoft Store. Some OEM machines ship with it installed, which explains why HEIC files open on one PC and fail on another with the same Windows version.
The conversion produced a small image. Did I lose the photo?
You may have received the embedded thumbnail rather than the photograph. Check the output’s pixel dimensions. If it is a few hundred pixels wide, the converter fell back to a secondary item; delete the output and work from the original HEIC, which still holds the full payload if it is readable on any device.
Can a corrupted HEIC be repaired into a full-size image?
Only if the payload is intact and the fault is in the container header or a metadata box. If the meta box that indexes the image items is destroyed, no tool can locate the payload, and reconstructing that index is laboratory-grade work. If the payload itself was overwritten, the image is gone.
Why does the same HEIC open fine on my phone but not on my PC?
Because the phone has the decoder and the PC does not. The test works in both directions: a file that opens on the phone that took it has an intact container, so the remaining problem is software rather than damage.