og:image tag was missing or pointed to a different image at that time, Facebook keeps the old version. Use the Facebook Sharing Debugger to scrape the URL again and force a cache refresh. Check with the link preview debugger.You share a link on Facebook and the wrong image shows up. Or no image at all. Or the title is outdated. Or the description is pulled from the wrong part of the page. This is one of the most common and frustrating problems on Facebook — and it happens because of how Facebook caches and reads your page's metadata.
The good news: link preview problems are almost always fixable. This guide explains exactly why Facebook link previews break, how Facebook decides what to show, and how to fix every common issue step by step.
When someone shares a link on Facebook, Facebook's crawler visits the URL and reads the page's Open Graph (OG) meta tags to build the preview card — the image, title, and description you see in the feed. Previews break when this process goes wrong.
og:image, og:title, and og:description meta tags, Facebook guesses what to show. It picks a random image from the page, pulls text from the body, and the result is unpredictable.og:image tag points to an image that returns a 404, is blocked by robots.txt, requires login, or is on a server that blocks Facebook's crawler.Facebook's crawler follows a specific priority order when building a link preview:
og:image meta tag — this is the primary source. If present and valid, Facebook uses this image for the preview. This is what you should always set.og:image:url — an alternative to og:image. Works the same way but is less commonly used.The same priority applies to titles (og:title → <title> tag) and descriptions (og:description → <meta name="description"> → first paragraph of body text).
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="A short description of the page.">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:url" content="https://example.com/page">
<meta property="og:type" content="website">
The og:image URL must be an absolute URL (starting with https://), not a relative path. Facebook's crawler cannot resolve relative paths.
Facebook is using a cached version of your page from before you added or updated the og:image tag. Scrape the URL in the Sharing Debugger to force a refresh. Use the link preview debugger to check what Facebook currently sees.
Either the og:image tag is missing, the image URL returns a 404, or the image is smaller than 200×200 pixels. Check that the image URL is publicly accessible — open it directly in a browser. If the server requires authentication or blocks bots, Facebook's crawler can't reach it.
Facebook shows a small square preview when the image is smaller than 600×315 pixels. Upload an image at 1200×630 to get the full-width preview card. Check your image dimensions before updating the tag.
Facebook is reading an old cached version or falling back to the <title> tag / body text because your og:title and og:description tags are missing. Add the tags and re-scrape.
The image aspect ratio doesn't match Facebook's 1.91:1 display ratio. Facebook center-crops images that don't fit, cutting off edges. Use a 1200×630 image to avoid cropping. Preview the result with the post preview tool.
Mobile and desktop Facebook apps cache independently. Scrape the URL in the Sharing Debugger to clear both caches. Also check that the image loads quickly — slow-loading images may time out on mobile connections.
Follow these steps in order. Most link preview problems are fixed by step 3.
Make sure your page has all five core OG tags in the <head>: og:title, og:description, og:image, og:url, and og:type. The og:image must be an absolute URL pointing to a publicly accessible image file.
The image should be 1200×630 pixels (1.91:1 ratio) for the full-width preview card. Images under 600×315 display as a small square. Verify with the image size checker.
Open the Facebook Sharing Debugger, paste your URL, and click "Scrape Again" (click it twice to be sure). This forces Facebook to re-crawl your page and update the cached preview. You can also use the link preview debugger to check what Facebook currently sees.
Open the og:image URL directly in a browser. If it returns a 404, redirects, requires login, or shows a "403 Forbidden" error, Facebook can't access it either. The image must be on a publicly reachable server with no authentication.
If your URL redirects (e.g., HTTP → HTTPS, non-www → www), make sure the OG tags are on the final destination page, not the redirect source. Facebook follows redirects but reads tags from the final URL.
After fixing, use the post preview tool to see exactly how your link will appear in the Facebook feed. This catches image cropping and text truncation before your audience sees it.
Getting the image size right is the difference between a full-width preview card that drives clicks and a tiny square thumbnail that gets ignored.
| Image Size | Result |
|---|---|
| 1200×630 (recommended) | Full-width preview card, sharp on all devices |
| 600×315 | Full-width preview but may look soft on high-density screens |
| Under 600×315 | Small square thumbnail, less prominent in feed |
| Under 200×200 | May be ignored entirely — no image shown |
| Over 8 MB file size | Facebook may fail to download the image |
Use the image size checker to verify your image meets these requirements before updating your OG tags.
Always test your link preview before sharing publicly. A broken preview is the first thing your audience sees — and you can't edit it after posting.
og:image through the image size checker to confirm it meets the 1200×630 minimum for a full-width card.og:image tag was missing or pointed to a different image at that time, Facebook keeps the old version. Use the Facebook Sharing Debugger to scrape the URL again and force a cache refresh. Check with the link preview debugger.og:image meta tag, the image URL returns a 404, the image is blocked by robots.txt or requires authentication, or the file is larger than 8 MB. Check that your image URL is publicly accessible by opening it directly in a browser.og:image, you must manually clear the cache by scraping the URL in the Sharing Debugger.