Free tool · Social

Open Graph Preview

Paste a URL — see exactly how it previews on Twitter/X, LinkedIn, Slack, and Facebook. Catches the most common cause of broken social shares: a missing or malformed og:image.

How to use this previewer

  1. Paste the URL. Any public URL — we fetch it server-side, the same way a social platform's crawler would.
  2. We extract the tag fallback chain. og:title/description/image first, falling back to <title> and the meta description when og:* tags are missing, plus every twitter:* override.
  3. Compare platform previews. See how the same tags render across Twitter/X, LinkedIn, Slack, and Facebook's different fallback rules.

What this tool extracts

  • Open Graphog:title, og:description, og:image, og:image:alt, og:site_name, og:type.
  • Twitter Card overridestwitter:card, twitter:title, twitter:description, twitter:image, twitter:site, twitter:creator.
  • Fallbacks when og:* is missing — title falls back to the page's <title> tag, description falls back to <meta name="description">.
  • Absolute image URLs — a relative og:image path is resolved against the page's final URL (after following redirects), so the preview doesn't break on a relative path that only works from the original document.
  • Favicon — read from a <link rel="icon"> tag, for the browser-tab-style detail in some platform previews.

Frequently asked questions

Why don't all platforms show the same preview?

Each platform reads a different combination of tags. Twitter prefers twitter:* tags but falls back to og:*. LinkedIn reads only og:*. Slack uses both plus oEmbed. Facebook uses og:* exclusively. A URL can look great on one platform and broken on another.

What size should my og:image be?

1200×630 pixels (1.91:1 aspect ratio). This is the size that works across every platform. Anything smaller gets upscaled (blurry). Anything wildly different may be cropped or rejected.

Why is my og:image showing the old version after I updated it?

Facebook and LinkedIn cache OG images aggressively. Update by submitting your URL to https://developers.facebook.com/tools/debug/ and https://www.linkedin.com/post-inspector/ to force a re-scrape.

Do I need both og:title and twitter:title?

Strictly no — Twitter falls back to og:title. But if you want different copy per platform (longer for LinkedIn, punchier for Twitter), setting both lets you control each separately. Most sites just set og:* and let everything cascade.

Is this an actual screenshot of how Twitter/LinkedIn render my link?

No — it reconstructs the preview from the tags it finds, applying each platform's documented fallback chain (Twitter reads twitter:* first, falls back to og:*; LinkedIn and Facebook read og:* only). It doesn't call Twitter's or LinkedIn's own preview APIs, so a platform-side quirk or an already-cached older version (see the caching question above) can still look different from what this tool shows.

Never ship a broken share card

InBuild renders a per-route Open Graph image and the matching og: and twitter: tags on every page it generates — so links look right in Slack, LinkedIn and iMessage the first time someone shares them.