SharePoint Document Issues

How to Fix SharePoint Pages Showing Old Images After Replacement

Algirdas Jasaitis Oct 10, 2026 868 views

Question details

The user is experiencing an issue where a newly replaced image displays correctly in edit mode, but the published SharePoint pages continue to show the old, outdated image.

How to Fix SharePoint Pages Showing Old Images After Replacement

Product: SharePoint
Device & OS: not provided
Scenario: Replacing an existing image file that is shared across multiple published SharePoint pages.
Observed behavior: The new image appears correctly in the preview and edit modes, but the inserted Image web part on published pages fails to update and still displays the old version of the image.

Before you start

Clear your local browser cache or open the SharePoint page in an incognito/private browsing window to verify if the old image is simply cached locally before assuming it is a server-side problem.

Solution 1Recommended

Test with a New Image Web Part and Check Cross-Site Behavior

Determine if the issue is restricted to a specific Image web part or if it affects the entire SharePoint environment.

SharePoint's caching mechanism can sometimes get stuck on specific web parts even after the underlying file in the document library is updated. Testing across different web parts and sites helps isolate the root cause.

Remove the existing web part

Click 'Edit' on your SharePoint page, select the problematic Image web part, and click the 'Delete' (trash can) icon to remove it entirely.

Add a new Image web part

Click the '+' icon on the page canvas, select the 'Image' web part from the menu, and browse to select your newly uploaded image.

Publish and verify

Click 'Republish' to save the changes. Refresh the page to see if the new image correctly replaces the old one.

Test on a different site

Repeat this image insertion process on a completely different SharePoint site within your organization. If the issue persists everywhere, it points to a tenant-wide backend caching issue.

Test with a New Image Web Part and Check Cross-Site Behavior

Backend Caching Delays: Content Delivery Network (CDN) caching on SharePoint servers can occasionally take up to 24 hours to clear automatically. If the new web part doesn't resolve it immediately, wait a few hours before escalating.

Solution 2

Raise a Service Request in the Microsoft 365 Admin Center

Contact Microsoft support for investigation when the issue is confirmed to be a persistent server-side caching error.

Free Microsoft Office alternative

Edit and Manage Your Documents Effortlessly with WPS Office

While managing web intranet content relies on SharePoint, creating and formatting the documents, presentations, and images you upload requires a powerful desktop suite. WPS Office is a highly compatible, lightweight, and free alternative to Microsoft Office that makes document creation seamless.

1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
2. Install the application: Run the downloaded installer file and follow the quick on-screen instructions to set up the software.
3. Open and edit your files: Launch WPS Office and open your existing Microsoft Office documents, spreadsheets, or presentations to start working immediately.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Easily insert, replace, and compress high-resolution images within your offline documents without caching glitches.Lightweight application that runs smoothly on almost any device.Completely free to use with a user-friendly, familiar interface.

microsoft office alternative - wps office

Frequently Asked Questions

Why does my SharePoint page show the old image instead of the new one?

This usually happens due to SharePoint's server-side caching or Content Delivery Network (CDN) settings. The system holds onto the older version of the image to load the page faster, causing a delay in displaying the newly uploaded file.

Will clearing my browser cache fix the SharePoint image issue?

Sometimes. If the old image is cached locally in your web browser, clearing your cache or opening the page in an incognito window will force the browser to fetch the new image. However, if the issue stems from SharePoint's backend servers, clearing local cache won't resolve it.

Does overwriting the image file cause this caching bug?

Yes. When you upload a new image with the exact same file name to the same SharePoint library, it replaces the file but keeps the same URL. This often triggers the caching problem because the browser and server assume the file hasn't changed based on the URL.

How can I avoid the image replacement caching issue in the future?

To bypass caching entirely, upload the new image with a slightly different file name (e.g., image_v2.jpg). Then, edit the Image web part on your SharePoint page to point to the new file URL. This forces the system to load the new asset immediately.

Document & File Issues