What Platforms Actually Read
You ship your landing page, paste the link into X, LinkedIn, Slack or a group chat, and get a blank box, a cropped logo or last week's headline. That happens because link previews are not screenshots. When someone shares a URL, a scraper fetches the raw HTML, reads a small set of tags in <head>, downloads the referenced image and caches the result.
Almost every platform starts with the Open Graph protocol (og:* tags), sometimes paired with X card tags (twitter:*):
- Meta apps (Facebook, Instagram, Messenger): Meta's web crawler docs state that
facebookexternalhit/1.1fetches shared URLs, reads Open Graph tags and caches the title, description and image. Without them, it guesses from page heuristics. - LinkedIn: LinkedIn's sharing guide requires
og:title,og:image,og:descriptionandog:url, plus specific image minimums. - Slack: Slack's unfurling docs confirm that classic link unfurling crawls the URL for common Open Graph and X (formerly Twitter) Card metadata whenever no custom Slack app handles the domain.
- Apple Messages (iOS and macOS): Apple TN3156 notes that Messages reads
og:titleandog:image, falls back to a gray bubble without them, and does not run JavaScript. - X (formerly Twitter): X reads
twitter:card(such assummary_large_image) to pick the wide card layout alongside Open Graph ortwitter:*title, description and image tags.
You do not need five metadata setups. One clean Open Graph block plus twitter:card in server-rendered HTML covers all of them. Launch boards rely on the same markup too: on Hauntboard, when a launch is approved, the platform fetches your homepage's og:image (PNG, JPEG, WebP or GIF, up to 5 MB) so your launch page carries your own image when shared.
Image Sizes, Formats and Safe Zones
Platforms enforce different dimensions and file caps, which is why one asset can look sharp on LinkedIn and shrink to a thumbnail elsewhere. Here are the verified requirements from official documentation:
| Platform | Size requirements | Aspect ratio | File limit | Key note |
|---|---|---|---|---|
| Meta (Facebook, Messenger) | 1200 x 630 px recommended; 600 x 315 px min for large cards; 200 x 200 px hard min | Close to 1.91:1 | 8 MB max | Add width and height tags for first-share rendering |
| 1200 x 627 px min in the sharing guide; under 401 px wide renders as a small thumbnail | 1.91:1 | 5 MB max | Must be publicly reachable without login | |
| Apple Messages | At least 900 px wide; under 150 px wide may be ignored or shown as an icon | Not fixed | 10 MB total resources (1 MB main page) | Add a square icon at least 108 x 108 px; avoid text-heavy images |
| Next.js file conventions | Matches your asset (commonly 1200 x 630 px) | Any | 5 MB for twitter-image, 8 MB for opengraph-image |
Build fails if static convention files exceed these caps |
X no longer hosts its legacy standalone Card specification pages on docs.x.com, so we do not quote unverified pixel limits for X. In practice, one 1200 x 630 px PNG or JPEG well under 5 MB (aim under 300 KB so crawlers fetch it quickly) meets Meta's recommendation, clears LinkedIn's 1200 x 627 minimum and 5 MB cap, exceeds Apple's 900 px guideline, and passes Next.js's 5 MB build check.
- Stick to PNG or JPEG. Avoid SVG, and be cautious with WebP. Meta's MIME-type reference lists
image/jpeg,image/pngandimage/gif, and Next.js's static file convention accepts.jpg,.jpeg,.pngand.gif. - Keep logos and text away from the edges. Feeds crop slightly differently across devices. Leave generous padding, and keep text sparse: Apple TN3156 warns that baked-in text shrinks poorly on mobile and is unreadable to screen readers.
- Export at exact size and preview first. Use our launch asset resizer to export a clean 1200 x 630 card, then check framing in the OG image previewer.
Why Previews Break (and Next.js Gotchas)
When a preview renders blank or drops its image, the culprit is almost always one of five issues.
Client-only metadata
Scrapers rarely execute JavaScript. Apple TN3156 states explicitly that Messages previews do not run JavaScript and do not follow <meta> redirects. If your SPA injects Open Graph tags after hydration, crawlers miss them. Render metadata on the server.
Next.js shallow metadata merging
In the App Router, this catches almost everyone once. The Next.js generateMetadata docs explain that metadata from app/layout.tsx and a child page.tsx is merged shallowly. If your root layout sets openGraph: { images: ['/og.png'], siteName: 'MyApp' } and a child page sets openGraph: { title: 'Pricing' }, the child completely overwrites the parent's openGraph object and silently drops images.
Spread a shared openGraph helper in child pages, or use the opengraph-image file convention (which applies whenever the page does not explicitly define openGraph.images). Also set metadataBase: new URL('https://yourdomain.com') in your root layout: relative metadata paths without it fail the build. Our Next.js technical SEO launch checklist covers the rest of App Router metadata.
WAF challenges, auth walls or blocked directories
If bot protection challenges non-browser user agents, scrapers receive a 403 or challenge page. LinkedIn Help calls out blocked crawlers and protected image directories as a common reason valid images fail to load. For pages behind login, Apple TN3156 advises serving meaningful public metadata rather than showing "Sign In" on every shared link.
Missing compression, slow responses or tags past 1 MB
Meta's crawler docs specify three server rules: enable gzip or deflate encoding, place all Open Graph tags within the first 1 MB of the response, and respond within a few seconds. Dynamic OG image routes that run slow queries on cold start often time out on the first share.
Non-HTTPS images or Slack's matching-label rule
Serve both the page and the image over https:// with a clean 200 status. And if a link will not unfurl in Slack, check the anchor text: Slack's docs state that Slack never unfurls a link whose visible label matches the URL minus the protocol (such as linking https://example.com with the text example.com).
Testing and Clearing Stale Caches
If you deployed a fix and the old card still appears, the platform is almost certainly serving a cached copy. First verify what your server actually returns using the crawler check from Meta's docs:
curl -v --compressed -H "Range: bytes=0-524288" -H "Connection: close" -A "facebookexternalhit/1.1 (+http://www.facebook.com/externalhit_uatext.php)" "https://yourdomain.com/"
Confirm four things: HTTP status is 200, every og:* and twitter:card tag appears near the top of <head>, the og:image URL is an absolute https:// link, and running curl -I on that image URL returns 200 with a real image Content-Type.
Then clear stale caches in two steps:
- Change the image URL. Meta's image docs warn that images are cached by their URL and will not update if you overwrite the same file in place. Rename the file (
og-home-v2.png) or add?v=2, and keep the old URL live for existing posts. - Force a re-scrape per platform:
- Facebook and Messenger: paste the URL into the Meta Sharing Debugger and click Scrape Again. Meta's best practices note this refreshes metadata immediately instead of waiting for the standard 24-hour update period.
- LinkedIn: run the URL through the LinkedIn Post Inspector to re-fetch your Open Graph tags and inspect redirects.
- X: X no longer runs its legacy public Card Validator. Paste the link into a draft post in the X composer without publishing to preview it. Our guides on announcing on X and announcing on LinkedIn cover when a link card works better than an attached image.
- Apple Messages and Slack: neither has a public cache-clearing tool. Using a new image filename refreshes newly sent links, and testing with a query parameter (such as
?preview=2) lets you verify live tags right away.
Make that five-minute check part of every launch: verify raw HTML with curl, inspect the crop in our OG image previewer, and warm Meta and LinkedIn before posting. Once your card looks sharp, you can submit your launch free on Hauntboard (reviewed by a person in about 72 hours, with 7 days in New this week and public visit counts).
Common Questions
Why does my preview work locally but break when shared?
Scrapers cannot reach localhost or auth-gated preview URLs, and WAF rules often block non-browser user agents. Running the curl check above shows the exact response crawlers receive.
Do I need separate images for Open Graph and X cards?
Usually no. One 1200 x 630 px PNG or JPEG under 5 MB with centered content works cleanly across Meta, LinkedIn, Slack, X and Apple Messages. Only add a separate twitter:image if a tight design crops poorly.
Why was the very first Facebook share blank even with valid tags?
Meta's docs note that the crawler must see an image once before rendering unless you declare og:image:width and og:image:height or pre-cache the URL in the Sharing Debugger first.
Can I use WebP for og:image?
Prefer PNG or JPEG. Neither Meta's webmaster MIME list nor Next.js's static file convention lists WebP for Open Graph images, and older chat clients can ignore it.