Why it happens

WhatsApp caches previews aggressively, from 24-48 hours to several weeks with no documented duration and no official way to force a refresh. Once cached, every share of that URL uses the cached version.

Append a query parameter

The fastest workaround. WhatsApp caches by exact URL, so ?v=2 is a “new” page:

https://example.com/page?v=2

The original URL still shows stale data until the cache expires on its own.

Use a URL shortener

A fresh Bitly or TinyURL link is a new URL, which forces a fresh crawl. Useful when you can’t control query parameters.

Force a re-crawl through Meta

WhatsApp and Facebook share Meta’s crawling infrastructure. Clicking “Scrape Again” in Meta’s Sharing Debugger (linked under Resources below) sometimes refreshes the WhatsApp cache too. Not guaranteed. Test your link afterward to see what WhatsApp serves now.

What does NOT work

• Clearing WhatsApp’s app cache: only clears your device. Meta’s server-side cache determines the preview for everyone else.
• Deleting and re-sending the message: the preview is baked into the message. Re-sending uses the same server-side cache.
• Waiting a few minutes: plan for at least 24-48 hours, often longer.

Prevention

• Test your link before sharing widely
• Version your og:image URLs if you update images often: https://example.com/images/preview.jpg?v=20260215
• Short Cache-Control headers on OG images may help: Cache-Control: max-age=86400 (not guaranteed)