How WhatsApp reads metadata
When a URL is pasted into a chat, WhatsApp sends a crawler to the destination and looks for Open Graph fields, especially og:image. If that field is wrong, inaccessible, or cached, the preview usually breaks.
WhatsApp Previews
How to change a WhatsApp link preview image.
Fix the metadata problems and cache issues that keep WhatsApp from showing the image you intended to share.
Required og:image checklist
- Absolute image URL over HTTPS
- Strong aspect ratio such as 1200x630
- Reasonable file size for fast fetches
- A publicly reachable image with no crawler barriers
Step-by-step fix
- Prepare a preview image at a stable public URL.
- Expose that URL inside the page head with a valid og:image tag.
- Update title and description metadata alongside the image.
<meta property="og:image" content="https://yourdomain.com/path-to-image.jpg" />Why the wrong image still appears
WhatsApp caching is aggressive. Even after you deploy a fix, the old preview can remain attached to the URL for days.
A common workaround is to paste the same URL with a harmless query parameter so WhatsApp treats it like a new fetch target.
FAQ
More WhatsApp preview questions
What is the minimum image size for WhatsApp?
WhatsApp can show smaller images, but a 1200x630 asset is far more reliable across higher-density displays.
Can I use GIF or WebP assets?
Support is inconsistent. Standard JPEG or PNG is still the safest option for public preview compatibility.
How long does WhatsApp cache previews?
It is not consistently documented, but it can last for days. Query-string tricks sometimes help force a new scrape.
Update sharing assets without a deploy.
Marketing teams often need to change public previews without waiting on developer cycles. Visualink sits in front of that distribution layer.