Force Refresh Your Cached OG Images
You updated your OG image but Facebook still shows the old one. This is the OG image caching problem, and it affects every social platform differently. Here is how to force each platform to pull the fresh version of your image.
Facebook Cache Refresh
Facebook caches OG data aggressively, sometimes holding onto stale images for weeks. The official way to refresh is through the Facebook Sharing Debugger at developers.facebook.com/tools/debug. Paste your URL, click 'Scrape Again', and Facebook will make a fresh request to your server and update its cache. You may need to click 'Scrape Again' twice for the changes to take effect. If the debugger shows the updated image but shared posts still show the old one, it means the feed cache is separate and can take a few hours to propagate. For programmatic cache clearing, you can use the Facebook Graph API's /?scrape=true endpoint with a POST request.
Twitter Cache Refresh
Twitter's cache is generally less stubborn than Facebook's, but it still holds onto OG data for a while. Use the Twitter Card Validator (cards-dev.twitter.com/validator) to preview and refresh your card. Simply entering your URL triggers a fresh crawl. If the validator shows the updated image but tweets still show the old one, it is usually because the tweet itself cached the preview at post time. New tweets sharing the same URL will use the updated image. Twitter does not offer a public API for cache invalidation, so the Card Validator is your only tool. One workaround for persistent caching issues is to add a query parameter to your URL when sharing it again.
LinkedIn Cache Refresh
LinkedIn is notorious for having the most stubborn OG image cache. The Post Inspector (linkedin.com/post-inspector) lets you re-scrape a URL, but it can take several hours for the updated image to appear in the actual feed. Unlike Facebook, there is no way to force an immediate update. If you need a LinkedIn post to show the correct image right away, the safest approach is to get your OG tags perfect before the URL is first shared. For already-shared URLs, use the Post Inspector, wait a few hours, and check again. LinkedIn also has a known issue where images hosted on certain CDNs take longer to update, so hosting your OG images on a fast, reliable CDN helps.
Discord, Slack, and Messaging App Caches
Discord caches link previews per-channel, so pasting the same URL in a new channel may show the updated image while the original channel keeps the old one. There is no official way to clear Discord's cache, but deleting and re-posting the message sometimes triggers a re-fetch. Slack caches link unfurls and refreshes them when you share a URL in a new conversation. For persistent Slack caching, appending a query parameter (like ?t=1) to the URL forces a fresh unfurl. iMessage and WhatsApp cache previews on the device level, so clearing the conversation or the app cache may be necessary to see updated images.
Proactive Cache-Busting Strategies
Rather than fighting cache refreshes after the fact, build cache-busting into your workflow. Use versioned image URLs by appending a hash or timestamp parameter: 'https://yoursite.com/og.png?v=abc123'. When you update the image, change the parameter, and platforms treat it as an entirely new URL with no cached version. Another approach is to include a content hash in your image filename, so the URL changes whenever the image content changes. If you use a CMS or publishing platform, set up a webhook that pings the Facebook and LinkedIn scrape endpoints automatically whenever content is updated. This keeps your social previews fresh without any manual intervention.
Generate your OG image in seconds
Paste a title, pick a brand color, and get production-ready social cards for every platform — with framework-specific meta tag snippets included.
Generate Fresh OG Images Instantly