og:image works on Facebook but not on WhatsApp

The Facebook Sharing Debugger shows a perfect card, then the same link in WhatsApp arrives as plain text or a tiny thumbnail. The Open Graph tags are often fine. Facebook and WhatsApp simply do not enforce the same rules.

Why Facebook can pass while WhatsApp fails

Typical causes, most common first:

1. The image file is too heavy for WhatsApp’s fetch.
2. WhatsApp cached an earlier empty or broken preview for that URL.
3. The image URL is not anonymous-reachable (cookies, hotlink rules, signed CDN).
4. Duplicate or incomplete tags cause WhatsApp to pick a bad value.
5. Unusual formats (WebP, animated files) that Facebook still displays.

Facebook’s Sharing Debugger is a useful first check. It is not a WhatsApp certification.

Fix 1: Shrink the image (most important)

Facebook may accept images up to roughly 8 MB. For WhatsApp link previews, aim for 200–400 KB, with about 600 KB as a practical ceiling. A detailed 1200×630 PNG can exceed that easily.

Practical approach:

1. Prefer JPG for photographs; optimized PNG for flat graphics and text cards.
2. Lower JPG quality gradually until you are under the target.
3. Use the Image Resizer target-size mode when you need a specific byte budget.
4. Confirm pixels with the Social Image Checker.

Create a clean card in the OG Image Generator if you are starting from a title. Platform numbers and a WhatsApp-oriented preset live on the WhatsApp preview size page and the shared OG image size guide.

Fix 2: Safe format and absolute URL

• Tag a PNG or JPG file.
• Use a full https:// og:image value—not /wp-content/uploads/….
• Open the image in a private window. If it needs login, cookies, or a special referrer, WhatsApp’s fetcher will fail too.
• Avoid long redirect chains to the binary.

Rebuild or compare tags with the Meta Tag Generator when your CMS output is noisy.

Fix 3: Clean up the tags

In View Source:

• Exactly one og:title, og:description, and og:image.
• Prefer adding og:image:width and og:image:height (1200 and 630) so crawlers do not guess.
• Disable extra theme/social plugins that print a second set of tags.

Paste the page into the Link Preview Checker and fix every warning before testing WhatsApp again.

Fix 4: Bust a stuck WhatsApp cache

WhatsApp does not offer a public “scrape again” tool. After the file and tags are correct:

1. Share a new URL variant, for example https://example.com/page/?v=2 (same content, unused string).
2. Send it to yourself in a fresh chat.
3. Once that preview works, prefer the clean canonical URL for future shares when you can.

This is a practical workaround only. WhatsApp’s caching rules are not fully documented in public developer docs.

If Facebook itself still shows the wrong card, fix that path first with Facebook link preview not updating.

Fix 5: Crawler access and redirects

Firewalls and bot management can allow Facebook while blocking other agents. Check logs for requests to the HTML and the image when you paste into WhatsApp. Allow common link-preview crawlers; keep the page off login/maintenance gates. See SocialImageKitBot for how our checker identifies itself during tests.

Also confirm og:url and the canonical tag match the URL you share so crawlers do not chase a different document.

How to test properly

1. Run the Link Preview Checker.
2. Confirm the image is in the 200–400 KB range (under ~600 KB) and opens logged-out.
3. Confirm Facebook Sharing Debugger if you still use it—but treat it as secondary.
4. Send the link in a new WhatsApp chat on a phone.
5. If it fails, try ?v=2 before redesigning the graphic again.

Desktop WhatsApp versus phone, and group chats

Previews can differ slightly between WhatsApp Web and the mobile apps, and group chats sometimes show a previously cached card for a URL that already failed once in that chat history. When you test:

1. Prefer a one-to-one chat with yourself on the phone app.
2. Avoid forwarding an old message that still carries the broken preview.
3. Paste the URL as new text after the image is fixed.
4. If needed, use the unused query variant only for the first successful test.

Also remember that WhatsApp may show a title with no image when the image fetch fails but the HTML title succeeds. That pattern almost always points back to file weight, format, or image-host blocking—not a missing og:title. Fix the binary and the image URL first; rewriting the title alone will not restore the picture in the WhatsApp chat preview.

Decision guide

Symptom	First action
Debugger OK, WhatsApp blank	Compress below about 600 KB and retest
WhatsApp shows old blank preview	Share ?v=2 after fixing the file
Image URL needs login	Move media to a public path
Multiple og:image tags	Keep one plugin as the source
Only some devices fail	Retest in a fresh phone chat; ignore forwarded message history

Quick checklist

• 1200 by 630 PNG or JPG, 200 to 400 KB preferred
• Absolute https:// image URL that opens in a private window
• One set of Open Graph tags in View Source
• Crawlers not blocked for HTML and media
• Tested in a real phone chat; URL variant used if cache stuck

For the full missing-image checklist across networks, see why your og:image is not showing. On WordPress, confirm which plugin owns social tags in How to set an OG image in WordPress.