Open Graph Preview
Preview how a link's Open Graph card looks when shared on social.
Prints the domain in small caps above the title and gives the description the least room of any platform — often a single line.
No Open Graph or Twitter tags found.
How Open Graph previews work
When a link is shared on Facebook, LinkedIn, Slack, Discord, or most chat apps, the platform scrapes your page's og: meta tags to build the preview card. The essentials are og:title, og:description, og:image (1200×630 works everywhere), and og:url. Paste your tags above to see the card and confirm nothing is missing. Parsing happens locally — no request is made to fetch the page.
Built and maintained by Meet Shah · Last updated
What this tool is used for
- Checking how a link will look before you share it anywhere.
- Diagnosing why a shared link shows no image or the wrong title.
- Confirming a tag change took effect after a deploy.
- Comparing how the same page renders across card types.
- Reviewing a partner's page before linking to it.
How it works in practice
A worked example
A title reads well in the editor and you want to see where each platform will cut it before the link goes anywhere.
<meta property="og:title" content="How we cut our build from fourteen minutes to ninety seconds"> <meta property="og:description" content="A step-by-step account of the profiling, the three changes that mattered, and the two that did nothing at all."> <meta property="og:image" content="https://example.com/og.png"> <meta property="og:url" content="https://example.com/blog/faster-builds">
Rendered per card: X large · X summary · Facebook · LinkedIn · Slack · Discord · WhatsApp Each one clamps the title and description to its own number of lines rather than to a character count.
Seven cards from one set of tags, because the tags are shared and the presentation is not. Every platform wraps into a fixed-height box and cuts at a line boundary, so what survives depends on the width of that box and the size of its font — which is why the previews here clamp lines rather than counting characters. A sixty-character title is a useful rule of thumb and not a rule: the same string can fit one card and lose its last two words on a narrower one.
The edge case that catches people
None of these platforms publish their exact cropping and truncation rules, so a preview is a model rather than a promise, and the honest version of that is to show several and look for the one that breaks. What compounds it is caching: each platform scrapes a URL once and holds what it found, often for days, so the first share of a page is the one that matters and a fixed tag may not appear until the cache is cleared through that platform's own debugger. Preview first, share second.
When not to use this tool
This reads tags you paste, not a URL you type, so it cannot tell you whether a live page actually serves them. That distinction matters more than it sounds: a page behind a login, one that blocks unfamiliar user agents, or one that injects its tags with JavaScript will hand a scraper nothing at all, and the tags you pasted here were never the problem. When a real card is wrong, fetch the page the way a crawler would — a plain request with no cookies and no scripting — and check what comes back before touching the markup.
Frequently Asked Questions
- Why does my link preview not match this?
- Because every platform crops and truncates differently and none publishes the exact rule. A preview shows the shape and roughly where truncation falls; the real card depends on the platform's current layout, which changes without notice.
- Why is the old image still showing after I fixed it?
- Aggressive caching. Every platform scrapes once and holds the result, often for days. Facebook's Sharing Debugger and LinkedIn's Post Inspector both force a re-scrape; X no longer offers one, so a cache-busting query string on the image URL is the practical fix.
- What image size is safe everywhere?
- 1200×630, a 1.91:1 ratio that Facebook, LinkedIn and X's large card all accept without cropping. Keep it under about 5 MB, serve it from an absolute HTTPS URL, and do not put it behind a redirect — most scrapers will not follow one.
- Where should the important content sit?
- In the centre. Platforms crop toward different ratios, so a headline near the top edge or a logo in a corner is the first thing lost. Designing to the safe centre rather than to the full canvas is what makes one image work in several places.
- Do previews affect search ranking?
- No — Open Graph is not a ranking signal. What it affects is whether a shared link gets clicked, which drives real traffic through an entirely social mechanism. The two are often conflated because both are called metadata.
Common errors and gotchas
- Assuming what you see is what a platform will show, since each renders and crops differently.
- Forgetting platforms cache aggressively, so an old card persists after a fix.
- Checking a staging URL whose tags point at production, or the reverse.
- Overlooking that a login wall or a bot block stops the platform fetching the tags at all.
- Testing a page whose tags are injected by JavaScript, which most scrapers never run.