Open iPhone HEIC Photos on Windows
Switch the iPhone's camera to Most Compatible and it shoots JPG from the start, or drop existing HEICs into the converter here: libheif, a real HEVC decoder compiled to WebAssembly, unpacks them in your browser and the browser's own JPEG encoder writes the copies. Nothing is uploaded.
以下の解説は英語のみでご覧いただけます。
Open iPhone HEIC Photos on Windows explained
Since iOS 11 shipped in 2017, every iPhone has saved photos by default as HEIC — a container defined by the HEIF standard, ISO/IEC 23008-12, holding images compressed with HEVC, the same codec family as 4K video. The point is space: a HEIC photo is roughly half the size of the equivalent JPEG at the same quality, which roughly doubles what fits on the phone. The cost arrives later, on whatever machine the photo lands on next.
That cost is compatibility, and it is uneven. Apple licenses HEVC for its own platforms, so Safari, iPhones, iPads and Macs open HEIC without a thought. Chrome and Firefox have declined to ship a decoder because HEVC is patent-encumbered, older Windows installs need a paid codec pack from the Microsoft Store, and older Android builds cannot read the format at all. Email a .heic file to the wrong recipient and the reply is a screenshot of an error icon.
This page is the recipe for the moment that reply arrives: when to convert (files that already exist, or anything headed off-Apple), when to change the camera setting instead (a daily need), and what the converter actually does — decode the HEIC to raw pixels with libheif running as WebAssembly in your tab, then let the browser's own JPEG encoder take over. The photos never leave the machine, which matters more here than almost anywhere else, because HEIC files are camera-roll photographs carrying the GPS coordinates of where they were taken.
Everything below happens in the HEIC to JPG converter — open it in a second tab, drop your photos in, and the batch converts one at a time.
If the difference between HEIC, JPEG, PNG and WebP is new territory, the image formats guide covers what each format trades away.
Why your iPhone shoots HEIC at all
HEIC is not an Apple eccentricity; it is the image sibling of a video-codec strategy. The HEIF container (ISO/IEC 23008-12) wraps image data compressed with HEVC (H.265), and HEVC is simply better at compression than the JPEG standard from 1992 — at the same visible quality, roughly half the bytes. On a device where photos are the largest consumer of storage, halving them was worth a compatibility bill Apple could pay, because it licenses HEVC for its whole operating system.
Recent iOS versions soften the edges further: when you share a HEIC to an app that cannot read it, the system converts to JPEG on the way out — iOS 17 and later do this automatically in many apps — and copying photos over a cable can do the same. So plenty of iPhone owners never meet the format, until they move files by folder sync, direct copy or email attachment, all of which pass the bytes through untouched.
Where HEIC breaks, and what to do there
The failure is never about the photo being damaged — the file is fine. It is that the receiving software has no licensed decoder, which splits the world into a short table:
| Where the HEIC lands | What usually happens | The fix |
|---|---|---|
| iPhone, iPad, Mac | Opens natively | None needed — keep the HEIC |
| Chrome or Firefox, any OS | No image: no HEVC decoder by policy | Convert once to JPG |
| Windows without the HEVC extension | Offers a paid codec from the Microsoft Store | Convert, or install the extension |
| Older Android | Usually nothing opens it | Convert before sending |
| Email attachment or upload form | Depends on the recipient's software | Convert — recipients should not need a codec |
The converter: a real decoder, in the browser
Outside Safari no browser will decode HEIC, so the converter brings its own: libheif, the open-source reference implementation, compiled to WebAssembly and loaded only after the browser has refused the file. It is about two megabytes, fetched once per session and cached, and a Safari user never downloads it at all because their browser decodes natively. The decoder turns the file into raw pixels; from there the browser's built-in JPEG encoder writes the output at the quality you choose.
Quality guidance is short and honest. HEIC is already lossy, and JPEG is a second lossy pass — at the default quality of 0.85 the difference is not visible on a photograph; you would need to compare pixel values to find it. Expect the JPG to be larger than the HEIC was, because HEIC is genuinely the more efficient format. If you want no second loss at all, choose PNG and accept a much larger file. Batches convert one photo at a time — up to 100 files, 250 MB in total — and orientation is applied during decode, so portrait photos come out upright rather than on their side.
Convert here, or change the camera setting?
There are two legitimate fixes, and the right one depends on how often the problem occurs:
- Files that already exist — a camera roll of HEICs, a folder synced to a PC — convert here, once, and move on. Nothing to install, nothing to sign up for.
- A daily need — photos constantly going to Windows colleagues or a printer — is fixed at the source: Settings → Camera → Formats → Most Compatible makes the camera shoot JPEG from then on, at roughly double the storage per photo.
- Keep HEIC but convert on the way out: Settings → Photos → Transfer to Mac or PC → Automatic converts photos as they are copied over a cable while the originals stay compact.
When converting is the wrong move
If your audience is entirely Apple — an iCloud family album, an all-Mac studio — converting is pure loss with no benefit, and HEIC is the better format to keep. Compatibility work is only worth doing when there is an incompatible destination, and the honest version of this page says so rather than recommending everyone flatten their library to JPG forever.
Frequently asked questions
Are my iPhone photos uploaded when I convert them here?
No. Decoding and re-encoding happen inside your browser tab, and there is no upload endpoint to send them to. You can verify it: open DevTools, watch the Network panel while a photo converts, and no request carries it. The page's Content-Security-Policy sets connect-src 'self', so the browser itself would refuse any attempt — and HEICs are camera-roll photos with GPS coordinates inside, which is why that matters.
Why can't Chrome or Firefox just open HEIC like Safari does?
HEIC wraps HEVC, and HEVC decoders are patent-licensed rather than free to implement. Apple licenses it for its own platforms, so Safari and macOS decode natively; Chrome and Firefox have chosen not to ship a decoder; Windows offers one as a paid store extension. Nothing is wrong with your files — the format simply is not free to support.
Will converting HEIC to JPG lose quality?
A little, unavoidably — it is a second lossy pass after the camera's first. At quality 0.85 the difference is invisible on a photograph; you would need to diff pixel values to find it. The JPEG will typically be larger than the HEIC was, because HEIC is the more efficient format. PNG avoids the second loss entirely, at a much larger file size.
How do I stop my iPhone taking HEIC photos in the first place?
Settings → Camera → Formats → Most Compatible. The camera then writes JPEG directly, at roughly double the storage per photo. Recent iOS also auto-converts on share in many apps, so the switch mostly pays off when files move by folder sync or attachment.
What happens to Live Photos, bursts and sideways shots?
A Live Photo or burst is several images in one container; the converter takes the first top-level image — the one the camera roll displays — and the video part is not carried into a JPG. Orientation is applied to the pixels during decode, so a portrait shot comes out upright instead of lying on its side.
Does the JPG keep the location and other metadata?
No. Decoding to pixels and re-encoding drops the EXIF block entirely — GPS coordinates, camera model, timestamps and the embedded thumbnail. For sharing, that is usually exactly what you want; the page on removing metadata from images covers that topic, and its trade-offs, in detail.
Which related tools should I use next?
- HEIC to JPGOpen iPhone photos on a machine that refuses to.Open
- Convert ImageJPG, PNG, WebP and AVIF, with transparency handled properly.Open
- Remove EXIF MetadataA real job, step by stepOpen
- Compress Image to 100KBA real job, step by stepOpen
- PNG vs JPG vs WebP vs AVIFPlain-English guideOpen
- Image ToolsCompress, resize and convert images in the browser.Open