You have a photo that will not open, and every explanation online uses three acronyms interchangeably. HEIC, HEIF, HEVC. They are not synonyms, and the difference between them is exactly what decides whether your file opens.
Here is the short version. HEIF is the box. HEVC is what squeezed the picture. HEIC is a HEIF box with an HEVC picture inside. Understanding heic vs heif takes about two minutes and saves a lot of confused searching.
The heif container explained in one paragraph
HEIF is a filing system, not an image format. It defines how a picture, its metadata, its thumbnail and any extras get wrapped into a single file.
Structurally it is a flat sequence of chunks. Each one declares its type and its length, then its content. One chunk holds an index of everything present, another holds the actual compressed data.
Crucially, HEIF says nothing about how the picture was compressed. That is somebody else's job, which is where the second acronym comes in.
What does hevc have to do with it?
HEVC, also called H.265, is a video codec standardised in 2013. It compresses moving pictures very efficiently, and a still photo is just a video that stopped after one frame.
Apple took that codec, pointed it at single frames, and put the output in a HEIF box. That combination is HEIC.
The video heritage explains something that puzzles Windows users constantly. The package you install to see photos is called HEVC Video Extensions, which sounds wrong until you know the decoder is the same one that plays 4K video.
It also explains the licensing. HEVC is covered by patents, so the decoder costs money to distribute. That single fact is behind almost every HEIC frustration: Windows not shipping it, free tools being scarce, and manufacturers bundling it on some laptops and not others.
We hit the same wall building our own tools. Our image toolchain will happily write AVIF and flatly refuses to write HEIC — the error is literally that the compression is unsupported. The licence is why.
So is heic the same as heif in practice?
Close enough to be interchangeable in conversation, and not close enough for a file that will not open.
Think of it as a promise. A file named .heic promises HEVC inside. A file named .heif promises only that the container is HEIF and leaves the codec open. If your decoder handles HEVC and nothing else, the first promise is the one you want.
In real life almost every .heif you meet is also HEVC, because that is what phones write. The distinction only bites when something unusual produced the file.
Reading the brand to settle it
Four ASCII characters at byte eight of the file record which flavour you have. That is the ftyp brand, and it is the first thing any well-written reader checks.
| Brand | Meaning | Codec inside |
|---|---|---|
| heic | HEVC stills, what an iPhone writes | HEVC, 8-bit |
| heix | The ten-bit variant | HEVC, 10-bit |
| mif1 | Generic HEIF, codec unspecified | Unknown from the brand alone |
| msf1 | Generic HEIF image sequence | Unknown from the brand alone |
| avif | Same container, different codec | AV1 |
Files usually list several compatible brands as well as one major brand. An iPhone photo typically declares heic as its major brand and lists mif1 among the compatible ones, which tells a strict reader that the generic profile is also satisfied.
What the mif1 brand meaning costs you in practice
A file marked mif1 is honest about being underspecified, and some tools handle that badly.
Our own signature table used to recognise exactly two brands. Everything else fell through to a default that assumed MP4, so a generic HEIF photo was reported as a video file with complete confidence. We fixed it while building this cluster, and it is worth knowing because plenty of other tools make the same shortcut for the same reason.
If a tool tells you your photo is a video, that is usually what happened. You can identify an unfamiliar HEIF file and see the brand written out rather than guessed.
Avif in a heif container, and why it breaks things
AVIF is the same container with AV1 inside instead of HEVC. AV1 is royalty-free, which is why the web adopted it fast while phones stayed on HEVC.
The trap is that both files look structurally identical. A HEIC decoder opens an AVIF, walks the boxes successfully, reaches the picture data and fails, because it is looking at a codec it has never heard of.
This shows up most often when an export tool writes AVIF and keeps the .heic extension. The fix is a rename rather than a conversion, and it is genuinely easier: most current browsers open .avif directly with no decoder install at all.
Why two file extensions confuse everyone
Because the naming was never designed for people. HEIF came from a standards body describing a container. HEIC came from Apple shipping a product. One name describes structure, the other describes a specific combination, and both ended up as file extensions users see.
The practical rule: trust the header, not the name. A name is a label anyone can change and it has no effect on the bytes. Most software reads the first few bytes and decides from there, which is why renaming a HEIC to .jpg never makes it open.
What this means for your photos
If you are just trying to see a picture, none of this matters and a browser-based HEIC viewer handles it regardless of brand.
It starts mattering when something fails. A file rejected by one program and accepted by another is usually a brand or codec mismatch, and knowing which acronym is which turns a mystery into a two-second check.
If you are weighing up whether to keep using the format at all, the comparison worth reading is whether HEIC beats JPG in practice rather than the specification differences. And if you have already decided against it, you can stop your iPhone writing HEIC in two settings, though it only affects photos you take from that point on.
The one-line summary
HEIF is the container, HEVC is the codec, HEIC is both together, and AVIF is the same container with a free codec instead of a licensed one.
Everything frustrating about heic vs heif traces back to that licence. It is why Windows charges for half the support, why free tools are scarce, and why the web went a different way entirely. The format is good. The licensing is the reason it feels difficult.