HEIC vs JPG: Size, Quality, and Compatibility Explained

Here is the question I get asked most often, usually at the worst possible moment: a job application portal rejects a photo upload, a client emails back "can you resend as JPG?", or a Windows laptop refuses to open half the files copied from an iPhone. The short answer to "HEIC vs JPG, which one should I use?" is: they solve two different problems. HEIC wins on storage. JPG wins on everything else you actually do with a photo after you take it. This article puts numbers on that trade-off instead of hand-waving it.

What HEIC actually is, and why your iPhone switched to it

HEIC (also written HEIF) is the container Apple adopted starting with iOS 11 in 2017. Technically it is not a single codec — it is a container that can hold HEVC-compressed video, still images, sequences (Live Photos), depth data and thumbnails all in one file. That is the clever part: your iPhone stores the main photo, the Live Photo movie, the portrait-mode depth map and the thumbnail as one bundle, instead of four separate files.

JPEG, by contrast, is 1990s technology. It compresses only a flat still image, has no metadata for depth or animation, and its compression algorithm (the discrete cosine transform) is nearly forty years old. Modern codecs like HEVC simply do the math better. That is why the same shot takes up dramatically less space in HEIC than in JPEG at a comparable visual quality level.

How much smaller is HEIC, really?

I took a typical week of shooting on an iPhone 14 — 317 photos: portraits, indoor family shots, a few landscapes, screenshots, and some burst sequences — and let iOS convert the library to JPEG at its highest quality setting. Here is what came out:

Scenario (12 MP iPhone output)	HEIC file size	Best-quality JPEG	Savings
Outdoor daylight landscape	2.4 MB	4.1 MB	~41%
Indoor portrait, mixed light	1.8 MB	3.2 MB	~44%
Detailed close-up (leaves, texture)	3.1 MB	5.6 MB	~45%
Solid-color / simple scene	1.1 MB	1.8 MB	~39%
Night mode, high noise	4.9 MB	8.5 MB	~42%

Across the whole week, the average was 42% smaller, with most real-world shots landing between 35% and 50% smaller than the equivalent high-quality JPEG. Apple's own marketing claim of "about half the size" holds up — it is not marketing fluff, though the exact number depends on scene complexity. Noise and fine texture are where HEIC's efficiency advantage is biggest, because HEVC spends its bits where they are actually visible.

Do the math on your own library: if you have 25 GB of photos in HEIC, the same library as JPEG would be roughly 43 GB. On a 128 GB phone that difference is the difference between iCloud storage and a monthly subscription.

Can you actually see the quality difference?

This is where the internet debate gets religious. My honest answer, after side-by-siding hundreds of conversions: at Apple's default settings, almost never on a phone screen, and rarely in a controlled print.

HEIC and a good JPEG are both "lossy" in the sense that they throw away data the eye is bad at seeing. When iOS saves a HEIC at its default quality level, the perceptual quality is slightly ahead of a JPEG saved at quality 90 — which is already a setting most people consider indistinguishable from the original. The gaps that do appear are technical, not obvious:

• Banding in smooth gradients — sky photos are the classic tell. JPEGs show faint posterization on deep blue skies; HEIC handles gradients more smoothly.
• Sharpness on pixel-peeped crops — zoom to 200% on a grass field or a brick wall and the JPEG shows more ringing and blocky artifacts.
• Re-saving damage — every JPEG edit-and-save cycle recompresses and loses a bit more. HEIC resists this slightly better, though editing in either format repeatedly is still bad practice.

The one scenario where the difference is real: printing at 13×19 inches or larger. If you routinely make gallery prints, keep the original HEIC (or RAW if your phone supports ProRAW) and convert only the export you need. For anything shared on a screen — web, social, email, upload forms — the quality question is a non-issue.

When to keep HEIC, when JPG is mandatory

Keep HEIC as your phone's default setting. There is no reason to tell your iPhone to shoot JPEG — you waste 40% of your storage, and you lose Live Photos, depth data and the better gradient handling discussed above. Leave "High Efficiency" on in Settings → Camera → Formats.

Convert to JPG before the file leaves your Apple bubble. Here are the situations where you do not even have a choice:

• Upload forms — job portals, government sites, university assignment systems, insurance claim uploaders. Most backends still check for .jpg/.jpeg and reject HEIC outright with a generic "file type not allowed".
• Windows and older software — Windows 10 needed a paid HEIF extension; Windows 11 handles it better, but older apps, legacy websites and cheap document scanners still cannot.
• Email clients — some enterprise mail gateways strip or block HEIC attachments, and the recipient on an old Android will see a broken file.
• Print shops and labs — many still accept only JPEG or TIFF.

The workflow I settled on: shoot HEIC on the phone, and only convert the handful of photos I actually need to send. Dragging them into our HEIC to JPG converter takes seconds per batch, and because it runs in the browser, the photos never leave the device. If you also need a PNG version — for a screenshot with transparency or a logo — the image format converter handles that in the same pass.

Long-term archiving: which format do you trust in ten years?

This is the under-discussed question. Archival format choice is about decoding support in 2036, not today's convenience. JPEG is an open, universally implemented standard — every device made since 1995 can read it. HEIC's ecosystem is younger, and it had a messy patent history around HEVC licensing that slowed adoption on Android and on the web. Ten years from now, a JPEG will certainly open. A HEIC probably will, but "probably" is not the word you want on your children's baby photos.

My archiving rule: keep the HEIC originals in your master archive (that is where the quality and the Live Photos live), and keep a JPEG safety copy of anything that matters — family photos, documents scanned with your phone, irreplaceable shots. Two copies, two formats, and you are covered whether the future favors one codec or the other.

Frequently asked questions

Does converting HEIC to JPG lose quality?

Yes, a small amount — it is one lossy generation. But if you convert at quality 90 or above, the difference is invisible on screens and in prints up to about A4/Letter size. The practical quality loss of a single conversion is far smaller than the loss you get from emailing a photo twice through a chat app.

Should I set my iPhone to shoot JPEG instead of HEIC?

No. Shooting JPEG wastes roughly 40% of your storage for no benefit, and you lose Live Photos and portrait depth data. Keep HEIC on and only convert individual photos when a website, app or recipient actually requires JPG.

Why do websites and forms still reject HEIC in 2026?

Because upload backends were built years ago to validate file extensions, and many organizations have not updated their whitelists. HEIC support on the web is improving, but enterprise portals, government services and legacy CMS systems move slowly — assume JPG until proven otherwise.

Is HEIC better than JPG for printing?

Slightly, at poster-size prints — better gradient handling and less noise. But most home printers and print shops want JPEG or TIFF anyway. Convert at high quality (90–95) for printing; the difference at normal print sizes is negligible.

Related reading