Fill in the fields and get the Open Graph and Twitter Card tags to paste into your page's head, with a live preview of how the card will look when someone shares it. Values are escaped properly for HTML attributes, which matters more than it sounds — a single unescaped double quote in a title ends the content attribute early and silently breaks the tag, and that is by far the most common reason a share card comes out blank. The tool also checks the things that only fail after you publish: image URLs must be absolute, because social crawlers fetch them from their own servers and will not resolve a relative path, and titles and descriptions get length guidance against where each platform truncates. Empty fields are left out rather than emitted blank. Nothing is uploaded — the image is referenced by URL, never sent anywhere.
| Tag | Required | Notes |
|---|---|---|
| og:title | Yes | About 60 characters before truncation |
| og:description | Recommended | About 155 characters |
| og:image | Recommended | Absolute URL, 1200 × 630 |
| og:image:alt | Recommended | Describes the image to screen readers |
| og:url | Recommended | The canonical absolute URL |
| og:type | Yes | website, article, product… |
| twitter:card | Yes for X | summary_large_image is the usual choice |
Nearly always because the URL is relative, the image is behind authentication, or the platform has cached an earlier version. Social crawlers fetch the image from their own infrastructure, so it must be an absolute https URL that is publicly reachable. This tool flags relative URLs before you publish.
1200 by 630 pixels is the safe default for a large summary card — it is the ratio Facebook, LinkedIn and X all handle well. Stay under about 5 MB, and avoid putting important text near the edges, since platforms crop differently.
X falls back to Open Graph for most properties, so strictly you only need twitter:card to choose the layout. Including the rest costs nothing and gives you explicit control if you want a different title or image there than elsewhere.
Around 60 characters for the title and 155 for the description keeps you clear of truncation on the major platforms. Going over is not an error — the text is just cut off, usually mid-word, which reads badly.
Platforms cache aggressively. Use each platform's own debugger — Facebook's Sharing Debugger, LinkedIn's Post Inspector — to force a refetch. Nothing you change on your own page clears their cache on its own.
No. Tags are generated in your browser and the image is referenced by URL — it is never uploaded or proxied. Unpublished page titles and URLs are never sent anywhere.
Tags are templated from the fields, with every value escaped for a double-quoted HTML attribute — ampersands first, then quotes and angle brackets, in that order so entities are not double-encoded. That escaping is the difference between a working tag and a broken one: a single unescaped double quote in a title terminates the content attribute early and the rest of the tag becomes stray markup, which is the most common way hand-written Open Graph tags fail. Empty fields are omitted rather than emitted with an empty content attribute, since a blank og:description is worse than none — some crawlers prefer it over the fallback they would otherwise choose. Image and page URLs are checked for being absolute http or https: social crawlers fetch them from their own infrastructure and will not resolve a relative path, which is why a card that previews correctly in a local test can show no image once published. Title and description lengths are measured against the points at which the major platforms truncate. The preview card is rendered from the same values that produce the tags, so what you see cannot drift from what you copy.