Apple switched the default capture format on iPhone to HEIF — High Efficiency Image File Format — starting with iOS 11 in 2017. If you didn’t go looking for that setting, you likely never noticed. The photos still looked like photos. The Camera app behaved identically. What changed was happening entirely inside the file, and the consequences only surface later: when you send an image to an older device, upload to a platform that rejects the format, or open a file in software that doesn’t speak HEIC.
Understanding what actually shifted requires looking at what HEIF is doing at the compression level — not just accepting Apple’s framing that it’s “better.”
What HEIF Actually Is (and What HEIC Has to Do With It)
HEIF is a container format, standardized by the Moving Picture Experts Group. It can hold still images, image sequences, depth maps, audio, and metadata in a single file. The image data itself is compressed using HEVC — High Efficiency Video Coding, also called H.265 — which is a video codec adapted for still-image compression.
The .heic extension you see on iPhone photos is simply the filename suffix Apple chose for HEIF files containing HEVC-compressed image data. The two terms are often used interchangeably in consumer contexts, but technically HEIC describes the specific codec variant, while HEIF is the broader container.
JPEG, by contrast, uses Discrete Cosine Transform compression applied in 8×8 pixel blocks. That block structure is why severe JPEG compression produces a characteristic grid-like artifact — the DCT coefficients are quantized block by block, and at low quality settings the discontinuities between blocks become visible. HEVC compresses using variable-size coding units that can range up to 64×64 pixels, adapting to content rather than applying a fixed grid. This allows HEIC to achieve similar perceived quality at meaningfully smaller file sizes, or better quality at the same size.
What You’re Gaining — And It’s Real
The efficiency improvement is not marketing copy. HEVC’s prediction coding is genuinely more sophisticated: it references neighboring regions, uses directional prediction modes, and applies transforms at multiple block sizes depending on local image complexity. Flat areas compress very efficiently; detailed textures get more coding units.
HEIF also supports 10-bit color depth natively, which matters for HDR content. iPhone’s HDR capture — and more recently, Apple’s Photographic Styles and Log video — relies on that bit depth to preserve highlight and shadow detail that 8-bit JPEG simply cannot store without clipping. A JPEG is capped at 8 bits per channel, which means HDR tone-mapped images saved as JPEG are already a degraded representation of what the sensor captured.
Equally significant: HEIF stores depth maps (used for Portrait Mode), Live Photo motion data, and multiple image representations — the main image plus a thumbnail, or a burst sequence — all inside a single file. JPEG can carry limited metadata via Exif, but it has no native mechanism for auxiliary images or depth information alongside the primary frame.
What You’re Actually Losing
The efficiency and capability gains are real, but the format carries genuine costs — mostly around compatibility.
The compatibility problem is not academic. Re-saving a JPEG loses data because the DCT quantization step is lossy every time you save. HEIC doesn’t have that specific problem, but what it does have is a conversion problem at every handoff point. The moment you send a HEIC file to someone on Windows (where native support has existed only since Windows 10 with a codec pack that isn’t installed by default), email it to a service expecting JPEG, or upload it to a platform that converts it server-side, you’ve introduced a transcoding step. That step is lossy. The platform receiving a HEIC often converts to JPEG for storage or delivery, and that conversion applies its own quantization. You’ve gained nothing from the HEIC’s efficiency if the destination immediately re-encodes it to JPEG at an unknown quality setting.
Editing software compatibility varies. Many consumer-level applications added HEIC support gradually, and even among those that nominally support it, behavior at export isn’t always consistent. Some will round-trip through an internal JPEG conversion without warning. The 10-bit color information a HEIC carries may be silently downsampled to 8-bit if the application doesn’t support wide color workflows. Checking whether your specific software reads and writes HEIC natively — rather than converting on import — is worth confirming before relying on it for any serious archival purpose.
The codec itself is encumbered. HEVC licensing is complex, and while Apple built the decoder into its hardware, other vendors have been slower or less consistent. This is part of why Google and the open-source community backed AVIF (based on AV1) as a royalty-free alternative with similar compression efficiency. HEIF as a container can technically hold AV1-compressed images — sometimes referred to as AVIF — but that’s a different codec chain than what iPhone is currently shooting.
For a broader look at how HEIC and JPEG compare in practice — including what the difference means when you’re choosing a camera’s default — our article on HEIF vs. JPEG: Which Camera Format Should You Use? covers the tradeoffs in more depth.
The iOS Compatibility Mode You Might Not Know About
Apple included a way to keep shooting HEIC on-device while sending JPEG automatically when the file leaves the phone. Under Settings → Camera → Formats, switching to “Most Compatible” forces JPEG capture entirely. Keeping “High Efficiency” selected but enabling Settings → Photos → Transfer to Mac or PC → Automatic instructs iOS to transcode to JPEG during any USB transfer to a non-Apple computer.
The third option — and the one most people don’t find — is in Settings → Photos → Export Options (the label and location have shifted across iOS versions). Enabling automatic conversion there means AirDrop, email, and share-sheet exports to non-Apple destinations automatically deliver JPEG, while the original HEIC stays on-device for iCloud sync and Apple ecosystem use.
If you’d rather not root around in menus and want to handle conversion file by file or batch, iOS itself offers a route. We’ve documented the exact steps in How to Convert HEIC to JPEG on iPhone Without Third-Party Apps.
When Sticking With HEIC Makes Sense
For most iPhone photographers staying primarily within the Apple ecosystem — iPhone to Mac to iCloud Photos — HEIC is a reasonable default. The space savings are real when you’re managing a library with tens of thousands of frames. The 10-bit HDR preservation matters if you shoot in challenging light and want the full tonal range available in editing. Portrait Mode depth maps are tied to HEIC storage; a JPEG capture won’t carry the depth data needed to re-edit the blur effect later.
The format also handles sequences efficiently. A burst of twelve frames in HEIF can occupy a fraction of the space that twelve individual JPEGs would require, because the container stores prediction deltas between frames rather than full pixel grids for each one.
What to Actually Do Next
The clearest decision point is your destination, not your capture. If your photos stay in Apple’s ecosystem and your editing software handles HEIC natively with full 10-bit support, there’s little reason to abandon the format. If you’re regularly sending files to collaborators, uploading to platforms with inconsistent HEIC handling, or archiving in software that converts silently on import, the practical move is to enable automatic JPEG conversion on transfer — and understand that those JPEGs represent a one-time, controlled lossy step you’ve chosen, rather than an uncontrolled transcoding step imposed downstream.
Check the Formats and Photos settings on your device now, confirm which conversion mode is active, and verify that your primary editing application reads HEIC natively rather than converting it quietly. Those two checks take under two minutes and determine whether the efficiency gains HEIC offers are actually reaching your workflow — or being discarded at the first handoff.