Here is the message Word shows in place of an image you can plainly see existed five minutes ago:

This image cannot currently be displayed.

That is the entire error. No code, no detail, no link to a help page. The forum advice you’ll find is a grab-bag — toggle hardware acceleration, repair Office, reinstall, run a registry tweak. Most of it is wrong, or at least misordered. The single most common cause of this message in modern Word is a wrap-style problem that Microsoft’s own documentation barely mentions, and it has a fix that takes ten seconds.

We’ll get to that fix first, then walk through the other real causes in the order you should actually check them.

The wrap-style cause (start here)

The image is in the document. The file isn’t corrupt. The placeholder setting isn’t on. Word has simply decided it can’t render this particular image at this particular wrap setting right now, and the message is its way of admitting defeat.

The fix is to change the wrap style:

  1. Click the placeholder where the image should be. You should see the image-selection handles even though the image itself isn’t visible.
  2. Open the Layout Options flyout (the small icon that appears next to the selected image) or right-click the image and choose Wrap Text.
  3. Change the wrap style. If it’s currently In Line with Text, switch to Square or Tight. If it’s already on one of the floating styles, switch to In Line with Text and then back to your preferred floating style.

In most cases the image reappears immediately. If it doesn’t, save the document, close it, reopen, and check again — sometimes Word needs a render-cycle reset to pick up the change.

This is the cause the forums consistently fail to lead with, and it’s the one that catches the most users. It happens disproportionately to documents that have been:

  • Round-tripped between desktop Word and Word for the web
  • Edited collaboratively with Track Changes on
  • Saved from a Word version newer than the one that’s now opening them
  • Pasted into Word from an Outlook draft or another Word document

If you’ve done any of those recently with this document, the wrap-style fix is almost certainly your answer.

Why the wrap-style cause exists at all

The short version: Word stores image positioning data and image rendering data as separate things, and the render pipeline has gotten increasingly opinionated about what combinations it will agree to display. Floating images (anything that isn’t In Line with Text) carry positioning metadata that newer Word builds occasionally disagree with — particularly when that metadata was written by a different version. Rather than do something sensible like ignore the bad positioning and show the image anyway, Word displays the “cannot currently be displayed” message and waits for you to fix it.

Toggling the wrap style forces Word to recompute the positioning, which usually resolves the disagreement. It’s a workaround for what is functionally a rendering bug Microsoft has never fully addressed.

The other real causes (in order of likelihood)

If the wrap-style fix doesn’t work, move down this list. We’re going in likelihood order, not alphabetical order or “what Microsoft Support tells you to try first.”

2. View mode mismatch

Word has several view modes, and a small number of images don’t render in all of them. If you’re in Web Layout or Draft view, switch to Print Layout (View tab → Print Layout). Draft view in particular has a long history of refusing to render floating images.

This is a five-second check. Do it before anything else if the wrap-style fix didn’t work.

3. Picture placeholders are switched on

This is a separate setting from the error message, but it produces a similar-looking outcome and gets confused with it constantly. We cover it fully in our dedicated picture placeholder boxes explainer, but the short version: go to File → Options → Advanced → Show document content and confirm Show picture placeholders is unchecked.

If that setting is on, you’ll see empty boxes rather than the “cannot currently be displayed” message — but enough people conflate the two that it’s worth ruling out.

4. Hardware acceleration on a graphics driver Word doesn’t like

This is the cause every forum thread reaches for first. It’s real, but it’s nowhere near as common as it’s claimed to be, and toggling it has side effects (slower scrolling, less smooth rendering) so it shouldn’t be your starting move.

If you’ve tried the wrap fix and view mode and you’re still seeing the error, then:

File → Options → Advanced → Display → Disable hardware graphics acceleration (check the box, restart Word).

If the image now displays, the cause was your graphics driver. You can either leave the acceleration off, or you can try updating your graphics driver from the manufacturer (not from Windows Update, which often serves stale versions) and then re-enable acceleration.

5. The image part inside the .docx is corrupted

A .docx file is a ZIP archive. Inside it, images live in a folder called word/media/. If the entry for your specific image is corrupted — bad bytes written to disk, an incomplete cloud sync, a hard crash during save — Word will tell you it can’t display the image rather than tell you the file is damaged.

To check:

  1. Make a copy of the document. Don’t do this on the original.
  2. Rename the copy from .docx to .zip.
  3. Open the ZIP and navigate to the word/media/ folder.
  4. Try to open the image file directly with Windows Photos or any image viewer.

If the image opens fine outside the .docx, the corruption isn’t in the image — it’s in the document’s relationship to the image (the document.xml.rels file), which is recoverable but messier. If the image won’t open outside the .docx either, the image part is corrupted and you’ll need to delete it from the archive and re-insert a fresh copy when you reopen the document.

6. A specific image format Word has decided not to display

Rare, but worth knowing about. Word has gotten stricter about which embedded image formats it will render in recent builds. We cover this in detail in the picture insertion error article, but the formats most likely to trigger silent display failures are:

  • EPS (deprecated in 2017, displayed inconsistently since)
  • HEIC without the HEIF Image Extensions codec installed
  • WMF with newer Word builds enforcing stricter rendering
  • Very large images (above ~30 megapixels) that Word refuses to render at full size

If you suspect format is the cause, extract the image (as in cause 5 above), convert it to PNG or JPG, and re-insert.

7. Resource starvation

If Word is running out of available memory or graphics resources — which happens more often than you’d expect on machines with several large documents open simultaneously — it sometimes responds by silently failing to render images and showing this message instead.

Close other Office applications, close other Word documents, and reopen the affected file. If the image renders, the cause was resource pressure.

What not to do

A few things commonly recommended that don’t address this error:

  • Repair Office. Office Repair is a sledgehammer fix that gets recommended for almost every Office problem. It does not fix the wrap-style cause. It does not fix the corrupted image part cause. It does not fix the view mode cause. Save it for when you genuinely suspect installation damage.
  • Reinstall Word. Same logic, more time wasted.
  • Edit the registry to change DrawingObjectFlags. This appears in a handful of old forum threads. It does nothing useful for this error in modern Word.
  • Convert the document to .doc and back. This sometimes works, but only because the conversion strips the positioning metadata that was causing the wrap-style problem. The toggle-wrap-style fix gets you the same result in less time and without losing other formatting.

The diagnostic order

If you want the short version to keep handy:

  1. Toggle the wrap style on the image.
  2. Confirm you’re in Print Layout view.
  3. Confirm Show Picture Placeholders is off.
  4. Try disabling hardware graphics acceleration.
  5. Open the .docx as a ZIP and check the image part.
  6. Check the image format and resource pressure.

The first three resolve the overwhelming majority of cases. If you’ve reached step four, you’re already in unusual territory.

For the broader context — how Word handles image positioning in the first place, why anchors behave the way they do, and what other rendering failures look like — see our comprehensive guide to Word image anchors. For the parallel insertion-time error message that often gets confused with this one, see Word cannot insert the picture from the specified file. And for the full library of decoded Word and Office image error messages, see the dialog string dictionary.