Why your iPhone photos won't open on Windows

You emailed yourself a photo and the computer shrugged. Nothing is damaged. This is a nine-year-old standoff between a better format and everything that came before it.

Updated 28 August 2026 · 10 min read

You emailed yourself a photo, or plugged the phone into a laptop and dragged a folder across, and what arrived is a file ending in .HEIC that nothing wants to open. Windows offers a blank preview or an apology. A website says the file type is not supported. An older program does not list it at all. The photo looked perfectly fine on the phone thirty seconds ago.

Nothing has gone wrong with the file. This is a format mismatch, and it is entirely fixable — usually in under a minute, and permanently if you want it to be. What follows is why it happens, the three genuinely different ways out, and the one surprise that catches people afterwards.

What the error actually means

Every image file is a container with a specific internal arrangement, and every program that opens images knows how to read a certain set of those arrangements. When a program says it cannot open a file, it is almost always saying one of two things: this file is damaged, or this file is intact and I do not speak this language. HEIC failures are nearly always the second.

Your photo has not lost data in transit. The email did not mangle it. The cable did not corrupt it. The bytes on your computer are, in all likelihood, byte-for-byte the ones that were on the phone. The receiving software simply has no decoder for the format and stops at the front door.

This distinction matters because it tells you what to try. A damaged file needs recovery, and recovery is usually a losing battle. A file in an unsupported format needs a translator, and translation is routine. You are in the easy case.

Why Apple changed formats, and why everyone else did not follow

With iOS 11 in 2017, Apple switched the iPhone camera's default output from JPG to HEIC. The reason was straightforward: HEIC stores a comparable-looking photograph in substantially less space — commonly 30–50% less. On a phone whose storage cannot be expanded and whose photo library grows every weekend, taking a third off every picture is a large, permanent win. Apple took it.

HEIC is not really a single thing. It is a container built on the HEIF standard — a wrapper that can hold an image, several images, and a collection of extra data describing them. The picture inside is compressed using HEVC, the same compression family used for high-efficiency video. That last detail is where the trouble starts.

HEVC carries patent-licensing obligations, spread across a number of rights holders. The widely understood explanation for HEIC's slow spread outside Apple's ecosystem is exactly this: shipping a decoder is not simply an engineering decision when there are licensing terms attached to it. Companies that give software away, browsers included, weighed that cost against the benefit and largely waited. This is not villainy on anyone's part. Apple had a device-wide storage problem worth paying to solve and controlled the whole chain from camera to display. A photo-viewing program written in 2012, or a web form maintained by nobody in particular, had neither the incentive nor the budget.

The result is a format that is genuinely excellent and genuinely awkward. Support has improved — Microsoft has offered codec components through its store, and which pieces you need, and whether they carry a charge, has varied between Windows versions — but "improved" is not "universal". Any given website, printing kiosk, older desktop application or workplace upload form may still refuse it, and you have no way to fix their end. If you want the underlying comparison in more depth, HEIC versus JPG covers what each format is good at.

The three routes out

There are exactly three things you can do, and they solve different problems. Most people need the first one immediately and one of the other two afterwards.

Convert the files you already have. This is the retrospective fix. It works on the folder sitting on your computer right now, including photos taken years ago, and it is the only route that helps with files already off the phone. It changes nothing about future photos.

Make the phone hand over JPG when it transfers. iOS has a setting governing what happens when photos are copied to a computer: it can pass the original files across untouched, or convert them automatically on the way out. Set to convert, the phone keeps its efficient HEIC library and your computer receives ordinary JPGs. This is in the photos settings, near the bottom, under the options about transferring to a Mac or PC — Apple moves and renames these between versions, so look for the wording about transferring rather than a specific menu path. It applies to transfers to a computer; photos leaving by other routes, such as messaging apps or direct uploads, follow their own rules.

Make the camera capture in the compatible format from now on. In the camera settings, under the formats option, the phone can be told to record photos in the widely compatible format instead of the high-efficiency one. From that moment every new photo is a JPG everywhere it goes — no conversion step, no transfer setting, no surprises at a print shop. The cost is real and lands on the phone: those photos take roughly twice the storage they otherwise would, for the rest of the phone's life.

The honest recommendation for most people is the middle one. It costs nothing, it is silent, and it leaves the phone's own library efficient. Switch the camera itself only if you are repeatedly caught out by photos going somewhere unexpected — a client, a printer, a form — and the storage is affordable to you. Neither setting is retroactive: the photos already taken stay as they are, which is why almost everybody needs to convert a batch at least once regardless.

Why the converted file is bigger

Here is the part that reliably surprises people. You convert a 1.4 MB HEIC to JPG and get back a file of 2.5 MB. It looks like something has gone wrong, or like the converter added something. It has not.

The two formats are just differently efficient at describing the same picture. HEIC's compression is more than a decade newer than JPEG's and does considerably more work per pixel: better prediction of what comes next, more flexible block sizes, smarter handling of areas that are nearly but not quite uniform. JPEG, designed in an era of far slower machines, uses a simpler scheme. Give both the same photograph and ask for the same visual result, and JPEG needs roughly twice the bytes to get there. That is the whole explanation. The efficiency you enjoyed on the phone is exactly what you are handing back in exchange for compatibility.

So a converted file being close to double the original is the normal outcome, not a fault. It is worth being clear that the picture is not better for being bigger — it is the same picture, described less economically. The general question of what makes a photo file large is covered in why image files get so large.

If the resulting size is a genuine problem — an upload cap, an email limit, a form with a stated maximum — the fix is a separate step, not a different conversion. Reduce the quality setting a little, reduce the pixel dimensions, or both, and a photo that arrived at 2.5 MB will sit comfortably under a limit with no visible difference on a screen. If there is a specific number you must land under, compressing to an exact file size explains how to hit it rather than guess at it.

What conversion actually discards

A HEIC file frequently holds more than one photograph's worth of information. JPG holds exactly one flat image and nothing else, so anything extra in the container has nowhere to go. This is worth understanding in general terms, though the specifics depend on the phone, the shooting mode and the version of iOS involved.

Motion becomes a still. A Live Photo pairs a still image with a short clip of the moments around it. The clip is not inside the still file, and JPG could not carry it if it were. What you get after conversion is a single frame — the photo, without the movement. The motion is not destroyed, it simply stays behind on the phone.

Auxiliary image data is dropped. Depth information from portrait-mode shots, and the extra data some phones store to reconstruct a brighter high-dynamic-range rendering on displays that can show it, both live alongside the main image in the container. A JPG has no place to keep them. The visible consequence is usually modest — the converted photo may look slightly flatter on an HDR-capable screen than the original did — but the ability to re-edit the background blur afterwards is gone.

Edits are baked in. Adjustments made on the phone are typically stored so the original can be recovered later. Once converted, you have the edited result as a finished picture. It looks the way it looked, but there is no longer a route back to the unedited version through the converted file.

None of this is an argument against converting. For the overwhelming majority of uses — sending a photo to someone, attaching it to a form, putting it on a website, printing it — a flat image is all that was ever going to be used. It is an argument for keeping the originals. Convert copies, leave the HEICs in place on the phone or in a backup, and nothing is truly lost.

Common questions

Is my photo damaged? Almost certainly not. If the phone still displays it and the file arrived at a sensible size, the bytes are intact and only the reader is missing. A genuinely corrupted file usually fails on the phone too, or arrives implausibly small.

Can I just rename the file to .jpg? No. The extension tells the operating system which program to hand the file to; it does not change the contents. Renaming produces a file that claims to be a JPG, is not one, and fails in a less informative way. The image has to be re-encoded.

Why did the file get bigger after converting? Because JPG is a less efficient format, and needs roughly twice the bytes to describe the same picture at the same visual quality. It is the expected result of trading efficiency for compatibility, not a sign that anything went wrong.

Will converting make the photo look worse? At a high quality setting, not in any way you will notice on a screen. JPG is lossy, so the re-encode discards a small amount of detail, but at around 90% quality that loss is invisible in a normal photograph. What you should avoid is converting a file that has already been converted several times.

Does the fix apply to photos I already took? Only the conversion route does. Changing the transfer setting affects future transfers, and changing the camera format affects future photos. Neither reaches backwards into the library, so a one-off batch conversion is usually needed as well.

Should I just shoot in the compatible format permanently? If you frequently hand photos to Windows machines, print shops or web forms, and phone storage is not tight, it is a reasonable trade. If storage is tight, keep the efficient format and convert copies as needed — you keep twice as many photos on the phone that way.