images
Why Does My iPhone Save Photos as HEIC (and How to Change It)
What HEIC is, how it differs from JPG (compression, size, compatibility), why Apple made it the default, how to shoot JPG again — and how to convert the HEICs you have.
By Kyle Hurst · · Updated October 23, 2026
You AirDrop a photo to a Windows laptop, upload it to a form that only takes JPG, or text it to a friend with an older Android phone — and it either won’t open or shows up as a weird .HEIC file nothing recognizes. Your iPhone didn’t do anything wrong; it’s just been shooting a format most of the outside world still doesn’t expect.
What HEIC actually is
HEIC (High Efficiency Image Container, technically HEIF) isn’t a new idea bolted onto JPG — it’s a completely different compression scheme borrowed from HEVC video encoding. That lineage is why it’s so much more efficient: a HEIC photo typically comes in at roughly half the file size of an equivalent-quality JPG. Same detail, same resolution, a fraction of the storage.
Apple made it the default camera format back in iOS 11, in 2017. On a phone where storage is finite and photo libraries are enormous, cutting file sizes in half without a visible quality hit was an easy call. It’s also why your phone can hold thousands more photos than it used to before nagging you to buy more iCloud storage.
HEIC vs JPG: what’s actually different
The two aren’t just different file extensions — they’re built on different compression technology, and that difference is exactly why one works everywhere and the other doesn’t.
| HEIC | JPG | |
|---|---|---|
| Compression tech | HEVC intra-frame coding | DCT (block-based) |
| Typical size, 12MP photo | ~1.5–2 MB | ~3–4 MB |
| Quality at equal file size | Noticeably sharper | More visible compression artifacts |
| Color depth | Up to 16-bit | 8-bit |
| Depth maps / Portrait data | Supported | Not supported |
| Multiple images per file | Supported | One image per file |
| Transparency (photos) | No (in practice) | No |
| Windows | Partial — needs a codec extension on many builds | Native |
| macOS | Native | Native |
| Android | Partial — recent versions only | Native |
| Browsers | Inconsistent (mostly no <img> support) | Universal |
| Web upload forms | Frequently rejected | Universal |
The compression difference is the whole story. JPG, standardized in 1992, uses the discrete cosine transform (DCT): it chops an image into blocks and discards high-frequency detail in each one independently. HEIC instead borrows intra-frame HEVC (H.265) coding from video — the same technology that keeps 4K streams compact. Predicting pixel blocks from their neighbors within the same frame beats JPG’s independent-block approach, which is where the halved file size comes from.
The container picked up more than efficiency from its video lineage. HEIF was built to hold more than one flat photo, so it allows color depth beyond JPG’s 8 bits, depth maps for Portrait Mode effects, and sequences of images in a single file. JPG has none of that; it was designed purely for single 8-bit still frames.
One thing HEIC does not give you is transparency. The container technically has room for an alpha channel, but the HEIC photos your phone actually produces are opaque, just like JPG. If you need a transparent background, reach for PNG or WebP after conversion.
So on-device, HEIC is the better format: half the storage, and every app in an iPhone-to-Mac-to-AirDrop workflow already reads it natively. JPG’s advantage isn’t technical — it’s that every browser, OS, printer, ad platform and upload form understands it without a plugin or codec pack. “Works absolutely everywhere” beats “half the file size” the moment a file leaves Apple’s ecosystem.
Why it keeps breaking things
The efficiency is real, but HEIC support outside Apple’s ecosystem is spottier than it should be:
- Windows didn’t ship native HEIC viewing until fairly recently, and even now some builds need an extra codec pack from the Microsoft Store before Photos will open one.
- Web upload forms — job applications, marketplace listings, contest entries — are frequently coded to accept only
.jpgor.png, and silently reject or fail on HEIC. - Older Android phones and a lot of enterprise software (image libraries, CMS platforms, print shops) still don’t recognize the format at all.
None of this is really “wrong” — it’s just the gap between a format Apple adopted early and a world that’s still catching up.
How to make your iPhone shoot JPG instead
If you’d rather avoid HEIC at the source, there are two settings worth knowing about:
- Change the capture format. Go to Settings → Camera → Formats and choose “Most Compatible.” New photos will be saved as JPG (and videos as H.264) going forward. This doesn’t touch photos you’ve already taken — only what you shoot from here on.
- Convert automatically on transfer. Even if you keep shooting HEIC, go to Settings → Photos → Transfer to Mac or PC and set it to “Automatic.” With this on, iOS converts HEIC to JPG (and HEVC video to H.264) the moment you plug in or AirDrop to a computer — the originals on your phone stay HEIC, but what lands on your Mac or PC is a universally readable JPG.
Between the two, “Automatic” transfer is the lower-friction option: you keep the storage savings on your phone and only pay the compatibility tax when a file actually leaves the Apple ecosystem.
Converting the HEIC photos you already have
If you’ve already got a folder — or a whole camera roll export — full of .HEIC files, changing a setting won’t touch them retroactively. For that, use HEIC to JPG. It runs the conversion entirely in your browser: your photos never get uploaded anywhere, which matters if the folder includes anything private. Drop in dozens of files at once and it’ll batch-convert the whole set, packaging the results into a single ZIP download instead of making you save each one individually.
If you specifically need a lossless result — say, an image you’ll edit further and want to avoid any additional compression — use HEIC to PNG instead. And if the batch needs more than a change of format — resizing every shot to a listing’s maximum dimensions, or compressing them under an upload cap — run the converted files through the Bulk Image Processor, which handles format, size and compression in a single pass over the folder. For a broader look at when PNG, JPG, WebP, and AVIF each make sense, see PNG vs JPG vs WebP vs AVIF: Which Format to Use and When.
Quick FAQ
Does converting HEIC to JPG lose quality? A little, technically — JPG is a different lossy codec — but at a quality setting of 92, the difference from the HEIC original is visually lossless for ordinary photos. You won’t see banding, blockiness, or softness at normal viewing sizes. If you’re feeding the image into further heavy editing or archival storage, PNG avoids the question entirely.
What happens to Live Photos? A Live Photo is really a still frame paired with a few seconds of video. Converting it to JPG or PNG keeps the primary still frame — the one you see as the thumbnail — but drops the motion and audio portion, since JPG/PNG have no concept of an attached video clip. If you need the motion preserved, keep the original HEIC/MOV pair alongside your converted still.
Does converting to JPG remove the location data? No — converting HEIC to JPG carries the GPS coordinates and other EXIF metadata over intact, so if you’re posting the photo publicly, strip it first with the EXIF Remover (here’s what a photo can leak).
Why not just leave everything as HEIC? If every device and service you use understands it, there’s no reason to change anything — you’re getting smaller files for free. The moment you need to share with Windows users, upload to a strict web form, or hand a photo to someone on an older Android phone, that’s when it’s worth converting.
Pick whichever fits your workflow: change the camera setting so new photos are already compatible, flip on automatic transfer conversion, or just convert the files you’ve got right now — no upload, no signup, no waiting.