You drag an iPhone photo into a Word document. Nothing happens. Or worse: the image appears to insert but renders as a broken placeholder. Or worst of all: Word throws “Word cannot insert the picture from the specified file” and refuses to even try.
This is not a Word bug. It is a deliberately convoluted licensing arrangement that Microsoft has structured to make HEIC support in Office formally available while keeping it practically broken for a large share of users. Understanding the arrangement matters because the fix is different depending on which side of it you are on.
Why HEIC in Word is broken by default
HEIC is the file extension Apple uses for photos encoded with the HEVC codec, stored inside a HEIF container. It is now the default capture format on every iPhone shipped in the past several years.
To open a HEIC file, Windows — and Office apps running on Windows — need two separate components:
- HEIF Image Extensions. The container parser. Free from the Microsoft Store.
- HEVC Video Extensions. The codec that actually decodes the compressed image data inside the container. Microsoft charges $0.99 (£0.79) for this.
Without both, HEIC files cannot be opened by Windows components, including Word. The container can be parsed, but the actual image data is locked behind a codec the user has not paid for. The result is the symptoms above: silent failure, broken placeholders, or error dialogs depending on the specific code path.
Microsoft’s official documentation describes both extensions as requirements but does not lead with the fact that one of them is paid. The Insert Picture dialog will happily let you select a .heic file without warning that the rendering will fail.
The free version of HEVC Video Extensions
This is the part Microsoft does not advertise. There are two listings for HEVC Video Extensions in the Microsoft Store:
- HEVC Video Extensions — listed at $0.99, what most people see.
- HEVC Video Extensions from Device Manufacturer — listed at free, accessible at a different URL.
Functionally, they decode the same content. The free version is theoretically restricted to devices where the manufacturer has pre-licensed HEVC support, but in practice it installs and works on most modern Windows machines. Microsoft has been slowly making this version harder to find. As of mid-2026 it is still discoverable via direct URL but no longer appears in Microsoft Store search.
If you can install it, do. The Office HEIC pipeline does not care which version is installed — it just needs HEVC decoding to be available.
The deeper consumer-rights discussion of this paywall — and which path is appropriate for which users — sits in the dedicated piece The HEVC Video Extension question: pay or free workaround?. The short version: pay if your time is worth more than the friction; use the free path if you are setting up a one-off machine and the savings matter.
Build requirements
HEIC insertion into Office apps has hard version requirements that get ignored in most troubleshooting threads:
- Microsoft 365 for Windows: version 2006 build 13020.10000 or later.
- Office 2019 perpetual licence: support is patchy; later updates added some HEIF handling but it remains less reliable than M365.
- Office 2016 and earlier: no native HEIC support. Conversion before insertion is the only path.
You can check your build at File → Account → About Word. If you are below the M365 minimum and on a managed device that does not update automatically, this is the first thing to fix — no amount of codec installation will help if the Office side is below the threshold.
The enterprise problem nobody talks about
This is where the situation gets genuinely difficult, and where IT teams in 2026 are still fighting the same battle they were fighting in 2023.
In any environment where the Microsoft Store is blocked by Group Policy, Intune, or any other restriction — which is most large enterprises — users cannot install HEIF Image Extensions or HEVC Video Extensions through the normal path. The Store is the only sanctioned distribution mechanism Microsoft offers, and Microsoft does not provide an offline MSIX/Appx package for IT to redistribute directly.
The supported path for IT teams is:
- Link Microsoft Store for Business (or Microsoft Store for Education) to Intune or Configuration Manager.
- Acquire HEIF Image Extensions through Store for Business.
- Deploy it silently to managed devices.
This works but it is not casual setup. For an IT team that has not previously integrated Store for Business with Intune, getting one codec deployed is a multi-day project. The result is that in many enterprises, HEIC support in Office is permanently broken because the deployment overhead has never been prioritised.
If you are an end user in this situation, the only thing that will work is converting HEIC files to JPEG before you insert them. That section is next.
The cleanest fix for everyone: convert HEIC to JPG before insertion
If the codec route is blocked, slow, or simply not worth the friction, the reliable approach is to never put a HEIC file in front of Word in the first place. Convert to JPEG and insert the JPEG.
There are four paths to this, in rough order of practicality:
On the iPhone, change the capture format. Settings → Camera → Formats → Most Compatible. This causes the iPhone to capture in JPEG instead of HEIC for new photos. This is the right answer for anyone whose primary use case is iPhone-to-Word and who does not specifically need HEIC’s compression benefits. You give up some storage efficiency on the iPhone; you eliminate the entire problem on the Word side.
Email or AirDrop to convert on the fly. Sending HEIC photos via Mail.app on iOS, or AirDropping them from a Mac, often triggers automatic conversion to JPEG when the destination cannot handle HEIC. This is unreliable as a deliberate workflow but useful in pinch moments.
Convert in bulk on Windows. Free tools — Imazing HEIC Converter, CopyTrans HEIC for Windows (the standalone converter), or the open-source ImageMagick at the command line (magick mogrify -format jpg *.heic) — handle batch conversion cleanly. ImageMagick is the best choice for IT teams scripting against folders of HEIC files; the consumer tools are better for end users who need a drag-and-drop interface.
Use an online converter for one-offs. HEIC-to-JPG conversion is the kind of trivial task online converters do well, and for one or two photos the friction of installing a tool is not worth it. The usual caveats apply: do not upload anything you wouldn’t be comfortable putting on a public server.
After conversion, insert the JPEG through Insert → Pictures → This Device the same way you would any other image. The image inserts reliably, renders correctly, and saves without codec dependency on the recipient’s machine.
When HEIC inserts but the image looks wrong
A subtler failure mode: HEIC inserts, the image appears, but it looks degraded compared to the original. This is a separate problem from the codec dependency — it is Word’s image compression behaviour, and it applies to every image format Word ingests.
The fix is to configure Word’s image quality settings before inserting the image. The detailed walkthrough is in Word: Image quality drops after save — the compression settings that matter, but the short version is: File → Options → Advanced → Image Size and Quality → Default resolution: High fidelity, with Do not compress images in file ticked. Word’s default of 220 ppi will downsample HEIC photos the same as it downsamples anything else.
Why this whole thing is consumer-hostile
There is a reasonable version of HEIC support on Windows. It would look like this: HEIF and HEVC extensions are bundled with Windows, install automatically with Office, and the question of which codec is licensed becomes Microsoft’s problem rather than the user’s. macOS does this. iOS does this. Android does this with the equivalent codecs.
Microsoft’s choice to gate basic image format support behind a paywall — and then make the free version available but hidden — is a deliberate decision that has been in place since 2018 and that Microsoft has had every opportunity to reverse. The fact that the Store is also the only legitimate distribution channel, and that the Store is blocked in most enterprise environments, compounds the problem.
If you have spent twenty minutes trying to insert an iPhone photo into a Word document and ended up here, you have not done anything wrong. The system has been designed to fail in exactly the way it is failing for you. The fastest path out of it is to convert HEIC to JPEG and move on with your day.
For the broader picture — HEIC across all of Windows, not just Word — see HEIC on Windows 11: the Microsoft paywall, free workarounds, and what actually works. For the codec question specifically, see The HEVC Video Extension question. And if you are hitting the insert dialog error rather than a rendering issue, the diagnostic order is in Word cannot insert the picture from the specified file.