# How to refresh a link preview on every platform (clear the cache)

**In short:** Each platform caches a link preview separately. Facebook: Sharing Debugger, Scrape Again. LinkedIn: Post Inspector. Telegram: @WebpageBot. Slack and Discord forget after about 30 minutes. X re-reads cards about weekly and WhatsApp, iMessage and Teams have no documented tool, so share a changed URL such as ?v=2. Always give a new image a new file name; existing posts mostly keep the old preview.

> Clear a stale link preview on Facebook, LinkedIn, X, WhatsApp, Slack, Discord, Telegram, iMessage and Teams: each official tool, how long caches last.

Published 2026-11-21 · https://shareglint.com/en/guides/refresh-link-preview

Every platform keeps its own copy of your link preview — the title, description and image it fetched the first time someone shared the URL. Fixing your page does not change that copy; you have to tell each platform to fetch again, and a few platforms give you no way to do so. This page lists, for each one, the official refresh tool if there is one, how long the cache lasts when the platform says so, and what happens to posts that are already published. If the preview is wrong *after* a refresh, the problem is on your page: start with [og:image not showing](https://shareglint.com/en/guides/og-image-not-showing).

**Where these facts come from.** Every row below cites the platform's own documentation, read on 2026-11-21 (X's card docs survive only in the Internet Archive). Where a platform documents nothing, the table says so rather than repeating a number from a forum. We did not run the refresh tools ourselves for this page — they need accounts and public test pages.

## The table

| Platform | Refresh tool | Cache, as documented | Posts already published |
|---|---|---|---|
| Facebook, Messenger, Instagram | [Sharing Debugger](https://developers.facebook.com/tools/debug/) → *Scrape Again*; Graph API `scrape=true` | metadata updated "every 30 days" | keep the old preview; *Refresh share attachment* in the post's menu |
| LinkedIn | [Post Inspector](https://www.linkedin.com/post-inspector/) | not documented | "will remain the same" |
| X | none | tags re-read "roughly every seven days" | not documented |
| WhatsApp | none | not documented | not documented |
| Slack | none needed | "around 30 minutes" | remove a preview with its × |
| Discord | [Embed Debugger](https://discord.com/developers/embeds) shows what Discord reads | "about 30 minutes" | not documented |
| Telegram | [@WebpageBot](https://t.me/WebpageBot) | not documented | not documented |
| iMessage | none | not documented | not documented |
| Microsoft Teams, Outlook | none | not documented | not documented |

## The rule behind every row: the image has its own cache

Platforms cache two things: the **page** (its tags) and the **image** (the file behind the `og:image` URL). Meta says it plainly: "We cache all images referenced based on each image's URL, so if you replace an image: Use a new URL for the new image or the image won't be updated" — and "Don't remove old images, as there maybe existing stories that reference the old image" ([Meta: Images in link shares](https://developers.facebook.com/docs/sharing/webmasters/images)).

So whenever the picture changes, change its address — `post.png` becomes `post-v2.png`, or `post.png?v=2` — and keep the old file online. Generated images can get this for free: when the image URL is built from the content (a hash of the title, or a [signed URL](https://shareglint.com/en/guides/signed-image-urls) that carries the title), a new title is a new URL.

Purge your own page cache and CDN first, too: refreshing a platform against a CDN that still serves yesterday's HTML fetches yesterday's tags again.

## Facebook (and Messenger, Instagram)

Meta's crawler, `facebookexternalhit`, builds previews for "Facebook, Instagram, or Messenger" ([Meta web crawlers](https://developers.facebook.com/documentation/sharing/webmasters/web-crawlers)). To refresh:

1. Paste the page URL into the [Sharing Debugger](https://developers.facebook.com/tools/debug/) and click **Scrape Again**. It also lists the image it chose and any warnings.
2. For many pages at once, use the Graph API: `POST /?id={your_url}&scrape=true`, with the URL percent-encoded ([Meta: change the metadata for an existing link](https://developers.facebook.com/documentation/sharing/webmasters/getting-started/change-link)).

Without either, "the Facebook crawler conserves resources by updating your link metadata automatically every 30 days." Two limits from the same page: a title "can be changed until it has 50 user interactions", and a link's `og:type` cannot change once it is used in a story.

**Posts already published** keep the old data. Meta's FAQ gives the one way to update them: open the post, click the ⋯ menu, select **Refresh share attachment** ([Meta: Link Sharing FAQ](https://developers.facebook.com/documentation/sharing/webmasters/faq)).

**"Facebook shows the wrong image"** is a different problem from a stale one. Check the debugger's list of `og:image` values: a theme and an SEO plugin often print one each, and Facebook takes the first. And Meta's FAQ: images "smaller than 600 x 315 pixels but larger than 200 x 200 pixels will be rendered with a small, square image." Our free [Facebook Sharing Debugger alternative](https://shareglint.com/en/tools/facebook-sharing-debugger) shows the same tags without a login, but only Meta's tool can refresh Meta's cache.

## LinkedIn

Enter the URL in [Post Inspector](https://www.linkedin.com/post-inspector/) and check the preview. LinkedIn's help: "The changes you make will only affect the URL's preview image and information for new posts that include it. The preview for any existing posts with this URL will remain the same" ([LinkedIn Help](https://www.linkedin.com/help/linkedin/answer/a6233775)). To change a post that is already live, delete it and post again. LinkedIn-specific causes — the 1200×627 minimum, formats, a bot rule that blocks LinkedInBot — are on [LinkedIn link preview not showing the image](https://shareglint.com/en/guides/linkedin-post-image-not-showing).

## X (Twitter)

There is no refresh tool. X's archived troubleshooting guide says the crawler "re-indexes the meta information on your tag roughly every seven days" ([archived X docs](https://web.archive.org/web/20241202114848/https://developer.x.com/en/docs/twitter-for-websites/cards/guides/troubleshooting-cards)). To see a fix now, share a URL X has not seen — `https://example.com/post?v=2` — and paste it into the composer to check before posting. Our [X card validator](https://shareglint.com/en/tools/twitter-card-validator) checks the tags and image; [the nine causes of a missing X card](https://shareglint.com/en/guides/twitter-card-not-showing-image) are on their own page.

## WhatsApp

WhatsApp documents no refresh tool and no cache duration. Its only test is the composer: type the link, do not send, and "If a preview does not come up above the composer box after 10 seconds, please check all the requirements above are met" ([WhatsApp link previews](https://developers.facebook.com/documentation/business-messaging/whatsapp/link-previews/)). To force a new preview, change the URL you share and the image URL. WhatsApp's own limits — 600 KB, 300 pixels wide, the first 300 KB of HTML — are on [WhatsApp link preview not showing](https://shareglint.com/en/guides/whatsapp-link-preview-not-showing).

## Slack and Discord

Slack: "Responses to these requests are cached globally across the service for around 30 minutes" ([Slack robots](https://api.slack.com/robots)). Wait half an hour, or share a changed URL. A preview that has been removed with its × stays removed; if someone also ticked *Also block previews from this website*, the whole site gets no previews in that workspace until an admin removes it under **Workspace settings → Attachments → Blocked previews** ([Slack Help](https://slack.com/help/articles/360001502048-Manage-link-previews)).

Discord: "Discord caches previews for about 30 minutes. While a preview is cached, editing your tags and resharing the same URL shows the old card. To see changes immediately, share the URL with a new query string, such as `?v=2`" ([Discord link previews](https://docs.discord.com/developers/link-previews/overview)). Its [Embed Debugger](https://discord.com/developers/embeds) shows which tags Discord picked up and which layout it chose.

## Telegram, iMessage, Teams and Outlook

- **Telegram:** send the URL to [@WebpageBot](https://t.me/WebpageBot), Telegram's bot for updating link previews. Telegram publishes no documentation page for it or for its preview cache, and we did not test it.
- **iMessage:** Apple's [TN3156](https://developer.apple.com/documentation/technotes/tn3156-create-rich-previews-for-messages) says how previews are built — no JavaScript, server redirects followed, a 1 MB page and 10 MB of images — but nothing about caching or refreshing. A changed URL is the only lever we can name, and we did not test it.
- **Microsoft Teams:** Microsoft documents no refresh. In a [Microsoft Q&A thread](https://learn.microsoft.com/en-us/answers/questions/5636536/how-do-i-update-the-thumbnail-in-a-url-preview-on) about a stale thumbnail, a Microsoft moderator tested adding `?v=2` and confirmed it "seems to work as a temporary workaround". If no preview appears at all, the tenant's messaging policy may have **URL previews** turned off ([Teams settings reference](https://learn.microsoft.com/en-us/microsoftteams/settings-policies-reference)).
- **Outlook:** link previews can be turned off per user ("Preview links in email"); Microsoft documents no cache or refresh ([Microsoft Support](https://support.microsoft.com/en-us/office/use-link-preview-in-outlook-com-and-outlook-on-the-web-ebbfd8ce-d38e-40ef-bb8c-a5362e881163)).

## Mastodon and Bluesky

- **Mastodon:** each server keeps its own card per URL and fetches it again only when the card is over two weeks old or has no image, and only when the URL is posted again; posts that already have a card keep it. Details from Mastodon's source: [Mastodon link preview not showing](https://shareglint.com/en/guides/mastodon-link-preview-not-showing).
- **Bluesky:** the card is stored inside the post when it is written, so it never refreshes; delete and repost, ideally with a new URL variant: [Bluesky link preview not showing](https://shareglint.com/en/guides/bluesky-link-preview-not-showing).

Platform-by-platform causes for Slack, Discord, Telegram, iMessage and Teams are on [link preview not showing in chat apps](https://shareglint.com/en/guides/chat-app-link-preview-not-showing).

## Before you share it again

- [ ] The page passes our [OG checker](https://shareglint.com/en/tools/og-checker): absolute `og:image`, one of it, in the server HTML.
- [ ] A changed image has a new URL, and the old file is still online.
- [ ] Your page cache and CDN are purged.
- [ ] Facebook: *Scrape Again*. LinkedIn: Post Inspector. Telegram: @WebpageBot.
- [ ] X, WhatsApp, iMessage, Teams: share the URL with `?v=2`.

## FAQ

### How do I refresh a link preview on Facebook?

Paste the URL into Meta's Sharing Debugger and click Scrape Again, or send POST /?id={url}&scrape=true to the Graph API. Without that, Facebook updates link metadata about every 30 days. For a post that is already published, open its menu and choose Refresh share attachment.

### How do I clear the LinkedIn link preview cache?

Enter the URL in LinkedIn's Post Inspector. LinkedIn says this only affects new posts that include the URL; existing posts keep their preview.

### How long do platforms cache link previews?

Documented values: Facebook refreshes metadata about every 30 days, X re-reads card tags roughly every seven days, Slack and Discord cache for about 30 minutes. LinkedIn, WhatsApp, Telegram, iMessage and Microsoft Teams publish no cache duration.

### What is the cache-busting trick for a link preview?

Add a query string the platform has not seen, such as ?v=2, to the URL you share, and give a changed image a new file name. The platform treats it as a new link and fetches it again. Discord documents this; on X, WhatsApp and Teams it is the only lever.

### Why does the old image still show after Scrape Again?

Facebook caches images by image URL, separately from the page. Meta's advice is to use a new URL for a new image, so post.png becomes post-v2.png. Keep the old file online, because existing posts still point at it.
