9314JIUsi
Checkpoint Converter

HEIC checks in, JPG checks out

iPhone photos that nothing else will open? Send them through this checkpoint — they come out as JPGs every device since 1992 can read.

📦 Drop HEIC photos here
Click to browse, or paste a screenshot with Ctrl/⌘+V · 30MB per file · up to 20

Accepts .heic / .heif / .hif · fake extensions get caught by byte-level inspection

Output
Quality 90
Engine: standby
Fetching the built-in conversion engine (~1.5MB, first use only, then cached by your browser)…

Photos are decoded and encoded inside this browser on this device only — nothing is uploaded, there's no account, and results vanish when you close the tab. Only your quality and format preferences live in this browser's localStorage. To wipe everything, use "Erase my data" in the footer.

Facts and limits

InputHEIC / HEIF (.heic / .heif / .hif). Files are verified by header bytes — a PNG renamed to .heic gets stopped at the gate.
OutputJPG (quality 1–100, default 90) or lossless PNG; filename = original + -converted
Key settingsQuality slider defaults to 90; format defaults to JPG; both pre-settable via ?quality=90&format=jpg in the URL
ProcessingEntirely in your browser: Safari uses the system's native HEIC decoder; Chrome/Firefox fetch a ~1.5MB self-hosted engine (libheif WASM) on first use, cached and reusable offline. No uploads; only preferences in localStorage
Limits30MB per file; 20 files per batch
Known edgesBurst sequences (several photos in one container) use the first frame only; 10-bit HEIC becomes 8-bit JPG (invisible in normal use); first conversion on Chrome/Firefox waits for the engine download; speed depends on your hardware; corrupted files fail with a clear reason instead of a garbled output

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

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.

FAQ

Does HEIC to JPG upload my photos?
No. Decoding and encoding happen entirely inside this device's browser: Safari uses the system's built-in HEIC decoder, Chrome and Firefox download a ~1.5MB conversion engine on first use (cached by the browser, works offline afterwards) — the photos themselves never leave your device.
Why won't HEIC files open on Windows or Android?
iPhones have stored photos as HEIC by default since iOS 11 to save space, but HEIC's compression core is HEVC — a licensed codec. Safari ships a decoder; Chrome and Firefox do not. Converting to JPG fixes it everywhere: JPG has been the universal format since 1992.
How many photos can I convert at once?
Up to 20 files per batch, 30MB each. Download individually or grab everything in one ZIP (stored without re-compression for the fastest packaging). Burst sequences (multiple photos inside one HEIC container) take the first frame only.
Will the orientation come out wrong?
No. The two orientation fields inside HEIC (irot and imir) are applied to the pixels during decoding, so the output JPG needs no orientation flag — portrait stays portrait. 10-bit HEIC files come out as 8-bit JPG; you won't see the difference in normal use.
What's the difference between Safari and Chrome here?
Safari 17+ calls the macOS/iOS system HEIC decoder directly — nothing to download, fastest. Chrome and Firefox fetch a ~1.5MB engine on first conversion (cached for reuse afterwards); speed then depends on your hardware. Output quality is identical on both paths.
Where are my settings stored?
Only the quality slider value and output format live in this device's browser localStorage (key y9314:heic-to-jpg-en:v1). Photos and conversion results are never written to disk. In private browsing the preferences vanish when the window closes — normal behavior. The footer's "Erase my data" wipes everything in one click.

Related tools