The file your iPhone makes without asking

Every photo you’ve taken on an iPhone 7 or newer (iOS 11+, 2017) is stored as HEIC by default. Not because Apple enjoys breaking compatibility — because the math is compelling: a 12-megapixel shot lands around 1.5–2.5 MB in HEIC versus 3–5 MB in JPEG at equivalent quality. Across a 40,000-photo library that’s the difference between a full phone and a comfortable one.

What’s actually inside a .heic file

Two standards stack up:

• HEIF (High Efficiency Image Format) — the container, standardized by MPEG in 2015. Think of it as a box: it can hold one image or a whole sequence, plus metadata, thumbnails, depth maps and edit instructions.
• HEVC (H.265) — the video codec repurposed to compress stills. Each photo is essentially one frame of HEVC video, which is why it squeezes so well: HEVC is a generation newer than JPEG’s 1992 algorithm and handles smooth gradients, shadows and fine textures far more efficiently.

Because the container isn’t one image but a collection, HEIC is also how Apple packs bursts (a sequence of frames), depth data for Portrait mode, and edit history (crop/rotate instructions applied non-destructively) into a single file — while a Live Photo pairs a HEIC still with a separate .mov clip. JPEG couldn’t do any of that — Apple would have needed a parallel file format anyway.

Why Apple picked it

• Storage: iPhones shoot 12–48 MP photos plus 4K video; halving photo bytes is the single biggest storage win available.
• Features: Live Photo, burst and Portrait depth need a multi-image container — HEIF was the standardized one that could carry what they needed.
• HDR: HEIC carries 10-bit color; the iPhone’s HDR pipeline uses it. JPEG is stuck at 8 bits.
• Ecosystem leverage: Apple controls both ends — camera and viewer — so the usual chicken-and-egg adoption problem didn’t apply inside its own walls.

The catch you already know

Outside Apple’s walls the adoption never finished. Chrome, Edge and Firefox still can’t display HEIC; Windows needs a codec extension; many apps, upload forms and embedded viewers reject it outright. iOS papers over this by auto-converting to JPEG when you share or transfer — but drag a .heic onto a Windows desktop or into a web form and it bounces. That’s the gap this site fills: the converter decodes HEIC locally in your browser, and the HEIC vs JPG compatibility matrix maps exactly what opens where.

If you’d rather not produce HEIC in the first place, stopping your iPhone from shooting it is a two-tap change — with a trade-off worth understanding first.

Frequently asked questions

Is HEIC the same as HEIF?

Almost. HEIF (High Efficiency Image Format) is the container standard — the box that holds images, metadata and image sequences. HEIC is Apple's name for HEIF files that use the HEVC (H.265) codec inside. In practice every .heic file on an iPhone is a HEIF container with HEVC-coded images; the words get used interchangeably.

Does HEIC look better than JPG?

At the same file size, yes — HEVC is a much newer codec and holds more detail per byte, especially in gradients and fine textures. It also supports 10-bit color (smoother HDR skies and skin tones) and true transparency, neither of which JPEG can do.

Can Android or Windows open HEIC?

Android 10+ and Windows 10/11 (with the free HEIF Image Extensions codec) can decode it, but support is patchy — older devices, many apps and virtually every non-Safari browser can't. That's exactly why this converter exists.

Why does my .heic file sometimes say .heif?

Same thing — Apple uses .heic for camera photos; other tools and cameras may write .heif or .hif. The converter sniffs the actual file signature, so either name works.