OpenGraphDebug
← All posts

How to Clear Open Graph Cache on Every Platform

A guide to clearing Open Graph cache on Facebook, Twitter, LinkedIn, Slack, Discord, Telegram, and WhatsApp.

•Dmytro Krasun
Open GraphTesting and Debugging

If your Open Graph preview looks wrong, outdated, or refuses to update, the cause is almost always the same: cache.

Social platforms aggressively cache Open Graph data. Changing your tags alone is not enough. You need to know how each platform refreshes previews.

Here’s how to clear (or bypass) Open Graph cache on every major platform.

Facebook

Tool: Facebook Sharing Debugger

How to clear cache:

  1. Open the Sharing Debugger
  2. Paste your URL
  3. Click Debug
  4. Click Scrape Again

This forces Facebook to re-fetch all Open Graph tags.

If it still doesn’t update: Change the URL temporarily:

https://example.com/page?v=2

Facebook treats it as a new URL and re-scrapes everything.

Twitter / X

Tool: Twitter Card Validator (or equivalent preview tools)

How cache works:

  • Twitter has no reliable manual cache clear
  • It re-fetches on URL changes or over time

Best workaround:

  • Change og:image URL (new filename or query param)
  • Or add a query param to the page URL

Twitter strongly prefers new URLs.

LinkedIn

Tool: LinkedIn Post Inspector

How to clear cache:

  1. Paste your URL
  2. Click Inspect
  3. Re-run after changes

LinkedIn usually updates faster than Facebook but still caches aggressively.

Slack

No official debugger

How to refresh:

  • Slack often re-fetches automatically after some time
  • Changing the URL (?v=2) forces a refresh
  • Clearing the message and reposting sometimes works

Slack heavily relies on Open Graph fallback behavior.

Telegram

No cache-clear button

What works:

  • Telegram caches previews strongly
  • New URL = new preview
  • ?v=timestamp is the most reliable method

Telegram often ignores updates to the same URL.

Discord

Partial cache control

How to refresh:

  • New URL works instantly
  • Editing the image URL often helps
  • Clearing embeds requires reposting

Discord is strict but predictable.

WhatsApp

No official debugger

Behavior:

  • Long-lived cache
  • URL changes almost always required
  • Image URL changes help more than text changes

Universal Cache-Busting Techniques (That Always Work)

When all else fails, do one of these:

1. Change the Page URL

?utm_source=share
?v=2

2. Change the og:image URL

og-image.png → og-image-v2.png

3. Ensure Images Are Cache-Friendly

  • correct content-type
  • fast response time
  • publicly accessible
  • no auth, no IP blocks

Platforms trust images more than text.

The Reality of Open Graph Caching

  • Platforms prioritize speed over freshness
  • Cache TTLs are undocumented and inconsistent
  • Most “bugs” are cache artifacts

Assume previews are cached forever unless proven otherwise.

Final Takeaway

Open Graph caching is not a bug. It’s a feature.

To control previews reliably:

  • use platform debuggers when available
  • version URLs deliberately
  • never expect updates to propagate instantly

If you don’t design for caching, caching will design your previews for you.