What is HEIC? Apple's image format, the compatibility cost, and when to convert

The one-sentence answer

HEIC is a file extension Apple uses for still images stored in the HEIF container and compressed with the HEVC (H.265) video codec. That's it — three things bundled together under one filename suffix.

• HEIF (High Efficiency Image File Format) is the container — a generic ISO/IEC 23008-12 wrapper that can hold image data, thumbnails, depth maps, burst stacks, and metadata. Defined 2015 by MPEG.
• HEVC (High Efficiency Video Coding, a.k.a. H.265) is the codec — the actual compression algorithm that turned a 10 MB RAW frame into a 1.5 MB encoded image.
• HEIC is Apple's specific pairing — HEIF container, HEVC codec, .heic extension — introduced as the iOS 11 default in September 2017.

So yes, HEIC is a container holding a single video frame. The clever part is that still-image compression inherits a decade of video R&D: intra-frame prediction, variable block sizes, CABAC entropy coding. The boring part is that Apple branded it, which is why "HEIC" gets used as a synonym for the whole stack even when the container is really HEIF and the codec is really HEVC.

Why Apple shipped it in 2017

JPG had been the camera-roll default since the first iPhone. It's reliable, universal, and 25 years old. By 2017 iPhones were shooting 12-megapixel Portrait mode, Live Photos, and burst sequences — storage started hurting. Apple needed either larger phones (expensive) or a smaller format (smart). HEIC cuts file size roughly in half at matched perceptual quality; on a 256 GB iPhone that's the difference between 20,000 photos and 40,000.

Two other wins came along for the ride:

• 10-bit colour depth. JPG is 8-bit. HEIC stores 10 bits per channel, which is why smooth skies and sunsets look less banded on newer iPhones.
• Multi-image containers. Live Photos, burst stacks, Portrait-mode depth maps, and exposure brackets all fit inside a single HEIF file with proper per-image metadata — a JPG can't carry any of that without sidecar files.

The cost is compatibility. HEVC isn't royalty-free (MPEG-LA licensing applies to encoders and decoders), which is why Google ignored it and built WebP and later why the industry built AVIF. HEIC is Apple saying "we'll pay the licence fee; you deal with it." Windows dealing with it is where things get awkward.

HEIC vs JPG vs WebP vs AVIF — the size chart

Here's the same 12-megapixel iPhone photo saved at matched perceptual quality (SSIM ≈ 0.96) in four formats. The source is a daylight outdoor scene — worst-case for any codec because of fine vegetation detail.

The takeaway: HEIC is genuinely smaller than JPG at the same quality — that's the claim Apple made and it holds up. AVIF edges HEIC, WebP is close to JPG but not as dramatic as HEIC's win. Compression ratio is not why you'd convert out of HEIC; compatibility is.

The honest compatibility matrix

As of early 2026, HEIC reads cleanly in some places, awkwardly in others, and not at all in a few:

Pragmatic summary: inside Apple's walled garden HEIC is frictionless; everywhere else it ranges from "one-time install" to "will not work, period." If you're sharing outside Apple, convert first.

HEIC vs JPG — what you actually gain and lose

You gain

• ~50% smaller files at matched visual quality.
• 10-bit colour — smoother gradients, less banding in skies, sunsets, smoke.
• Multi-image containers — Live Photos, bursts, depth maps, exposure brackets in one file.
• Transparency — HEIC supports alpha (JPG doesn't). Most iPhone camera HEICs don't use it; Procreate and some shortcut exports do.
• Lossless mode — HEIC has a proper lossless setting; JPG's "quality 100" is not actually lossless.

You lose

• Universal compatibility. JPG opens on literally everything. HEIC doesn't.
• Simpler EXIF. JPG's EXIF is a battle-tested format every tool reads; HEIF metadata is technically richer but inconsistently supported.
• Cheaper editing. A JPG is basically free to decode; HEVC decoding is CPU-intensive and can choke older or lower-end devices.

Live Photos, burst mode, and what's actually inside a HEIC

An iPhone HEIC isn't always one image. A Live Photo saves a still HEIC plus a short MOV sidecar of the surrounding ~3 seconds. When you AirDrop a Live Photo to another Apple device, both travel together; when you share outside Apple, only the still usually survives.

Burst-mode and exposure-bracketed captures can pack multiple frames into the same HEIF container with per-frame metadata. Most third-party converters only extract the primary frame and silently drop the rest — ours does the same by default, which is the right behaviour for 99% of users but worth knowing if you're chasing a specific burst frame.

Portrait-mode photos embed a depth map alongside the primary image. That's what enables after-the-fact bokeh adjustment on iOS. A conversion to JPG or PNG flattens the final rendered result and discards the depth map — the bokeh is baked in, no longer editable. If you need non-destructive Portrait edits, keep the HEIC.

EXIF and privacy

HEIC from an iPhone typically carries EXIF metadata: GPS coordinates, camera model, lens, shooting time, shutter speed, Apple-specific fields like face-detection metadata. If you're posting the photo publicly, that's potentially leaking your home address.

Most conversion tools preserve EXIF by default (which is the wrong default for privacy). Ours strips it by default (privacy-safe) with an opt-in toggle if you need to preserve shooting metadata for a photography workflow. Apple's own "Share" menu has a Location → Off option that scrubs GPS on export; use it before AirDropping outside your household.

When to convert HEIC (and to what)

Convert to JPG when…

• The recipient isn't on Apple hardware. Universal compatibility wins.
• You're uploading to a website, a job portal, an insurance form — anything that has a strict format allow-list.
• Size still matters but not to the last kilobyte. JPG at Q90 is near-HEIC quality at double the size, but opens everywhere. See our full HEIC-to-JPG guide.

Convert to PNG when…

• You need lossless — editing in Photoshop/GIMP, making a print master, preserving screenshots with sharp text edges.
• Transparency matters (Procreate or Shortcut HEICs with alpha).
• You accept that the PNG will be 3-8× larger than the HEIC (PNG is lossless; HEIC was lossy). See the Windows-focused HEIC-to-PNG workflow.

Convert to PDF when…

• Turning HEIC photos of documents, receipts, or whiteboards into a single shareable file.
• Multiple photos → one paginated PDF; the receiving side gets a bookmark-friendly doc, not a ZIP of images.

Keep HEIC when…

• Everyone in the workflow is on Apple hardware.
• You're archiving for iCloud Photos — Apple will redownload as HEIC anyway; JPG doubles your bill.
• You need Live Photos or Portrait-mode depth editing to survive.

How we handle HEIC

The honest version of the pipeline: your HEIC stays in your browser tab. We decode HEVC via a WebAssembly build of libheif, extract the primary image (plus alpha if present), attach a proper sRGB ICC profile (wide-gamut P3 preservation on toggle), and export to JPG / PNG / PDF at your chosen quality. Batches run sequentially in a web worker so the tab stays responsive; we hand back a ZIP for multi-file jobs.

A recent pipeline rewrite made the decoder 14–16× faster than a naive libheif wrapper, and fixed the colour-profile bug that was silently washing out conversions on wide-gamut monitors. Details in the HEIC-to-PNG deep-dive. Files never upload, never hit our disks, and auto-evict from browser memory as soon as you close the tab.

Frequently asked questions

What does HEIC stand for?

High Efficiency Image Container (or High Efficiency Image Coding, depending on who's writing). It's Apple's branding for HEIF-containerised HEVC-coded still images. The extension is always lowercase .heic by convention; some Apple tools also produce .heif, which is the same container with a different codec (e.g. AV1 in theory, though no shipping iPhone uses that yet).

Is HEIC better than JPG?

At matched visual quality, yes: HEIC files are ~50% smaller, support 10-bit colour, carry multiple images, and support transparency and lossless mode. At matched compatibility, no — JPG wins by a mile. "Better" depends on whether the recipient's software can open it.

Why won't Windows open HEIC?

HEVC is patent-encumbered. Microsoft ships the HEIF container support for free but charges $0.99 for the HEVC codec to cover licensing costs — and many corporate-managed Windows fleets block the Microsoft Store outright, so paying isn't always an option. Our browser tool sidesteps the whole problem because the decoder is a WebAssembly library bundled with the page.

Does converting HEIC to JPG lose quality?

Slightly, yes — both are lossy, and you're re-encoding. At our default JPG Q90 the loss is imperceptible on photographic content; at Q95 it's undetectable without pixel-peeping. If you care about truly zero loss, convert to PNG instead — PNG preserves the HEIC decoder's output byte-for-byte, at the cost of 3–8× file size.

Can I set my iPhone to save JPG instead of HEIC?

Yes: Settings → Camera → Formats → Most Compatible. This switches camera output to JPG+H.264 at the cost of roughly doubling per-photo storage. Worth doing if you share primarily with non-Apple users; otherwise leave it on High Efficiency and convert on-demand.

Is HEIC the same as HEIF?

Close, not identical. HEIF is the container. HEIC is HEIF+HEVC specifically. You can have HEIF files with other codecs inside (AV1 variants exist in spec), but in everyday usage "HEIF" and "HEIC" are used interchangeably because Apple's HEVC pairing is the only one most people encounter.

Can I batch-convert a whole camera roll?

Yes. iOS Photos → select range → Share → Save to Files → pick a folder → copy to any device → drop the folder on our converter. We process sequentially and hand back a ZIP. On a modern laptop, 60 iPhone HEICs take ~60-90 seconds thanks to the recent speed fix.

Ready?

Pick the target that matches where the file is going: HEIC to JPG for universal sharing, HEIC to PNG for editing, HEIC to PDF for document-style bundles. Free, runs in your browser, no Microsoft Store extension required. If you want the other side of the format debate, read what WebP is and what AVIF is — they're the web-native rivals that solve the same problem without the licensing tax.