HEIC to JPG: What to Do When iPhone Photos Won't Open Anywhere
Why iPhones shoot HEIC, exactly where the format breaks — Windows, older Android, web forms — how to convert to JPG, and what happens to Live Photos and depth data along the way.
Prerequisites
- One or more .heic files from an iPhone or iPad
- Omnvert HEIC → JPG Converter
Step-by-step
- 1
Understand why your iPhone shoots HEIC in the first place
HEIC is Apple's implementation of the HEIF container, and the image inside is compressed with HEVC — the same compression family used by H.265 video. That newer compression is the whole point: a HEIC photo is typically around half the size of a JPEG at comparable visual quality, which is why Apple made it the default camera format back in iOS 11. Halving every photo matters enormously on a phone that shoots thousands of them and syncs them all to iCloud. HEIC also stores things JPEG structurally cannot: the paired video of a Live Photo, portrait-mode depth maps, and multiple images in one container. None of that is a problem — until the file leaves the Apple ecosystem.
- 2
Recognize where HEIC breaks
The pain points are predictable. Windows cannot decode HEIC out of the box on many installations — it needs HEVC codec support that is not always present, so Photos shows an error or a blank thumbnail. Older Android devices lack HEIC support entirely, and even where the OS can display the file, individual apps may not accept it. The web is the biggest minefield: a large share of upload forms — job applications, government portals, CMS media libraries, forum attachments — validate against a whitelist that says JPEG and PNG, and silently or loudly reject .heic. Email recipients on older systems, print shops, and office document workflows round out the list. If a photo needs to travel to an unknown destination, HEIC is the wrong format to send.
- 3
Convert the files you need to share
Open the HEIC → JPG converter, add your .heic files, and download the JPEG results. Convert only the photos that actually need to leave your device rather than your whole library: JPEG copies are roughly twice the size, and the HEIC originals remain the best masters to keep. Give the converted files recognizable names before sending them, since a recipient who receives IMG_4821.jpg has no idea what it is — and neither will you in six months.
- 4
Know what conversion does to Live Photos and depth data
A JPEG can hold exactly one still image, so everything auxiliary in the HEIC container is dropped at conversion: the Live Photo's motion clip, portrait-mode depth maps, and any secondary frames. The main image — the photo as you see it — survives intact, and for sharing that is almost always all you need. But it is a one-way door: a JPEG converted back to HEIC does not regain the motion or depth data. This is another reason to keep the HEIC originals. If the recipient specifically needs the living, moving version of a Live Photo, send it through an Apple-native channel or export it as a video instead of converting to JPEG.
- 5
Decide: change the camera setting, or convert after the fact
If HEIC friction is a rare event for you, keep the default and convert the occasional file — you keep the storage savings on thousands of photos and pay a small conversion cost a few times a year. If you constantly feed photos into HEIC-hostile systems — a company CMS, Windows-based clients, web forms — flip the phone itself: Settings → Camera → Formats → Most Compatible makes the camera capture JPEG directly. The trade-off is real: your future photos will take roughly twice the space on device and in iCloud, and the setting does nothing for the HEIC photos you already have, which still need converting. Most people are best served by leaving High Efficiency on and converting on demand.
- 6
Set realistic quality expectations
HEIC to JPEG is a re-encode, not a repackaging: the image is decoded and compressed again with a different, older algorithm, so one generation of loss is inherent to the process. At a sensible quality setting this loss is invisible in normal viewing — the photo will not look worse to anyone you send it to. What you should avoid is stacking generations: converting, editing the JPEG, re-saving, compressing again for upload. Each lossy save compounds. The clean pattern is to keep the HEIC as the master, do any editing before or during a single export, and treat every JPEG as a final output rather than a working file.
- 7
Check the metadata before you share
Converting the format does not automatically strip the photo's metadata — the JPEG you send can still carry EXIF fields such as capture time and, if location was enabled, GPS coordinates. Before posting a converted photo publicly or attaching it to an application, run it through the EXIF Remover and verify what it carries. Ten seconds of checking beats broadcasting your home address embedded in a photo of your sofa.
Why not just make everything JPEG forever?
Because HEIC is genuinely the better archive format for your own library: same visual quality at roughly half the storage, plus the motion and depth data JPEG cannot hold. The compatibility problem lives at the edges — the moment of sharing — not in storage. Solving an edge problem by doubling the size of your entire photo library is a poor trade for most people. Convert at the boundary, keep efficiency inside it.
Sending to a person or uploading to a form → convert that file to JPG. Sharing between Apple devices → do nothing, it just works. Feeding a Windows/CMS workflow weekly or more → consider switching the camera to Most Compatible. Archiving your own library → keep HEIC.
One more practical note: iPhones already convert on the fly in some paths — AirDrop to a Mac, the Mail app, and many share-sheet targets send JPEG automatically when the receiver may not handle HEIC. This is why the problem often surfaces only when you copy files off the phone by cable or cloud drive: those raw file transfers hand over the .heic untouched, and that is exactly the moment a converter earns its keep.