2026-08-15
Last year I imported about 3,000 photos from my phone to a Windows PC. A third of them wouldn't open. At the time I figured the computer was broken. Turns out the problem was the format—HEIC, the default photo format on iPhones, which Windows doesn't natively recognize.
This isn't a niche complaint. The **HEIC vs JPG** dilemma hits almost every iPhone user eventually. I'm not here to pick a side. I want to lay out what each format is good for, and when you really have no choice but to convert to JPG.
HEIC (High Efficiency Image Coding) is what Apple has used by default since iOS 11, built on the HEIF standard. Its goal is simple: same quality, smaller size. JPG is a 30-year-old format with unbeatable compatibility and a bit of a legacy problem.
In one sentence: HEIC is the space-saving new format, JPG is the old format that works everywhere.
The numbers tell the story. For the same 12-megapixel photo, HEIC lands around 2-3MB where JPG takes 4-6MB. Over 10,000 photos a year, that's tens of gigabytes of difference. That's HEIC's biggest value, and honestly its whole reason to exist.
If you only handle photos on your iPhone, HEIC never gives you trouble. But photos are meant to move. The real friction in **HEIC vs JPG for iPhone photos** shows up the second a file leaves the Apple ecosystem.
You don't need to hit all of these. One is enough to stop you cold. In practice, a lot of people meet HEIC for the first time when submitting a resume or uploading an ID photo.
In rough order of urgency, convert in these situations:
1. **Website uploads**: job portals, visa applications, e-commerce platforms—most accept only JPG or PNG
2. **Sending to non-Apple users**: original photos over WeChat or email, where the receiver is on Android or Windows
3. **Printing**: many online labs and self-serve printers have spotty HEIC support
4. **Archiving**: if you're unsure what software will open a file in ten years, JPG is the safer bet
5. **Professional delivery**: don't make clients, editors, or partners deal with codecs
On the flip side, if your photos stay on your own devices and back up to iCloud, HEIC is fine as-is. No need to convert. Conversion has a cost—an extra step, an extra compression pass. Skip it when you can.
The good news: converting to JPG isn't a technical feat. In iCloud settings you can switch downloads to "Most Compatible," but more often you just need to convert a few files on the spot—with built-in tools, Shortcuts, or an online converter.
My own routine: keep the originals in HEIC on iCloud, batch-convert a JPG copy whenever something needs to go out. A **HEIC to JPG converter** exists exactly for this. A decent one reuses the original decode data instead of re-encoding from a compressed image, so nothing gets blurrier.
And if this all sounds familiar, you're right. We've written about
**HEIC vs JPG** has no absolute winner. On pure storage efficiency, HEIC wins easily. On universality, JPG is still the "can't go wrong" option. The smart move isn't choosing one. It's switching by scenario: keep HEIC on your device, convert to JPG when it goes out.
If a HEIC file is blocking you somewhere, use our
**Q: Which has better quality, HEIC or JPG?**
A: At equal quality, HEIC is about half the size. At equal size, HEIC keeps more detail. But at normal phone viewing distances, the difference is usually invisible. JPG loses on file size, not on quality your eyes can notice.
**Q: Is HEIC the default format on iPhone?**
A: Yes, since iOS 11. You can switch to "Most Compatible" under Settings → Camera → Formats, which makes the iPhone save JPG directly—at the cost of larger files.
**Q: Why can't my friend open the HEIC photo I sent?**
A: Their device or app doesn't support the format. Android phones, Windows, and many web apps have no native HEIC support. If you need them to see it, convert to JPG first.
**Q: Does converting damage image quality?**
A: A proper tool decodes the HEIC and re-encodes as JPG—one compression pass with theoretically slight loss, usually invisible to the eye. The real risk is double compression, compressing the JPG again after conversion. That's when things get mushy.