Guide · Apple formats
What HEIC Is, and When to Convert It
Your iPhone saves photos in a format that half the world's software refuses to open. That is not a bug and it is not Apple being difficult — it is a specific engineering trade with a specific licensing consequence. Here is what HEIC actually is, and the three cases where converting is the right call.
The format is efficient and modern. The problem is never the file — it is whatever you are trying to open it with. Converting takes seconds, and here it happens inside your browser with nothing uploaded.
Why your iPhone stopped making JPGs
JPEG dates to the early 1990s. It has been extraordinarily successful — it is the closest thing digital imaging has to a universal language — but it encodes photographs with techniques that are now three decades old, and modern codecs simply do the same job with fewer bits.
HEIC is what Apple chose instead, starting with iOS 11 in 2017. The name refers to two separate things stacked together. The outer layer is HEIF, a general-purpose image container standardized as ISO/IEC 23008-12, which can hold one image or many, plus depth maps, thumbnails, and editing data. The inner layer is the compression itself: the image is encoded with HEVC, also known as H.265, the same codec used for 4K video. Encoding a still photo with a video codec sounds odd until you remember that a video codec's whole job is squeezing a single frame efficiently before it ever gets to motion.
The payoff is roughly half the file size at comparable visual quality, which on a phone that shoots thousands of photos is the difference between running out of storage and not. HEIC also carries things JPG cannot: ten bits per color channel instead of eight, an alpha channel, and multiple images in one file — which is how bursts and the still frames of a Live Photo travel together.
Why Windows and Chrome often can't open it
The obstacle is licensing, not difficulty. HEVC is covered by a large portfolio of patents administered through licensing pools, and any platform that ships a decoder has to account for that. Apple, which encodes and decodes HEIC across its whole device line, handles it as part of the product. Other vendors have been more cautious, and the result is support that is patchy in a way that looks arbitrary from the outside.
In practice: Apple platforms open HEIC everywhere, including Safari. Windows has historically required extra codec components installed from the Microsoft Store, and the HEVC part of that has not always been free or preinstalled — behavior varies by Windows version and by what the device maker bundled. Chrome and Firefox do not decode HEIC on most platforms, so a HEIC dropped into a browser window frequently shows nothing at all. Android support depends on the version and the manufacturer. Older photo editors, print kiosks, content management systems, and upload forms written before 2017 have no idea the format exists.
So the failure is always at the boundary. The photo looks perfect on your phone and dies the moment it meets someone else's software: the job application form rejects it, the client on a Windows laptop sees a blank icon, the forum post shows a broken image, the photo lab counter person shrugs.
The decision, in three lines
Keep HEIC when the file is staying with you. If the photo lives in your library, syncs between your own Apple devices, and gets backed up, converting it accomplishes nothing except doubling the space it takes. The efficient format is the correct format for storage. Convert at the moment of sharing, not at the moment of capture.
Convert to JPG when the file is leaving your control. Uploads, email attachments, web forms, printing services, marketplace listings, anything going to a Windows or Android recipient, anything going into a website. JPG is the format nothing refuses. This is the overwhelming majority of conversions and it is what the HEIC to JPG converter exists for.
Convert to PNG only when lossless genuinely matters. That means an image with sharp edges and flat color — a screenshot, a diagram, a scan of a document, artwork with text — or an image you intend to edit and re-save repeatedly, or one that needs real transparency. For an ordinary camera photograph, PNG is the wrong answer: the file will often be several times the size of a high-quality JPG for no visible gain, because lossless compression has to preserve every speck of sensor noise faithfully.
What converting actually costs
The file gets bigger, not smaller. This surprises people every time. HEIC's whole advantage is efficiency, so converting to a less efficient format spends that advantage. A JPG made from a HEIC is commonly one and a half to two times the original's size. Nothing has gone wrong; you traded bytes for compatibility, which was the point.
You spend one lossy generation. JPG is lossy, and a HEIC-to-JPG conversion is a re-encode, so a small amount of detail is discarded. At a high quality setting this is invisible in a photograph. What you should avoid is looping — converting, editing, re-saving, converting again — because each lossy pass compounds the last.
Ten-bit and HDR captures get flattened. JPG holds eight bits per channel and standard dynamic range, so wider-gamut captures are mapped down. For most photos this is imperceptible; for a deliberately graded HDR shot it is a real loss, and the HEIC original is the one worth keeping.
Extra images in the container can be silently dropped. A burst or a Live Photo export can hold several images in one HEIC. A conversion that only reads the first one throws the rest away without telling you. Good converters surface all of them.
Metadata is stripped. Re-encoding through a canvas produces a file containing pixels and nothing else — no GPS coordinates, no device model, no capture timestamp. For a photo you are about to publish, losing the location data is a feature rather than a cost, and it is worth understanding on purpose rather than by accident. Note the capture date first if you need it.
Converting back gains you nothing. Turning a JPG back into HEIC does not recover the detail the JPG discarded. You get a smaller file containing a degraded image, in a format your recipient still cannot open. The original HEIC is the archive; the JPG is the copy you send.
A workflow that avoids the problem
The habit that works is simple: shoot and store in HEIC, convert only what you send. Your library stays compact, and the handful of photos that need to be portable get made portable on demand. Keep the HEIC as the master copy — it is the higher-fidelity file, and it costs less space to keep.
If you would rather not think about it at all, iOS offers two switches. Under Settings, Camera, Formats, choosing Most Compatible makes the camera shoot JPG directly; you give up roughly half your storage efficiency along with the depth and wide-color advantages, which is a steep price for avoiding an occasional conversion. Separately, under Settings, Photos, the Transfer to Mac or PC option set to Automatic converts photos to compatible formats as they leave the phone over a cable, while Keep Originals sends the HEIC untouched.
Neither switch helps when the photo is already on your computer and the upload form is already refusing it, which is the situation most people are actually in. That is a two-minute conversion, and there is no good reason for the file to make a round trip to somebody else's server to accomplish it.