WhatsApp Link Preview Not Working
You send a link in a WhatsApp chat and there's no preview — just a plain URL with no image, title, or description. Or the preview shows outdated information. WhatsApp's preview system has no official debugging tool, strict HTTPS requirements, aggressive on-device caching, and parsing quirks that make it one of the trickiest platforms to troubleshoot.
Common Causes
1. Page not served over HTTPS — WhatsApp strictly requires HTTPS. HTTP pages get no preview at all.
2. OG tags placed too late in the <head> — WhatsApp's parser stops reading the HTML after the first few kilobytes. If your OG tags appear after large inline CSS or JavaScript blocks, WhatsApp never sees them.
3. Image too large — WhatsApp struggles with images over 300KB, especially on mobile connections. The preview may show the title and description but no image, or fail entirely.
4. Unsupported image format — GIF and SVG are not supported for OG images on WhatsApp. Use JPEG, PNG, or WebP.
5. Image URL redirects — WhatsApp's crawler may not follow redirects on image URLs.
6. OG tags rendered by JavaScript — WhatsApp does not execute JavaScript when fetching previews.
7. Cached old or broken preview — WhatsApp caches previews aggressively on the device itself, not just server-side.
8. User has disabled link previews — WhatsApp has a privacy setting that disables preview generation entirely.
9. robots.txt blocking the crawler — WhatsApp uses WhatsApp/2.x as its user agent. If blocked, no preview is generated.
Step 1: Use Facebook Sharing Debugger as a Proxy
WhatsApp has no official debugging tool. However, WhatsApp (owned by Meta) shares infrastructure with Facebook for link preview fetching. The Facebook Sharing Debugger gives you a close approximation of what WhatsApp sees:
1. Go to Facebook Sharing Debugger
2. Paste your page URL
3. Click "Debug"
4. Review the OG tags Facebook found — WhatsApp reads the same tags
If the debugger shows correct OG tags and image, the issue is likely WhatsApp-specific (caching, image size, or tag placement).
Step 2: Ensure HTTPS Everywhere
WhatsApp is strict about HTTPS — stricter than most platforms:
The page URL must use HTTPS. The og:image URL must use HTTPS. Any redirects must stay within HTTPS (no HTTP-to-HTTPS redirects on the image). Mixed content (HTTPS page with HTTP image) will fail.
Step 3: Move OG Tags to the Top of <head>
WhatsApp's HTML parser has a limited read buffer. Place your OG tags immediately after the <head> tag, before any large CSS or JavaScript blocks:
<head>
<meta charset="utf-8" />
<meta property="og:title" content="Your Page Title" />
<meta property="og:description" content="Description here." />
<meta property="og:image" content="https://example.com/preview.jpg" />
<meta property="og:url" content="https://example.com/page/" />
<!-- Everything else (CSS, scripts, etc.) goes after OG tags -->
<link rel="stylesheet" href="/styles.css" />
</head>If you have large inline <style> or <script> blocks in the <head>, they can push your OG tags beyond WhatsApp's parsing window. Move them after the meta tags or externalize them.
Step 4: Optimize the Image
WhatsApp has the most restrictive image handling of any major platform:
File size: Keep under 300KB. Images over 300KB frequently fail to load in previews, especially for recipients on mobile data.
Format: JPEG or PNG. WebP works on newer versions. GIF and SVG are not supported.
Dimensions: 1200x630px recommended. Minimum 200x200px.
Compression: Use JPEG at 80-85% quality for photos. Run through an image optimizer.
No redirects: The image URL must return a 200 status directly.
Step 5: Clear WhatsApp's Cache
WhatsApp caches link previews on the device, which makes troubleshooting frustrating. Each platform (iOS, Android, WhatsApp Web) caches independently.
Method 1: URL Cache Busting
Append a query parameter to your URL to force WhatsApp to treat it as a new, uncached link:
https://example.com/page/?v=2Change the number each time you need to bust the cache. This is the most reliable method because it bypasses all caching layers.
Method 2: iOS Cache Clearing
1. Delete the entire conversation containing the old link
2. Send the link again in a new message
3. If that doesn't work, go to Settings › Storage and Data › Manage Storage and clear cached data
Method 3: Android Cache Clearing
1. Go to Android Settings › Apps › WhatsApp › Storage
2. Tap "Clear Cache" (not "Clear Data" — that deletes your messages)
3. Re-open WhatsApp and send the link again
Method 4: WhatsApp Web
1. Close and reopen WhatsApp Web
2. If the old preview persists, clear the browser cache for web.whatsapp.com
Step 6: Check the Recipient's Settings
WhatsApp has a privacy setting that disables link previews entirely:
iOS: Settings › Privacy › Advanced › Link Previews
Android: Settings › Privacy › Link Previews
If this setting is off, no links will generate previews for that user — regardless of how correct your OG tags are. This is a user-side setting you cannot control.
Platform-Specific Notes
iOS vs. Android vs. Web behavior: iOS generates previews on the sender's device before the message is sent. The preview is included with the message, so recipients see it even with previews disabled. Android generates previews on the sender's device as well, but the behavior varies by device manufacturer and WhatsApp version. WhatsApp Web generates previews server-side using Meta's crawlers, which is more reliable but subject to server-side caching.
End-to-end encryption and previews: WhatsApp generates link previews before encrypting the message. The preview is fetched from the sender's device (or server-side for WhatsApp Web), not the recipient's. This means the sender's network conditions, DNS, and access control affect whether a preview is generated.
No server-side cache clearing: Unlike Facebook (Sharing Debugger) and LinkedIn (Post Inspector), there is no tool to clear WhatsApp's cache on Meta's servers. The URL cache-busting method (appending ?v=2) is the only reliable workaround.
Group chats: In group chats, the preview is generated by the sender. If the sender's WhatsApp version or device has issues generating previews, no one in the group sees a preview for that message, even if their own devices would generate one fine.
Prevention Checklist
Use this checklist before sharing any link on WhatsApp:
Page and image URLs use HTTPS. OG tags are in the first few KB of the <head> (before large CSS/JS blocks). og:image file size is under 300KB. Image format is JPEG or PNG (not GIF or SVG). Image dimensions are at least 1200x630px. Image URL returns 200 with no redirects. robots.txt allows WhatsApp user agent. OG tags are in static HTML (not JavaScript-rendered). After changes, test by sending the link with a cache-busting parameter (?v=2).
FAQ
WhatsApp Web generates previews using Meta's server-side crawlers, while the mobile app generates them on your device. If your phone has network restrictions (corporate firewall, DNS filtering, slow connection), it may fail to fetch the preview. Try on a different network (e.g., switch from Wi-Fi to mobile data).
WhatsApp caches on-device and has no cache-clearing tool. The most reliable fix is to append a query parameter to the URL: https://example.com/page/?v=2. WhatsApp treats this as a completely new URL and fetches fresh preview data.
The image file is likely too large. WhatsApp has a soft limit around 300KB for preview images. Compress your image to under 300KB using JPEG at 80-85% quality. Also verify the image URL is direct HTTPS with no redirects.