HEIC vs JPG: Why Your iPhone Photos Won't Open Everywhere

If you’ve ever tried to upload an iPhone photo to a website or send it to a Windows or Android user and hit a wall, the culprit is almost always the file format: .heic, not the .jpg most of the internet expects.

What HEIC actually is

HEIC (High Efficiency Image Container) is Apple’s default photo format since iOS 11. It’s built on the HEIF container format and typically uses HEVC (H.265) compression — the same codec family used for efficient video — applied to still images. The payoff is real: Apple states HEIC photos can be roughly half the file size of an equivalent-quality JPG, which matters a lot when you’re storing thousands of photos on a phone with fixed storage.

HEIC also supports some features JPG doesn’t, like storing multiple images in one file (useful for Live Photos and burst shots) and better handling of transparency and higher bit-depth colour.

HEIC vs JPG at a glance

	HEIC	JPG
Typical file size	~50% smaller at similar quality	Baseline
Colour depth	10-bit and higher	8-bit
Transparency	Yes	No
Multiple images per file	Yes	No
Universal support	No	Yes, effectively everywhere
Age	2015, mainstream 2017	1992

That last row explains most of the friction. JPG’s compatibility isn’t a technical achievement — it’s a thirty-year head start.

Why it doesn’t “just work” everywhere

JPG has been a universal standard since the 1990s — every browser, OS, and image tool supports it natively. HEIF/HEIC is much newer, and support depends on licensing and platform decisions outside Apple’s control: many Android devices, older software, and plenty of websites simply never added a HEIC decoder, because JPG or WebP already covers their needs and HEIC brings patent-licensing complexity that the older formats don’t.

The result: a photo that opens perfectly on the iPhone that took it can show up as a blank icon or an “unsupported file” error the moment it reaches a website, a Windows Photos app without the HEIF extension, or an older Android phone.

The part that confuses everyone

Your iPhone often converts HEIC to JPG automatically — which is exactly why the problem feels so random.

Share a photo through Messages, Mail, or most share-sheet targets and iOS quietly hands over a JPG. AirDrop to a Mac and you get the original HEIC. Plug into a Windows PC and what you get depends on a setting buried in Settings → Photos → Transfer to Mac or PC: “Automatic” converts to JPG, “Keep Originals” hands over raw HEIC files.

So the same photo, sent two different ways, arrives in two different formats. People reasonably conclude the file is corrupted or their phone is broken, when the real explanation is that one path ran a conversion and the other didn’t.

When you actually need to convert

If you’re only ever viewing and sharing photos between Apple devices, you may never notice the format at all. Conversion becomes necessary when:

• Uploading to a website or web app that doesn’t decode HEIC (common with older CMS platforms and some social tools).
• Sending to someone on Windows or Android without a HEIC viewer installed.
• Feeding the image into software or a pipeline that only accepts JPG/PNG.
• Archiving photos somewhere you want readable in twenty years without depending on a licensed decoder.

Stop it at the source

If you’d rather not convert repeatedly, change what the camera writes in the first place: Settings → Camera → Formats → Most Compatible. Your iPhone then shoots JPG directly.

The trade is real — you lose roughly half your storage efficiency and the 10-bit colour depth, and on a 128 GB phone full of photos that adds up. Worth it if you’re constantly moving photos to non-Apple systems; not worth it if the friction is occasional. “High Efficiency” stays the better default for most people.

Does converting lose quality?

Slightly, and unavoidably. Both HEIC and JPG are lossy, so decoding a HEIC and re-encoding it as JPG means a second generation of lossy compression. In practice, at a high JPG quality setting the difference is invisible for normal viewing — you’d need to pixel-peep gradients and flat colour areas to spot it.

Two caveats worth knowing. First, converting to JPG drops HEIC’s 10-bit colour to 8-bit, which occasionally shows as faint banding in smooth skies or studio backdrops. Second, don’t convert the same file repeatedly — each round trip compounds the loss. Keep the HEIC original and convert from it each time you need a JPG, rather than converting a converted copy.

If you need a truly lossless intermediate — for editing rather than sharing — convert to PNG instead. The file will be much larger, but the re-encode adds no further loss.

Converting HEIC files

HEIC to JPG and HEIC to PNG decode the format directly in your browser, via a WebAssembly build of the HEIF decoder, and re-encode to the format you need. Nothing is uploaded, which matters more than usual here — these are typically personal photos, and the alternative is handing your camera roll to a server you know nothing about.

If you’re converting a batch and want to keep file sizes down afterward, pair it with Image Compressor — useful for clawing back some of the size advantage you gave up by leaving HEIC. And if you’re going the other direction, cleaning up a plain JPG for wider compatibility or for a transparent background, JPG to PNG covers that swap.