When to reach for HEIC over JPEG

If you shoot on an iPhone, your photos are already HEIC by default. It packs a lot more image into a lot fewer bytes than JPEG — but it isn't a drop-in replacement everywhere. Here's when HEIC is the right call and when plain old JPEG still wins.

What HEIC actually is

HEIC is HEVC (H.265) intra-frame compression wrapped in the HEIF container. In plain terms: it borrows a modern video codec's smarts to compress a single still, then stores it in a flexible container that can also hold depth maps, alpha, image sequences and Live Photos. That's why a HEIC photo is typically 30–50% smaller than the same JPEG at comparable quality.

Where HEIC wins

Beyond size, HEIC supports 10-bit color, so it holds up far better on smooth skies and gradients where 8-bit JPEG bands visibly. It also carries alpha transparency and auxiliary data JPEG can't. For an Apple-centric photo library — Photos.app, AirDrop, modern iPhones and Macs — it's an excellent default that quietly saves a lot of storage.

Where JPEG still wins

Compatibility, plainly. JPEG opens everywhere — every browser, OS, CMS, printer and decade-old device. HEIC also leans on patent-encumbered HEVC, which complicates support outside Apple's ecosystem. If an image is going onto the open web or into a tool you don't control, JPEG (or WebP/AVIF for the web) is the safer bet.

A practical rule

Keep your originals in HEIC where Apple devices handle them natively and the storage savings are real. The moment a photo needs to travel — a website, an email attachment, a partner's system — convert it to JPEG, WebP or AVIF on the way out. You get HEIC's efficiency at rest and JPEG's reach in transit.

HEIC is a great place to store photos and a risky place to send them. Convert on the way out, not the way in.

# Batch-convert an iPhone export to web-ready files
imageforge ./Photos/*.heic --convert jpeg --quality 88
imageforge ./Photos/*.heic --convert avif --quality 80