How to Fix Site Logo Shows the Old Image After Upload

After uploading a new logo for a SharePoint site, many users see the old image still displayed on the site pages, in the browser tab, or in search results. This problem occurs because SharePoint and web browsers aggressively cache site assets including the logo file. The cached version of the old logo can persist for hours or even days, making the upload appear to have failed. This article explains why the old image remains visible, provides step-by-step methods to force the new logo to appear immediately, and covers related caching issues that affect other site images.

Why the Old Site Logo Still Appears After Upload

When you upload a new logo in SharePoint site settings, the platform stores the image file in a content database and updates the site’s logo URL reference. However, the old logo remains visible because both SharePoint and the web browser cache the image. Caching is designed to reduce load times by serving stored copies instead of fetching the file from the server each time. The cached copy can have a time-to-live (TTL) value set by SharePoint that delays the refresh, sometimes for 24 hours or longer.

The browser cache stores the logo based on its file name. If you upload a new file with the same name as the old logo, the browser sees the same URL and serves the cached version. SharePoint itself may also serve the cached version from its own front-end servers or content delivery network (CDN) endpoints. This double caching makes the problem appear worse than it actually is. The new logo is stored correctly on the server, but the cached copies prevent it from being displayed.

Steps to Force the New Site Logo to Display

Use the following methods in order. Start with the simplest browser refresh, then move to clearing the cache, and finally re-upload the logo with a new file name if the problem persists.

Method 1: Hard Reload the Site Page

1. Open the SharePoint site in your browser
   Navigate to the site where you uploaded the new logo. Make sure you are on the home page or any page that shows the logo.
2. Press Ctrl + F5 (Windows) or Cmd + Shift + R (Mac)
   This keyboard shortcut tells the browser to reload the page and ignore the cached version of all assets on that page, including images, CSS, and JavaScript. The new logo should appear after the page finishes reloading.

Method 2: Clear the Browser Cache for the Site

1. Open your browser’s settings or history panel
   In Chrome, click the three-dot menu in the top right corner, then select Settings > Privacy and security > Clear browsing data. In Edge, use the same path. In Firefox, click the menu button and select Settings > Privacy & Security > Clear Data.
2. Select the time range and cache option
   Choose “All time” or “Everything” for the time range. Check only the box labeled “Cached images and files” or “Cache.” Do not clear cookies or site data unless you want to lose login sessions.
3. Click Clear Data or Clear Now
   After the cache is cleared, reload the SharePoint site. The new logo should appear. If it does not, proceed to Method 3.

Method 3: Re-upload the Logo with a Different File Name

1. Rename the logo image file on your computer
   Change the file name to something unique that was not used before. For example, rename “logo.png” to “company-logo-2024.png.” This forces SharePoint to generate a new URL for the image.
2. Go to SharePoint site settings
   Click the gear icon (Settings) in the top right corner of the site, then select Site Information. In the Site Information panel, click the current logo image or the Change button next to the logo.
3. Upload the renamed logo file
   Click Change Logo or Upload, select the renamed file from your computer, and confirm the upload. Wait a few seconds and reload the site. The new logo should now appear because the URL is different from the cached version.

If the Site Logo Still Shows the Old Image After All Methods

SharePoint CDN cache is not cleared

If your SharePoint environment uses a Content Delivery Network (CDN) for static assets like images, the CDN may serve the old logo even after clearing the browser cache. CDN caches have their own TTL settings, typically 24 to 72 hours. To force a CDN cache flush, go to the SharePoint admin center, select Content services > Content Delivery Network, and click Purge CDN Cache. This action removes all cached files from the CDN endpoints and forces the next request to fetch the latest version from the origin server.

Site logo change has not replicated across SharePoint servers

In multi-server SharePoint farm deployments or geo-distributed environments, the logo change may take a few minutes to replicate to all front-end servers. This delay is normal. Wait 15 minutes and then perform a hard reload using Ctrl + F5. If the logo still does not appear, check that the logo file is stored in the site assets library and that the URL in the site settings points to the correct file.

Browser extension or proxy is caching the image

Some browser extensions, such as ad blockers or privacy tools, cache images independently of the browser cache. Corporate proxy servers may also cache web content. Try loading the SharePoint site in a private or incognito window. If the new logo appears there, the issue is caused by an extension or proxy. Disable extensions one by one to identify the culprit, or contact your IT department to clear the proxy cache for the SharePoint site domain.

Method	Speed	Effectiveness
Hard reload (Ctrl + F5)	Immediate	Works if only browser cache is the issue
Clear browser cache	1-2 minutes	Works for most single-browser scenarios
Re-upload with new file name	2-3 minutes	Works even when server-side cache is persistent
Purge CDN cache	5-10 minutes	Required for CDN-cached environments

Now you can force the new SharePoint site logo to appear immediately using hard reloads, browser cache clearing, or renaming the image file. If the old logo persists after these steps, check the CDN cache or proxy settings. For future logo updates, always rename the image file before uploading to prevent cache collisions from the start.