You changed the OG image or copy and want to confirm it looks right before deploying. You're choosing a hero image and want to see whether the focal point will survive the 1.91:1 crop. You're writing the title/description copy and want to know where each platform will clip it. You inherited a page with no OG tags and want to draft them by previewing the rendered card.

(absolute URL, 1200×630 ideal) (for the X/Twitter big-image style)

This is a static preview, not a live fetcher. Real platforms scrape your page from their servers; if your real site has a different image, this tool won't catch it. Use the platforms' own debuggers (Twitter's card validator , Facebook's Sharing Debugger, LinkedIn's Post Inspector) for the authoritative check. Image URLs must be absolute. /og.png won't work — scrapers don't know your origin. Image must be publicly reachable. Authentication walls, CDNs that require referer, or hot-link protection will leave you with a broken card. Aspect ratio matters. 1.91:1 (1200×630 is canonical) renders well on every platform. Square or portrait crops badly. File size matters. Some scrapers reject images over 8 MB; aim for sets the left border colour on Discord embeds.

OG Tag Preview

Paste OG meta tags or fill title/description/image — preview share cards as they look on Twitter/X, Facebook, LinkedIn, and Discord.

Paste meta tags (optional — fields below are filled from this if provided)

Title

Site URL

Description

Image URL

Site name

Twitter / X (summary_large_image)

Facebook

Discord

What is this for?

When you share a link in Twitter/X, Facebook, LinkedIn, Discord, Slack or any modern chat or social app, the link is unfurled into a "card" — title, description, and image — based on the Open Graph meta tags in the page head. The various platforms render these cards differently and clip text at different lengths. This tool gives you side-by-side previews of how the same content will appear in each, without having to actually share the URL on every platform.

When to use it

You changed the OG image or copy and want to confirm it looks right before deploying.
You're choosing a hero image and want to see whether the focal point will survive the 1.91:1 crop.
You're writing the title/description copy and want to know where each platform will clip it.
You inherited a page with no OG tags and want to draft them by previewing the rendered card.

The minimum tags

<meta property="og:title" content="…">
<meta property="og:description" content="…">
<meta property="og:image" content="https://…"> (absolute URL, 1200×630 ideal)
<meta property="og:url" content="https://…">
<meta property="og:type" content="website">
<meta name="twitter:card" content="summary_large_image"> (for the X/Twitter big-image style)

Common gotchas

This is a static preview, not a live fetcher. Real platforms scrape your page from their servers; if your real site has a different image, this tool won't catch it. Use the platforms' own debuggers (Twitter's card validator, Facebook's Sharing Debugger, LinkedIn's Post Inspector) for the authoritative check.
Image URLs must be absolute. /og.png won't work — scrapers don't know your origin.
Image must be publicly reachable. Authentication walls, CDNs that require referer, or hot-link protection will leave you with a broken card.
Aspect ratio matters. 1.91:1 (1200×630 is canonical) renders well on every platform. Square or portrait crops badly.
File size matters. Some scrapers reject images over 8 MB; aim for <1 MB to keep first-load snappy.
Cache invalidation is real. Once a platform has scraped your URL, it caches the card. Use the platform debuggers to force a re-scrape.
Title/description length limits vary. Twitter/X clips title around 70 chars; Facebook around 88; LinkedIn around 100. Front-load the important words.
Discord prefers theme-color. Adding <meta name="theme-color" content="#xxxxxx"> sets the left border colour on Discord embeds.