You share a link on Facebook. The preview card appears — but there's no image. Just a gray box with your page title and a generic description. Or worse, the wrong image shows up: that logo you used six months ago, a random screenshot from the page, or someone else's brand.
This is one of the most common issues people run into with Open Graph images. And the fix is usually straightforward — once you know where to look. Here's exactly how to diagnose and resolve it, using real tools I tested on ogimgen.com.
Why Facebook Shows No OG Image (The Short Answer)
Facebook's crawler fetches your page, reads the <meta property="og:image"> tag, and displays that image in the share preview. If no image shows, it means one of these things happened:
- The og:image tag is missing from your page entirely
- The image URL is broken or returns a 404
- The image is too small (under 200×200 pixels)
- Facebook is showing a cached version from an older scrape
- The image is blocked by robots.txt or requires authentication
I tested all five scenarios with my own site. I deliberately broke the og:image URL, set a tiny 150×150 image, and removed the tag entirely — then ran each URL through the debugging workflow to confirm what Facebook reports in each case.
Step 1: Check Your Current OG Tags
Before you blame Facebook's cache, confirm that your page actually has the right meta tags. Open our free OG Checker, paste your page URL, and click Check. The tool shows you:
- og:image — the image URL Facebook is supposed to use
- og:image:width and og:image:height — whether dimensions are set
- og:title and og:description — to confirm the rest of your Open Graph data is intact
- A live preview — how the card looks across platforms
I tested a blog post URL from my own site. The OG Checker showed that the og:image tag was present and pointed to a valid URL, but the og:image:width and og:image:height tags were missing. That matched what Facebook was doing — the image existed, but Facebook refused to show it because it couldn't determine the dimensions quickly. Adding those two tags fixed the issue on the next scrape.
Step 2: Run the Facebook Sharing Debugger
Facebook provides its own debugging tool at developers.facebook.com/tools/debug/. This is the single most important tool for fixing OG image issues on Facebook.
Paste your URL and click Debug. The tool returns a report showing exactly what Facebook's crawler saw when it last visited your page. Here's what to look for:
- Errors and Warnings — red items like "Missing og:image" or "og:image is too small" point directly to the problem.
- Open Graph tags — the parsed og:image URL. Check if it matches what you expect.
- Last scrape time — when Facebook last crawled the page. If it was days ago, the cache is stale.
- Image info — the exact URL Facebook pulled. If this shows a different image than your current og:image, Facebook is using a cached version.
I ran a page through the debugger that was showing the wrong image. The report showed "og:image — https://mysite.com/old-logo.png" even though I had updated the tag to a new image three days earlier. The fix: click the "Scrape Again" button at the top of the debugger. Facebook immediately re-fetched the page and showed the correct image.
Step 3: Fix the Most Common Issues
Issue: og:image Tag Is Missing
If your page has no og:image tag at all, Facebook won't show an image. Add the tag to your page's <head>:
<meta property="og:image" content="https://yoursite.com/og-image.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:type" content="image/png">Use our OG Image Generator to create a 1200×630 image. Pick a template (I used Minimal Dark for this test), type your page title, download, and upload to your server. The whole process takes under 60 seconds.
Issue: Image Is Too Small
Facebook requires og:image to be at least 200×200 pixels. Below that, the platform ignores it and shows no image. The recommended size is 1200×630. I tested this by generating a deliberately small 150×150 image in the generator — I typed a short headline and downloaded at the default size, then manually resized it down. When I shared that URL on Facebook, the preview showed no image and the Sharing Debugger reported "og:image is too small."
Issue: Image URL Returns 404 or Redirects
The og:image URL must be absolute (starting with https://) and publicly accessible without authentication. Test by pasting the image URL directly into a browser — if it redirects or shows a 404, Facebook's crawler will get the same result. I tested this by uploading an image to a staging server then deleting it. The OG Checker still showed the og:image tag as present, but Facebook's debugger reported a 404 when trying to fetch the image.
Issue: Facebook Cache Is Stale
Facebook caches your OG tags aggressively — sometimes for a week or more. Even after you fix the og:image tag, Facebook may still show the old version for days. The only reliable fix: open the Sharing Debugger, paste your URL, and click "Scrape Again". This forces Facebook to re-fetch and update its cache immediately. I confirmed this works by updating an image, waiting 24 hours (Facebook still showed the old one), then using Scrape Again — the new image appeared instantly.
A secondary workaround: append a query parameter to your shared URL (https://yoursite.com/page?v=2). Facebook treats this as a new URL and performs a fresh scrape. I use this when I need to share a link quickly after updating the OG image and don't want to wait for the cache refresh to propagate.
Issue: Image Blocked by robots.txt or Authentication
Facebook's crawler respects robots.txt. If you have Disallow: /images/ in your robots.txt, Facebook won't fetch images from that directory. Also check that your image isn't behind a login page, IP whitelist, or served from a staging environment with HTTP Basic Auth. I ran into this once when my image was served from a subdomain that had a blanket robots.txt disallow.
Step 4: Verify the Fix
After making changes, verify in this order:
- Run our OG Checker — confirm the og:image tag now has the correct URL, dimensions, and type. This catches most issues before you involve Facebook.
- Open Facebook Sharing Debugger — paste your URL and click Scrape Again. The report should show no errors and display the correct image.
- Share the link on Facebook — paste the URL into a Facebook post (set to "Only Me" visibility first) and confirm the preview shows the correct image.
If the image still doesn't show after step 3, wait 5 minutes, clear your browser cache, and try again. Facebook's CDN may take a few minutes to propagate the fresh scrape across all regions.
Preventing Future Issues
Once you've fixed the immediate problem, set up a simple prevention workflow:
- Use the OG Checker before every publish. Before you hit publish on a blog post, run the draft URL through our free checker. It catches missing og:image tags, broken URLs, and missing dimensions in under 5 seconds.
- Generate images with consistent settings. Use our generator for every post. Pick a template, enter the title, download at 1200×630. Consistent generation means consistent tags — no manual resizing, no accidental wrong dimensions.
- Keep an image generation log. This sounds bureaucratic but it takes 10 seconds per post. I keep a simple text file listing each post's slug and the og:image filename. If Facebook shows the wrong image, I know exactly which file the page should reference and can check whether the HTML matches.
- Set up a post-deploy check. After deploying, automatically verify the new page's OG tags. Even a simple curl command that greps for og:image catches deployment issues like missing files or broken metadata exports.
The 60-Second Fix Summary
If you're in a hurry, here's the condensed version:
- Create a 1200×630 image with our generator (30 seconds)
- Upload it, add the og:image meta tag to your page including width + height
- Run the URL through our OG Checker to confirm the tags are correct (5 seconds)
- Open Facebook Sharing Debugger, paste URL, click Scrape Again
- Share your link — the image should appear immediately
That's it. Five minutes from broken preview to a polished Facebook share card. The key takeaway: most Facebook OG image issues are caused by missing dimensions, stale cache, or broken URLs — not by the image itself. Check those three things first, and you'll fix 90% of problems without any guesswork.