What is a Open Graph Preview?
An Open Graph preview shows what a link will look like when someone pastes it into a chat, a feed or a post. The card is drawn from `og:` tags in the page's head — a title, a description, an image and the URL itself — not from the page's visible content.
The protocol was introduced at Facebook in 2010 and is now read by LinkedIn, Slack, Discord, WhatsApp, Telegram, iMessage and most others. X uses its own `twitter:` tags but falls back to Open Graph. That is why one well-built set of tags covers almost every platform, with `twitter:card` added to choose the large-image layout.
The image does most of the work. The standard size is 1200 × 630 px, a 1.91:1 ratio, and platforms crop from the centre when the ratio is off. Anything under 200 × 200 px is usually dropped entirely, which is how a carefully written post ends up as a bare grey link.
How to preview a social card
- Type the title as it appears in the page's `og:title`, not the browser tab title — they are often different.
- Paste the description. Keep it under about 155 characters; the counter warns when you pass it.
- Add the absolute image URL. A relative path cannot be fetched by a scraper, so the card falls back to no image.
- Enter the page URL. Its host is shown above the title, the way most platforms render the source.
- Read the card and adjust. If the title wraps past two lines, shorten it — every platform truncates there.
- Copy the values into your meta tags. This preview does not fetch the live page, so it cannot tell you whether the tags are already deployed.
Open Graph Preview limits and rules
| Item | Limit |
|---|---|
| Card ratio | 1.91:1 — 1200 × 630 px is the standard size |
| Minimum image | About 200 × 200 px; smaller images are often dropped |
| Image size cap | 5 MB on most platforms, 8 MB on some |
| Title truncation | Two lines, roughly 60–70 characters |
| Description truncation | Two to three lines, roughly 155 characters |
| URL format | Must be absolute and publicly reachable; no auth, no localhost |
| Live fetching | Not done — browsers block cross-origin scraping, so the card is drawn from your input |
| Platform differences | Facebook, LinkedIn and Slack crop and wrap slightly differently |
When to use it
- Writing a title that fits two lines before it is published, rather than discovering the truncation in a feed.
- Checking that a social image has enough contrast and no text near the edges where crops happen.
- Explaining to a client why their link preview looks empty — usually a missing `og:image` or a relative URL.
- Drafting metadata for a launch post without touching the live page.
- Comparing two descriptions side by side to see which one reads better in a card.
Is it private?
Everything runs inside your browser. Your text and files are never uploaded, never stored and never seen by anyone else — including me. You can use the tool with the network tab open and watch no request leave the page. Closing the tab erases the input.
Frequently asked questions
No, and no browser-only tool can. Reading another site's HTML requires a cross-origin request that the target server almost never allows, so every “URL preview” tool either asks a server to fetch the page or draws from values you type. This one does the latter, which keeps it private and dependency-free.
Each platform has its own layout, crop and truncation rules, and they change without notice. The preview shows the common shape: host, two-line title, two-line description, 1.91:1 image. Treat it as a layout check, not a pixel-perfect mock.
1200 × 630 px, under 5 MB, JPEG or PNG, on an absolute HTTPS URL. That ratio survives the crops on Facebook, LinkedIn, Slack and X. Keep text at least 80 px from every edge, because some surfaces crop tighter than others.
Caching. Facebook and LinkedIn store scraped cards for days or weeks. Force a refresh with each platform's debugger — Facebook's Sharing Debugger and LinkedIn's Post Inspector both re-scrape on request. X rebuilds the card the next time the URL is posted.
Yes, to choose the layout. Without it, X falls back to a small square image rather than the wide card. `summary_large_image` is the value that gives the 1.91:1 presentation most sites want.
No. The card is rendered from React state in your browser. The image is loaded from its URL by your browser, exactly as it would be on a web page — so use a URL you are comfortable requesting.
Related tools
Written and maintained by Md. Nur Hossain Repon.