HEIC vs JPG on iPhone: What Changes When You Convert, and When You Should

If you've ever emailed a photo from an iPhone and had the other person reply "I can't open this", you've met HEIC. It's been the default iPhone photo format since iOS 11 in 2017. It's a perfectly good format with real advantages, but it still trips up Windows PCs, older software, web upload forms and plenty of websites. This guide explains what HEIC actually is, why Apple picked it, what you lose and keep when you convert to JPG, and how to stop the problem at the source.

What HEIC actually is

HEIC is a file that follows the HEIF standard (High Efficiency Image File Format) and stores its images using HEVC compression, the same codec family that's used for H.265 video. In practice, "HEIC" and "HEIF" get used interchangeably. The important part is the codec. HEVC came out more than two decades after the JPEG standard, and it uses better prediction and larger, more flexible blocks. That lets it keep similar visual quality at a smaller size.

HEIF is also a container, not just a picture. A single HEIC file can hold several images and extra layers: a depth map for Portrait mode, an HDR gain map, a thumbnail, or the still frame of a Live Photo. JPEG was designed to hold one image, plus metadata bolted on afterwards.

Why Apple switched

When Apple introduced HEIF support, it said the format could make photos up to half the size of JPEG at similar quality. "Up to" is doing a lot of work in that sentence, and the actual saving varies by scene, but the direction is right. On a phone with a fixed amount of storage and an iCloud plan billed by the gigabyte, smaller photos are a direct saving.

Here's what that means over time. These are illustrative numbers, not measurements of your phone. Suppose an average JPEG from your camera is 3 MB and the equivalent HEIC is 1.5 MB. Then:

With a 50 GB iCloud tier, that's the difference between 10,000 photos fitting comfortably and not fitting at all. So keeping HEIC on the phone is usually the right call. The friction only shows up when a photo leaves the Apple ecosystem.

Where HEIC causes trouble

• Windows 10 and 11 can show HEIC files, but only after installing the HEIF Image Extensions and HEVC Video Extensions from the Microsoft Store. The HEVC one has been a paid add-on in many regions, so lots of PCs simply don't have it.
• In browsers, only Safari can display HEIC on recent Apple systems. Chrome, Edge and Firefox can't decode it in an image tag. That's why many websites reject HEIC uploads outright.
• Upload forms on job portals, government sites and visa applications often accept only JPG, PNG or PDF, with strict size caps. A HEIC file fails on format before size is even checked.
• Photo kiosks, older versions of editing software and many content management systems expect JPEG.

iPhones do try to hide this. When you share to many apps, iOS converts to JPEG automatically. Email and messaging apps often get a JPEG too. The problem tends to show up when you copy files over a cable, export from iCloud on the web, or AirDrop to a Mac and then move the files on to something else.

What you keep and lose when converting to JPG

Converting HEIC to JPG decodes the HEVC image to pixels and encodes those pixels again as JPEG. That second encode is lossy. You don't lose resolution, so a 4032 × 3024 photo stays 4032 × 3024, but you do add a second round of compression artefacts. At a quality setting around 85 to 92 these are very hard to spot. At 60 they start to show in skies and skin.

The JPEG will also usually be bigger than the HEIC it came from, often noticeably so. That surprises people, but it's expected. You're moving from a more efficient codec to a less efficient one. If a site has a 2 MB upload limit and your HEIC is 1.8 MB, the JPG might not fit. Lower the quality a little or resize the photo.

The colour depth line matters if you shoot HDR. A 10-bit HEIC can store more gradations of brightness than an 8-bit JPEG. On a standard screen you won't see the difference. On an HDR-capable display, the converted JPG will look flatter than the original.

Converting in the browser

The HEIC Converter decodes HEIC with a WebAssembly build of an open-source HEIF decoder, then writes JPG, PNG or WebP. The WebAssembly code downloads the first time you convert and then runs on your device, so the photos themselves aren't sent anywhere. That matters for personal photos, which are exactly the kind of file you shouldn't be uploading to random conversion sites.

1. Drop one or more HEIC files on the converter.
2. Choose JPG for maximum compatibility, PNG only if you need lossless output and don't mind much bigger files, or WebP for a smaller file that modern browsers accept.
3. For JPG, a quality between 85 and 92 is a good default. Use lower values only to hit a strict upload limit.
4. Download the result, then check its size against whatever limit you're working with.

Stopping the problem at the source

If you're constantly converting, you can change how the iPhone saves or exports photos instead. There are two settings, and they do different things.

• Settings → Camera → Formats → Most Compatible. The camera shoots JPEG instead of HEIC from now on. Every photo will take more space, and some features that depend on HEIF, such as certain high-resolution or HDR capture modes, may be unavailable.
• Settings → Photos → Transfer to Mac or PC → Automatic. Photos stay HEIC on the phone but are converted to JPEG when copied to a computer over a cable. This is usually the better choice: you keep the storage saving and only pay the compatibility cost when files leave the phone.

For most people, the second option plus an occasional browser conversion is the sweet spot. Switching the camera to Most Compatible makes sense only if nearly every photo you take ends up on a Windows machine or a website.

Limitations and honest caveats

• Metadata may not survive. Browser-based conversion paints decoded pixels to a canvas and encodes from there, and that path doesn't carry EXIF data across. Capture date, camera model and GPS location may be missing in the output. Removing location can be a plus when sharing, but keep the originals if you sort photos by date.
• Extra layers are discarded. Depth maps, Live Photo motion and HDR gain maps aren't kept. You get a flat still image.
• Large batches are slow on phones. Decoding HEVC is heavy work. Converting a few hundred photos on a mid-range phone browser can take a while and use a lot of memory. A desktop browser handles big batches better.
• It's a second lossy step. Always keep the original HEIC. If you need a different size or quality later, convert from the original again rather than from the JPG.
• Some cameras and Android phones write HEIF variants (image sequences, unusual bit depths) that a decoder may not handle. If a file fails, check whether it opens in the Photos app on a Mac or iPhone first.

Quick answers

Is HEIC better quality than JPG? At the same file size, usually yes. At the same visual quality, it's usually smaller. Will converting ruin my photo? No, not at sensible quality settings, but don't convert the same image back and forth repeatedly. Should I delete the HEIC originals after converting? Not unless you're sure you don't need the extra data. Storage is cheaper than reshooting a moment.