Why HEIC exists — and why it’s a hassle
Apple switched its cameras to HEIC (High Efficiency Image Container) with iOS 11 because it stores photos at roughly half the size of JPEG at equivalent quality, using the modern HEVC codec. The catch: that efficiency comes at the cost of compatibility. Plenty of Windows apps, older Android devices, web upload forms, and image tools still can’t open .heic files — which is exactly why you end up needing to convert one. JPG and PNG remain the universally accepted formats.
JPG or PNG?
| Choose | When |
|---|---|
| JPG | Photographs — small files, adjustable quality, universal support |
| PNG | Screenshots, graphics, transparency, or zero-loss needs |
For the typical “I just need this iPhone photo to open on Windows” case, JPG at 85–92% quality is ideal. Reserve PNG for images with sharp text/edges or where you can’t tolerate any compression.
Quality setting cheat sheet
- 95%+ — near-lossless; for print or portfolio masters.
- 85–92% — the sweet spot; visually indistinguishable from the original at a fraction of the size.
- 70–80% — when file size matters more than fidelity (email, thumbnails).
A note that surprises people: the converted JPG can be larger than the original HEIC, because HEIC compresses more efficiently than JPEG. Lower the quality setting if you need a smaller output.
Private and batch-friendly
Conversion happens entirely in your browser — HEIC is decoded and re-encoded locally, so your photos never upload, which matters for personal and family pictures. You can drop in many files at once and convert them in a batch. Decoding HEVC in JavaScript is computationally heavy, so large files may take a few seconds each; that’s the cost of doing it privately on-device rather than on a server.