HEIC vs JPG: Which Should You Actually Keep?

If you have an iPhone made after 2017, every photo you take is saved as HEIC unless you’ve gone into Settings and changed it. Most people never notice, because the Photos app handles HEIC invisibly — until the moment they try to share, upload, or open one of those photos somewhere that isn’t an Apple device, at which point HEIC’s near-invisibility becomes a real, practical problem. The question of which format to actually keep isn’t abstract; it has a fairly clear answer once you understand what each format is actually trading off.

What HEIC gets right

HEIC (High Efficiency Image Coding) earns its name honestly — at the same visual quality, a HEIC file is typically 30-50% smaller than the equivalent JPG. For Apple, storing potentially tens of thousands of photos per user across hundreds of millions of devices, that’s a genuinely significant saving, which is exactly why they made it the default. HEIC also supports some technical conveniences JPG doesn’t, like storing multiple images (such as a Live Photo’s burst frames) in a single file, and better handling of wider color gamuts on newer devices.

None of this is marketing fluff — HEIC is a more modern, more efficient format on a technical level. The problem isn’t the format’s quality; it’s where you can actually use it.

What JPG gets right

JPG’s entire advantage is that it’s old. Released in 1992, it’s had over three decades to become the default assumption baked into nearly every piece of software, every website upload form, every email client, every printer, and every device that has ever needed to handle a photo. That ubiquity is worth more in practice than HEIC’s efficiency gains for the simple reason that a smaller file you can’t actually open or upload anywhere is worse than a larger file you can use immediately, everywhere, without a second thought.

This is the crux of the decision: HEIC wins on pure technical efficiency; JPG wins on the thing that actually matters most of the time, which is “will this work where I need it to.”

So which should you keep?

For photos you’re done taking and plan to keep long-term, share with people on a mix of devices, upload to forms, or use anywhere outside Apple’s ecosystem: convert to JPG and keep that. The storage savings from staying in HEIC rarely outweigh the recurring friction of running into a device or website that can’t open it — and that friction tends to show up at inconvenient moments, like trying to attach a photo to a time-sensitive email or finish an application form.

For photos you’re confident will only ever live within Apple’s ecosystem — backed up to iCloud, viewed only on Apple devices, shared only via AirDrop or iMessage to other iPhone users — keeping HEIC is genuinely fine, and you get the storage benefit without any real downside, since Apple’s own software handles the format transparently end to end.

The middle-ground approach most people actually want

If you don’t want to think about this on a photo-by-photo basis (reasonably so — nobody wants to manually triage their camera roll), there are two practical defaults to choose between:

Switch your iPhone to save JPG directly going forward. Under Settings → Camera → Formats, choosing “Most Compatible” makes new photos save as JPG (and video as H.264) automatically, at the cost of somewhat larger files. This is the simplest fix if compatibility issues have bothered you more than once — it stops the problem at the source rather than requiring you to convert files after the fact.

Keep HEIC as your camera default, convert on the way out. If storage efficiency on your phone matters to you — useful if you’re frequently near your storage limit — keep shooting in HEIC, and convert specific photos to JPG only when you’re about to share, upload, or send them somewhere outside Apple’s ecosystem. This gets you HEIC’s storage benefit on-device while still producing universally-compatible files at the point you actually need them.

What you lose either way

It’s worth being honest that converting HEIC to JPG isn’t perfectly lossless — it involves decoding the HEIC’s already-compressed data and re-encoding it with JPG’s own lossy compression, which introduces a small amount of additional quality loss on top of whatever HEIC already discarded when the photo was taken. In practice, at a reasonable JPG quality setting, this is genuinely hard to notice without zooming in and comparing closely — but it does mean converting back and forth repeatedly isn’t free. If there’s a chance you’ll need the original again, it’s worth keeping the HEIC file around rather than deleting it once you’ve made a JPG copy, rather than relying on converting back from the JPG later.

A word on Android and other non-Apple phones

If you’re comparing formats from the other direction — wondering whether you should switch a non-Apple phone to shoot in HEIF/HEIC if it offers the option — the same logic mostly applies, just from the other side. The storage savings are real, but you’ll run into the exact same compatibility friction the moment you try to use one of those photos outside an ecosystem that handles HEIC natively, which for non-Apple users is an even narrower slice of the software you’re likely to encounter day to day. For most people outside Apple’s ecosystem, sticking with JPG (or, for newer use cases, WebP or AVIF where genuinely supported) remains the more practical default.

The bottom line

HEIC isn’t a worse format than JPG — it’s a more efficient one that happens to live inside a much smaller compatibility bubble. Decide based on where the photo is actually going: staying inside Apple’s ecosystem, HEIC is fine and even slightly advantageous; going anywhere else, JPG remains the format that won’t surprise you with a “can’t open this file” error at the worst possible moment.