You share a link on LinkedIn and the preview has no picture, a tiny thumbnail where a wide image should be, or last month's image. LinkedIn builds the preview with its own crawler, LinkedInBot, which downloads your page, reads its Open Graph tags and downloads the image. Anything that stops one of those steps leaves the preview empty, and once LinkedIn has a preview for a URL, it keeps it until you refresh it in Post Inspector. This page lists what LinkedIn itself documents, what we reproduced, and the fix for each cause.
What we did and did not test. On 2026-11-21 we served test pages from a local Node.js server and fetched them with curl 8 using the user agents LinkedInBot/1.0, facebookexternalhit/1.1, WhatsApp/2.22.20.72 A and four other preview bots, and ran test images (made with ImageMagick) through the platform checks of our OG checker. We did not post the test pages on LinkedIn — they were not public — so what LinkedIn shows comes from LinkedIn's own help pages: Make your website shareable on LinkedIn and Use Post Inspector to refresh URL, plus the Images API reference for uploaded images. LinkedIn does not publish its crawler's full user-agent string on those pages.
What LinkedIn documents
LinkedIn's help page lists four tags that "must exist": og:title, og:image, og:description and og:url. Then the image rules "specific to the LinkedIn sharing module":
| Rule | LinkedIn's value |
|---|---|
| Max file size | 5 MB |
| Minimum image dimensions | 1200 (w) × 627 (h) pixels |
| Recommended ratio | 1.91:1 |
| Formats | not listed for link previews |
The same page then lists the specifications for single image ads — "File types: JPG, PNG, or GIF" — and notes: "Images less than 401 pixels wide display as a thumbnail image." And it ends with the cause most people hit: "If the image meets the requirements, but it still does not appear in updates on LinkedIn, your website may be blocking us from pulling the image or the image may be located on a protected directory or website."
Size is where most sites fail: in our census of the top 10,000 sites (2026-11-17), 38.0% of the homepage og:images we could measure were smaller than LinkedIn's 1200×627. A 1200×630 image, the size most sites already use for Facebook and X, meets LinkedIn's minimum too; the OG image size page has every platform's numbers side by side.
What we measured
| Test | Result |
|---|---|
| Page behind a rule that returns 403 to any user agent containing "bot" | 403 for LinkedInBot/1.0, Twitterbot/1.0, Slackbot, TelegramBot, Discordbot; 200 for facebookexternalhit/1.1 and WhatsApp/2.22.20.72 A |
| 1200×627 PNG, 3.1 MB | within LinkedIn's limits |
| 1200×600 PNG | our checker: too small for LinkedIn (1200×600 against 1200×627) |
| 400×209 PNG | too small for LinkedIn, and for Facebook's 600×315 |
| 2000×400 PNG | too small for LinkedIn: the height is under 627 |
The first row explains a common report: "the preview works on Facebook and WhatsApp but not on LinkedIn". Facebook's and WhatsApp's user agents do not contain the word "bot"; LinkedIn's does. Any firewall rule, security plugin or .htaccess line that matches on "bot" turns LinkedIn away and lets Facebook in.
The causes, one by one
1. A tag is missing or the image URL is relative
All four tags must be in the HTML your server sends, with absolute URLs: https://example.com/og/post.png, not /og/post.png. Tags inserted by JavaScript after the page loads do not count; preview crawlers read the server's HTML. Paste the URL into our LinkedIn Post Inspector alternative — it reports missing tags and relative image URLs as errors, checks the image against LinkedIn's limits and previews the LinkedIn card, without a LinkedIn login.
2. LinkedInBot is blocked
The cause LinkedIn names itself. Fetch the page and the image the way LinkedIn does:
curl -s -A "LinkedInBot/1.0" -o /dev/null -w "%{http_code}\n" https://example.com/post
curl -s -A "LinkedInBot/1.0" -o /dev/null -w "%{http_code} %{content_type} %{size_download}\n" https://example.com/og/post.png
A 403, a 503, a login page or a "checking your browser" page means LinkedIn is turned away. Look for a rule on "bot" in your firewall or bot-protection settings, a robots.txt section that disallows LinkedInBot (or Disallow: / under User-agent: *), hotlink protection on the image folder, or a staging password.
3. The image is too small, too large or the wrong shape
Under 1200×627 LinkedIn may show the image small; under 401 pixels wide its help page says it becomes a thumbnail. Over 5 MB it is outside LinkedIn's limit. Our two 1200×630 test JPEGs weighed 16 KB (a flat gradient) and 743 KB (random noise at quality 97, close to a worst case), so a social image has no reason to come near 5 MB — the 3.1 MB PNG in our table was the outlier, and it would already break WhatsApp's 600 KB.
4. The format is not one LinkedIn names
For link previews LinkedIn lists no formats at all. Everywhere it does list them — ads, and images uploaded through the Images API ("JPG, GIF, and PNG formats") — WebP, AVIF and SVG are missing. So the documented choice is JPEG or PNG; a WebP og:image may work, but nothing from LinkedIn promises it. The og:image formats page compares every platform.
5. LinkedIn's cache
LinkedIn's help: "if you have shared the same URL before, the image might already have been stored in the cache and that's what you see". The fix is Post Inspector (below). LinkedIn does not say how long its cache lasts.
"Image not available" and urn:li:image
The search "image not available: urn:li:image:…" is not about link previews. A urn:li:image is an image uploaded to LinkedIn — by a scheduling tool, an integration or your own code through the Images API. LinkedIn's API reference gives each such image a status:
WAITING_UPLOAD— the file has not been uploaded yet, or the upload is still running;PROCESSING— LinkedIn is still generating its versions;PROCESSING_FAILED— "due to client error such as file size too large, unsupported file format, internal error … or other issue";AVAILABLE— "The asset is available to be served."
The API also says the image's downloadUrl "is empty if the media asset isn't available, failed processing, etc." and that its download URLs expire. So a post that references an image before it reaches AVAILABLE, or one whose upload failed, has nothing to show. The Images API supports "Images with less than 36,152,320 pixels" in "JPG, GIF, and PNG formats". We did not reproduce this error ourselves — it needs a LinkedIn app and token — and LinkedIn does not document the error text itself; if you see it, ask the tool that created the post to retry the upload with a JPEG or PNG.
Refresh the preview with Post Inspector
- Fix the tags or the image. If you changed the image, give it a new file name (
post-v2.png) so no cache holds the old file under the same address. - Open Post Inspector, enter the URL and check that the preview shows the right title and image.
- Create the post again.
LinkedIn's note matters: "The changes you make will only affect the URL's preview image and information for new posts that include it. The preview for any existing posts with this URL will remain the same." A post that is already live keeps its old picture; to change it, delete it and post again. The same steps for Facebook, X, WhatsApp, Slack and the rest are on the refresh a link preview page.
An image that meets LinkedIn's rules on every page
Shareglint renders a 1200×630 JPEG or PNG for each page from an HTML template and the page's title, served from an absolute HTTPS URL that LinkedInBot can fetch — through the API, or with a signed image URL placed straight in the og:image tag. Change the title and the URL changes with it, so LinkedIn never holds a stale file. The free plan covers 100 images a month.