“The linked image cannot be displayed” (The Red X Error)

The “The linked image cannot be displayed” error (often accompanied by a small Red X icon) occurs when Microsoft Word or PowerPoint loses the path to an externally referenced graphic file. Instead of embedding the image directly inside the file, the document contains a text-based pointer directing the system to a local folder or network address. If that source file is moved, deleted, or blocked by local security settings, the asset pointer breaks completely.

Fast-Fix: The 45-Second Solution

This error stems from a broken file path reference or aggressive security zone settings blocking the directory. The risk is low for data safety but disrupts layout presentation. Resolve this by pressing Alt + F9 to toggle field codes, then update the path string to point to the current file location.

Diagnostic Snapshot

• Severity Tier: Moderate (does not corrupt text files, but entirely breaks the visual presentation)
• Data Safety Risk: Low (the core text remains completely safe; only the visual path link is broken)
• Common Cause: Moving documents without their associated image folders, broken corporate network drive mappings, or strict browser security zones blocking local temporary file folders
• Admin Requirement: Standard local user permissions; registry modifications require local user access

Condition: Low Risk vs. High Risk

• Low Risk Scenario: The image displays perfectly on your own machine but turns into a Red X when emailed to a colleague or opened on another computer. This means the image file itself is safe; it is simply linked to a local drive path that the other computer cannot reach.
• High Risk Scenario: The Red X appears on your primary creation computer, and checking the target folder confirms the original source photos have been deleted or overwritten.

The System Break (What This Means)

To understand why this happens, think of an embedded image like a photo glued directly onto a paper report—it travels wherever the report goes. A linked image, however, is like a note on the paper that says, “Go look at the photo hanging on the wall in room 402.” If someone repositions the photo, or if you take the report to an entirely different building, that note becomes useless. You are left staring at an empty space.

Microsoft Office uses a background command syntax called an INCLUDEPICTURE field code to pull linked images dynamically. When you open a file, Word reads this field code and attempts to pull the raw graphic data from the specified path. If the storage drive is disconnected, or if local security boundaries block the application from reading that path, the layout engine fails to render the asset and drops a generic Red X placeholder into the frame.

Root Cause Probability

• Likely (60%): Absolute file path mismatch. The source image was moved, renamed, or deleted after being inserted into the document.
• Possible (30%): Blocked temporary cache paths. Windows security updates or strict internet properties configurations have locked down the local path cache or turned on policies that prevent Office from reading images linked via web addresses.
• Rare (10%): Picture placeholders active. Word’s optimization settings have been toggled to hide graphics to save processor memory on large files.

Conflict Escalators

Certain environments drastically increase the likelihood of severs in your file links:

• Disconnecting from Corporate VPNs: If your image paths point to a shared network share (like X:\Marketing\Graphics\), disconnecting your network access instantly breaks every image in the document.
• Email Attachments: Sending a raw document with local links straight to an external recipient detaches the file from its source environment, causing instant path breaks for the viewer.
• BlockHTTPimages Registry Restrictions: Enterprise lockdown policies often include a background registry key that blocks Office programs from resolving links from external servers.

Progression: 1 Hour → 24 Hours → 1 Week

• At 1 Hour: The reference link is completely repairable if the source image is still on your computer. You can rewrite the path or move the asset back.
• At 24 Hours: If a coworker modifies and saves the broken document on a separate network, the underlying path metadata can become altered or permanently truncated.
• At 1 Week: If the images were stored in temporary internet folders or automated system scratchpads, the file system may clear the cache, making original data recovery impossible without a backup.

Common Misdiagnoses

This path block is often confused with a total graphics engine import failure. If your file path is accurate but the graphic format itself cannot be decoded by Microsoft Office, you will get a distinct import error message. For broken vector graphics handling, see “An error occurred while importing this file” for SVG graphics. If the target image folder was intentionally renamed or migrated across your company’s network infrastructure, review “The source file for this link has been moved or renamed”.

Immediate Action Steps

Step 1: Reveal and Repair the Path Strings

1. Launch the problematic document in Word.
2. Press Alt + F9 (or Alt + Fn + F9 on compact keyboards). Your document will instantly swap its images for their raw code names.
3. Locate the broken asset block. It will look like this: { INCLUDEPICTURE "C:\\Users\\Admin\\Pictures\\Project\\Chart.png" \* MERGEFORMAT }.
4. Verify if that folder and file exist exactly as written. If the path is wrong, type the correct folder location directly inside the quotation marks.
5. Press Alt + F9 again to restore your layout, click on the Red X frame, and press F9 to force the program to reload the image from the new path.

Step 2: Disable Document Picture Placeholders

If the path is accurate but nothing displays, verify that Word isn’t intentionally hiding the image to save system performance:

1. Go to File -> Options -> Advanced.
2. Scroll down until you reach the Show document content grouping.
3. Locate the checkbox for Show picture placeholders. Ensure this is unchecked.
4. Click OK, close the file, and restart Word.

Step 3: Toggle the BlockHTTPimages Policy Registry Fix

If images pulling from web servers or cloud portals are failing, a local registry key may be blocking them:

1. Press Windows Key + R, type regedit, and hit Enter.
2. Go to the following directory path: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options.
3. Look in the right-hand pane for a entry named BlockHTTPimages. If it is present and set to 1, double-click it, change the value to 0, and click OK.

Hard-Stop Red Flags

Stop troubleshooting manual links immediately if you observe these conditions:

• Null Pointer Paths: If you hit Alt + F9 and the code reads { INCLUDEPICTURE "" } with nothing inside the quotation marks, the original link details were wiped during a save file crash. The path is gone.
• Wiped Temporary Directories: If the image path maps to a user temporary folder (AppData\Local\Temp) and you have recently run an automated disk utility tool, the temporary source files have been scrubbed.

What the IT Admin Will Check

An enterprise administrator tracking this issue on managed endpoints will check:

• Trust Center Group Policies: Ensuring that administrative templates are not explicitly blocking remote files or external asset loading inside un-trusted directories.
• IE/Edge Security Zone Mapping: Verifying that local internal servers hosting resources are explicitly declared inside the “Intranet Zone” or “Trusted Sites Zone” in Windows Internet Options.

Resolution Complexity

• User Action Level: Minor to Moderate. Requires toggling basic system field codes or navigating advanced software options menus.
• Time Commitment: 5 to 10 minutes.

Related Error Escalators

If your image paths reconnect successfully but the graphics appear blurry or heavily distorted upon rendering, see How to Fix Blurred Images in PowerPoint after Saving to adjust your application compression values.

Ticket Closed

To ensure this error never happens again, convert your external links into embedded assets before sharing your file. Press Alt + F9 to reveal the raw INCLUDEPICTURE code strings. Highlight the entire line of code for the broken image, then press Ctrl + Shift + F9 on your keyboard. This command instantly severs the external path dependency and welds the picture directly into the document file, allowing it to open perfectly on any computer.