The full error reads: “Word cannot insert the picture from the specified file. The file may be in use by another program, the file may be read-only, or you may not have permission, or the file may be damaged.”
Microsoft’s dialog gives you four possibilities. There are actually closer to eight, and the order Microsoft lists them in is wrong. The single most common cause in 2026 — by a wide margin — isn’t on Microsoft’s list at all.
Here’s the actual cause hierarchy, ordered by how often it’s the real culprit, with the fix for each. Work down the list. Stop when one of them solves the problem.
1. The file lives in OneDrive (or another cloud-sync folder) and isn’t fully downloaded
This is the dominant cause in 2026, and almost nothing else online emphasises it properly. If your image is in your OneDrive folder, in a Pictures or Documents folder that’s been redirected into OneDrive by Known Folder Move, or in any other Files-On-Demand location, what you see in File Explorer is often a placeholder — not the actual file bytes.
Word’s Insert Picture dialog can navigate to that placeholder and present the filename perfectly normally. The thumbnail even renders. Then when you click Insert, Word asks the file system for the bytes, OneDrive has to fetch them, and somewhere in that handshake the operation fails. You get “cannot insert the picture.”
The fix:
- Open File Explorer and navigate to the image.
- Look at the status icon next to the file. A blue cloud means the file is online-only — those bytes aren’t on your disk yet. A green tick means it’s fully local. A green tick on white background means it’s local and pinned.
- Right-click the file and choose Always keep on this device.
- Wait for the icon to change to a green tick.
- Try Insert Picture again.
If the image is in a SharePoint library mounted through Files-On-Demand, in a OneDrive for Business folder, or on a Teams channel files area, the same logic applies. Mark the file or the parent folder for local availability and retry.
This single fix resolves the majority of cases we see now that OneDrive’s Known Folder Move is aggressive about pulling user Documents, Pictures, and Desktop folders into the cloud on first sign-in. Microsoft’s own error dialog and its support article on this error mention “the file may be in use by another program” before any of the actual common causes — which is exactly backwards.
2. The file path contains characters Word doesn’t handle well
Word’s image insertion pipeline has known weaknesses around specific path constructions. The triggers we see most often:
- Very long paths (anything over about 260 characters total, particularly under cloud-sync folders that nest deeply)
- Paths with non-ASCII characters when the system locale doesn’t match the file system encoding
- Paths that include network shares mapped through Quick Access shortcuts rather than directly
- UNC paths (
\\server\share\...) to a server that’s not currently responding - Paths inside Personal Vault or other on-demand secured locations
The fix: copy the image to a short, simple local path. C:\Users\[you]\Desktop\test.jpg is the cleanest test. If it works from the desktop, you’ve confirmed the problem is path-related rather than file-related. From there you can decide whether to keep working from the desktop copy or fix the original location.
3. The file is open in another program
This is the cause Microsoft’s error message leads with, and it’s a real one — just less common than the dialog text implies. If you’ve just been editing the image in Photoshop, Affinity, GIMP, Paint.NET, or even a browser’s image preview, the application may still be holding an exclusive lock on the file even after you think you’ve closed it.
The fix: close every application that might have the image open, including image viewers running in the background. If you’re not sure what’s holding the lock, the file’s Properties dialog won’t tell you, but Resource Monitor will. Press Windows+R, type resmon, open the CPU tab, expand Associated Handles, and search for the filename. Anything listed there is currently holding a handle to it.
Restarting the computer is the lazy version of this fix and is usually faster than hunting down the offending process. If you only get the error after a specific workflow (export from Lightroom, save from Photos, etc.), that application is your suspect.
4. The file is read-only or in a protected location
If the image is on a read-only network share, in a folder you don’t have permissions to, or has been marked read-only by attribute, Word can fail to read it cleanly even though access isn’t strictly being denied.
The fix:
- Right-click the file and choose Properties.
- On the General tab, uncheck Read-only if it’s ticked.
- On the Security tab, confirm your user has at least Read permission listed.
- If the file is in
Program Files,Program Files (x86),Windows, or any folder owned by another user account, move or copy it to your own Documents or Desktop folder before inserting.
Files extracted from a downloaded ZIP sometimes inherit a Mark-of-the-Web flag that Word treats as suspicious. If the Properties dialog shows an Unblock button at the bottom, tick it and click Apply, then try the insert again.
5. The file extension is lying
A file called vacation.jpg is not necessarily a JPEG. If a file has been renamed from .heic to .jpg, saved through a phone import that used the wrong extension, or exported from an editor that wrote unexpected bytes under the JPG name, Word will see the extension, try to decode the bytes as JPEG, fail, and throw the insertion error.
The fix: open the image in Windows Photos or Paint and look at it. If it opens fine, choose File → Save As and save it as a fresh JPG or PNG. The save process rewrites the file from decoded pixels and produces a clean image that Word will accept.
If the file won’t open in Photos either, you’re probably looking at HEIC without the codec (next cause) or an actual format Word doesn’t handle. EPS, for example, was deprecated in Office in 2017 and is no longer supported by default — the most common “weird format” we still see causing this error.
6. It’s a HEIC from an iPhone and Windows doesn’t have the codec
Modern iPhones default to HEIC for photos. Windows 11 includes the free HEIF Image Extensions but not the HEVC Video Extensions required for the codec underneath. Without HEVC, HEIC files render thumbnails in File Explorer but fail when Word tries to actually decode the pixels for insertion.
The full HEIC story is covered in our HEIC images in Word troubleshooting guide. The short version: install HEIF Image Extensions from the Microsoft Store (free), and if that alone doesn’t unlock decode, either pay £0.99 for HEVC Video Extensions or install the free OEM version. The simplest workaround — convert the HEIC to JPG with Photos before inserting — works every time and avoids the codec question entirely.
7. The image has corrupt or unusual metadata
JPEGs from certain camera apps, screenshots edited by certain tools, and images that have been through aggressive optimisation can have malformed EXIF, ICC profile, or alpha channel data. Word’s image pipeline is strict about these structures and will refuse files it considers malformed even when every viewer renders them fine.
The fix is the same as cause 5 but applies to files with the correct extension: open the image in Paint, File → Save As, save as a new JPG or PNG. This rewrites the file with clean metadata and minimal headers. It’s the universal “no questions asked” fix for any image that should work but doesn’t.
8. Office itself is broken
This is Microsoft Q&A’s go-to answer and it’s almost never the actual cause. But if you’ve worked through causes 1–7 and they’ve all failed, and the error happens with every image you try across multiple documents, then the Office installation is genuinely the suspect.
The fix:
- Close all Office apps including Outlook, Teams, and anything in the system tray.
- Open Settings → Apps → Installed apps.
- Find Microsoft 365 or Microsoft Office in the list.
- Click the three dots, choose Modify, then Online Repair — not Quick Repair.
- Wait. Online Repair takes 15–30 minutes and reinstalls Office components fresh from the cloud.
Online Repair is much more thorough than Quick Repair and is the only one worth running for image-pipeline issues. If Online Repair doesn’t fix it, you’re looking at a Windows-level problem (graphics drivers, system file corruption, antivirus interference) rather than an Office one. At that point a fresh Windows user profile is the next step — that’s a separate troubleshooting path.
What about disabling hardware graphics acceleration?
This advice appears in nearly every forum thread about Word image issues. It’s worth a try as a last resort but it almost never fixes the insertion error — it’s a fix for rendering and display problems, where the image inserts successfully but then doesn’t display. If your image inserts but appears as a blank placeholder, hardware acceleration is a reasonable suspect. If you can’t insert at all, it isn’t. Don’t waste time on it until you’ve worked through the eight causes above.
When to give up and use the paste workaround
If you’ve worked through the list and nothing has fixed it for a specific image, just paste the image instead. Open the file in Photos or any image viewer, copy it to the clipboard with Ctrl+C, then paste into Word with Ctrl+V. Word’s clipboard paste pipeline is more forgiving than the Insert Picture pipeline — it receives decoded pixels rather than a file path, so it bypasses every cause on this list except the rendering ones. It’s a workaround, not a fix, but it gets you back to work in ten seconds and that’s often what matters.
For the broader picture of which Office image errors mean what, see the Microsoft Office image error messages dictionary. For related image-display problems where the picture inserts but doesn’t show, see our piece on the wrap-style cause of “This image cannot currently be displayed”. And if your inserted images keep jumping to different pages when you edit, that’s the anchor behaviour problem — a different issue entirely.