OG Image Not Updating? How to Force a Refresh on Every Platform

Why the old OG image persists

Social platforms cache your page's Open Graph metadata aggressively — sometimes for days or weeks. When you update your og:image and redeploy, the platform's scraper may not revisit your URL for a long time. Until it does, everyone who shares your link sees the stale preview.

The fix is different for each platform. Some have official debugger tools that force an immediate re-scrape. Others require URL tricks or just waiting.

Step 1: Confirm the new image is deployed

Before fighting platform cache, verify the fix is actually live. Fetch your page and check the og:image tag:

curl -s https://yoursite.com/your-page | grep -i "og:image"

If the tag still shows the old image URL, the deploy hasn't propagated yet — or the fix didn't ship. Wait a few minutes and try again. Platform cache is irrelevant until the source HTML is correct.

Force refresh: Twitter / X

Use the Twitter Card Validator. Enter your URL and click Preview card. This triggers an immediate re-scrape. The cache clears within minutes after validation.

If the validator already shows the correct image, the old preview will update naturally within 24–48 hours as Twitter re-scrapes shared URLs.

Force refresh: LinkedIn

Use the LinkedIn Post Inspector. Enter your URL and click Inspect. If it shows the old data, click Scrape again to force a re-fetch. LinkedIn's cache typically clears within 10–30 minutes after an inspect.

Force refresh: Facebook

Use the Facebook Sharing Debugger. Enter your URL, then click Scrape Again. You may need to click it 2–3 times for Facebook to fully propagate the update across its CDN. Facebook caches can take up to 24 hours to fully clear even after a forced scrape.

Force refresh: Discord

Discord has no manual scrape tool. Its cache TTL is typically 30 minutes to a few hours. The fastest workaround is to add a query string to the URL when sharing — Discord treats ?v=2 and ?v=3 as different URLs and re-fetches each:

# Share this instead:
https://yoursite.com/your-page?v=2

# If that's already cached, use:
https://yoursite.com/your-page?v=3

This is a one-time workaround. The canonical URL (without query string) will eventually refresh as Discord re-scrapes it organically.

Force refresh: Slack

Slack caches link unfurls per workspace. To force a re-fetch:

1. Delete the original message that shared the link (if possible).
2. Re-paste the link in the same or a different channel.
3. Alternatively, add a query parameter: ?ref=slack2

Slack's cache TTL is usually 30 minutes to a few hours after the link was first shared in that workspace.

Prevent stale OG images in the future

• Version your OG image URLs: use og.jpg?v=2 or include a build hash in the filename. This makes the new URL unique and bypasses all platform caches automatically.
• Set Cache-Control headers: on the image itself, use a short max-age (e.g., max-age=3600) so platforms re-check frequently.
• Test before launch: use OGFixer to verify your OG tags are correct before publishing — catching problems early prevents the cache-fighting cycle.