Why iPhone photos refuse to open on half your devices
HEIC (High Efficiency Image Container) is Apple's default photo format since iOS 11, built on the HEIF standard. It uses a fundamentally different compression method than JPEG — modern video-codec-derived compression rather than JPEG's older discrete cosine transform approach — which is why it can store the same visual quality in roughly half the file size. That efficiency is the whole point of Apple defaulting to it.
The catch is support. HEIC decoding isn't built into most non-Apple software, browsers, and older systems, so a photo that opens instantly on an iPhone can show up as an unreadable file, a broken thumbnail, or an outright upload rejection everywhere else. JPEG, despite being decades older and less efficient, is decodable by essentially everything — which is exactly why converting to it solves a compatibility problem, not a quality problem.
Browser support for reading HEIC directly
| Browser / platform | Native HEIC decode | Notes |
|---|---|---|
| Chrome, Edge, Brave, Opera (85+) | Yes | Uses the OS-level decoder where available |
| Safari on macOS Big Sur+ | Yes | Apple's own format, full native support |
| Older Chromium versions | No | Update to a current version |
| Firefox (most versions) | Limited/no | May not decode HEIC reliably |
Converting a HEIC photo to JPG
Drop a HEIC / HEIF photo onto the zone.
Choose JPG quality with the slider (50–100%).
Click Convert to JPG — the file is generated locally and downloads instantly.
Choosing a quality setting that doesn't show
Since HEIC compresses more efficiently than JPEG at a given visual quality, converting isn't a lossless swap — you're moving from a more efficient codec to a less efficient one, and the quality slider controls how much of that efficiency gap shows up as visible loss versus file size. At 90% and above, the difference from the original is generally not visible to the eye even though the file is technically re-encoded; the file size increase over the original HEIC is simply the cost of switching to a universally compatible format.
Lower quality settings (50–70%) make sense when file size matters more than fidelity — attaching several photos to an email with a strict size cap, for instance — but expect visible softening or blocking artifacts in areas of fine detail at those levels.
What doesn't survive the conversion
Converting to JPG rasterizes and re-encodes the pixel data, but it's worth knowing that HEIC files can also carry things a JPG doesn't handle the same way — some HEIC photos captured with iPhone features like Live Photos or Portrait mode's depth data are more than a single flat image internally. Converting to JPG produces a standard flat image; format-specific extras like a Live Photo's motion component aren't part of what a JPG can represent.
Common mistakes
Assuming a 'can't decode HEIC' error means the photo file is corrupted — it almost always means the browser lacks native HEIC support, not that anything is wrong with the image.
Converting at a low quality setting for a photo you plan to print or zoom into — save higher quality (90+) for anything beyond casual screen sharing.
Deleting the original HEIC immediately after converting — the original stays untouched on disk during conversion, so it's safe to keep as your highest-fidelity source if you need to reconvert later.
Expecting to batch-convert dozens of HEIC files in one pass — this tool processes one file at a time by design; for many files, run it repeatedly per photo.
Real use cases
Converting an iPhone photo before uploading it to a website or form that rejects HEIC files.
Preparing photos to share with someone on Windows or Android whose device can't open HEIC.
Converting screenshots or photos before attaching them to a work email system with limited format support.
Getting a photo into a universally readable format before running it through Image Compressor for further size reduction.
Frequently asked questions
Q: Why does my browser say it can't decode HEIC?
A: HEIC decoding requires Chromium 85+ (Chrome, Edge, Brave, Opera) or Safari on macOS Big Sur or later. If your browser lacks native support, update to a current Chromium browser or use Safari on a recent macOS.
Q: Is there quality loss when converting HEIC to JPG?
A: Yes — JPG is lossy, so some re-encoding loss is unavoidable. Use a quality of 90% or higher for results that are visually indistinguishable from the original. Your original HEIC file stays untouched on disk regardless.
Q: Will my photo be uploaded anywhere?
A: No. Conversion happens entirely in your browser using the Canvas API, with zero outbound upload requests.
Q: Can I batch convert multiple HEIC files at once?
A: This tool handles one file at a time for simplicity. For several files, run it repeatedly, or use the Image Converter for other format options.
Q: Will a Live Photo still animate after converting to JPG?
A: No — a Live Photo is more than a single flat image internally, and converting to JPG produces a standard static image. The motion component isn't something a JPG format can carry.
Q: If HEIC is more efficient, why convert at all instead of keeping everyone's software HEIC-compatible?
A: In an ideal world you wouldn't need to, but plenty of active websites, forms, and older software still don't support HEIC — converting to JPG is the practical fix for compatibility today, even though it costs some of HEIC's efficiency advantage.
Convert your photo now
Get a universally compatible copy with the HEIC to JPG tool. Need a different target format? Try the Image Converter. Converting from WebP instead? See WebP to JPG, or shrink your converted photo further with Image Compressor.
