Social Preview Tester

See your link the way X, WhatsApp and LinkedIn will show it

When someone shares your page on a social media platform, the platform reads the Open Graph and Twitter tags embedded in your page, and builds a card from them. Every platform reads a different mix of them, with different fallbacks when they're missing. Paste your page's HTML below (or fetch a live URL) to preview the share card on six platforms at once, with the real fallback chain and your og:image measured at its actual pixel size.

Page HTML or head tags

Pull a page's social tags straight in. Fetching sends this URL to our fetch service, which reads the page and checks the og:image file - nothing else you've typed leaves your browser.

Findings

How platforms actually read your tags

The one near-universal rule is that og: tags are the baseline everywhere, and twitter: tags are an overlay only some platforms read. X reads twitter:card to choose its layout, then falls back through twitter:title → og:title → your title tag. Facebook and LinkedIn read og: exclusively. WhatsApp reads og: and decides between a large and a small preview based on your image's real dimensions. Discord and Slack read both families and honour twitter:card for the large-image layout.

That fallback chain is where shares can go wrong. A page with no og:title still "works", it just might not look like you would want it to. The platform might grab the title tag, complete with the "| Brand | London" suffix written for Google, and puts it on the card where it looks like a mess. A relative og:image path might "work" in your own testing and then render as no image at all when the scraper resolves it without your domain. This tool shows the chain explicitly so you can see what each platform will really use.

The caveat: these previews are careful approximations, not pixel guarantees. Platforms redesign their cards constantly and A/B test layouts. What is stable - and what this tool checks - is which tags are read, in what order of preference, and what the image needs to measure. For the final word, share the URL in a private message to yourself, or use each platform's own debugger (linked below).

Tag habits that pay off

Write og:title for humans

The share card is not a search result. Drop the brand-and-location suffix, lead with the claim, and keep it inside roughly 60 characters so no platform clamps it mid-thought.

One image, 1200×630, under 300 KB

That single size is Facebook's own recommendation and almost exactly LinkedIn's (1200×627). X prefers 2:1, so expect a slight crop there. WhatsApp is the fussy one: the dimensions get you the large preview rather than a thumbnail, but it is reported to drop images past roughly 300 KB altogether, so compress hard. Declare og:image:width and height so Facebook renders it full-size on the very first share.

Always declare twitter:card

One line, summary_large_image, is the difference between a full-width card and a cramped thumbnail on X, and Discord and Slack read it too.

Scrapers cache aggressively

Fixed your tags but the old card keeps showing? Platforms cache scrapes for days. Force a refresh with Facebook's Sharing Debugger or LinkedIn's Post Inspector.

Where this fits

Social cards are one of the three faces your page shows machines. Preview the Google result with the SERP Snippet Preview, check what the page declares itself to be with the Structured Data Inspector, and check the file that introduces the whole site to AI assistants with the llms.txt Validator.