How to Open HEIF Files on Windows (or Convert Them to JPG)

The short answer

To open HEIF files on Windows you need both the free HEIF Image Extensions and the $0.99 HEVC Video Extensions from the Microsoft Store - the first parses the container, the second decodes the image data inside it. That combination works for most standard 8-bit HEIF files. It frequently does not work for 10-bit .HIF files from Canon, Sony, and Fujifilm cameras, which users report failing even with both extensions installed and paid for. For those files, and for anyone who would rather not install codecs at all, converting to JPG removes the problem permanently: JPG opens everywhere, no extensions required.

Why Windows can't open HEIF files

HEIF support is missing from Windows because of patent licensing, not technical difficulty. HEIF is a container format, and the image data inside almost every real-world HEIF file is compressed with HEVC (H.265), a codec covered by multiple patent pools. Rather than absorb the royalty cost for every Windows license, Microsoft moved the decoder into a paid Store add-on and left the OS without one by default.

The result is the error family every Windows user with HEIF files has seen: "You need an extension to use this file" is the one Microsoft's own support documentation describes, and community threads add "It looks like we don't support this file format" and plain "Unable to open this file" depending on the Windows and Photos app version.

The browser situation is just as closed. Per caniuse.com's HEIF support table, as of August 2026 Safari 17 and later is the only major browser that displays HEIF at all. Chrome (through version 154), Edge (151), and Firefox (157) do not support it, for the same licensing reason. So on a Windows machine there is no native app and no browser that will show the file - which is why a format that phones and cameras have used since 2017 still feels broken on the desktop.

Which HEIF do you actually have?

Check the file extension before you fix anything, because the extension tells you which path you are on. Three extensions share the HEIF family:

• .heic - Apple's variant, written by iPhones. If your files are .heic photos from an iPhone, that is a different workflow with its own tool: the HEIC to JPEG converter is the direct route, and the rest of this guide will still apply to the Windows-codec mechanics but not to the iPhone-side settings.
• .hif - the extension professional cameras write. Canon EOS R-series, Sony Alpha, and Fujifilm X-series bodies save HEIF stills as .HIF, typically 10-bit, often with HDR (PQ or HLG) encoding. These are the files with the extra failure mode covered in the 10-bit section below. Our what is a HIF file guide has the full background.
• .heif - the generic extension, rarer in the wild: exports from software, some Android devices, and stray files from image pipelines.

Same container standard underneath, but the hardware that wrote the file determines the bit depth, the HDR encoding, and therefore whether Windows can decode it at all. Keep that in mind as you pick a fix.

Fix 1: the two Microsoft Store extensions

The official fix is installing both Store packages, and for standard 8-bit files it works. The two pieces:

1. HEIF Image Extensions (free) - teaches Windows to parse the HEIF container. Microsoft's Store listing is explicit that it covers files with the .heic, .hif, and .heif extensions, and equally explicit that it is not enough on its own.
2. HEVC Video Extensions ($0.99) - the actual decoder for the HEVC-compressed image data inside. Without it, the container opens and the picture does not.

Requirements and caveats worth knowing before you spend the dollar:

• You need Windows 10 version 1809 (build 17763) or later; on older builds the extension refuses to install.
• The free "HEVC Video Extensions from Device Manufacturer" listing that used to be the workaround is effectively gone: it no longer surfaces in normal Store search, and 2025 reporting found it obtainable only through archive mirrors, with no guarantee current apps accept it. Budget for the $0.99 rather than chasing the free variant.
• Nothing in recent Windows 11 releases changed this. We looked for evidence that 23H2, 24H2, or 25H2 bundled free HEVC decoding and found none - the paid model is unchanged as of August 2026.
• It does not always work even when correctly installed. A steady stream of Microsoft Q&A and Community Hub threads document users who installed and paid for both extensions and still get "we don't support this file format," with some threads tracing failures to a specific buggy extension version and suggesting repairs, reinstalls, or downgrades. Set your expectations accordingly: this is the official path, not a reliable one.

Our honest read as engineers: a $0.99 decoder for a format your own phone and camera write by default is an irritating tax, but it is the only supported way to make the Photos app itself display HEIF. If you need HEIF working inside Windows' own apps, buy it. If you just need to see and use your photos, keep reading - there are better-value routes.

Fix 2: a viewer with its own decoder

A third-party viewer that ships its own HEIF decoder bypasses the Store extensions entirely - but most Windows viewers do not actually ship one, so pick carefully:

• XnView MP decodes HEIC/HEIF with its own built-in decoder - its documentation states directly that a fresh install opens the files with no Store purchase and no codec pack. Free for private use. This is the strongest no-cost option for simply viewing files.
• IrfanView and FastStone both lean on Windows' own codec chain (WIC) for HEIF, per their own plugin and format documentation - meaning they inherit the same Store-extension dependency and the same failures, and do not solve the problem on a machine without the codecs.
• Adobe's position is split: Adobe's Lightroom documentation states Lightroom, Lightroom Classic, and Camera Raw support HEIF files on Windows 10 directly, while Photoshop's help pages document installing the Windows HEIF and HEVC codecs as the prerequisite. If you live in Lightroom, you may never notice the problem; Photoshop users are back at Fix 1.

A viewer solves looking at the files. It does not make them attach cleanly to emails, upload to marketplaces and portals, or open on the other side for whoever you send them to - the compatibility gap follows the file wherever it goes.

The 10-bit problem: pro-camera .HIF files

If your .HIF files from a Canon, Sony, or Fujifilm body still will not open after installing both extensions, the file's bit depth is the likely reason, and no amount of reinstalling fixes it. Windows' HEIF support handles the standard 8-bit files phones produce. Pro bodies write 10-bit HEIF, frequently with HDR PQ or HLG encoding - Canon's own EOS R5 manual documents HEIF capture as part of its HDR PQ mode, and Sony's HEIF documentation specifies 10-bit color with HLG and BT.2020 support. The pattern users have pinned down across Canon and Adobe community threads is consistent: 8-bit HEIF opens, 10-bit .HIF fails, even with both extensions installed and paid for. One documented Canon R6 II owner's summary is the whole story in a sentence: bought both extensions, still cannot open his camera's files.

Two more things the forums have established so you do not have to:

• Renaming .HIF to .heif or .heic does not work. Users report trying it; the decoder gap is about what is inside the file, not the label on it.
• The camera makers' own software is the reliable native route. Canon's Digital Photo Professional and Sony's Imaging Edge Desktop open and convert their own HEIF files without touching the Windows codec stack - Sony's support pages explicitly direct users there. It works, with the usual cost: one vendor application per camera brand, and a manual export step every time. Our complete HEIF to JPG conversion guide walks through each maker's software path in detail.

There is also a subtler issue once files do open somewhere: 10-bit HDR data has to be tone-mapped down for standard displays, and different applications do it differently. Photographers report the same HLG HEIF file looking correct in one viewer and oversaturated in another. That is not one bug - it is what happens when a format outruns the software around it.

Cheat Sheet: symptom to fix

FAQ