Where the HEIC wall actually is
An iPhone photo lands in your chat or your USB stick as IMG_2043.HEIC. Double-click on Windows or open it on Android: gray icon, "format not supported." Since iOS 11, iPhones store photos as HEIC — same quality, roughly half the size of JPG — because its compression core, HEVC, is efficient. But HEVC is a licensed codec, and only Safari ships a decoder among the major browsers. Chrome and Firefox still don't, years later.
The fix is conversion, and the minefield is choosing where. Phone settings ("Settings → Camera → Formats → Most Compatible") only affect future photos; the existing few thousand stay HEIC. Online converter sites mean uploading every photo — and your family album — to somebody else's server.
This page moves the converter into your browser: photos never leave the device. Safari rides the built-in system decoder with zero downloads; other browsers pull a 1.5MB self-hosted engine (libheif compiled to WebAssembly, cached after first use — works offline afterwards).
How it works: three steps
- Check in: drag, click to browse, or paste with Ctrl/⌘+V. Up to 20 files per batch, 30MB each.
- Inspection: every file passes a byte-level header check that confirms a real HEIC/HEIF container. A PNG wearing a .heic costume gets rejected on the spot with the reason stated — no garbage decode, no purple-noise screenshot.
- Release: pick JPG (quality slider, default 90) or PNG; download one by one or grab a single ZIP (stored uncompressed, fastest packaging). Output files are named "original-converted.jpg" — your originals are never touched.
Orientation is handled where it should be: the two metadata fields inside HEIC (irot/imir) are applied to the pixels during decoding, so what comes out is already upright — no sideways portraits. A burst sequence packs a dozen shots into one file; this converter takes the first frame, which is normally the shot you saw when you pressed the button.
Two engines, one lane
Safari 17+ users get the fast track: macOS and iOS ship a native HEIC decoder and this page calls it directly — zero download, best speed. Chrome and Firefox take the backup lane: a self-hosted libheif build (WebAssembly, ~1.5MB) loads only when the first conversion actually happens, with a progress bar; it initializes once and is reused for the rest of the session.
Honest edges: both lanes produce identical-quality JPG, but 10-bit HEIC files (some ProRAW derivatives and third-party camera outputs) come out as 8-bit JPG — indistinguishable in everyday use; go PNG if you want lossless. Speed scales with your hardware; a five-year-old laptop will breathe hard on twenty 48-megapixel files. That's physics, not a bug.