Free Online Open Graph Preview
Preview how a page looks when shared on social platforms.
The server reads the page and fills the fields from its Open Graph, Twitter, title, and description tags. You can edit the result in the manual tab.
Recommended image size is 1200 × 630 pixels (1.91:1). Use an absolute HTTPS URL.
Share previews
Generated meta tags
Previews are approximations. Each platform crops images, truncates text, and may fall back to its own metadata when a tag is missing.
About the Open Graph Preview
A link shared in a chat or on a social network is rarely just a URL. Most platforms turn it into a card with a title, a short description, and an image, all pulled from the page's metadata. Open Graph tags were introduced by Facebook for this purpose and are now understood by LinkedIn, Slack, Discord, and many others. X uses its own Twitter card vocabulary but overlaps heavily. This tool shows a rough preview for four common presentations and writes the tags that produce them.
Two ways to start
- Fetch from a URL: the server reads an existing page, resolves the important tags, and fills the form. This is useful for auditing a live page before a redesign.
- Manual entry: type a title, description, image, site name, and page URL to experiment with copy before publishing.
Each platform has its own personality. Facebook favors a large 1.91:1 image with a bold headline and a domain line in small capitals. X displays a wide image above the title and may show a domain at the bottom. LinkedIn often uses a smaller thumbnail beside the headline, so a busy image with tiny text becomes unreadable. WhatsApp renders a compact bubble with a square thumbnail, a two-line title, and a short description, which means the most important words must survive aggressive truncation. The previews here are stylized approximations, not pixel-perfect clones, but they make the trade-offs visible.
Image handling is the most common source of broken previews. Platforms require an absolute URL, usually HTTPS, and many reject images that are too small, too large, or served with a restrictive content type. A 1200 by 630 pixel JPEG or PNG is a safe default. If the image cannot be loaded, the preview shows a placeholder, just as a real platform would omit the visual rather than wait forever. A missing image does not necessarily break the card, but it reduces click-through compared with a strong visual.
The generated block includes the core Open Graph properties, a site name, a canonical page URL, and a Twitter card declaration. Paste it inside the document head, replace the placeholder values, and test the live URL with each platform's own debugger. Caching is the next trap: platforms store previews for days or weeks, so an update may not appear immediately. Re-scraping through a platform's debugging tool forces a refresh. Social metadata should also agree with the page's visible title; a mismatch looks like clickbait and erodes trust.
How to use this tool
- Paste a public URL and fetch its tags, or switch to manual entry.
- Edit the title, description, image, site name, and page URL.
- Compare the four previews and check that the important text stays visible.
- Copy the generated meta tags or download them as an HTML snippet.
Frequently asked questions
Why does the real preview look different?
Platforms use their own layouts, fonts, image cropping, and fallback rules. They may also ignore tags they consider low quality or stale. Use this tool to check content and proportions, then confirm with the platform's official debugger.
What image size should I use?
1200 by 630 pixels is a widely compatible choice for a large landscape card. Keep important text away from the edges, use a high-contrast composition, and serve the image over HTTPS with a standard format such as JPEG or PNG.
Do I need both Open Graph and Twitter tags?
Not strictly. X can fall back to Open Graph, but explicit Twitter tags give you control over the card type and title. Including both is the safest approach for sites that are shared widely.