HEIC vs JPG: Which Should You Use?

Every iPhone user has met the HEIC problem: you take a photo, transfer it to a PC or upload it to a website, and get told the format isn't supported. Why does Apple use HEIC at all, and when should you convert to JPG?

Short answer: keep HEIC for storage, convert to JPG for sharing. Here's the full reasoning.

What each format actually is

JPG (JPEG) is the 1992-era workhorse. It uses lossy compression based on the discrete cosine transform, capped at 8-bit color, no transparency. Its advantage is universal: every device, browser, and app on earth reads JPG. Its disadvantage is age — the compression is inefficient by modern standards.

HEIC is a container format built on HEIF (High Efficiency Image Format), using HEVC/H.265 video-style compression on still images. iPhones have saved photos as HEIC by default since iOS 11 (2017). The practical result: same visual quality as JPG at roughly half the file size.

HEIC also carries features JPG fundamentally can't: 16-bit color depth, transparency, and multiple images per file (that's how Live Photos and burst sequences pack into one file).

Disclosure: I'm the developer of FileOnTap, a free in-browser file converter — so I think about format friction a lot. If you want the deeper dive on what HEIC is, this free what-is-HEIC explainer covers the technical background.

Head-to-head comparison

When to keep HEIC

• Storing photos on your iPhone or iCloud. Half the file size means twice the photos on the same storage. This is the entire reason Apple switched.
• Editing. The 16-bit color gives you more headroom in adjustments before banding shows up.
• Archiving originals. Keep the best-quality smallest file as your master copy.

When to convert to JPG

• Sharing on the web or with others. Most websites, messaging apps, and non-Apple devices either reject HEIC or silently mangle it. If you don't know what the recipient uses, JPG is the safe answer.
• Uploading to services that require JPG/PNG (forums, forms, profile pictures).
• Moving photos to Windows for editing in software without HEIC support.
• Printing at a shop that only takes standard formats.

The practical workflow

The annoying part isn't the theory — it's the friction of converting. A few rules of thumb:

1. Don't convert your whole library. Convert on export: keep HEIC masters, convert copies when you need JPG.
2. For quick batches, skip installing anything. An in-browser converter that processes locally (no upload) converts a folder of HEICs to JPG in seconds. The no-upload part matters: uploading personal photos to a random converter's server is a privacy trade-off you don't need to make.
3. For future photos, iPhone users can stop the HEIC supply entirely: Settings → Camera → Formats → "Most Compatible" saves new photos as JPEG. (Existing photos stay HEIC.)
4. Quality note: HEIC→JPG is a transcode between two lossy formats, so technically a little data is lost. In practice, at high quality settings it's visually indistinguishable. If you need zero loss, convert to PNG instead.

Will HEIC eventually win?

Probably, but slowly. Android supports HEIF capture now, Windows 11 reads it with a free extension, and AVIF (a sibling format) is gaining web traction. But JPG's thirty-year head start in "works everywhere" isn't going away — browsers still can't render HEIC in <img> tags. For at least the next few years, the answer stays the same: HEIC for storage, JPG for sharing.