Twitter Card Showing Old Image: Fix a Stale X Preview
Learn why X may keep an old Twitter Card image and how to separate a cache issue from broken metadata, image delivery, or an unchanged asset URL.
First prove that the live page has the new image
Do not assume a stale X preview means the platform cache is the only issue. The deployed page may still output the old twitter:image or og:image, the new asset may redirect to an old CDN object, or the image URL may return an error to a crawler. Inspect the raw head HTML and image final URL before treating the issue as cache-only.
Use an immutable image URL for intentional replacements
When the creative changes, publish it at a distinct URL rather than overwriting bytes at the old path. A versioned filename makes the change visible to crawlers, CDNs, and your own deployment checks. Update both Twitter and Open Graph image tags to that final public HTTPS URL.
<meta name="twitter:image" content="https://your-domain.com/images/launch-social-card-v3.jpg" /> <meta property="og:image" content="https://your-domain.com/images/launch-social-card-v3.jpg" />
Validate, then allow refresh time
Once the raw HTML points to the new image and the image diagnostic returns a clean status, the remaining behaviour may be cache propagation. Preview caching is not exposed as a guaranteed timer for every URL, so avoid changing correct tags repeatedly. Keep the versioned image URL stable, re-check the deployed response, and review the cache guidance if the card has not refreshed after normal crawler recrawl time.