You paste a link into a WhatsApp chat, hit send — and the preview shows a blank gray box, a random screenshot from your site, or the logo you replaced three months ago. WhatsApp is the most-used messaging app on Earth (over 2 billion users), yet its link preview behavior is notoriously inconsistent. The good news: the fix is almost always in your OG tags — and it takes about five minutes.
WhatsApp's preview system is different from Facebook's or Twitter's in three important ways: it has no public debugger tool, it caches previews aggressively, and it crops your image to a square thumbnail. Most of the "WhatsApp preview not working" complaints I see come from people who optimized for Facebook and never checked how WhatsApp actually renders their card.
In this guide, I'll walk through how WhatsApp reads your Open Graph tags, the exact image specs you need, and the reliable steps to force a fresh preview — verified with ogimgen's free tools.
Why Your WhatsApp Preview Is Broken: Root Causes
WhatsApp doesn't crawl your page the way Google does. When you paste a URL into a chat, WhatsApp's crawler fetches the page once, reads the Open Graph meta tags, and generates a preview. If the tags are missing, incomplete, or the image fails to load, you get a bare link or a blank card.
Here are the three most common root causes, in order of frequency:
- No og:image tag at all. WhatsApp falls back to scraping any image on the page — usually a logo, a screenshot, or nothing.
- An image that's too small. WhatsApp ignores images under 300×300 pixels. A 200×200 logo gets rejected silently.
- A stale cached preview. WhatsApp caches the preview with the URL. If you change the image later, the old one can stick around for days — this is the "wrong logo" problem.
There's a fourth cause that surprises people: your image is fine, but it gets cropped. WhatsApp displays link previews as a square thumbnail. A 1200×630 landscape image gets center-cropped, so anything important in the left or right 25% of your design disappears in the chat.
The OG Image Specs WhatsApp Actually Needs
WhatsApp follows the same Open Graph protocol as Facebook (both are Meta products), so a correctly configured og:image tag works on both. But the practical requirements differ, especially around the square crop:
| Setting | WhatsApp Requirement | Why It Matters |
|---|---|---|
| Minimum size | 300×300 px | Below this, the image is rejected entirely |
| Recommended size | 1200×630 px | Same as Facebook; works everywhere |
| Display crop | Square (center) | Keep key text in the center 50% of the canvas |
| File size | Under 1 MB | Large images delay preview or fail to load |
| Format | PNG or JPG | Both work; PNG for text-heavy cards |
| HTTPS | Required | HTTP images are blocked by WhatsApp's crawler |
The most important takeaway: design for the center square. When you create an OG image, assume WhatsApp will crop everything outside the middle 50%. That's where your headline and logo should live. Our free OG image generator places titles in the safe zone by default, which is why its templates work well in WhatsApp chats.
The required meta tags are the same as everywhere else — og:title, og:description, og:image, and og:url. Adding og:image:width and og:image:height helps Facebook render faster and doesn't hurt WhatsApp:
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="A short, punchy description">
<meta property="og:image" content="https://yoursite.com/og-image.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:url" content="https://yoursite.com/page">How to Fix a Stale WhatsApp Preview (Step by Step)
Unlike Facebook, WhatsApp has no debugger tool you can use to force a rescrape. That makes the "old image" problem the hardest to fix. Here's the reliable sequence I use:
- Verify your tags first. Paste your URL into our free OG image checker. It shows exactly what WhatsApp's crawler sees — title, description, image, and dimensions. If the image is missing here, WhatsApp will never show it.
- Fix the underlying issue. Add or correct the og:image tag on your page, then confirm the checker shows a valid 1200×630 image. If your image is smaller than 300×300, regenerate it — that's the single most common cause of blank WhatsApp previews.
- Bust the cache with a query parameter. WhatsApp keys its cache on the full image URL. Appending
?v=2(or any unique string) to the og:image URL makes the crawler treat it as a brand-new image. Update the tag, save, and re-verify with the checker. - Send the link to yourself in WhatsApp. Paste the URL into your own chat or a group with just you. This forces a fresh crawl on the current URL. If the old preview still appears, delete the message and paste again after 30 seconds.
- Wait out aggressive caching. In rare cases WhatsApp caches the preview for 24-48 hours even with a new URL. If the image is correct per the checker, the preview will update on its own — usually within a day.
One more tip that solves a lot of "it works on Facebook but not WhatsApp" reports: check whether the image is reachable without redirects. WhatsApp's crawler is stricter about redirects than Facebook's. If your image URL 301-redirects to a CDN, WhatsApp may give up. Use the final, direct CDN URL in your og:image tag.
WhatsApp vs. Other Platforms: What Changes
If you're already set up for Facebook, you're 90% of the way there. The table below shows where WhatsApp diverges:
| Aspect | Twitter / X | ||
|---|---|---|---|
| Image crop | Square (center) | 1.91:1 landscape | 1.91:1 or 2:1 |
| Debugger tool | None | Sharing Debugger | Card Validator |
| Cache refresh | URL query param | "Scrape Again" button | Validator rescrape |
| Min image size | 300×300 | 200×200 | 300×157 |
| Twitter card tags | Ignored | Ignored | Used |
Because WhatsApp has no debugger, your best testing workflow is: fix the tags → verify with our OG checker → send the link to yourself. That loop is fast, free, and catches 95% of problems before you share a broken card with a client or a group of thousands.
Summary
WhatsApp link previews fail for three reasons: missing og:image tags, images under 300×300, and stale caching. The fix is straightforward — generate a 1200×630 image with your key content in the center square, set the og tags correctly, and append a query parameter to force a fresh preview.
If you publish content that gets shared in groups and forwarded to clients, WhatsApp previews are worth getting right — a clean branded card builds instant trust, and a blank or wrong-image preview looks broken. Generate your OG image with ogimgen in about 30 seconds, verify it with the OG checker, and test by sending the link to yourself. Five minutes now saves you from sharing ugly links for the rest of the year.