Facebook · Open Graph
Facebook Sharing Debugger alternative
SocialImageKit is an independent tool — not affiliated with Meta or Facebook. Meta’s officialSharing Debuggerstill owns “Scrape Again” and cache refresh. What we add: an instant, no-login preview of the tags crawlers see so you fix the page before you scrape.
- 1200 × 630Image size
- 1.91:1Aspect
- 8 MBMax file
- 200 × 200Min size
How it works
How Facebook builds a link preview
When someone shares a URL, Meta’s crawler fetches the public HTML and reads Open Graph tags. The usual fields are og:title,og:description, og:image,og:url and og:type. Tags must exist in the first HTML response — not only after client-side JavaScript.
For the image, use 1200×630 (1.91:1). Meta documents a200×200 absolute minimum and recommends at least 1200×630 for large link cards. Keep the file under 8 MB, use an absolute https URL, and prefer sizes closer to a few hundred KB for fast mobile loads.
Details:Facebook image sizes·OG image size guide·LinkedIn Post Inspector.
Stuck preview
Why Facebook shows the wrong image or old preview
- Cache. Facebook keeps a scraped copy of your tags. Editing a post does not refresh it. After the live page is correct, openSharing Debuggerand use Scrape Again.
- Image too small. Files under ~600×315 often render poorly. Rebuild at 1200×630.
- Image not public. Hotlink protection, signed URLs, or a 403 to bots looks like a missing image in Facebook.
- Redirects. Long chains or a final URL that differs from the one you scraped can leave the feed on an older card.
- robots.txt. If Meta’s crawler is blocked, Debugger cannot read the page you think you fixed.
- Missing og tags. Relative
og:imagepaths and tags injected only after JS are common failures. - Same image URL after a change. Updating pixels at an unchanged path often keeps the cached file. Prefer a new path, then scrape again.
No Facebook login
Preview your Facebook link now
Paste the public URL into the Link Preview Checker. Confirm title, description and image, then use official Sharing Debugger → Scrape Again if the feed is still stale.
Before you share
Checklist before you share
- Canonical https URL opens without login.
- og:title, og:description, og:image, og:url and og:type appear in View Source.
- og:image is an absolute https URL returning 200 anonymously.
- Image is about 1200×630 (1.91:1), under 8 MB (aim under 1 MB).
- Important text sits inside a safe margin — Facebook crops edges.
- If artwork changed, use a new image path so the cache cannot reuse the old file.
- Run this site’s Link Preview Checker, then Scrape Again in official Sharing Debugger.
Troubleshoot
Common problems and fixes
Scroll sideways on small screens. Start with cache and absolute URLs — they cause most “wrong image” reports.
| Common problem | Cause | Fix |
|---|---|---|
| Old image still shows | Facebook cached an earlier scrape of the same URL. | Fix live tags, prefer a new image path, then Scrape Again in Sharing Debugger. |
| Small or soft card | Image under 600×315, or far from 1.91:1. | Use at least 1200×630 and set og:image:width / height. |
| No image at all | Missing og:image, relative path, or file blocked to anonymous GET. | Absolute https URL that returns 200 in a private window. |
| Wrong title or description | Tags only injected by client JS, or a different URL was scraped. | Put tags in the first HTML response; scrape the canonical https URL. |
| Debugger cannot fetch the page | robots.txt blocks facebookexternalhit, auth wall, or redirect loop. | Allow Meta’s crawler, remove login gates on the public URL, shorten redirects. |
Next steps
Related tools and guides
- Link Preview Checker— see tags crawlers receive
- OG image size— default canvas and file limits
- LinkedIn Post Inspector— LinkedIn cache and 1200×627 workflow
- Facebook image sizes— platform-specific notes
- OG Image Generator— export a 1200×630 PNG
- og:image not showing— general missing-image checklist