How to Fix a LinkedIn Preview That Shows the Wrong Image

If a LinkedIn link preview shows the wrong image, paste the exact page URL into LinkedIn Post Inspector to refresh its cached preview. If the image is still wrong, fix the source page’s Open Graph metadata and make sure the image URL is publicly fetchable. Allow time for LinkedIn’s cache to update, then inspect the URL again. A refresh affects future shares; it does not change previews on posts already published.

1. Refresh the URL in LinkedIn Post Inspector

Open LinkedIn’s Post Inspector.
Enter the exact URL people share. Check the canonical URL too if it differs from the URL you entered.
Inspect the resulting preview. If it now shows the right image, share the URL again in a new post.

LinkedIn may have stored an older image for a URL. Post Inspector refreshes preview information for new posts; it does not rewrite an existing post’s preview. If you need to correct a published post, the refresh alone will not do that.

2. Check the page’s Open Graph metadata

LinkedIn uses oEmbed and/or Open Graph Protocol information to build a link preview. Check the HTML returned for the page and confirm the title, description, image, and canonical URL are the intended values. The tags should be present in the document’s <head> when LinkedIn fetches it.

<head>
  <title>A useful article title</title>
  <link rel="canonical" href="https://example.com/article/">
  <meta property="og:title" content="A useful article title">
  <meta property="og:description" content="A short description of the article.">
  <meta property="og:url" content="https://example.com/article/">
  <meta property="og:image" content="https://example.com/images/article-share.jpg">
</head>

Replace the example values with your own canonical page and image URLs. Make sure og:url matches the page you intend to share. If your site generates metadata dynamically, verify the HTML LinkedIn receives rather than relying only on what a browser renders after JavaScript runs. LinkedIn’s website sharing guidance describes the metadata used for share previews.

3. Make the image accessible and correctly sized

Open the full og:image URL in a private browser window. It should return the intended image without a login, expiring token, or human-only interstitial.
Check that the web server and CDN do not block LinkedIn’s crawler or require cookies to retrieve the file.
Use an image at least 1200 × 627 pixels. LinkedIn recommends a 1.91:1 aspect ratio and lists a 5 MB maximum file size.
Confirm the URL points directly to an image and returns a successful response with an appropriate image content type.

LinkedIn notes that protected directories or site rules can prevent image retrieval. If the image URL redirects, verify that the final destination is also public and stable. See LinkedIn’s image and website sharing requirements.

4. Wait for the cache and inspect again

After changing metadata or the image, allow up to 48 hours from the last share or metadata update for the changed information to appear, according to LinkedIn’s URL troubleshooting guidance. Then submit the same URL to Post Inspector again. Check that the inspector is evaluating the exact URL variant users share, including its hostname, path, and redirects.

5. If you are composing a LinkedIn Page post

An eligible LinkedIn Page super admin or content admin can customize the preview image and title while composing a Page post. LinkedIn recommends 1200 × 627 pixels; images narrower than 200 pixels display as thumbnails. This is an option for eligible Page posts, not a general override available to every member for every link share. See LinkedIn’s Page preview customization instructions.

Troubleshooting

Symptom	Likely cause	What to do
Post Inspector still shows the old image	LinkedIn has stale cached data, the page still serves old tags, or the wrong URL variant was inspected.	Verify the live page’s `og:image` and canonical URL, inspect the exact shared URL again, and allow up to 48 hours after the update.
The preview has no image	The image URL is blocked, protected, invalid, or otherwise inaccessible to LinkedIn.	Make the image publicly retrievable, check redirects and server rules, and confirm the URL returns the intended image.
The preview uses an unrelated site image	The page lacks usable metadata or LinkedIn is reading a different canonical page.	Set `og:title`, `og:description`, `og:image`, and `og:url` correctly, then refresh with Post Inspector.
A Page post says it cannot display a preview	LinkedIn lists the landing page’s SSL certificate as one possible cause.	Check that the page’s HTTPS certificate is valid and that the page loads correctly, then try composing the post again.
An existing published post remains wrong	Post Inspector refreshes data for future shares, not previews already attached to posts.	Share the URL in a new post after the preview is corrected. For eligible Page posts, use the composition-time preview override.
The preview looks wrong only in your browser	Local browser cache or cookies may affect what you see.	Clear browser cache and cookies or check in a private window, then compare with Post Inspector.

LinkedIn’s troubleshooting pages cover URL sharing issues and Page post troubleshooting.

Or skip the browser setup

When you need a clean screenshot of the corrected page for a review or workflow, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF. This does not refresh LinkedIn’s preview cache or modify a LinkedIn post; use Post Inspector for those tasks.

cURL:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article/ -o shot.webp

Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com/article/"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

Node.js:

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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

See the ScreenshotNeo API documentation for parameters and configuration. Cookie banners, popups, and chat widgets are removed before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers say which verdict and billing outcome applied. An MCP server lets AI agents using Claude, Cursor, or any MCP client take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month.

Performance, reliability, and cost notes

For fixing the LinkedIn preview: Post Inspector and metadata corrections are the relevant workflow. The main wait is cache propagation; LinkedIn advises allowing up to 48 hours.
For capturing page evidence: A screenshot API avoids maintaining your own browser capture setup. ScreenshotNeo offers caching with a chosen TTL, async jobs with signed webhooks, bulk capture for up to 100 URLs per call, and controls such as waiting for a selector, delay, or network idle. Use waits only when the page needs time to render.
Billing: ScreenshotNeo bills clean shots only; bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing. Plans are Free: 1,000/month; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan.

FAQ

Will refreshing the URL fix posts that are already published?

No. LinkedIn says the refreshed preview applies to new posts sharing that URL; existing posts retain their previous preview.

Does changing the image file alone guarantee the preview changes?

No. LinkedIn may still have old preview data, or the page may still point to a different image. Check the live Open Graph tags and refresh the URL in Post Inspector.

Can every LinkedIn member manually choose a link preview image?

The documented image and title override applies to eligible admins composing LinkedIn Page posts. It is not a general control for every member’s link post.

Does ScreenshotNeo fix LinkedIn’s cached preview?

No. ScreenshotNeo captures web pages; LinkedIn Post Inspector refreshes LinkedIn’s preview data.