When you update an image on a webpage, Facebook often keeps showing the old thumbnail in link previews. This happens because Facebook caches the page’s metadata. This guide shows you how to force Facebook to refresh that cache so your updated image appears correctly in shares and messages.
What You’ll Need
- Access to the webpage whose link preview you want to fix
- The exact URL of that page (including the https:// part)
- A Facebook account (you don’t need to be logged in for the debugger, but it helps for some features)
Step-by-Step
- Verify your page’s meta tags. Open the HTML source of your webpage and confirm that the
og:imagemeta tag points to the new image URL. Also check that the image file itself is accessible—open the image URL directly in a browser to make sure it loads and isn’t blocked by a login or hotlink protection. - Go to the Facebook Sharing Debugger. In a browser, navigate to
developers.facebook.com/tools/debug/. This is Facebook’s official tool for inspecting how it reads your page. - Paste your URL. In the input field labeled “URL to debug,” enter the full, exact URL of the page you changed. Click the blue “Debug” button.
- Click “Scrape Again.” The debugger will show the information Facebook currently has cached. Look for a button that says “Scrape Again” or “Fetch new scrape information.” Click it. This forces Facebook to re-read your page’s meta tags and update its cache.
- Check the preview. After the scrape completes, scroll down to the “Share Preview” section. It should now display the new image. If it still shows the old one, wait a few minutes and repeat the scrape.
- Test in a real post. Paste your URL into a Facebook post or Messenger chat. The preview should show the updated image. If it doesn’t, try adding a query string to the URL (like
?v=2) to create a slightly different URL that Facebook will treat as new—but remember to use the original URL for the final share.
Common Mistakes
- Forgetting to update the og:image tag. If you only replaced the image file but didn’t update the meta tag in the HTML, Facebook will still look for the old URL. Always edit the tag first.
- Using a relative image path. The
og:imagetag must contain an absolute URL (starting withhttps://), not a relative path like/images/photo.jpg. Facebook cannot resolve relative paths. - Image too large or too small. Facebook recommends images at least 1200×630 pixels for link previews. If your image is smaller, it may be ignored or displayed poorly.
- Scraping the wrong URL. If your page has tracking parameters (like
?utm_source=facebook), Facebook treats that as a different URL. Debug the exact URL you intend to share, and make sure you’re not sharing a version with parameters that you didn’t debug. - Not waiting after the scrape. Facebook’s cache update isn’t always instant. Sometimes it takes a few minutes to propagate. Don’t give up after one try.
Tips
- Use a unique image URL. If you change the image file but keep the same filename, Facebook’s cache might not notice the file changed. Rename the file (e.g.,
image_v2.jpg) and update the og:image tag accordingly. This makes it easier for Facebook to detect a change. - Check other social platforms. Twitter/X, LinkedIn, and others also cache link previews. They each have their own debugger tools (like Twitter’s Card Validator). Use them if you need to update previews there too.
- Set a default og:image. If your page dynamically selects an image, ensure there’s always a fallback og:image tag so Facebook never has to guess.
- Use the debugger’s “Show existing scrape info” feature. Before scraping, review what Facebook currently sees. This helps you confirm whether the issue is a cache problem or a tag problem.
Troubleshooting
If the debugger shows an error: Common errors include “Could not retrieve data from URL” or “Object at URL doesn’t exist.” These usually mean the page is not accessible to Facebook’s crawler. Check that the page isn’t behind a login, doesn’t block bots via robots.txt, and that the server isn’t returning a 404 or 500 error.
If the old image still appears after multiple scrapes: The issue is likely not the cache but the meta tag itself. Open the page source and search for og:image. Make sure there are no typos, the URL is correct, and that it’s in the <head> section of the HTML. Also, ensure there isn’t a plugin or script overriding it.
If the new image appears in the debugger but not in a post: Facebook may have cached the URL from a previous share. Try sharing the URL with a query string (e.g., ?fbclid=refresh) to bypass the cache. Once the new preview appears, share the clean URL—the cache should now be updated for that URL too.
If the image is not loading at all: Test the image URL in a browser. If it doesn’t load, the file may be corrupted, the server may be down, or the image format may not be supported (Facebook supports JPG, PNG, GIF, and WebP). Also, check that the image does not exceed Facebook’s size limit (8 MB).
Frequently Asked Questions
Q: How long does it take for Facebook to update the link preview?
A: After using the debugger’s “Scrape Again,” the update is usually immediate. However, in some cases, it can take a few minutes to propagate across Facebook’s servers. If you don’t see it right away, wait 5–10 minutes and check again.
Q: Do I need to be logged into Facebook to use the debugger?
A: No, you can use the Sharing Debugger without logging in. However, logging in may give you access to additional features like viewing the last scrape time and error details.
Q: Will the debugger work for any URL, or only for pages I own?
A: It works for any public URL. You can debug any page, even if you don’t own it. But you can only fix the meta tags on pages you control.
Q: What if my page uses JavaScript to load the image?
A: Facebook’s crawler does not execute JavaScript. The og:image tag must be present in the raw HTML source. If your image is loaded dynamically, you need to either add a static og:image tag or use server-side rendering to include it.
Q: Can I change the link preview title and description too?
A: Yes, the same process applies. Update the og:title and og:description meta tags, then scrape the URL again in the debugger.
Q: Why does the preview show a different image than the one I set?
A: This can happen if there are multiple og:image tags, if the page has a default image that overrides yours, or if Facebook is picking an image from the page content instead. Ensure your og:image tag is the first one and that the image meets Facebook’s recommended dimensions.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Spotify Jam Not Working on Mobile? Fixes That Work
- Windows 10 No Internet Secured WiFi Error Fix
- Multi-Cloud GPU Failover Design Guide
- Error Code Currant Destiny? Meaning & Fixes
- How to Set a Timer on iPhone (iOS 18 & 17)
- Block Clipboard Access on Android: Step-by-Step