// free tool
OG Image Debugger
Paste any URL. See how its OG image renders on Facebook, X, LinkedIn, Slack, Discord, and iMessage in parallel. Fix common unfurl problems instantly. Free, no signup.
What this debugger checks
- og:title, og:description, og:image, og:type, og:site_name
- twitter:card, twitter:title, twitter:description, twitter:image
- Document <title> and meta description fallbacks
- Canonical URL declaration
- Image-URL absolute vs relative resolution
- http:// vs https:// safety
- HTTP status and redirect chain
- Common platform unfurl pitfalls
Frequently asked questions
Is the debugger really free?
Yes — paste any URL, get a full breakdown of its OG and Twitter Card meta tags plus per-platform previews. No signup required for the debugger itself; the optional 'Generate with Linkshot' CTA leads to a 7-day free trial without a credit card.
Why do I need a debugger? Doesn't Facebook have one?
Facebook has its own Sharing Debugger, X has a Card Validator, LinkedIn has a Post Inspector — all useful but each only tests one platform. Linkshot's debugger fetches your meta tags once and shows you what FB, X, LinkedIn, Slack, Discord, and iMessage will each render in parallel. Faster feedback, fewer browser tabs.
My OG image is not showing on Facebook — does this debugger help?
Yes. Common causes: relative URL instead of absolute, http:// instead of https://, image too small or too large, response is HTML/redirect instead of an image binary, or the platform cached an older version. The debugger surfaces the first four immediately. For the cache issue, use Facebook's own Sharing Debugger to force a re-scrape (the debugger links out to it).
Why do platforms cache OG images?
To make link unfurls fast. When someone shares a URL, the platform fetches the page once, caches the meta tags + image, and reuses them for every subsequent share. Cache TTLs vary: Facebook ~30 days, X ~7 days, LinkedIn ~7 days, Slack indefinite per workspace. To bust the cache, use the per-platform debugger — each platform has a 'Scrape Again' button.
How does the platform preview render?
Each platform has its own card UX. Linkshot's debugger renders a simplified visual approximation of how each platform's card will look using your meta tags — domain, title, description, image. The previews are designed to surface obvious problems (missing image, mismatched aspect ratio, truncated title) rather than be pixel-perfect.
My page returns 200 but the debugger reports an error — why?
Possible causes: page returns HTML but the debugger timed out (8s limit), page response is too large (1.5MB cap), or the response is not text/html. Some pages also require JavaScript to render meta tags client-side; this debugger only reads server-rendered HTML. Linkshot's full screenshot pipeline runs JavaScript, so client-rendered pages still work for OG image generation.
How do I fix a missing or broken OG image?
Start with Linkshot. Drop one meta tag in your <head> with your page URL as a parameter — Linkshot screenshots your live page at 1200×630 and returns a guaranteed-valid og:image. The debugger then verifies the result across all platforms. The full loop: paste URL → fix what's broken → regenerate with Linkshot → re-test in debugger.
Can I debug a URL behind authentication?
No — the debugger fetches the URL anonymously, the same way social-media crawlers do. If your page requires auth, social platforms can't render previews either. The fix is usually to make the OG meta tags reachable without auth (server-render them on the public-facing version), even if the rest of the content is gated.
Generate OG images that pass every debugger
Linkshot screenshots your real page and returns a guaranteed-valid og:image. $9/mo, 7-day free trial, no credit card.
7-day free trial · no credit card required