Why LinkedIn Images Aren’t Showing and How to Fix Them
Find out whether a LinkedIn display, upload, or link-preview problem is hiding your image, then follow the fix for that exact failure.
LinkedIn images can disappear at three different stages: LinkedIn may fail to display an image already in a profile or feed, a Page cover image may fail during upload, or LinkedIn may generate a link preview without the image from your website. Identify the stage first, because each problem has a different fix.
For a missing image already inside LinkedIn, start with LinkedIn’s browser troubleshooting sequence. For a failed Page or Showcase Page cover upload, check the image requirements and retry with LinkedIn’s recommended browser and file steps. For a missing website thumbnail, inspect Open Graph Protocol (OGP) or oEmbed data and make sure LinkedIn can fetch the image.
1. Identify which LinkedIn image is missing
| What you see | Likely owner | Start here |
|---|---|---|
| A profile photo, post image, or feed image is blank or does not load | LinkedIn member and browser | Sign out, test an incognito window, clear cache and cookies, try another browser, and check the pop-up blocker. |
| A Page or Showcase Page cover image will not upload | Page administrator | Check the surface’s image requirements, try PNG, refresh your session, and retry in a current or different browser. |
| A shared website URL has no thumbnail | Website owner or Page admin | Check OGP/oEmbed metadata and whether LinkedIn can retrieve the image. |
| The thumbnail is an old image after a website update | LinkedIn preview cache | Confirm the new tags and allow LinkedIn’s stated refresh period. |
Do not change Open Graph tags to fix a missing profile or feed image. Those tags describe previews of URLs hosted on your website, not images that LinkedIn is already displaying inside its own product.
2. Fix a profile or feed image that is not displaying
LinkedIn’s general troubleshooting guidance recommends changing one variable at a time so you can see which step affects the behavior.
- Sign out of LinkedIn and sign back in.
- Open LinkedIn in an incognito or private browser window.
- Clear the cache and cookies for the current browser.
- Try a different, up-to-date browser.
- Check whether a pop-up blocker is interfering with the page or upload flow.
These steps can isolate a stale session, damaged local data, a browser-specific problem, or an extension conflict. They do not establish the cause of every account-wide image failure. If the image is still missing across browsers and devices, contact LinkedIn support with a reproduction description, browser and version details, and a screenshot, as LinkedIn recommends. See LinkedIn’s troubleshooting guidance.
3. Fix a Page or Showcase Page cover upload
First check the image specifications for the exact Page surface. If the file meets the requirements but the upload still fails, LinkedIn lists these troubleshooting steps:
- Try saving or exporting the image as a PNG.
- Clear browser cookies, then sign in again.
- Use an up-to-date browser or try another browser.
- Disable the pop-up blocker while completing the upload.
These are LinkedIn’s suggested recovery steps, not proof that the file format or browser is always the cause. Keep the original file so you can compare a PNG retry with the first upload attempt. The official procedure is in LinkedIn’s cover-image troubleshooting article.
4. Fix a missing LinkedIn link-preview image
When you paste a website URL into a LinkedIn post, LinkedIn fetches preview information from that website. LinkedIn says its share box relies on websites using oEmbed and/or Open Graph Protocol (OGP) to supply the title, description, and image. A preview can therefore be missing an image even though the page itself displays correctly in a browser.
Check the page source for preview metadata
Put Open Graph tags in the HTML <head> of the page being shared. Replace the example values with the canonical URL, title, description, and an image URL that is publicly retrievable.
<head>
<link rel="canonical" href="https://example.com/article">
<meta property="og:type" content="article">
<meta property="og:url" content="https://example.com/article">
<meta property="og:title" content="An example article">
<meta property="og:description" content="A concise description for the preview.">
<meta property="og:image" content="https://example.com/images/article-preview.jpg">
<meta property="og:image:alt" content="Description of the preview image">
</head>
Use an absolute HTTPS image URL. Check the final URL after redirects, authentication, and CDN rules. LinkedIn’s developer-facing guidance warns that a website can block LinkedIn from pulling the image or keep it in a protected directory. A page that requires a login, a private network, or an access token cannot provide a public preview image. See LinkedIn’s website-sharing guidance.
Inspect the response from outside your browser
A browser may display an image using your existing cookies while LinkedIn receives a different response. Check the image URL without an authenticated session:
curl -I -L "https://example.com/images/article-preview.jpg"
Look for a successful final response and a stable image resource. Review your web server, CDN, firewall, and robots or access controls if the request is redirected to a login page, denied, or served an error. The official LinkedIn sources do not identify one universal header, file extension, JavaScript behavior, or firewall rule as the cause in every case, so confirm the actual response for your URL.
Use LinkedIn’s Page-admin preview controls when available
When preparing a post as a Page super admin or content admin, paste the URL and use the Edit control below the text box to choose the preview image or edit the article title. This control is documented for LinkedIn Page administrators; do not assume that every member can edit every preview. See LinkedIn’s Page preview instructions.
5. Check dimensions and preview behavior
LinkedIn’s Page preview guidance gives a 1.91:1 ratio and 1200×627 pixels as image guidance. Images narrower than 200 pixels are described as appearing as a left-side thumbnail instead of the larger image format. Treat these as LinkedIn product guidance for that preview surface, not as a guarantee that every post or device will render identically.
6. Wait for stale preview data to refresh
If you corrected the OGP tags or replaced the image, LinkedIn says to allow 48 hours from the last time the URL was shared or from the website tag update before trying again. During that period, verify the live HTML and image URL so you know the next fetch will see the intended values. The 48-hour period is platform guidance, not a guaranteed maximum. See LinkedIn’s URL-sharing troubleshooting article.
7. Troubleshooting checklist
| Symptom | Possible cause to investigate | Action |
|---|---|---|
| Only one browser is affected | Cache, cookies, extension, or pop-up blocker | Use private mode, clear site data, disable the blocker, then try another current browser. |
| Cover upload fails repeatedly | Surface requirements, session, browser, or file processing | Check requirements, export PNG, sign in again, and retry in another browser. |
| URL preview has title but no image | Missing OGP/oEmbed image data or inaccessible image URL | Inspect the page source and request the image URL without authentication. |
| Preview still shows an old image | LinkedIn cache | Confirm the live tags and wait up to the platform’s stated 48-hour refresh period. |
| Image works on your site but not in LinkedIn | Your browser has access that LinkedIn’s fetcher does not | Check redirects, protected directories, firewall rules, and unauthenticated responses. |
| Image is missing everywhere for an account | Account or platform issue with no documented universal cause | Collect reproduction details, browser versions, and a screenshot, then contact LinkedIn support. |
8. API-specific upload failures
If you are uploading images through LinkedIn’s Marketing API, keep that workflow separate from consumer feed troubleshooting. The API documentation lists JPG, GIF, and PNG support and describes failure categories such as oversized files, unsupported formats, internal errors, and network failures. Apply those details only to the API endpoint you are using; they are not a diagnosis for every LinkedIn image feature. See Microsoft Learn’s LinkedIn Image API documentation.
9. Or skip the browser setup
If your goal is to capture a reliable image of a LinkedIn-visible page or another public URL for documentation, QA, or preview checking, ScreenshotNeo provides a website screenshot API. It accepts one GET request and returns PNG, JPEG, WebP, or PDF. Before capture, it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, 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.
See the ScreenshotNeo API documentation for all options. This one-call example captures a page as WebP:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
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)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
Relevant capture controls include full-page screenshots with lazy images loaded, CSS-selector element capture, dark mode, 12 device presets or any viewport, retina scale, custom CSS and JavaScript, clicks, selector or network-idle waits, request and resource blocking, custom headers, cookies, user agents, authorization, timezone and geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.
ScreenshotNeo has a free plan with 1,000 shots per month and no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free, and every feature is available on every plan. Its MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients, so AI agents can take screenshots. Sign up free for 1,000 screenshots a month with no card.
10. Performance, reliability, and cost notes
- For a browser-only problem, local troubleshooting is fastest because it removes cache, cookie, extension, and pop-up-blocker variables.
- For link previews, make the image URL publicly fetchable and stable before changing tags repeatedly; otherwise a cache refresh can preserve the same failure.
- For automated captures, wait for a selector, a delay, or network idle when the page builds its content after the initial HTML response. Use full-page capture when lazy-loaded content matters.
- Block ads, trackers, unnecessary requests, or resource types when they slow a capture or introduce changing content.
- Use caching with a TTL you choose for repeated URLs. ScreenshotNeo identifies cache hits and does not bill them.
- For high-volume work, asynchronous jobs, signed webhooks, and bulk capture reduce client-side polling and request overhead. Use the usage API to watch consumption.
- Cost depends on successful clean captures under your plan. ScreenshotNeo does not bill bot checks, blank pages, timeouts, failed loads, or cache hits.
FAQ
Why is my LinkedIn link preview image not showing?
The page may not expose usable OGP or oEmbed data, or LinkedIn may be unable to retrieve the image because access is blocked or the file is protected. Inspect the live HTML and request the image URL without authentication.
Will changing the image filename force LinkedIn to refresh?
The reviewed LinkedIn guidance specifies allowing 48 hours after a share or tag update. It does not promise that renaming a file alone forces an immediate refresh.
Can I edit a preview image after pasting a URL?
LinkedIn documents image and title editing for Page super admins and content admins through the Page post preview’s Edit control. Availability for ordinary member posts can differ.
Does an Open Graph fix repair a missing profile photo?
No. OGP describes previews for website URLs. Use LinkedIn’s browser troubleshooting sequence for an image already inside LinkedIn.
Should I contact LinkedIn if the image is missing on every device?
Yes. Provide a reproducible description, browser and version details, and a screenshot, following LinkedIn’s support guidance.


