# Link preview checker

> See how your link looks in iMessage, WhatsApp, X, Discord, Slack, Telegram, LinkedIn and Facebook. A free Open Graph checker with a score and the tags to fix.

Paste a link and see the preview each app will draw from its tags, side by side, with a score out of 100 and what to change first. Copy it all as a prompt for your AI agent. For a page that isn't live yet, paste its head tags instead. The tool runs on its page, https://construct.computer/tools/link-preview-checker/.

## What each app reads

| App | Reads | Picture and video | Fetched and refreshed |
| --- | --- | --- | --- |
| iMessage | og:title, og:image, og:video, apple-touch-icon | Large from 900 pixels wide; plays an MP4 og:video muted on a loop when it's served in byte ranges, within 10 MB for everything the preview loads | On the sender's phone, for each message |
| X | twitter:* first, then og:* | Large only with summary_large_image, cropped to 2:1 with the title over the bottom left | X's servers, kept about 7 days, with no tool to refresh |
| Discord | og:* first, then twitter:*; the last theme-color colours the bar; oEmbed adds an author line | Large only with summary_large_image; up to 4 og:image tags make a gallery; an MP4, WebM or MOV og:video plays when og:type is video.other | Discord's servers, kept about 30 minutes |
| WhatsApp | og:title, og:description, og:image, in the first 300 KB | Under about 600 KB and 300 pixels wide or more; small when square | On the sender's phone, for each message |
| Telegram | og:* | A small square unless the page is a video or the sender makes it large | Telegram's servers; @WebpageBot refreshes |
| Slack | oEmbed, then og:* and twitter:*, in the first 32 KB; twitter:label and twitter:data show as facts under the title | Large with summary_large_image | Slack's servers, kept about 30 minutes |
| LinkedIn | og:title, og:image, og:description, og:url | 1.91:1, at least 1200x627; a thumbnail under 401 pixels wide | LinkedIn's servers; Post Inspector refreshes |
| Facebook and Messenger | og:* | 1.91:1, large from 600x315; a first share needs og:image:width and og:image:height | Facebook's servers, every 30 days; the Sharing Debugger refreshes |
| Signal | og:title, og:description, og:image | Up to 1 MB; full width unless near square | On the sender's phone, through Signal's proxy |
| Bluesky | Read by the app the post is written in | Always 1200:630, made into a JPEG | Frozen into the post |
| Mastodon | The first og:image only; fediverse:creator adds the author's byline | Cropped to 1.91:1, about 640 pixels wide | Each server on its own, kept two weeks |

From each app's documentation, its source code where it's open, and tests on real devices in November 2026. Apps change these without saying so.

## The tags every page needs

Every app above draws a full preview from these. Make the picture 1200x630 and keep it under 300 KB.

```html
<title>Spring menu | Yoursite Bakery</title>
<meta name="description" content="Six new cakes, baked every morning until May.">
<link rel="canonical" href="https://yoursite.com/spring-menu">
<meta property="og:title" content="Spring menu">
<meta property="og:description" content="Six new cakes, baked every morning until May.">
<meta property="og:image" content="https://yoursite.com/share/spring-menu.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Six cakes on a long wooden table">
<meta property="og:url" content="https://yoursite.com/spring-menu">
<meta property="og:site_name" content="Yoursite Bakery">
<meta property="og:type" content="website">
<meta name="twitter:card" content="summary_large_image">
```

## Check from an agent or a script

Fetch this page with a link after url= and it answers in Markdown: the score, each app's score, what's left to change with the tag for each, and the address for the next check. Add &format=json for JSON. In a browser with WebMCP, the page offers the same check as its check_link_preview tool.

```
https://construct.computer/tools/link-preview-checker/?url=example.com
```

## Questions

### What is Open Graph?

Open Graph is the set of og: meta tags in a page's head, like og:title, og:description and og:image, that apps read to draw a link's preview. Facebook made it in 2010, and nearly every app that previews links reads it now. X reads its own twitter: tags first and falls back to these. A page without them leaves each app to guess from its title and first picture, or to show the bare link.

### What size should a link preview picture be?

1200x630, as a JPEG or PNG under 300 KB. That clears LinkedIn's 1200x627, Facebook's 600x315 and iMessage's 900 wide, and stays well under WhatsApp's limit of about 600 KB. Keep words out of the bottom left, where X lays the title, and keep anything that must survive a square crop in the middle.

### Why does WhatsApp show no picture?

Usually the picture is over about 600 KB, or the tags sit past the first 300 KB of the page, or a bot check answers WhatsApp's request instead of the page. WhatsApp fetches from the sender's phone, so a challenge page set up for crawlers can catch it too.

### Why does iMessage show a small picture?

iMessage draws the picture large only when it's at least 900 pixels wide. A narrower one sits small beside the title, and one under 150 pixels isn't shown at all, so iMessage falls back to the site's apple-touch-icon. A 1200x630 og:image is large in iMessage and in every other app.

### Why does my link still show the old preview?

Apps keep a preview after they first fetch it. Refresh Facebook's with its Sharing Debugger, LinkedIn's with Post Inspector and Telegram's by sending the link to @WebpageBot; X has no tool and fetches again after about a week. A new picture address, like image.jpg?v=2, gets fetched fresh by every app that keys pictures by address. iMessage and WhatsApp build the preview on the sender's phone, so the next message shows the change.

### Does it replace X's Card Validator?

X's Card Validator no longer shows a preview, and X draws a card only in its composer, once you're writing a post. This checker draws X's card from the same tags X reads, twitter: first and then og:, and says whether it will be large or small. X keeps a card for about 7 days with no way to refresh it, so check a page before you share it.

### Can I check a page on localhost or a staging site?

Paste the page's head tags into the field in place of a link. They're read in your browser and never sent, and every preview draws from them the same way. Neither the checker nor the apps can reach localhost or a private network, so check the real address once the page is deployed, even to a preview address.

### How is the score worked out?

Each of the eight apps starts at 100. Every fix that names an app takes 50 off it and every improvement 15, down to 0, and the score is the average of the eight. Good to know items cost nothing, so a page scores 100 once nothing is left to fix or improve. A page that fails, or that a bot check answers for, scores 0, since no app can show it. Copy prompt for your agent hands the list to an AI agent with an address that checks the page again, so it can keep going until the page scores 100.

### Does the checker see what each app sees?

It fetches the page once as its own crawler, named in its user agent, and applies each app's rules to what comes back. A site that answers named crawlers differently, or blocks crawlers it doesn't know, can show the apps something else.

### Is anything I check kept?

Not from this page. A check here sends the link in the request's body, so it stays out of request logs, and nothing about the page is stored. Pasted tags are read in your browser and never sent. A GET with ?url=, the way agents check, carries the link in its address, which our request logs keep for up to 7 days. Each visitor gets 20 checks a minute.

Construct can check every page on your site this way, tell you which ones each app gets wrong, and draft the fixed tags for each. [Try it in Construct](https://construct.computer/?prompt=Check%20how%20every%20page%20on%20my%20site%20looks%20when%20shared%20in%20iMessage%2C%20X%2C%20Discord%2C%20WhatsApp%2C%20Slack%20and%20LinkedIn%2C%20and%20list%20what%20to%20fix%20on%20each%20page.).

---

The Markdown copy of https://construct.computer/tools/link-preview-checker/. Everything Construct Computer publishes is listed in https://construct.computer/llms.txt.
