HEIC vs JPG: What Actually Changed, and Why Apple Made the Switch

JPG is built on a 30-year-old idea, and it still works

JPEG compression, standardised in 1992, works by transforming blocks of pixels into frequency information and then throwing away the frequencies the human eye is least sensitive to — a deliberately lossy trade that made digital photography practical on the storage and bandwidth of the era. It has been refined and re-implemented endlessly since, but the core algorithm hasn't fundamentally changed. That's precisely why it still works everywhere: three decades of software, from web browsers to printers to medical imaging systems, has JPEG support baked in at the lowest level.

HEIC isn't a new photo format — it's a video codec wearing a photo's clothes

This is the part that surprises people. HEIC (High Efficiency Image Container) doesn't define its own new way of compressing images. Instead, it takes HEVC — H.265, the video compression standard built for 4K and 8K video streaming — and uses it to encode a single frame as a still photo. The "container" part of the name is doing real work: HEIC is fundamentally a video-codec technology repurposed for photography.

This matters because HEVC is a substantially newer and more sophisticated compression design than JPEG's, built specifically to squeeze more video quality out of fewer bits. Applied to a single still frame, that sophistication translates into a real, measurable win: Apple's own figures put HEIC photos at roughly half the file size of an equivalent-quality JPEG, and independent testing generally backs that up. For a company shipping cameras that capture 48-megapixel photos across a billion devices, halving average photo size is not a cosmetic improvement — it's a meaningful reduction in the iCloud storage Apple has to provision and the cellular data its customers burn syncing photos.

Apple made the switch official with iOS 11 in 2017, and HEIC has been the default capture format on iPhones ever since.

Why almost nothing outside Apple could just adopt it too

If HEIC is genuinely more efficient, the obvious question is why every other platform didn't immediately follow. The honest answer is licensing, not technical merit. HEVC is covered by a tangle of patents held across multiple licensing pools, and using it — whether for encoding or decoding — can require royalty payments. This is a fundamentally different situation from JPEG, which is old enough that its core patents expired long ago and implementing it costs nothing.

That licensing reality is the direct, traceable cause of the compatibility mess that followed:

• Windows doesn't bundle a HEVC decoder by default, and Microsoft sells the pieces you need as separate Microsoft Store add-ons rather than including them free in the OS — largely a function of per-install licensing costs at Windows' scale. See our Windows-specific guide for the exact extensions involved.
• Browsers other than Safari generally don't decode HEIC natively at all, which is why converting a HEIC file in Chrome or Firefox depends on a JavaScript-based decoder rather than the browser's own built-in image handling.
• Android added OS-level HEIC support starting with Android 9 in 2018, roughly a year behind Apple, once the licensing and implementation questions had settled — see our Android guide for how that plays out in practice today.

None of this is a conspiracy or an oversight. It's the predictable outcome of one company controlling both the hardware and the licensing terms shipping a technology everyone else has to separately license or work around.

What you actually lose converting HEIC to JPG

Converting is not free of cost, and it's worth being precise about what that cost is. HEIC is lossy — detail was already discarded when the photo was first captured and encoded. Converting to JPG means decoding that lossy result and re-encoding it into a second lossy format, so a small amount of additional detail is discarded in the process. At a reasonably high JPG quality setting (85 or above), this second pass is not visible at normal viewing sizes. It becomes noticeable only if you convert the same file repeatedly, or push the quality setting low to save space.

The other predictable cost is size: since HEIC is the more efficient format, converting to JPG generally means the file gets larger for the same visual quality — you're spending back some of the storage efficiency Apple's switch bought you, in exchange for a format literally everything can open.

So which one should you actually use?

If your photos never leave Apple's ecosystem — iPhone, iCloud, Mac, sharing via Messages or AirDrop to other Apple users — HEIC costs you nothing and saves real storage. The moment a photo needs to go somewhere that isn't fully HEIC-aware — a Windows PC without the codec installed, an upload form that checks file extensions, older software, a printer — converting to JPG is the pragmatic choice, and it's a one-time, low-cost trade for guaranteed compatibility.

Related

• HEIC to JPG converterKeeps the capture date, camera and GPS data intact
• WebP vs JPG vs PNGThe same "which format actually wins" question, measured