HEIC vs JPG: Differences & Which to Use

HEIC files are half the size of JPGs with better quality — so why isn't everyone using them? Compression, compatibility, and when to convert.

September 28, 2026 By Formatly

Every iPhone photo you’ve taken since 2017 is probably a HEIC file, and every photo on the web is probably a JPG. They’re solving the same problem — storing a photo in as few bytes as possible — with technology decades apart. Here’s what actually differs, and which one you should use.

The short version

HEIC = better compression (roughly 2× smaller than JPG at equal quality), supports transparency, 16-bit color, and burst/live-photo sequences in one file. Poor compatibility outside Apple.
JPG = universal compatibility (works on literally everything), larger files, 8-bit color only, no transparency. The safe default for sharing.

Use HEIC for storing photos on your Apple devices. Use JPG when the photo needs to work everywhere — the web, email, Windows PCs, print shops.

Compression: where HEIC wins decisively

JPG uses compression technology from 1992. HEIC uses HEVC (the same codec behind 4K video), which is dramatically more efficient. In practice:

A 12 MP iPhone photo: ~2–3 MB as HEIC vs ~5–7 MB as JPG at comparable visual quality.
At very low bitrates (thumbnails, messaging apps), HEIC holds detail where JPG falls apart into blocky artifacts.

This isn’t a subtle 10% improvement — it’s roughly half the storage for the same photo. That’s why Apple switched: it cut iCloud storage usage and made photo libraries load faster.

Features JPG simply doesn’t have

Transparency. HEIC supports an alpha channel like PNG. JPG never will.

16-bit color. JPG is locked to 8 bits per channel (16.7 million colors). HEIC supports 10- and 12-bit, which means smoother gradients — no banding in skies and sunsets — and far more headroom for editing before colors break down.

Multiple images in one file. An iPhone “Live Photo” is a single HEIC containing the still plus the video frames. JPG can’t do that; Apple had to pair JPGs with separate .MOV files.

Lossless option. HEIC can store images losslessly (like PNG but smaller). JPG is always lossy.

Compatibility: where JPG still wins

This is the entire reason HEIC hasn’t taken over. JPG opens on every device, browser, app, and operating system made in the last 30 years. HEIC support is still spotty:

Windows: needs a codec install (here’s how).
Web browsers: as of 2026, no major desktop browser decodes HEIC natively. You cannot put a HEIC on a webpage and expect it to render.
Older Android: supported since Android 9, but inconsistent before that.
Many web services: upload forms, CMSs, and social platforms often reject .heic outright.

So the rule is simple: HEIC for capture and storage, JPG for distribution. Your iPhone is right to shoot in HEIC. You should convert to JPG the moment a photo needs to leave the Apple ecosystem.

How to check (and change) what your iPhone shoots

Not sure which format your iPhone is currently using? Check in 10 seconds:

Open Settings → Camera → Formats.
High Efficiency = HEIC/HEVC. Most Compatible = JPG/H.264.

Should you switch to “Most Compatible”? Usually no. High Efficiency halves your storage use and iCloud bandwidth, and Apple auto-converts when sharing to non-Apple destinations (AirDrop to a Mac, iMessage to Android, or USB transfer to a PC with “Automatic” transfer mode all convert to JPG on the way out — see Settings → Photos → Transfer to Mac or PC → Automatic). The HEIC files only bite you when you bypass those pipelines: manual file copies, third-party transfer apps, or accessing iCloud Photos from a Windows browser.

One setting worth knowing: Settings → Photos → Transfer to Mac or PC. “Automatic” converts HEIC→JPG during USB transfer (convenient, but you lose the HEIC originals on the PC side). “Keep Originals” transfers the true HEIC files (better for archiving, but then you need one of the viewing methods above). Pick based on whether the PC is a destination or an archive.

Converting between them

Going HEIC → JPG is the common direction: for web uploads, sharing with Windows users, or archiving in a universal format. Our HEIC to JPG converter does this entirely in your browser — batch conversion, quality control, no uploads.

Going JPG → HEIC is rarely useful. You can’t regain quality that JPG compression already discarded, and you lose compatibility. The one exception: recompressing a large JPG archive to save space, where you control the playback environment.

Practical advice by scenario

Phone photography: Leave your iPhone on HEIC (“High Efficiency” in Settings → Camera → Formats). Convert to JPG only when sharing outside Apple apps. AirDrop, iMessage, and iCloud handle the conversion automatically when sending to non-Apple recipients — it’s the manual transfers (USB, email attachments) that bite you.

Website images: Neither — use WebP or AVIF for the web in 2026. Both beat JPG on size and are universally supported by modern browsers. Convert your JPGs with our WebP optimizer.

Long-term archiving: HEIC is technically the better archive format (smaller, higher bit depth), but JPG’s universality is a form of insurance. Archivists still debate this; a pragmatic approach is keeping originals in HEIC and exporting JPG copies for anything you share.

Editing: Convert to a lossless working format (TIFF, PNG, or your editor’s native format) before heavy editing. Editing a HEIC or JPG directly and re-saving stacks compression artifacts — “generation loss” — with every save.

The bottom line

HEIC is the better technology; JPG is the better lingua franca. That tension will persist for years because compatibility moves slower than codecs. Until browsers decode HEIC natively, the practical workflow is: shoot HEIC, share JPG.