Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Check the destination platform’s own preview before you publish. A page can look perfect in a browser while its share card shows an old image, the wrong title, or no thumbnail at all. The reliable workflow is to verify the public URL, inspect its Open Graph metadata, test the rendered card, and refresh the platform’s cache when necessary.
What a website thumbnail actually represents
A social thumbnail is not necessarily the hero image a visitor sees on the page. A platform fetches the public URL as a crawler, reads sharing metadata, applies its own card rules and may reuse a cached result. LinkedIn says it uses Open Graph and/or oEmbed to display link information. That means a visual check of the page alone cannot confirm the image, title or description people will see in a post.
For a LinkedIn share, the source page should provide four Open Graph values:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallog:title— the headline shown in the card.og:image— the absolute URL of the intended thumbnail.og:description— the supporting text.og:url— the canonical URL represented by the card.
Other networks can use different metadata, crops and limits. Treat LinkedIn’s dimensions as LinkedIn guidance, not a universal image specification.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Run this pre-publication check
- Open the exact public URL. Confirm that it is the intended canonical page, loads without authentication, and is the URL you will actually paste into the post composer. Check redirects, spelling, language and query parameters.
- Paste the URL into the destination platform. In LinkedIn, use the share composer or Post Inspector. Allow a few seconds for the platform to retrieve the preview image before judging it.
- Inspect all three visible fields. Compare the thumbnail, title and description with the copy approved for publication. Look for an old campaign image, an unexpected crop, an internal page title or a description pulled from body text.
- Inspect the server-delivered metadata. View the page source or response HTML and locate
og:title,og:image,og:descriptionandog:url. Make sure each value belongs to this page and that the image URL is absolute, publicly reachable and not protected by a login or firewall rule. - Check the image file itself. Open the image URL directly in a private browser window. Confirm that it returns an image rather than an HTML error page, requires no cookies, and has the expected dimensions and file size.
- Review the rendered crop. Important text and logos should sit inside the center-safe area. A platform may crop the source to its card frame even when the original image looks correct.
- Fix and fetch again. Correct the metadata or image, deploy the change, then run the platform’s inspector or refresh workflow again. Do not assume that changing the file on your server instantly changes a cached card.
LinkedIn thumbnail requirements
LinkedIn’s sharing guidance specifies a minimum image size of 1,200 × 627 pixels, a recommended 1.91:1 aspect ratio and a maximum file size of 5 MB. The sharing module uses a 1,200 × 627 frame. Images under 401 pixels wide may appear as a smaller thumbnail.
| Check | LinkedIn guidance | How to use it |
|---|---|---|
| Minimum dimensions | 1,200 × 627 px | Export at or above this size so the card has enough source detail. |
| Recommended ratio | 1.91:1 | Compose for the card frame; keep text away from edges that may be cropped. |
| Maximum file size | 5 MB | Compress the image without making text illegible. |
| Small-image behavior | Under 401 px wide may display as a thumbnail | Do not use a tiny social asset merely because it looks acceptable on your site. |
An image that meets these numbers can still be absent. LinkedIn says retrieval may fail when a website blocks its crawler or when the image is in a protected directory or site. Check access controls, hotlink protection, robots or firewall challenges, redirects and content negotiation if the direct image request does not succeed.
How to inspect and correct Open Graph tags
Confirm the values in the delivered HTML
Inspect the response received by an unauthenticated visitor, not only a CMS preview. A minimal head section looks like this:
Rank #2
<meta property="og:title" content="The title for the share card">
<meta property="og:image" content="https://example.com/images/article-card.jpg">
<meta property="og:description" content="A concise description for sharing.">
<meta property="og:url" content="https://example.com/article">Use one canonical value per page. If a plugin emits several competing og:image tags, the platform may choose an unexpected one. Ensure the image URL uses HTTPS, returns a supported image MIME type and does not depend on a browser session.
Make the image crawler-friendly
- Serve the file from a stable, public URL with a successful response.
- Permit the platform’s fetcher through the CDN, WAF and origin rules.
- Avoid requiring a signed cookie, login, JavaScript execution or a consent action to retrieve the file.
- Use a filename and URL that remain valid after publishing; changing only the pixels at the same URL can interact with caches.
- Keep critical words and faces away from the outer edges of the 1.91:1 composition.
Refreshing a stale LinkedIn preview
When an image, title or description is old, submit the URL to LinkedIn Post Inspector after the corrected page is live. Inspect the returned card, then create a new post only after it shows the desired result. LinkedIn states that this refresh applies to future posts; it does not rewrite previews already attached to published posts.
Updated information can take up to 48 hours to appear according to LinkedIn’s troubleshooting guidance. Plan the correction before a deadline rather than relying on an immediate cache purge. If the inspector still shows the old result, verify that the URL is identical, the origin returns the new HTML to an anonymous request, and an intermediary cache is not serving an earlier response.
Choose the right checking method
| Method | Best for | What it can verify | Limit |
|---|---|---|---|
| Destination platform inspector | Publishing to one network | The platform’s own fetched card, including its crop and cached state | Usually focused on that network; refresh rules vary. |
| Platform share composer | A final visual sanity check | What the composer will attach to a new post | It may not expose every extracted tag or image dimension. |
| Third-party multi-platform checker | Comparing several networks before a campaign | Often displays extracted metadata, image dimensions and simulated cards | Its simulation is not a guarantee of each destination’s current behavior; review data handling and account requirements. |
| Direct source inspection | Debugging a page you control | The exact metadata and image URL delivered by your server | It cannot reproduce a platform’s crop or cache on its own. |
Use the destination inspector for the final decision. A multi-platform checker is useful for finding inconsistent tags, but the network that will receive the post remains the authority.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Or skip the browser setup
ScreenshotNeo can fetch a public page and return a PNG, JPEG, WebP or PDF through one request. It is useful when you need a repeatable image of the page itself alongside the platform-card check. Its cleanup step accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup action can be disabled. Failed loads, bot checks or CAPTCHAs, blank pages, timeouts and cache hits are not billed, and response headers identify the page verdict and whether the request was billed.
Use the API documentation at screenshotneo.com/docs/ for all 63 options, including full-page capture with lazy images, CSS-selector element capture, device and retina settings, custom CSS or JavaScript, click and wait actions, request blocking, headers and cookies, geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed links, asynchronous webhooks, bulk capture of up to 100 URLs and usage reporting.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info and capture_pdf tools, so Claude, Cursor and other MCP clients can inspect pages without custom browser automation. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Every feature is available on every plan. Create a free ScreenshotNeo account to run the first checks.
Rank #4
Troubleshooting checklist
No thumbnail appears
- Confirm that
og:imageexists in the delivered HTML. - Paste the image URL into a private window and verify a successful, public response.
- Remove authentication, protected-directory rules and crawler blocks affecting the image.
- Check that the URL points to the image file rather than a page that generates it only after JavaScript runs.
The wrong image appears
- Search the source for multiple
og:imagetags and remove unintended values. - Verify that your CMS template is using the page’s featured image rather than a site-wide default.
- Refresh the destination inspector after deployment and wait for its cache to update.
The title or description is wrong
- Compare the platform card with
og:titleandog:descriptionin the anonymous response. - Check for HTML escaping, truncated CMS fields or a template that outputs metadata from the wrong locale.
- Confirm
og:urlmatches the URL being tested, including redirects and trailing slashes.
The preview is still old after a fix
- Run the exact URL through LinkedIn Post Inspector again.
- Confirm the corrected HTML and image are visible outside your logged-in browser.
- Allow up to 48 hours for LinkedIn’s updated information to appear.
- Remember that a refresh cannot change a preview already attached to a published post.
The image meets the size rules but remains missing
Investigate delivery rather than resizing first. A blocked crawler or protected image location can prevent retrieval even when the dimensions, ratio and file size are valid.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Final release checklist
- Correct canonical URL pasted into the destination composer.
- Correct
og:title,og:description,og:urlandog:imagein public HTML. - Image opens anonymously, is under 5 MB for LinkedIn and is at least 1,200 × 627 pixels.
- Card crop keeps essential text and branding visible.
- Inspector result refreshed after the final deployment.
- New-post preview approved; previously published posts understood to be unchanged.
Frequently Asked Questions
Can I verify a thumbnail by looking only at the webpage?
No. The share card is generated from crawler-fetched metadata and platform rules, so use the destination composer or inspector as well as checking the page source.
Will refreshing LinkedIn Post Inspector change an existing post?
No. The refresh affects previews for future posts; an already published post retains its attached preview.
Are LinkedIn’s 1,200 × 627 dimensions required everywhere?
No. They are LinkedIn’s stated guidance. Other networks can use different ratios, limits and selection logic.
Why can a publicly visible image still fail to load for LinkedIn?
The site may block LinkedIn’s retrieval request, or the image may be stored in a protected directory or site.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
