How to Convert HEIC to JPG (and Why Files Get Bigger)

You copied photos off an iPhone, pasted one into a website or a chat, and got a file nobody can open. That's HEIC — Apple's default photo format since 2017, chosen because it stores a photo in roughly half the space of a JPEG. Great for your storage, awkward everywhere else: Chrome and Firefox won't display it, plenty of Windows machines need a codec pack first, and most upload forms reject it. Here's what HEIC is, where it works, and how to convert to JPG without handing your camera roll to a random upload site.

What is HEIC, exactly?

HEIC (High Efficiency Image Container) is the file wrapper Apple uses for HEIF images — pictures compressed with HEVC, the same codec family behind modern video. Same scene, same visual quality, roughly half the bytes of JPEG. Apple switched the iPhone camera to it in iOS 11 (2017) and never switched back; a decade of camera rolls later, HEIC is the most common "why won't this open?" format in the wild.

The main camera on a recent iPhone shoots 4032×3024 pixels — 12,192,768 pixels, or 12.2 megapixels, in a 4:3 frame. Stored as HEIC that typically runs 1.5–3MB. The same photo as a quality-0.9 JPEG typically runs 1.6–2.2× larger, which is the whole storage argument in one sentence.

Where does HEIC open — and where does it fail?

The pattern: HEIC is safe inside the Apple ecosystem and a coin flip outside it. If a photo needs to leave that ecosystem — a website, a client, a school portal, a marketplace listing — make it a JPG.

How do I convert HEIC to JPG?

Three routes, fastest first:

1. In the browser, locally. A converter that ships the HEVC decoder as WebAssembly — like our HEIC to JPG converter — decodes the file inside the tab. No upload, no queue, no size cap beyond your RAM. Batch convert, pick JPEG quality, optionally resize the long edge, download.
2. On the iPhone itself. Sharing or exporting from Photos (Save to Files, or share to most third-party apps) commonly hands over a JPEG copy automatically. Settings → Camera → Formats → Most Compatible makes the camera shoot JPEG going forward — storage cost returns, compatibility pain leaves.
3. On Windows. Install the HEIF extensions, then open-and-export one at a time in Photos — fine for two files, miserable for two hundred.

Avoid the "free online HEIC converter" that requires an upload unless the photos are truly throwaway. A converter that runs locally gives you the same result with none of the privacy exposure, and no watermark pitch at the end.

Why do converted JPGs come out bigger?

Because HEIC won. At equal visual quality, HEVC encoding stores a photo in about half the bytes of JPEG — that's the entire reason Apple adopted it. So when you convert, you're re-encoding a efficiently-stored image into a less-efficient format. A 4.5MB JPEG-quality photo is about a 2.25MB HEIC: 50% smaller. Run the conversion the other way and the file grows.

Numbers for a typical 12MP shot stored as a 2.4MB HEIC:

Ranges, not promises — JPEG size depends on what's in the photo, not just how many pixels. A brick wall compresses harder than confetti.

What quality setting should you use?

0.9 for anything you'll look at again. At 0.9 and above, the re-encode is visually invisible at normal viewing sizes, including prints at typical dimensions. Drop to 0.75 when the destination is a web page or an email batch and size matters more than zoomed-in detail. 0.5 is thumbnail territory. If you're converting for editing masters, stop: keep the HEICs and convert working copies, because every JPEG save re-compresses.

The batch math: a 60-photo trip

Sixty HEIC photos at 2.4MB average is 60 × 2.4 = 144MB. Converted to quality-0.9 JPGs at 1.6–2.2× the original, the same batch runs roughly 230–317MB. Two consequences worth planning around:

• A 25MB email attachment fits 10 of the HEIC originals but only about 5 of the JPGs. For email, convert at 0.75 quality or resize the long edge to 2048px first.
• Cloud-sync services don't care; upload pipelines with per-file caps might. A quality-0.9 JPG from a 12MP phone stays well under any 10MB-per-file limit you'll meet.

Doing the shrinking after converting is where you lose control — start with the destination (email, listing, portfolio) and pick quality and dimensions for it once. Need files smaller still? Run the results through the image compressor after converting. Curious what your camera leaves embedded in every file? The EXIF viewer shows the metadata riding along — location included — and the metadata remover strips it before you publish.

The bottom line

HEIC exists because it's genuinely better at storage — half the size of JPEG at the same quality — and it breaks because the rest of the world standardized on JPEG decades ago. Keep HEIC masters on Apple gear, convert JPG copies for everything that leaves, choose quality 0.9 unless size forces 0.75, and use a converter that decodes locally. The HEIC to JPG converter does the whole pipeline in your browser, the image compressor trims the results further, and the image formats guide covers when to reach for PNG, WebP, or SVG instead.

Frequently Asked Questions

Related Tools