Make your links look good when they're shared. Fill in the title, description and image, or paste a page's HTML to read its current tags, and see the preview as Facebook, X, LinkedIn, Slack, Discord and WhatsApp show it. The image is checked for size and shape, and the tags are ready to copy as HTML or Next.js metadata.
Previews follow each site's current layout closely; the sites change their designs from time to time and may crop images differently in feeds.
<!-- Open Graph (Facebook, LinkedIn, WhatsApp, Slack, Discord) --> <meta property="og:type" content="website"> <meta property="og:locale" content="en_US"> <!-- X (Twitter) --> <meta name="twitter:card" content="summary_large_image">
When someone shares your page on Facebook, X, LinkedIn, WhatsApp, Slack or Discord, the app builds a preview card from a few meta tags in the page's <head>: the Open Graph tags (og:title, og:image and friends) and X's twitter: tags. This tool writes those tags for you, shows the card as each app draws it, and checks the things that most often go wrong: a missing or tiny image, the wrong shape, a relative address, no alt text. You can also paste a page's HTML to read the tags it already has and see what its shares look like.
Tip: Make one 1200×630 pixel JPG or PNG for each important page, with the main words of the title in big type and a clear picture. It works everywhere: Facebook, X large cards, LinkedIn, Slack and WhatsApp all use the same 1.91:1 shape.
Use 1200×630 pixels for a large card. Facebook needs at least 200×200 and shows anything under 600 px wide as a small thumbnail; X crops large-card images to 2:1 and summary images to a square, so keep the important part in the middle. JPG, PNG and WebP work; SVG, AVIF and HEIC don't. Keep the file under 5 MB for X and 8 MB for Facebook, and much smaller is better: a 150 KB JPG loads fast in every app.
The image must be reachable by the apps' crawlers: a full https:// address that opens without logging in, isn't blocked by robots.txt and doesn't depend on cookies. The preview here loads it in your browser, so if it doesn't appear, the crawlers probably can't load it either.
Facebook, LinkedIn and X store a copy of each card for days or weeks. After changing the tags, ask them to read the page again: Facebook's Sharing Debugger has a Scrape Again button, LinkedIn's Post Inspector refreshes when you inspect the URL, and X refreshes its cache on its own after about a week (adding a harmless query such as ?v=2 to the shared link gives a fresh card at once). WhatsApp, Slack and Discord also cache previews per link.
If the card is still wrong, check the live page's HTML rather than your template: themes, SEO plugins and tag managers sometimes add a second og:image, and apps usually take the first one they find. Paste the live source into this tool to see exactly which tags are there.
Put the tags inside the <head> of each page, with values for that page; the same image and title on every page wastes the chance to sell each one. In WordPress, an SEO plugin such as Yoast, Rank Math or All in One SEO writes them for you from fields under each post. In Next.js, use the metadata object (the Next.js tab here) or generateMetadata for pages with dynamic content. Shopify, Wix and Squarespace have social sharing settings in each page's SEO options.
Most people see the image before the title. A few large words on it, readable on a phone, raise clicks.
Keep text and faces away from the edges; X and some feeds crop the sides or the top and bottom.
A specific image for each article or product beats a site-wide logo every time.
/images/og.jpg works in your browser but not for crawlers. Always write the full https:// address.
Paste the published page's source to confirm there's only one og:image and the values are right.
A social title can be more conversational than the search title; a question or a number works well.
1200×630 pixels (a 1.91:1 shape) is the standard that works on Facebook, X large cards, LinkedIn, Slack and WhatsApp. The minimum Facebook accepts is 200×200.
X reads og:title, og:description and og:image when its own tags are missing, but it needs twitter:card to show the large image card. Adding the twitter: tags too is the safe choice.
Usually the address is relative or not public, the image is too small or in an unsupported format, or the app is showing an old cached copy. The checks here catch the first three; use the apps' debuggers for the cache.
Not directly in Google's rankings, but better previews bring more clicks and shares, and more visits and links from social media help a page do well.
Yes. og:title and twitter:title can differ from the <title> tag; many sites use a shorter, catchier version for sharing.
No. The checks and previews run in your browser, on your device. Nothing you type or paste is uploaded, stored or logged.
Updated