Image Tools·4 min read

What Is HEIC Format? Why iPhone Photos Won't Open

You take a photo on an iPhone, AirDrop it to a colleague's laptop, and the file won't open. The extension says .HEIC. So what is heic format, exactly, and why does it feel like Apple is the only place you ever meet it? This article covers where HEIC came from, the real reason iPhones default to it, why so much software still rejects it, and how to turn a stubborn .heic file into a JPG that opens everywhere, without installing codecs or sending your photos to a server.

Open the tool All insights

What is HEIC format under the hood

A container built on video technology.

HEIC is Apple's flavor of HEIF, the High Efficiency Image File format standardized by the MPEG group in 2015. The container can hold a lot more than one picture: image sequences, depth maps, thumbnails, and edit history all fit inside a single .heic file. The compression itself comes from HEVC, the same codec used for 4K video, applied to a single still frame.

That video heritage is the point. HEVC intra frame compression squeezes photographic detail far more efficiently than the 1992 era JPEG algorithm, so a HEIC photo takes noticeably less space than an equivalent quality JPEG. Apple flipped the default on with iOS 11 in 2017, and every iPhone since shoots HEIC out of the box.

Why iPhones use HEIC and Windows resents it

Storage on one side, patent licensing on the other.

Multiply the savings per photo by a camera roll of ten thousand shots and you have the answer to why iPhones use HEIC: it roughly stretches the same storage budget across many more photos and burst sequences. Apple controls the whole pipeline on its own hardware, so it could adopt the format overnight.

The rest of the world had licensing to worry about. HEVC decoding is covered by multiple patent pools, and Microsoft chose to sell the HEVC Video Extensions as a paid add on rather than absorb the fee for every Windows license. The practical result is that sharing HEIC with Windows users often ends with a reply asking what this weird file is. Web upload forms that whitelist .jpg and .png, older Android phones, and long serving tools like legacy CMS image pipelines pile onto the same problem.

A worked HEIC to JPG conversion, start to finish

One file in, one file out.

Say your camera roll gives you IMG_4032.HEIC, a 4032x3024 photo weighing 2.1 MB. Drag it onto the HEIC to JPG uploader, which accepts .heic and .heif files up to 50 MB each. The first visit shows a brief decoder loading message while the WebAssembly module arrives.

Press Convert to JPG. The file is decoded locally, redrawn at full 4032x3024 resolution, and encoded as JPEG at 92 percent quality. Your browser downloads IMG_4032.jpg automatically, same name, new extension, and that file opens in Windows Photo Viewer, uploads to any form, and attaches to any email without complaint. Queue five files and you get five separate downloads.

HEIC mistakes that cost people photos

Learned the hard way by plenty of camera rolls.

Most HEIC pain comes from a handful of repeatable errors:

Renaming photo.heic to photo.jpg and assuming it converted. The bytes are still HEVC, and anything that trusted the extension now fails in a more confusing way.
Deleting originals right after conversion. Canvas based converters drop EXIF metadata, so the GPS location and capture timestamp live only in the .heic you just trashed.
Converting an entire library up front. You pay double storage for thousands of files when only the handful you actually share ever needed converting.
Emailing .heic files to a mixed group and assuming everyone sees them. Windows and older Android recipients frequently can't open the attachment at all.
Forgetting that a burst or Live Photo container holds more than one frame. A converter outputs the primary still, not the whole sequence.

Three habits for painless HEIC handling

Keep the savings, skip the friction.

First, leave your iPhone shooting HEIC and convert at the edge, meaning only the specific files that need to cross into unfriendly territory. You keep the storage benefit for the other 99 percent of your library.

Second, when a batch is headed for the web, convert with a heic to jpg converter before uploading rather than trusting the site to transcode. Server side converters often recompress aggressively or fail silently. Third, if metadata matters for a given shot, export it from the Photos app instead, which writes a JPEG with EXIF intact, and reserve browser conversion for speed.

HEIC to JPG or another tool: matching format to job

JPG isn't always the right landing spot.

JPG is the correct destination when the goal is compatibility: sharing, uploading, embedding. If the image is going to be edited repeatedly, converted to PNG instead via HEIC to PNG, since JPEG loses a little detail on every save. If the converted photos are headed for a website, run them through the Image Compressor afterward to cut the transfer size.

And when a set of photographed documents needs to become a single attachment, convert to JPG here first, then feed the results to JPG to PDF. Each tool does one job, and chaining them beats hunting for one giant app that does everything badly.