iMessage & WhatsApp Link Previews: The Forgotten Channels

iMessage and WhatsApp build link previews from the same Open Graph meta tags that Facebook and LinkedIn read — og:title, og:description, and og:image. There are no messaging-specific tags. The two differences that trip people up: iMessage prefers a square 1200×1200 image and a short title, and WhatsApp will silently drop the thumbnail if your image is over 300 KB. Get those two right and your links look as polished in a text thread as they do in a feed.

Do iMessage and WhatsApp read Open Graph tags?

Yes — both consume standard Open Graph markup, the <meta property="og:..."> tags platforms use to build a rich preview. When you paste a link, the app fetches the page, parses the og: tags, and renders a card with your image, title, and description. There is no separate iMessage or WhatsApp tag namespace to learn.

That is the high-leverage fact: the same correct Open Graph markup that fixes your Twitter/X card and your Facebook preview also fixes the preview in every messaging app. You debug it once. For the full tag breakdown, see Open Graph Meta Tags.

Why bother with messaging-app previews at all?

Because a link shared in a one-to-one message is a personal endorsement, and it gets clicked. Posts in a public feed compete with an algorithm and a thousand other cards; a link a friend texts you arrives with built-in trust. A blank, untitled link in that context looks broken — and a broken-looking link rarely gets tapped.

The visual payoff is real and measurable across the board:

What are the exact image specs for each app?

iMessage leans square; WhatsApp leans small. Here is what each expects, alongside the universal 1200×630 baseline for context.

A few notes the table can't hold:

• iMessage renders the card inside a rounded chat bubble. A 1.91:1 banner gets letterboxed with empty bands above and below; a square 1200×1200 fills the bubble. Keep the title short — iMessage shows far less text than a feed card.
• WhatsApp is the strict one. Its 300 KB ceiling is roughly a third of what other platforms tolerate, and it times out on slow image responses. This is the single most common reason a WhatsApp link comes back as plain blue text.
• Both read absolute HTTPS og:image URLs only. A relative path renders blank everywhere, messaging apps included.

How small does the WhatsApp image really need to be?

Under 300 KB, full stop. Dimensions decide whether an image fits; file size decides whether it loads at all — and WhatsApp's budget is tight.

Practical rules that keep you under the ceiling:

• Export as JPEG at quality ~80 for photographic cards. It is visually indistinguishable from quality 100 at a fraction of the bytes.
• Keep critical content — logo, headline — inside the center safe zone (~60 px margins, about 1080×510 on a 1200×630 card) so nothing important is lost when iMessage crops to square.
• Serve the image from a fast, cacheable absolute URL. WhatsApp's fetch timeout is unforgiving on slow redirects.

When a preview still refuses to appear, work through Why Your Link Preview Is Broken — the messaging-app failures are almost always file size or a relative URL.

One card that works everywhere

The winning move is a single card that satisfies the strictest constraints at once: square-safe content for iMessage, under 300 KB for WhatsApp, 1.91:1-compatible for the feeds. Build the image at 1200×630 with everything important centered, export it as a sub-200 KB JPEG, and serve it from an absolute HTTPS URL — it renders cleanly in a text thread, a group chat, and a public feed alike. Generating exactly that card — branded, correctly sized, and never broken — for every post automatically is what Social Card Studio does.