Free tools Windows power users keep installed
One-click scans. No signup required.
If a social card still shows an old image, fix both sides of the problem: verify that your live page serves the intended og:image, then refresh the affected platform’s stored preview. Editing a page does not automatically replace a preview that a platform already cached, and a refresh on one service does not clear another service’s copy.
What an outdated Open Graph image means
Open Graph (OG) metadata lives in the HTML document’s <head>. The og:image property identifies the image representing a shared page; og:url identifies the page’s canonical object. LinkedIn also lists og:title, og:description, og:image, and og:url among the tags it uses when building a share preview. Its help documentation says the LinkedIn share box relies on oEmbeds and/or Open Graph Protocol to display the most accurate title, description, and image.
There are therefore four distinct failure points:
| Layer | What to check | What the symptom suggests |
|---|---|---|
| Metadata | The deployed HTML contains one correct og:image URL. |
A missing, misspelled, or old URL causes the wrong image everywhere. |
| Image delivery | The image URL returns the intended file to an unauthenticated crawler. | Authentication, a firewall, a broken response, or an unsupported file can prevent extraction. |
| HTML or CDN cache | Your origin and CDN return the new HTML and image bytes. | An upstream cache can keep serving the previous tag or file. |
| Platform cache or post snapshot | The social service has fetched the current metadata. | A platform may still show its stored copy, especially in an already-published post. |
1. Inspect the deployed page, not just the browser view
- Open the exact public URL that people share, including its canonical host, path, and query handling.
- View the returned source or fetch it with an HTTP client. Search the
<head>forproperty="og:image". - Confirm that the
contentvalue is the replacement image’s absolute HTTPS URL, for examplehttps://example.com/images/article-new.jpg. - Check the related fields so the inspector is evaluating the intended object:
<meta property="og:title" content="Article title"><meta property="og:description" content="Description"><meta property="og:url" content="https://example.com/article"><meta property="og:image" content="https://example.com/images/article-new.jpg">
Use the deployed response, rather than a local build, a CMS editor preview, or what a logged-in browser happens to render. Server-side templates, redirects, and edge rules can produce different HTML for crawlers. If multiple og:image tags exist, compare the order and values returned by the platform inspector; do not assume the last one wins.
2. Verify that the image can be fetched
Paste the exact image URL into a private browser window and fetch it without site credentials. It should return a successful response and actual image bytes, not an HTML error page or a login redirect. Check the following:
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
- The URL is absolute and uses HTTPS.
- The server permits the social crawler to reach it without authentication, a VPN, or an allow-list rule.
- Your CDN is not returning the old file under the same URL.
- The response has an appropriate image content type and the file is within the destination platform’s limits.
- Hotlink protection, robots rules, WAF challenges, or expiring signed URLs are not blocking retrieval.
If you replaced the file in place and the old pixels persist, publish the replacement at a new filename or path (for example, article-new-v2.jpg) and update og:image. A new URL helps distinguish an image-file cache from a page-metadata cache; it is a diagnostic technique, not a guarantee for every platform.
After changing the tag, purge or revalidate your framework, reverse proxy, and CDN caches. Then fetch the page again and verify that the returned HTML—not merely the origin dashboard—contains the new URL.
3. Refresh the platform that shows the stale card
Open LinkedIn’s Post Inspector, enter the exact URL, and inspect the extracted title, description, and image. LinkedIn documents that the inspector can refresh the data it has for a URL. A successful refresh updates previews for future posts; an existing published post retains the preview captured when it was created. If the inspector displays the new image but an old post does not, the post snapshot—not your HTML—is the explanation.
LinkedIn’s troubleshooting guidance says to allow up to 48 hours after sharing a URL or updating tags for changes to take effect. That is LinkedIn’s stated interval, not a universal cache lifetime. Check the current inspector and Help documentation if the interface or timing changes.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsOther platforms
Facebook, X, Slack, Discord, WhatsApp, and other services maintain separate crawlers and caches. Use the service’s current URL-debugging or preview-inspection tool when one is provided, and test a new draft share after the inspection reports the replacement image. A refresh on LinkedIn does not establish that another service has refreshed its copy, and there is no single command that clears every platform.
4. Read inspection output as a diagnosis
The inspector still reports the old image URL
- Old HTML: Your CDN, framework, or redirect is serving an earlier document. Purge that cache and inspect the final URL again.
- Wrong candidate: Multiple OG tags, structured data, or platform-specific extraction rules may cause another image to be selected. Remove obsolete tags and compare the inspector’s fetched URL with your source.
- Blocked fetch: Check firewall logs, authentication, robots policies, WAF challenges, and image response headers.
The inspector reports the new URL, but the pixels are old
The image is probably cached under the same filename or path. Deploy a new image URL, update og:image, and purge the asset cache. Confirm the bytes from an unauthenticated request before running the platform inspection again.
The inspector reports the new image, but an old post is unchanged
That is expected LinkedIn behavior: its refresh applies to future posts, while previously published posts keep their original preview. Create a new post or edit the existing post only if the platform offers an explicit re-preview action.
LinkedIn image requirements
LinkedIn Help documents a minimum image size of 1,200 × 627 pixels, a maximum file size of 5 MB, and a recommended 1.91:1 aspect ratio for website sharing. These are LinkedIn-specific requirements, not universal rules for every social service. Keep important text away from edges and test the actual crop in the inspector.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
A repeatable maintenance checklist
- Record the exact URL, current
og:imageURL, and the platform where the card is wrong. - Fetch the deployed HTML and verify
og:title,og:description,og:url, andog:image. - Fetch the image anonymously and verify status, content type, dimensions, and current pixels.
- Purge HTML and asset caches, or deploy a new image URL if in-place replacement remains stale.
- Run the affected platform’s inspector and compare its extracted URLs with your fetch results.
- Publish a new test share. Treat an existing post as a separate, potentially immutable snapshot.
- For LinkedIn, allow the documented 48-hour interval before escalating, while continuing to verify the live response.
Or skip the browser setup
For a reproducible check of the page and its delivered image, ScreenshotNeo provides a website screenshot API and MCP server. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP tools—take_screenshot, get_page_info, and capture_pdf—let Claude, Cursor, or another MCP client inspect pages without custom browser automation.
Use one GET request (see the ScreenshotNeo API documentation) to capture the page you are debugging:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o shot.webpEquivalent clients are useful in deployment checks:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/article"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/article' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo supports full-page captures with lazy images loaded, CSS-selector element captures, device presets and custom viewports, dark mode, retina scale, custom CSS and JavaScript, click and wait actions, request or resource blocking, headers, cookies, user agents, authorization, timezone and geolocation, transparent backgrounds, resizing, TTL-based caching, signed links, asynchronous webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Its parameter names are compatible with those used by other screenshot APIs, which can simplify migration.
The Free plan includes 1,000 shots per month with no card. Paid plans are Starter $5 for 3,000 shots, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free, and every feature is included on every plan. Create a free ScreenshotNeo account to start with 1,000 screenshots a month and no card.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Troubleshooting common errors
“The tag is correct, but no platform sees it”
Confirm you inspected the final redirected URL and the server response seen by an unauthenticated request. A client-rendered tag added only after JavaScript runs may not be available to a crawler; emit the OG tags in the initial HTML or use server-side rendering.
“The image URL works for me but not for the inspector”
Test outside your office network and remove login requirements, IP restrictions, bot challenges, and expiring authorization. Review WAF and CDN logs for the crawler request.
“Changing the filename did nothing”
Verify that the page’s HTML now points to the new filename. If it does, run the platform inspector again; if the inspector is current but a published card is not, the old-post snapshot is the remaining cause.
“The preview is cropped or rejected”
Check the destination’s documented dimensions, ratio, and file-size limits. For LinkedIn, use at least 1,200 × 627 pixels, stay under 5 MB, and target 1.91:1.
FAQ
Does changing og:image edit an already-shared post?
Not necessarily. LinkedIn explicitly keeps the preview captured in an existing post even after Post Inspector refreshes the URL for future posts.
Should I add a cache-busting query string?
A new image URL can help identify an asset-cache problem, but platform behavior varies. Verify the fetched bytes and inspector output rather than relying on a query string alone.
Is og:image required if the page has a normal HTML image?
For predictable social cards, provide the explicit OG metadata in the document head. A visible page image does not guarantee that a platform will select it.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Frequently Asked Questions
Does changing og:image edit an already-shared post?
Not necessarily. LinkedIn explicitly keeps the preview captured in an existing post even after Post Inspector refreshes the URL for future posts.
Should I add a cache-busting query string?
A new image URL can help identify an asset-cache problem, but platform behavior varies. Verify the fetched bytes and inspector output rather than relying on a query string alone.
Is og:image required if the page has a normal HTML image?
For predictable social cards, provide the explicit OG metadata in the document head. A visible page image does not guarantee that a platform will select it.
Quick Recap
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.
