Skip to content
Plumb
Light theme onCheck a URL

DocsSearch Appearance

Social Card Preview

See the link card a URL gets on X, Facebook, LinkedIn, Slack, Discord, WhatsApp, iMessage, Telegram and Pinterest, with the tags each one reads, the share image measured, and the tags to add.
  • 10 platforms
  • Fetched as the real crawler
  • Live editor
  • JSON API

What it Checks

When a link is shared, each platform sends its own crawler to the page, reads the Open Graph (og:*) and Twitter Card (twitter:*) tags, and builds a card. Each platform reads different tags and falls back differently when one is missing. The tool fetches the page as that crawler would, reads every sharing tag, and draws the card each platform would show from them.

It also downloads the share image and reads its real pixel size from the file header (PNG, JPEG, GIF, WebP, AVIF, SVG, ICO), its byte size and content type, and checks them against each platform's limits.

Run a Test

  1. Paste the URL of the page you want to share.
  2. Pick the crawler to fetch it as. Facebook's facebookexternalhit is the default; X, LinkedIn, Slack, Discord, WhatsApp, Telegram and iMessage are available.
  3. Press Preview. The result opens with the verdict: Ready to share. when nothing needs fixing, or N issues. with the number of errors and warnings.
Open the Social Card Preview

Options

  • Fetch as. The User-Agent header sent for the page and the image. Some sites serve different tags to different crawlers, and firewalls often block some of them: a 403 for one crawler and a 200 for another explains a card that works on one platform only.
  • Edit. Change the title, description and image URL: every preview, every check and the suggested tags update as you type. A new image URL is downloaded and measured. Copy tags copies the full tag set with your values.

Reading the Result

  • Verdict: the final URL after redirects and its status, the crawler, the share image (size, format, file size, aspect ratio), how many platforms show an image, and the X card type.
  • Checks: errors (the card breaks), warnings (it shows, but worse than it could) and tips, each with the platforms it affects.
  • Previews: each platform's card in its light theme, with the layout it picks (large image, thumbnail, text only, no card) and the tag each text came from, for example title ← twitter:title.
  • Tags: every sharing tag on the page with its value and where it was found (meta property, meta name, link rel, or in <body>).
  • Suggested tags: the tags to add or fix, or the full set, ready to paste into <head>.

What each platform reads, in order of preference:

PlatformTitleDescriptionImage and layout
Xtwitter:title, og:titletwitter:description, og:descriptiontwitter:image, og:image. Large card only with twitter:card = summary_large_image and an image of at least 300×157; otherwise the small summary card (image at least 144×144). No title tag: no card.
Facebookog:title, <title>og:description, meta descriptionog:image. Large from 600×315, a thumbnail from 200×200, nothing below.
LinkedInog:title, <title>not shownog:image as a thumbnail beside the title.
Slack, Telegramog:title, twitter:title, <title>og:description, twitter:description, meta descriptionog:image, twitter:image. Large unless twitter:card = summary or the image is under 400px wide. Site name from og:site_name.
Discordog:title, twitter:title, <title>og:description, twitter:description, meta descriptionLarge only with summary_large_image, otherwise a thumbnail. The side bar takes the theme-color.
WhatsAppog:title, <title>og:description, meta descriptionog:image. Large when at least 300px wide and landscape; images over about 600 KB are often left out.
iMessageog:title, <title>not shownog:image, twitter:image; without one, the apple-touch-icon or favicon.
Google<title>meta descriptionNo share image. Measure the snippet in the SERP Simulator.

Image limits checked: at least 200×200 (Facebook), 1200×630 recommended everywhere, about 1.91:1 for large cards, at most 5 MB (X, LinkedIn) and 8 MB (Facebook), PNG, JPEG, WebP or GIF (no SVG), an absolute https URL that answers 200 with an image content type.

Good to Know

  • The previews follow each platform's current layout and published limits. Platforms change their cards without notice; truncation lengths are approximate because cards cut by lines, not characters.
  • Requests come from this server, not from the platforms' own networks. A firewall that allows the real Facebook IP ranges but blocks data-centre traffic answers differently here.
  • Pages are read as served (no JavaScript runs), like the platforms' crawlers do: tags added by client-side scripts don't count.
  • The page is read up to 3 MB and the image up to 8 MB.

API

POST /api/social-preview

Send the URL and, optionally, the crawler: facebook (default), twitter, linkedin, slack, discord, whatsapp, telegram or imessage. The response has the page's tags, the measured images, each platform's card, the issues and the suggested tags.

Request
curl -X POST https://plumb.reacthive.dev/api/social-preview \
  -H "content-type: application/json" \
  -d '{ "url": "https://github.com/", "agent": "facebook" }'
Response (Trimmed)
{
  "finalUrl": "https://github.com/",
  "status": 200,
  "agent": { "id": "facebook", "name": "Facebook (facebookexternalhit)" },
  "fields": {
    "title": "GitHub · Change is constant. GitHub keeps you ahead. · GitHub",
    "og": { "og:title": "GitHub · Change is constant. …", "og:image": "https://images.ctfassets.net/…/GH-Homepage-Universe-img.png" },
    "twitter": { "twitter:card": "summary_large_image", "twitter:site": "@github" }
  },
  "images": {
    "https://images.ctfassets.net/…/GH-Homepage-Universe-img.png": {
      "status": 200, "contentType": "image/png", "format": "png",
      "width": 1200, "height": 630, "bytes": 618778
    }
  },
  "cards": [
    { "platform": "x", "size": "large", "title": "GitHub · Change is constant. …",
      "titleFrom": "twitter:title", "imageFrom": "twitter:image", "notes": [] }
  ],
  "issues": [
    { "severity": "warn", "title": "og:image is 604 KB",
      "detail": "WhatsApp often skips images over about 600 KB…", "platforms": ["whatsapp"] }
  ],
  "suggested": "<meta property=\"og:image:width\" content=\"1200\" />\n<meta property=\"og:image:height\" content=\"630\" />"
}

To measure an image on its own, send image instead of url:

Request
curl -X POST https://plumb.reacthive.dev/api/social-preview \
  -H "content-type: application/json" \
  -d '{ "image": "https://example.com/share.png" }'
Response
{
  "image": {
    "url": "https://example.com/share.png", "status": 200, "contentType": "image/png",
    "format": "png", "width": 1200, "height": 630, "bytes": 84213,
    "declaredBytes": 84213, "truncated": false, "redirected": false
  }
}