What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Update the live page’s Open Graph metadata—especially og:image—and confirm the intended image is publicly fetchable. If WhatsApp still shows the old image, try sharing a new image URL or a versioned page URL as a fresh link. That is a practical workaround, not a guaranteed way to clear WhatsApp’s cached preview.
Check the page’s Open Graph metadata
WhatsApp link previews use information associated with the shared page. The Open Graph protocol identifies og:title, og:type, og:image and og:url as basic metadata properties. og:image identifies the image representing the page; og:url identifies its canonical URL. See the Open Graph protocol.
As an Amazon Associate I earn from qualifying purchases.
- Open the live page’s HTML and inspect its Open Graph tags—not just the image shown on the page.
- Confirm that
og:imagepoints to the intended image and that the image URL can be fetched publicly. - Check that
og:urlis the expected canonical page URL. - If there are several
og:imagetags, inspect their order. The Open Graph protocol gives the first value preference when image values conflict; move the intended image first or remove obsolete entries. - Verify the corrected metadata is deployed on the live page. A CMS preview or an updated image file alone does not establish that the page now serves the corrected tags.
Try a new URL if the preview remains stale
If the metadata is correct but WhatsApp continues to show the old image, change the URL that you share so the service has a different link to inspect. You can use a new filename for the image and update og:image, or append a harmless query parameter to the page URL, such as ?preview=2. Then send that revised URL as a new link and check the preview.
Third-party troubleshooting guides describe changed image or page URLs as cache-busting workarounds, not as official Meta instructions or guaranteed cache invalidation. A query string may be treated as a different URL, but the Open Graph protocol does not guarantee that WhatsApp will refresh a preview because of it. See OpenGraphDebug.com’s WhatsApp Open Graph guidance and the CachePlex Social Share Preview Checker.
Keep the original share URL, or test a changed one?
| Approach | When it fits | What to expect |
|---|---|---|
| Keep the original URL and wait, or try Meta’s Sharing Debugger | You need to keep sharing the same URL. | It may help with diagnosis, but the reviewed guidance does not establish a reliable refresh or a guaranteed result for WhatsApp. |
| Share a changed image URL or versioned page URL | You control the page or link and want to test a new preview directly. | It gives WhatsApp a new URL to fetch, but it is still a workaround—not a guaranteed cache purge. |
Meta’s Sharing Debugger is a Facebook-facing tool, not an established public WhatsApp preview debugger. You can try it to see whether the page metadata is being re-scraped, then test the link in WhatsApp. Any effect on WhatsApp is uncertain; the OpenGraphPlus guide also describes debugger behavior as uncertain.
What happens to a preview already sent?
The available guidance does not establish that an already-sent WhatsApp message can have its preview image edited retroactively. Treat these steps as ways to test a newly shared link; do not assume deleting and resending the identical URL will refresh its image.
Does this fix work differently in India?
No India-specific refresh method or technical difference is established by the sources cited here. Check the exact URL you are sharing and use the same metadata and changed-URL steps regardless of location; do not assume Indian accounts, networks or WhatsApp versions have a special cache-clearing option.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsTroubleshoot the common causes
- The image changed on the website, but WhatsApp still shows the old one: Check the live page’s
og:image. If the URL is unchanged, try a new image filename and update the tag, then share the revised page link. - The page has the right image, but its preview is wrong: Inspect the actual HTML tags and the order of multiple
og:imagevalues. Confirm the intended image comes first. - The page looks correct in your CMS but the shared link does not: Confirm the corrected tags are deployed on the live page and that the image URL is publicly fetchable.
- The Sharing Debugger appears to refresh the page, but WhatsApp does not: Retest by sending a new link in WhatsApp. The debugger’s effect on WhatsApp is not guaranteed.
- You need to keep the exact same URL: You can wait or try the debugger, but the cited sources do not establish a cache duration or guarantee that either approach will refresh the preview.
Or skip the browser setup
For checking a page capture after updating its metadata, ScreenshotNeo can return a screenshot or PDF with one GET request. Its response identifies page verdict and billing status; clean captures are billed, while bot checks, blank pages, timeouts, failed loads and cache hits are not. ScreenshotNeo also has an MCP server for AI agents to take screenshots, inspect page information and capture PDFs. It does not clear WhatsApp’s preview cache.
Quick Recap
Best Value
Rank #4
Example cURL request, using the target page URL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups and chat widgets are removed before capture; bot checks, blank pages and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
