HEIC to JPG — When to Convert and How to Do It Right

If you’ve ever tried to email a photo from your iPhone and had the recipient complain the file “won’t open,” you’ve met HEIC. It’s been the default iPhone camera format since iOS 11 in 2017, it compresses roughly twice as well as JPG at the same visible quality, and outside the Apple ecosystem it’s a pain. This guide covers when converting to JPG makes sense, when it doesn’t, and how to do it without wrecking the image.

What HEIC actually is

HEIC is a file extension for images stored in the HEIF container format, using the HEVC (H.265) codec for compression. In plain terms, it’s a still image compressed with the same technology as modern video codecs — which is why it’s so efficient.

The technical pitch is real. A typical 12 MP iPhone photo is 1.5-2 MB as HEIC and 3-4 MB as JPG at matched visible quality. Across a 10,000-photo iCloud library, that’s 20 GB of storage difference.

The web-compatibility pitch is grim. As of 2026, HEIC has no native browser support outside Safari. Chrome, Firefox, Edge — none of them display HEIC images. Most CMSes choke on HEIC uploads. WordPress has a plugin layer but it’s not universal. Shopify rejects HEIC outright. Email clients mostly fail. Microsoft Office programs vary.

The short version: HEIC is an excellent storage and transmission format inside the Apple walled garden and outside it you are going to have a bad time.

When to convert

Convert HEIC to JPG (or WebP/AVIF, more on that below) when:

• You’re uploading to any web CMS other than one you know supports HEIC.
• You’re emailing to a recipient who isn’t on Apple hardware.
• You’re sharing via a platform that doesn’t explicitly handle HEIC (Slack, Discord, most form uploads).
• You’re archiving somewhere outside iCloud and want long-term accessibility without needing Apple software.
• You’re using the image in a document, presentation, or design tool that doesn’t read HEIC.

Keep HEIC when:

• The image stays in Photos on your iPhone or Mac.
• You’re sharing between Apple devices via AirDrop, iMessage, or iCloud shared albums.
• Storage space on the device is the constraint and you don’t need to share outside Apple.

The quality question

Converting HEIC to JPG is inherently lossy — you’re going from one lossy format to another. The question is how much quality you lose, and the practical answer is “very little if you’re careful, quite a bit if you’re not.”

JPG at quality 90-95 preserves essentially all visible detail from a HEIC source. Quality 80 introduces noticeable compression in smooth gradients (sky, skin tones). Quality 70 starts to show chroma artifacts at display size.

A sensible default for most web use:

Use case	JPG quality	Expected size (12 MP source)
Archive / print	95	4-6 MB
Web hero / portfolio	85-90	1.8-2.8 MB
Blog / article body	80-82	1.0-1.5 MB
Thumbnail	75	200-400 KB

For the web use cases, most people would get even better results converting directly to WebP or AVIF instead of JPG. But JPG is the safe universal fallback, and if you’re converting for “just in case it opens everywhere,” JPG at 85 is the right call.

The metadata trap

HEIC files from an iPhone include a substantial pile of EXIF metadata: GPS coordinates (unless you disabled Location Services for Camera), the specific device model and software version, timestamps down to the second, and in some cases the original camera settings.

Most HEIC-to-JPG converters preserve this metadata by default. That’s fine for personal archiving. It’s not fine if you’re:

• Publishing real estate photos (GPS coords that reveal the property location — and sometimes the photographer’s home if they shot indoor test photos).
• Sending proof-of-concept images to a client with timestamps and location you’d rather not share.
• Posting to forums or social platforms that don’t strip EXIF on upload (most don’t, despite what people assume).
• Sharing anything where you wouldn’t want the full camera/location history attached.

The fix is simple: strip EXIF on export. OpenImages’ Remove EXIF tool handles this client-side, so the metadata never leaves your machine. For a proper overview of what EXIF contains and why it matters, see our dedicated guide on EXIF metadata and what it leaks.

The Live Photo wrinkle

iPhone photos are often Live Photos, which means the HEIC file is paired with a short video clip. When you convert a HEIC to JPG, the video is discarded — the output is a single still image from the “key frame” of the Live Photo.

This usually isn’t a problem, but two things to know:

1. The key frame isn’t always the moment you thought you were capturing. Some apps let you pick a different frame; most HEIC-to-JPG converters just take the first frame.
2. If you want both the still and the motion, export the HEIC and the associated .mov separately from Photos before converting.

Batch conversion and privacy

If you’re converting one photo, any tool works. If you’re converting a thousand — a wedding gallery, a portfolio archive, a real-estate shoot — the workflow matters more.

Things to look for in a batch workflow:

• Local processing. HEIC files often contain GPS and personal content. A tool that uploads to someone else’s server is handing over all of that. OpenImages’ HEIC to JPG tool runs entirely in your browser — the file never leaves your device.
• Preserving or stripping EXIF on your choice, not by default.
• Consistent quality setting across the batch. Don’t mix quality 75 and quality 95 in the same output folder and try to sort it later.
• Preserving file naming. Some converters rename everything to IMG_00001.jpg, which loses the original timestamp-based naming iPhone uses.

A reasonable batch pipeline looks like:

1. Export originals from Photos to a working folder.
2. Convert HEIC to JPG (or WebP for web-only) at quality 90.
3. Strip EXIF for anything that will be published.
4. Resize to delivery size if the originals are huge.
5. Re-compress the resized output with a image compressor if you want smaller files.

Should you just convert everything forever

One question people ask: “Should I just set my iPhone to shoot JPG instead of HEIC?” Settings → Camera → Formats → Most Compatible does exactly that.

The right answer depends on your workflow. If 90% of your photos end up shared outside Apple, shooting JPG directly saves a conversion step and avoids any quality loss from re-encoding. If most stay inside Apple and you occasionally need a JPG, shoot HEIC and convert on the way out. The storage savings alone justify HEIC for pure archival use.

Either way, the tool chain matters. A clean HEIC-to-JPG conversion — right quality, stripped metadata, original naming — takes fifteen seconds with the right tool and an hour of grief with the wrong one.