SharePoint Document Issues

How to Fix SharePoint Image Web Part Not Refreshing Replaced Images

Maira Mehtab Sep 22, 2026 868 views

Question details

Users need to resolve an issue where replacing an image on a SharePoint page using Power Automate does not visually update in the browser if the filename remains unchanged.

Product: Microsoft SharePoint and Power Automate
Device & OS: not provided
Scenario: Automating page updates by replacing existing image files in a SharePoint document library via Power Automate.
Observed behavior: The browser continues to display the older, cached version of the image instead of the newly replaced file because the file URL and name have not changed.

Before you start

Verify that you have adequate edit permissions for both the Power Automate flow and the target SharePoint site to implement API changes and rename files.

Solution 1Recommended

Append Unique Timestamps to Image Filenames in Power Automate

Force the browser and SharePoint to recognize the new image by generating a unique filename using timestamps for each replacement.

SharePoint frequently references images by their internal library ID and caches them based on the filename to improve page loading speeds. Merely replacing the file content without changing the filename does not immediately invalidate this cache.

Edit the Power Automate Flow

Open Microsoft Power Automate, locate the flow responsible for replacing the SharePoint image, and click Edit.

Add a Timestamp Variable

Modify the file creation or update step to append a timestamp to the image filename (for example, by using the utcNow() expression).

Update the Web Part Reference

Add a 'Send an HTTP request to SharePoint' action in your flow to update the target page's Image Web Part properties so it points to the newly generated image filename.

Cache Bypassed Successfully: By changing the filename, browsers will treat the image as a completely new asset, bypassing all local and server-side caching mechanisms.

Solution 2

Clear Local Browser Cache

Manually clear your browser's cached files to force it to download the latest version of the image from SharePoint.

Free Microsoft Office alternative

Manage Your Documents Without Cloud Synchronization Delays Using WPS Office

While resolving SharePoint caching and Power Automate flow errors can be tedious, creating and editing your daily documents shouldn't be. WPS Office offers a lightweight, completely free alternative to Microsoft Office, allowing you to manage your work locally or via reliable cloud options without struggling with complex backend syncing issues.

1. Download and Install WPS Office: Get the free WPS Office suite from the official website and install it on your PC or Mac.
2. Open Your Microsoft Files: Double-click your existing Word, Excel, or PowerPoint files to open them directly in WPS Office.
3. Edit and Save Locally: Enjoy seamless editing and save your progress locally to bypass complex cloud caching errors.

Fully compatible with Microsoft Office formats, including .docx, .xlsx, and .pptx.Edit and save documents locally to avoid unexpected cloud caching or synchronization delays.Lightweight software installation with a familiar, easy-to-use tabbed interface.Built-in PDF editing, conversion, and collaboration tools.

microsoft office alternative - wps office

Frequently Asked Questions

Why does my SharePoint page show the old image after I replaced the file?

SharePoint and web browsers aggressively cache images based on their filenames to reduce loading times. If you replace an image but keep the exact same filename, the browser assumes the file hasn't changed and loads the previously stored version from its cache.

Can I force the SharePoint Image Web Part to refresh automatically?

The most reliable way to force an automatic refresh is to append a unique string, such as a timestamp, to the image filename during the upload process. You must then programmatically update the page's web part to point to the new URL.

Is there a delay when updating SharePoint files via Power Automate?

Yes, Microsoft 365 backend systems do not always synchronize file updates and web parts in real-time. Even if a file is successfully replaced in the document library, it may take some time before the changes reflect across all servers and user devices.

Document & File Issues