HEIC vs JPG

Every iPhone since 2017 saves photos as HEIC by default. Windows PCs, most websites, and many Android phones still expect JPG. The two formats solve the same problem - compressing a photo so it takes less space - but they make opposite trade-offs. HEIC prioritizes efficiency. JPG prioritizes universal support.

What each format actually is

JPG, or JPEG, is a standard from 1992 that uses lossy compression based on discrete cosine transforms. It is supported by every web browser, operating system, printer driver, and social platform built in the last three decades. A JPG stores a single image with 8-bit color depth and no transparency.

HEIC is Apple's branding for HEIF, the High Efficiency Image File Format standardized by MPEG under ISO/IEC 23008-12. HEIF is a container, not a compression method. The actual compression inside an HEIC file uses HEVC, the same codec behind high-efficiency video. HEIF can store 16-bit color, transparency, multiple images in one file, and even image sequences. That is how Apple builds Live Photos - one HEIC file holding a still frame and a short video clip.

File size: the biggest practical difference

HEIF with HEVC compression produces files that are roughly 40 to 50 percent smaller than JPEGs at the same visual quality. Apple states that HEIF and HEVC "offer better compression than JPEG while preserving the same visual quality." Independent benchmarks consistently confirm the same range. On a 128 GB iPhone, shooting HEIC instead of JPEG effectively doubles the number of photos you can store before running out of space.

That efficiency is why Apple switched. It is also why many Android manufacturers, including Samsung and Google, adopted HEIF for their own camera apps. The trade-off is that smaller files need more processing power to decode, which is why older devices and some budget PCs struggle with HEIC.

Quality and features

At equivalent visual quality, a HEIC file is smaller. At equivalent file size, a HEIC file looks better. That is because HEVC uses more advanced prediction and larger transform blocks than JPEG's 1992-era DCT engine. For casual phone photos viewed on screens, the difference is subtle. For landscapes, portraits with fine hair detail, or images that will be printed large, the gap is visible.

HEIF also supports features JPEG cannot match:

• 16-bit color depth, compared to JPEG's 8-bit maximum
• Alpha transparency for graphics and logos
• Multiple images in one file, used for bursts and Live Photos
• Non-destructive editing instructions stored alongside the image

For photographers who edit in Lightroom or Capture One, the 16-bit color is meaningful. For someone posting to Instagram, it is not.

Compatibility: where each works

JPG works everywhere. Every browser, email client, print shop, and social network accepts it. HEIC does not.

macOS and iOS have supported HEIC natively since High Sierra and iOS 11. Windows 10 and 11 can open HEIC only after installing the HEIF Image Extension from the Microsoft Store, which is free but requires Store access. Many corporate and school PCs block the Microsoft Store entirely, making HEIC unviewable.

Chrome, Firefox, and Edge do not natively render HEIC in web pages. That means you cannot embed a HEIC file in a blog post or view it in most web-based CMS dashboards. Web forms, job portals, and social platforms generally reject HEIC uploads. When you need to share a photo outside the Apple ecosystem, JPEG is still the safe default.

When to keep HEIC and when to convert

Keep photos as HEIC when they live inside the Apple ecosystem - on your iPhone, in iCloud Photos, or on a modern Mac. The format preserves the most data in the smallest space.

Convert to JPG when you need to:

• Upload to a website, store, or form that rejects HEIC
• Share with someone on Windows who lacks the HEIF extension
• Send to a print shop, lab, or photo book service
• Edit in older desktop software without HEIF plugins
• Archive for maximum long-term compatibility

How to convert without giving up your privacy

Most online HEIC converters work by uploading your photo to a remote server, queuing it, and sending back a download link. Your image sits in someone else's storage, passes through their logs, and may be cached by their CDN. You have no control over retention or access.

A better approach is to convert locally in your browser. The same libheif decoder that powers desktop apps can be compiled to WebAssembly and run entirely on your device. The file never leaves your computer. Not even a thumbnail is sent to a server.