Why your iPhone photos are HEIC (and when to just make them JPG)
Dov Azencot
@DovAzencotThe first time it bit me, I was trying to attach a photo to a support form for my landlord. I dragged the picture over, the upload spinner turned once, and the form said "unsupported file type." The photo looked perfectly normal in my Photos app. The file was called IMG_4471.HEIC, and the form had no idea what to do with it.
That's the whole story of HEIC in one sentence. It's a better format than JPG in almost every measurable way, and a stubborn slice of the software you touch every day still stares at it blankly.
Why Apple went HEIC in the first place
Around 2017, iPhones quietly switched their default photo format from JPEG to HEIC — High Efficiency Image Container, built on the HEVC video codec. The reason was storage. HEIC stores roughly the same photo in about half the space. A picture that would have been a 4 MB JPEG lands closer to 2 MB, and your eye can't tell the two apart.
It does more than shrink, too. HEIC can hold 16-bit color instead of JPG's 8-bit, so it keeps more of the tonal range your camera captured. It stores Live Photos, depth maps, and bursts inside a single container. On the phone, it's the right call. Apple wasn't wrong.
The catch nobody mentions at the Genius Bar
HEIC is patent-encumbered, and support outside Apple's world is patchy in a way JPG's simply isn't. Here's where I've personally hit walls:
- Government and banking upload forms
- Older Windows machines without the paid HEVC codec pack
- A lot of image fields in web apps and CMSs
- Group chats with Android friends, which sometimes recompress it into mush
- Almost any "attach a photo" flow written before 2020
JPG, by contrast, has been openable by literally everything since the 1990s. There is no device, no browser, no form, no ancient office PC that chokes on a JPG. That universality is the entire reason to convert.
What you actually give up
Let me be honest, because this is the part most "convert HEIC now" pages skip. Going from HEIC to JPG is not free. It's a lossy-to-lossy conversion, so you're re-encoding already-compressed data, and JPG is the less efficient format. Three real costs:
| What HEIC keeps | What JPG does |
|---|---|
| ~2 MB for a 12 MP photo | ~3.5–4.5 MB for the same photo |
| 16-bit color depth | 8-bit — banding possible in skies |
| Live Photo, depth, HDR gain map | Flattened to a single still |
So the file gets bigger and the color range gets smaller. That sounds like a bad trade until you remember the point: a slightly larger file that opens everywhere beats a smaller file that opens nowhere you need it. For a photo you're uploading, emailing, or handing to someone on a PC, that trade is worth making every time.
The quality drop, in practice, is small. At a sensible quality setting a converted JPG is visually indistinguishable from the HEIC for anything you'd view on a screen. You'll only notice the 8-bit ceiling in extreme cases — a smooth sunset gradient can show faint banding. For a snapshot going into a form, you will never see it.
When I don't convert
If the photo is staying inside Apple's ecosystem — living in my library, syncing to my other devices, getting printed through Apple's own path — I leave it HEIC. Converting there would just make the file bigger and throw away color depth for no reason. HEIC is the better archive format. I only reach for JPG at the moment a photo needs to leave the walled garden.
The other thing I never do is convert the only copy. The original HEIC on my phone stays put. I export a JPG for wherever it's going, and the master keeps its full color and depth. Same rule I follow for every format: convert the copy you send, keep the original you own.
How I actually do it
You can turn off HEIC at the source — Settings, Camera, Formats, "Most Compatible" — and your iPhone will shoot JPG from then on. That works, but it means every photo pays the JPG tax forever, even the ones that never leave your phone. I'd rather shoot HEIC and convert the handful I actually share.
For that I use the HEIC-to-JPG converter on this site. It runs in your browser, so the photo never leaves your device — which matters more than usual here, because these are your actual personal photos, not stock screenshots. Drop the HEIC in, get a JPG that the landlord's form, your aunt's Windows laptop, and every upload box on earth will accept without complaint.
The format war isn't worth fighting on a support form at 9 PM. Convert the one photo, send it, move on. That's what I do now, and IMG_4471 finally uploaded.
Related posts
PNG or JPG? The ten-year rule I use to decide
Lossless versus lossy, edges versus photographs, transparency versus none. One simple question tells you which format a file should be — with a real size table to prove it.
Why I convert PNG to WebP (and the one time I don't)
PNG is a brilliant format to edit in and a wasteful one to ship. Here's what WebP actually saves you, where it saves you nothing, and the single rule I never break.
How in-browser image conversion actually works (and why I built it that way)
"Your files never leave your device" is an architecture, not a marketing line. Here's how WASM does the conversion right in your browser, and the one real limit it has.
All posts