Why Can't I Open HEIC Files on My PC — and Six Ways to Fix It

The symptom, and the short answer

You copied photos off an iPhone — over USB, out of a cloud library, from a messaging app — and File Explorer now shows blank rectangles where thumbnails should be, while double-clicking a file does nothing or complains about an app that is not installed. The photos are not damaged. The byte count is normal, the pixel dimensions are what the camera produced, and re-copying them will change nothing.

What is missing is a decoder: the component that turns the compressed data inside the file back into pixels an application can display. That distinction is the whole story, because it tells you which fixes can possibly work. There is no file to repair. Either something on the PC learns to decode the format, or you hand the file to something that already understands it and get back a format every machine does.

• Fastest and most universal: convert the file to JPG or PNG. No install, no admin rights, and no upload if you use an in-browser converter.
• Most permanent fix on the PC: install a decoder so HEIC opens natively, thumbnails included.
• Best fix at the source: stop the phone writing HEIC, or make copies arrive already converted.

If you only need this done today

Convert one file to JPG and open that. When it opens — and it will — convert the rest as a batch. If you would rather never deal with this again, also change the camera format on the phone so future photos are written as something else, and the transfer setting so copies arriving on the PC are converted on the way in.

What a HEIC file actually is

HEIC stands for High Efficiency Image Container. Inside, the file is an instance of HEIF — High Efficiency Image File Format, standardised as ISO/IEC 23008-12 — which comes from the ISO base media file format family: the same structural family MP4 video files belong to. The extension distinguishes contents: HEIF is the container generally, HEIC is that container holding a still photo, which is what you are looking at.

The container is only half the story. The picture itself is compressed with HEVC, the codec also known as H.265, using the parts of it that encode a single frame independently. That is where the compression advantage comes from: HEVC's block-based prediction and filtering are much better at discarding detail the eye does not miss than the decades-old transform JPEG relies on.

Because container and codec are separate pieces, opening the file needs both to be handled, which is exactly why behaviour varies so much between machines and apps. A program that plays MP4 video does not necessarily ship an HEVC image path; a program that decodes HEVC for playback does not necessarily handle the HEIF item structure around it; and software that never needed either shows you an error. Worth knowing too: HEIF is item-based rather than one-picture-per-file, so it can hold several images plus auxiliary and derived items and descriptive data in a single file. Most of your HEICs are one still photo, but the container is not restricted to that.

Why the format exists instead of JPEG

Encode the same scene as JPEG and as HEIC at comparable visual quality and the HEIC is the smaller file. That is the entire pitch, and it is a real one — the gain shows up precisely in the detailed areas where JPEG produces ringing and blocky edges.

On a phone that saving compounds. Photos are the biggest thing most people store, the camera fires constantly, and space freed per shot goes into more shots rather than an empty settings screen. The format also carries things JPEG cannot: several images in one file, auxiliary images alongside the main one, and structure for edits and derived versions instead of destructive re-saving.

The cost is compatibility, and you are paying it now. JPEG is decoded by effectively everything, because it has been the universal interchange format since the nineties. HEIC is decoded only by software that ships a decoder, which is a shorter and far less predictable list. Apple devices read it without complaint — which is exactly why the format never looks like a problem until the photos leave the Apple ecosystem.

Why your particular PC can't open them

The honest answer: HEIC support is not universally present out of the box across every Windows version and edition, and it is not consistent between machines that nominally run the same thing. Decoding HEIF and HEVC is not a service the operating system guarantees to every application. It is a component that has to be there, and whether it is there on your machine depends on which build you are on, which updates have been applied, and what other software has installed a decoder of its own.

That is why the same file opens on a colleague's laptop and not yours, even when both look identical in the About screen. An OEM image — the software configuration a manufacturer ships — can include media components a clean install from generic media does not, and the reverse happens too. Some machines pick up a decoder incidentally from a photo suite, video editor or media app that bundles one for its own use.

So expect inconsistency with a recognizable shape: Photos errors while a third-party viewer opens the file; Explorer thumbnails stay blank in a folder where full-size viewing works; some files in one batch open and others do not, which usually means the batch is a mix of formats rather than a mix of good and bad files. That last one causes the most confusion — a camera setting that changed at some point, or photos imported over years from different devices.

Installing a codec is one route, and for people who receive HEIC files constantly it is the right one: once a decoder is in place the format opens natively across the machine. But it adds a system component, availability varies by edition and build, it may need administrator rights, and it does not automatically reach every application. If you have a folder you need today, converting is faster, and the other routes below leave your system alone.

Where the HEIC files came from

Apple made HEIC the default camera format on iPhone several generations ago, and it has been the source of this problem ever since. iPhones and iPads do the same, Macs read the files happily, and if your photos came from an iPhone camera they are HEIC unless somebody changed a setting. Two settings on the phone decide what your PC receives, and they are independent of each other.

The camera format setting chooses what the shutter writes: either the high-efficiency format, which stores more photos per gigabyte, or the most compatible format, which every machine opens without help. Switch to the compatible option and new photos are universally readable the moment they are taken. It does nothing to the photos you already have — those keep the format they were shot in.

The transfer setting governs what happens to copies leaving the device. Its purpose is to decide whether exports keep the original format or are converted to a broadly readable format on the way out. Converted copies mean the PC receives something readable while the efficient original stays on the phone; original-format copies mean you get an exact duplicate of what the camera wrote — including the format your PC cannot read.

Two limits. The transfer setting applies to the transfer path it describes: a photo you email, send through a messaging app, or sync through a cloud service follows that app's rules instead, and plenty of apps re-encode without telling you. And if your library lives in the cloud rather than on the device, the service decides what you download — it can arrive in the original format whatever the setting says, and on-device copies may be reduced stand-ins until opened.

The six routes, with the honest tradeoff on each

Three of these deal with the file in front of you, two deal with the phone, one deals with the whole PC. Pick according to whether this is a one-off folder or a permanent condition.

• Convert the file. Produce JPG or PNG and open it anywhere, installing nothing, uploading nothing if the converter runs in your browser. Tradeoff: the output is a re-encode, and a converter that carries no metadata — including the one linked below — loses capture date, GPS and camera information.
• Change the camera format on the phone. No future photo needs a decoder. Tradeoff: files get larger, so you pay in storage, and the photos you already have are unaffected.
• Change the transfer setting so copies arrive converted. Fix the import path once and every future copy lands readable, with no per-file work. Tradeoff: it only governs that path, existing files stay as they are, and the PC copy is the converted one rather than the original.
• Install a codec on the PC. HEIC then opens natively, thumbnails included, for everything using the system's decoders. Tradeoff: a new system component, availability differing by edition and build, possible admin rights, and apps with their own decoding stack may still not see it.
• Open it in an app that ships its own decoder. Works regardless of what is installed on Windows, so you can look at a photo with no system changes at all. Tradeoff: viewing only — the moment the image has to go somewhere else, you are back to converting.
• Convert on a device that already opens them. A Mac or the iPhone can export a JPEG copy, which is fine when the phone is in your hand. Tradeoff: a round trip through a second machine, and moving the result back can re-create the same problem.

Which route is actually yours

A handful of photos you need now: convert them. Do not install anything for twelve files.

A steady stream from one iPhone: fix the transfer setting first, since it stops the format ever reaching the PC and costs nothing on the phone side; camera format second, if you also want the originals to stop being HEIC.

Other people's HEIC files you have to work with — client photos, shared albums, downloads: you do not control the sender's settings, so install a decoder or keep a batch converter in your bookmarks.

What you lose when you convert

Conversion is not free, and that is how people end up with a folder of flattened photos and no way back. Two things cost you: metadata, and one generation of lossy compression.

A HEIC carries capture date, exposure settings, camera model, orientation and often GPS coordinates. The converter linked at the end of this guide states plainly that original EXIF metadata — GPS, capture date, camera model — is not carried into the JPG or PNG output. The picture looks identical; the record of when and where it was taken is gone from the file. If you sort by date taken, if a photo has to show when it was shot, if location is how you organise a trip, keep the originals. Do not delete the HEIC folder after converting; the originals are the only place that information still exists.

One route loses nothing here, and it is worth naming: a codec install, or a viewer with its own decoder, never re-encodes at all. It only decodes for display, so the file on disk keeps every byte of metadata. That is a real argument for the decoder route when the photos are precious.

Then the compression. A HEIC was already compressed once; encoding its decoded pixels to JPEG applies a second lossy pass, and generations compound — artifacts that were subtle become visible in skin tones, sky gradients and fine texture. There is no way around it when the target is JPEG, so treat conversion as one deliberate step: convert from the original once, keep that output, and never re-save a converted JPEG again. Choose PNG when you want no further quality loss: it re-encodes the decoded pixels without discarding anything more, though it cannot undo what the original compression already dropped, and the file is much larger. If you ask for a maximum-dimension cap you are also trading resolution for size — right for an attachment, wrong for anything you may print or crop.

Live Photos, mislabeled files, and odd inputs

Live Photos are the most common surprise in a HEIC folder, because what you see on the phone is not one file. The still image is the HEIC; the moving part, the short video with its audio, is a separate companion file. Converting gives you a still JPG or PNG of the key frame and leaves the motion in the video file, untouched. Nothing is destroyed and the Live Photo on the phone is unaffected — but a JPEG cannot hold a moving picture, so if the movement is the point of the shot, keep the video.

Mislabeled files are the second surprise, and they explain a lot of “why do some open and some don't”. An extension is a hint, not a fact: photos renamed by an app, re-saved into a different container under the same name, or stripped of their name by a mail client all end up disagreeing with their own contents. A file named photo.jpg that really holds a HEIF container fails in a JPEG viewer and an HEIC converter alike, and software that trusts the extension is why the errors look random.

So when a batch half-fails, suspect the labels before you suspect the tool. The converter linked below identifies files by the container brand written inside the file rather than trusting the extension, so HEIF content saved under a JPEG name still gets decoded. That is the general lesson: when a photo behaves inconsistently, use something that inspects contents rather than names.

How the browser converter works, step by step

The linked tool converts HEIC and HEIF files to JPG or PNG inside your browser tab, and the mechanism is worth being precise about. The decoder is a WebAssembly build of a HEIF/HEVC decoding library bundled inside the page itself — not a separate file fetched from a third-party service, and not a server doing the work. Your browser loads the page, runs the decoder over your photo, draws the result to a canvas, and hands the finished file back as a download. The photo is never uploaded.

The workflow: add your files — several at once are accepted, which is the point when you have a folder to clear. Choose JPG or PNG. For JPG, set quality on a slider running 0.5 to 1.0, default 0.92; it is disabled for PNG, because PNG has no quality knob to turn. To get smaller outputs, set the maximum-dimension cap to 4096 or 2048; leave it unset to keep native size. Convert. Each output is named with the source name plus its pixel dimensions, which tells you at a glance whether you capped it. Download files individually or take the batch as one ZIP.

Two caveats, stated honestly. The ZIP option pulls a compression library from a content delivery network, so the page does make network requests — the accurate claim is that your photos are never uploaded, not that nothing is ever downloaded. And when a file fails you get an error and can try again; there is no batch-recovery feature to lean on, so work through erroring files one at a time.

Problems you hit after converting

The converted file is much bigger than the HEIC was. Normal: PNG is a lossless encoding of a full-resolution photo, and even a full-resolution JPEG is bigger than an efficient original by design. If size was the problem rather than the format, re-run at the default JPEG quality or set the dimension cap.

The converted photos still will not open in Windows Photos. Converting installs no decoder, so the HEIC files stay unopenable in that app until you delete them or add a codec — check the extension of the file you are double-clicking, since it is easy to be looking at the originals in the same folder.

Date taken and location are missing. Expected, and not fixed by re-converting: the metadata stays with the original. If you need it in the JPG, use a route that never re-encodes, or a metadata tool that writes capture date and coordinates into the existing file from what the originals say.

The output resolution is lower than you wanted. You set the maximum-dimension cap; re-run without it, and glance at the pixel dimensions in the output filename before deleting anything.

A file errors out. Try it on its own instead of inside the batch, and check whether the extension is telling the truth before concluding the file is broken.

The phone is still producing HEIC after you changed the setting. Take one new photo and check that one: the camera format applies to shots taken after the change, which is why one folder holds both kinds and why today's folder still needs converting.

Frequently asked questions