WhatsApp does not use a special proprietary image format for link cards. It fetches Open Graph tags from a public URL and draws a small preview in the chat. When the bubble shows a title and no picture—or nothing useful at all—the problem is almost always in the HTML, the image file, crawler access, or WhatsApp’s aggressive cache.
This guide is a WhatsApp-first troubleshooting hub. If Facebook already looks perfect and only WhatsApp fails, also read og:image works on Facebook but not WhatsApp. For dimensions alone, use the WhatsApp image size page.
Why WhatsApp link previews fail
Common causes, most likely first:
og:imagemissing from the first HTML response (or only injected by client JavaScript).- Relative image URL (
/uploads/cover.png) that crawlers cannot resolve reliably. - File too heavy for WhatsApp’s fetch (aim 200–400 KB; practical ceiling ~600 KB).
- Image not anonymously reachable (login, cookies, hotlink rules, signed CDN URLs).
- Cached empty or broken preview stuck on that URL in chat history.
- Bot or firewall rules blocking WhatsApp’s fetcher on the page or media host.
Step 1: Confirm the raw Open Graph tags
Crawlers read the HTML your server returns. Open the live URL, choose View Source (not DevTools Elements), and search for og:image.
You want one absolute tag, for example:
<meta property="og:image" content="https://example.com/images/share.png" />
Also confirm og:title and og:description exist once each. Duplicate tags from a theme plus an SEO plugin often confuse clients.
Paste the page into the Link Preview Checker. Compare against a clean snippet from the Meta Tag Generator if your CMS output is noisy. For the cross-platform checklist, see why your og:image is not showing.
Step 2: Size, weight, and format
| Check | Pass condition |
|---|---|
| Pixels | About 1200×630 (≈1.91:1) |
| Format | PNG or JPG (avoid SVG; do not rely on WebP) |
| Weight | Prefer 200–400 KB; treat ~600 KB as a practical ceiling |
| URL | Absolute https://, opens in a private window |
Create a landscape card in the OG Image Generator, compress with the Image Resizer, and sanity-check with the Social Image Checker. Pixel and weight notes also live on WhatsApp sizes and OG image size.
Step 3: Make the image fetchable
Open the og:image URL in a private window with no login. If it redirects through several hops, requires a cookie, or returns HTML instead of an image, WhatsApp will fail even when your own browser works.
Avoid hotlink protection that blocks empty Referer headers. Prefer a stable public object URL—not a short-lived signed CDN link.
Step 4: Clear WhatsApp’s cache the practical way
WhatsApp does not offer a public “scrape again” tool. After the HTML and file are correct:
- Prefer a new image file name and update
og:image. - Or share a new page URL variant such as
https://example.com/post/?v=2. - Paste into a new one-to-one chat on the phone app—not a forward of an old message that still carries the broken card.
- WhatsApp Web and group chats can retain older results; retest on the phone after a successful private chat.
Step 5: Crawlers, robots, and speed
Review robots.txt and WAF/bot rules so anonymous fetchers can reach both the HTML and the image. Slow origins and dynamic image endpoints that take many seconds to respond can time out. Serve a static file when you can.
You can optionally cross-check with Facebook’s Sharing Debugger—shared fetch failures often show up there—but a green Facebook result does not prove WhatsApp will accept a heavy file.
Common mistakes
- Testing only in a forwarded group message that still holds the old card.
- Fixing Facebook and assuming WhatsApp’s byte budget matches Meta’s debugger.
- Using a featured-image thumbnail path from a CMS instead of the full-size media URL.
- Emitting tags only after React hydration (see OG images for React SPAs if that is your stack).
- Blocking bots on the CDN while allowing browsers.
On WordPress, confirm which plugin owns social tags in How to set an OG image in WordPress.
Quick checklist
- One absolute
https://og:imagein View Source - PNG/JPG about 1200×630, preferably under 400 KB
- Image opens logged out
- New filename or
?v=2after fixes - Tested in a fresh phone chat
When Facebook is already correct and only WhatsApp fails, continue with og:image works on Facebook but not WhatsApp.
How WhatsApp differs from “any OG client”
WhatsApp is not trying to be a full social network debugger. It wants a fast card in a chat bubble. That product goal shows up as stricter practical limits on file weight and less patience for slow or authenticated image hosts. Teams that only test in Facebook’s Sharing Debugger routinely ship “perfect” Meta scrapes that still fail in chat.
When you triage, ask which symptom you have. Title with no image usually means the HTML title was readable but the image fetch failed or the file was rejected. No card at all can mean the page fetch failed, redirects looped, or the URL is not public. An old card that never updates is cache—not a reason to redesign the graphic five times.
Keep a short internal runbook: View Source, private-window image URL, byte size, then a new chat. Only after those four checks should you touch DNS, plugins, or redesign. Most WhatsApp preview tickets end in one of those four buckets.
Field notes from real share failures
Most broken previews are boring: a relative URL, a duplicate plugin tag, a cache that nobody re-scraped, or a file that is fine in Chrome but too heavy for a messenger. Resist the urge to rewrite the entire brand system until those basics are proven in View Source and a private window.
Write down the exact URL string you tested, including trailing slash and query parameters. Support threads go sideways when one person scrapes example.com/page and another shares example.com/page/. Treat the share string as part of the specification.
When you finally change artwork, change the path. Overwriting og.png in place is the most common reason a “fixed” card never appears. Pair the new file with a short note in your changelog so the next person knows which version is live.
Frequently asked questions
Short answers from this guide.
Why is my WhatsApp link preview not working?
WhatsApp reads Open Graph tags from a public URL. A title with no picture usually means a missing or relative og:image, a blocked image fetch, a file that is too heavy, or a hard cache. Fix the public HTML, use an absolute https image URL, then paste the link in a new chat.
What size should a WhatsApp preview image be?
Use 1200×630 pixels as the default. Aim for 200–400 KB, with about 600 KB as a practical ceiling. Keep on-image text short and high-contrast because the bubble is small.
Why does my WhatsApp preview show a small thumbnail?
The image is probably too small or far from a ~1.91:1 landscape ratio. Use a 1200×630 PNG or JPG so WhatsApp can show a larger card.
Does WhatsApp use og:image or twitter:image?
WhatsApp reads Open Graph tags. Set og:image. You do not need twitter:image for WhatsApp.
How do I refresh a WhatsApp preview?
There is no official refresh tool. Fix the page, rename the image file or add ?v=2 to the shared URL, then paste again in a new chat—not a forwarded message.
Facebook shows my image but WhatsApp does not. Same fix?
Often yes on tags, but WhatsApp is stricter on file weight. See the dedicated comparison guide if Facebook’s debugger already passes.