HEIC is Apple's default photo format since iOS 11 (2017) — a container, not just a compressed image, built on the HEVC video codec. It's roughly half the size of an equivalent JPG, and the reason it's a "container" rather than a simple file is that Live Photos, Portrait mode depth maps, and burst sequences all need to store more than one flat image. The trade-off is compatibility: HEVC's patent licensing is split across several competing pools, which is why most of the non-Apple world built a separate royalty-free format (AVIF) instead of adopting HEIC. Skip to whether you should keep shooting in HEIC for the practical recommendation.
You open your Camera Roll, AirDrop a photo to a friend with an Android phone, and they get back to you confused — the file won't open. Or you try to upload an iPhone photo to a website and it gets rejected outright. You check the file and see .heic instead of the .jpg you expected.
HEIC isn't a mistake or a glitch. Apple chose it deliberately in 2017, and the reasons are more specific — and more interesting — than "it saves space," which is where most explanations stop.
The real reason: HEIC isn't really an image format, it's a container
Here's the distinction almost every explanation skips: HEIC is a container, not a codec. A codec is the actual compression math that turns pixels into a smaller file. A container is the wrapper that organizes what's inside — one image, several images, metadata, whatever the format allows.
JPG conflates the two: there's effectively one way to compress a JPG, and the file holds exactly one image and nothing else. HEIC separates them. The container is called HEIF (High Efficiency Image Format), developed by MPEG and finalized in 2015. The codec doing the actual compression inside an iPhone's HEIC file is HEVC (High Efficiency Video Coding, also called H.265) — the same codec used for 4K video streaming. When you see "HEIC," you're looking at a HEIF container specifically holding HEVC-compressed content. That's the whole acronym, decoded: a container format wrapping a video codec, repurposed to hold still images.
This isn't a technicality. It's the reason everything else about the format makes sense.
Why iPhone photos specifically need this
A plain JPG can only ever be one flat image. Several of the iPhone's signature camera features need to store more than that in a single file, and a container is what makes it possible.
- Live Photos. When you take a Live Photo, the iPhone captures a still frame plus roughly 1.5 seconds of video before and after the shutter. Inside the HEIC file, the still frame is stored as the primary image, and the video clip is stored as a separate auxiliary item with its own timing metadata, all in the same container. JPG has no slot for that second item — there's nowhere to put it.
- Portrait mode depth maps. The adjustable background blur in Portrait photos works because the iPhone stores a grayscale depth map — how far each pixel is from the camera — as an additional image inside the same HEIC file. That's why you can still adjust the blur strength on a Portrait photo months after taking it: the depth data never left the file.
- Burst mode. Instead of writing dozens of separate files for a rapid sequence, a burst can be stored as one HEIC container holding multiple independently compressed images that share metadata like timestamp and camera settings.
Convert any of these to JPG and you keep only the primary still frame. The video clip, the depth map, the rest of the burst sequence — none of it has anywhere to go in a format that only ever holds one image. This is the actual answer to "why does my iPhone use HEIC": the camera features Apple wanted to ship needed a container that could hold more than a single picture, and JPG architecturally can't be that container.
Why HEIC files are roughly half the size of JPG
The size difference everyone quotes — HEIC files running about half the size of an equivalent-quality JPG — comes directly from the codec underneath, not from anything Apple invented.
JPG's compression dates to 1992. It splits an image into fixed 8×8 pixel blocks and transforms each independently, without considering how neighboring blocks relate. It's effective, but blunt by modern standards.
HEVC, designed decades later for video, predicts blocks using more sophisticated reference patterns and variable block sizes. Video compression has to be efficient since a single clip contains thousands of frames; that same efficiency, applied to one still image, produces smaller files at equal visual quality. A 12-megapixel iPhone photo typically runs 1.5–2.5MB as HEIC versus 3–5MB as JPG for comparable detail. Apple didn't invent new compression — it borrowed an already-excellent one from video and repackaged it for photos.
Why didn't everyone else adopt it?
This is the question most articles either skip or answer with a vague wave at "licensing issues." The actual story is more specific, and it explains the compatibility mess in one clean shot.
HEVC's patents aren't held by one company with one license to sign. They're split across competing pools — MPEG LA, Access Advance, and Velos Media among them — each charging separate royalties to anyone shipping a decoder. A company adding HEVC support doesn't negotiate one deal; it potentially negotiates several, with no single point of clarity on total cost.
Apple absorbed that cost across its own ecosystem and moved on. Google and the rest of the browser/Android world looked at the same fragmented landscape and backed AV1, a royalty-free codec, building AVIF as the image-format equivalent of what Apple did with HEIC. Chrome, Firefox, and Android increasingly favor AVIF over HEIC for exactly this reason — same container logic, but built on a codec nobody has to pay to use.
That's why HEIC stayed an Apple-ecosystem format instead of a universal standard: not a technology failure, just licensing terrain nobody outside Apple wanted to build on.
Should you keep shooting in HEIC?
For most people, yes — with a JPG converter kept on hand for when compatibility actually matters.
| Your situation | Recommendation | Why |
|---|---|---|
| You mostly share photos within iMessage, AirDrop, or iCloud | Keep HEIC | Stays in the Apple ecosystem; no compatibility issue ever comes up |
| You regularly email photos to non-Apple users or upload to older websites | Switch to "Most Compatible" | Solves it at the source instead of converting every time |
| You need to free up storage but still want occasional JPGs | Keep HEIC, convert as needed | Keeps the storage savings; conversion only when actually required |
| You take a lot of Live Photos or Portrait shots you want to keep editable | Keep HEIC | JPG conversion permanently discards the video clip and depth data |
| You upload to a platform that flatly rejects HEIC (some CMS tools, Salesforce) | Convert before uploading | No setting fixes this — the platform doesn't support the format at all |
Convert iPhone HEIC photos to universal JPG with no quality loss beyond the unavoidable re-encode, entirely in your browser. No upload, batch-ready, free.
Open toolThe practical middle ground most people land on: leave HEIC on for the real storage savings and seamless Apple-to-Apple sharing, and keep a converter on hand for when a specific platform or person needs a JPG instead.
Edge cases: Android, Photoshop, and rejected uploads
Android's HEIC support is inconsistent. Android added HEIF support starting with Android 9 (Pie) in 2018, and some Qualcomm Snapdragon chipsets (865 and newer) capture HEIC directly. Unlike Apple's ecosystem, where every iOS 11+ device behaves identically, Android support varies by manufacturer, chipset, and OS version — there's no single answer for whether a given Android phone supports it.
Photoshop's bit-depth limitation. Older and even some current Photoshop versions only support HEIC at 8-bit color depth, not the 10-bit or higher depth some iPhone cameras capture. For color-critical editing, this can introduce a quality ceiling that wouldn't exist with a fully supported format.
Outright rejection by specific platforms. Some services don't support HEIC at all — Salesforce is a commonly cited example, and in 2020, some online AP exam submission portals couldn't process HEIC photos of handwritten answers, leaving affected submissions blank. No setting fixes this; the platform simply doesn't support the format, and conversion before upload is the only workaround.
Frequently asked questions
Does HEIC lose quality compared to JPG?
No — at the same file size, HEIC generally looks better than JPG, since HEVC compresses more efficiently than JPG's older method. What does cost quality is the reverse direction: converting an existing HEIC photo to JPG involves re-encoding with a less efficient codec, which introduces a small, usually invisible amount of additional loss.
Why do some of my iPhone photos save as JPG and others as HEIC?
Screenshots always save as PNG regardless of your camera format setting. Some third-party camera apps default to their own format choice. Photos received from non-Apple devices via Messages or AirDrop keep whatever format they arrived in. If native Camera app photos aren't saving as HEIC and you expect them to, check Settings > Camera > Formats to confirm "High Efficiency" is selected.
Can Android phones use HEIC?
Some can, inconsistently. Android 9 (Pie) and later support HEIF, and certain Snapdragon chipsets can capture HEIC directly, but support varies by manufacturer and Android version rather than being guaranteed across the platform the way it is on every iPhone running iOS 11+.
Does converting a HEIC Live Photo to JPG lose the video part?
Yes, and there's no way to get it back afterward. The video clip is stored as a separate item inside the HEIC container alongside the still frame. JPG has no structure to hold that second item, so converting keeps only the still image — the motion and any audio are discarded for good.
Is HEIC the same as HEIF?
Close, but not identical. HEIF is the general container standard that can technically hold images compressed with different codecs. HEIC specifically means a HEIF container holding HEVC-compressed images — which is what an iPhone produces. On an iPhone the two terms end up meaning the same file in practice, but other HEIF variants exist that aren't necessarily interchangeable with HEIC.
Will HEIC ever become as widely supported as JPG?
Unlikely at the codec level, since the fragmented patent licensing behind HEVC isn't likely to simplify on its own. What's more probable is continued growth in conversion tools and broader operating-system support that lets HEIC files be viewed without every platform needing to license HEVC directly — rather than HEIC becoming a true universal standard the way JPG is.
Does switching to "Most Compatible" convert my existing photos?
No. That setting, found in Settings > Camera > Formats, only changes the format of photos and videos captured after you switch it. Photos already on your phone remain in HEIC and need a separate conversion step if you want them as JPG.
The bottom line
HEIC exists because a plain compressed image was never going to be enough for what Apple wanted iPhone cameras to do. Live Photos, depth-aware Portrait shots, and burst sequences all need a container that can hold more than one image, and JPG simply isn't built that way. HEVC's compression, borrowed from video, gets the file size down to roughly half of an equivalent JPG as a side benefit.
The compatibility friction isn't a bug Apple forgot to fix — it's a direct consequence of HEVC's fragmented patent licensing, which is also why the rest of the industry built AVIF instead of adopting HEIC. That's not changing soon.
The practical takeaway: HEIC is worth keeping for how you actually use your iPhone day to day, and worth converting to JPG specifically when you're sending a photo somewhere that doesn't support it. Those are two different problems, and now you know which one you're actually solving each time.