The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →If a shared link still shows an old image, check two separate caches: the CDN’s response for the image file and the social platform’s saved preview. Confirm the live page points to the intended og:image, update the image at its origin, purge or version the image URL, then request a fresh scrape in the platform showing the stale card. Clearing the CDN alone does not refresh every platform’s stored preview.
First find which cache is stale
An Open Graph image can look outdated for two different reasons. The CDN may still return old image bytes for the URL in og:image, or the social network may be showing preview data it saved earlier. Both can be stale at once, so verify the page, image response, and social preview separately.
As an Amazon Associate I earn from qualifying purchases.
- Page metadata: the live HTML must expose the intended
og:imageURL. - Image delivery: requesting that URL must return the intended image bytes.
- Social preview: the platform must fetch or refresh the page’s preview data.
Diagnose the page and image response
1. Check the live page HTML
Inspect the publicly served page, not just a CMS editor or local preview. Find the actual og:image value and confirm it is the image URL you expect. If the shared page redirects or has a canonical URL, check the HTML the crawler reaches for the URL being shared. A guide to image-preview troubleshooting also recommends verifying the crawler-facing HTML: Kinsta’s Open Graph image troubleshooting guide.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute2. Request the image URL directly
Open or fetch the exact image URL from the live metadata. Confirm that it is publicly retrievable without authentication and that the returned image is the new one, not merely a file with the right name. If it still contains old pixels, the problem is in the origin, CDN, or another image-delivery cache—not just the platform’s saved card.
3. Verify the CDN response
For Cloudflare, request the asset after a purge and inspect the CF-Cache-Status response header. A value of HIT indicates the response was served from cache. Cloudflare recommends single-file purging by URL; a successful purge API response confirms the request was received, not necessarily that the object has been evicted. See Cloudflare’s cache-purge guidance.
Refresh the CDN without re-caching the old file
Update the origin first
Replace or update the image at its origin before purging the cached object. Cloudflare warns that purging before updating or removing origin content can allow the old version to be cached again. Once the origin serves the intended bytes, purge the exact image URL rather than the entire zone when only one image is affected. A zone-wide purge forces subsequent requests to miss cache and return to the origin.
Verify the purge result
- Request the image URL and confirm its response body is the intended image.
- Check
CF-Cache-Status; after a targeted purge, verify the object is no longer reported asHIT. - Request it again as needed to see whether the CDN is now serving the correct version.
Cloudflare’s cache key and purge behavior are documented at Cloudflare cache keys and Cloudflare cache purging. Other CDN providers use their own controls and headers, so do not assume Cloudflare’s header or interface applies elsewhere.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Choose between purging and changing the image URL
| Approach | Use it when | Important detail |
|---|---|---|
| Purge the existing image URL | You want to keep the current URL and your CDN lets you target the one asset. | Update the origin first, then purge and verify the returned bytes. |
| Publish a versioned filename | You want the changed image to have a clearly new URL. | For example, change social-card.jpg to social-card-v2.jpg, then update the page’s og:image. |
| Add a query parameter | Your CDN cache key distinguishes query strings. | ?v=2 only creates a distinct Cloudflare cache object when the active cache key includes the query string. Cloudflare’s default key includes the full URL and query string, but configurable cache rules can ignore query strings: Cloudflare cache key documentation. |
A versioned filename is the more explicit URL change. If you use a query parameter, check the active cache-key configuration first; otherwise, the “new” URL may map to the same cached object.
Refresh the social platform’s saved preview
After the page metadata and image response are correct, request a new scrape in the platform where the card is wrong. Secondary technical guides describe using Facebook’s Sharing Debugger and its “Scrape Again” action, and LinkedIn’s Post Inspector. Their interfaces and behavior can change; check the current platform tools rather than relying on an old sequence of clicks. The descriptions are summarized in Kinsta’s troubleshooting guide.
Review the preview shown by the inspector, then check the actual shared post if needed. There is no universal refresh time or guarantee that one platform’s refresh action updates another platform’s saved preview.
Rank #4
Troubleshoot common stale-image cases
| What you see | Likely cause | What to do |
|---|---|---|
The live HTML has the old og:image URL. |
The page metadata was not updated or the shared URL serves different HTML than the editor preview. | Fix the live page metadata and inspect the exact URL being shared, including redirects. |
The og:image URL is correct, but the downloaded image is old. |
The origin, CDN, or another image proxy is returning old bytes. | Update the origin, target-purge the image URL, and verify the response body and CDN status. |
| The CDN no longer reports a cache hit, but the social card remains old. | The platform is showing saved preview data, or it fetched a different URL than expected. | Use that platform’s current inspection tool and confirm the fetched page and image URLs. |
A new ?v=2 URL still returns the old image. |
The CDN may be configured to ignore query strings in its cache key. | Check the active cache-key rules or publish a versioned filename instead. |
| The inspector sees the new image URL but displays old pixels. | The image response may still be stale in a delivery cache or proxy. | Fetch the image URL directly, verify its bytes, and consider a new versioned path before refreshing the platform again. |
Or skip the browser setup
To inspect a page’s rendered appearance after fixing its metadata and image, you can request a screenshot with one API call. ScreenshotNeo is a website screenshot API and MCP server for developers: ScreenshotNeo. The screenshot is useful for checking the page itself; it does not purge a CDN cache or force a social platform to refresh its saved preview.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for free and get 1,000 screenshots a month with no card.
Frequently Asked Questions
Will adding ?v=2 always force a new image to load?
No. It works as a distinct Cloudflare cache object only when the active cache key includes the query string. Check your cache-key rules or use a versioned filename.
Best Value
Does purging the CDN refresh Facebook or LinkedIn previews?
No. CDN purging refreshes image delivery; request a fresh scrape separately in the platform showing the stale preview.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
