Why Video Previews Don’t Work on LinkedIn and How to Fix Them
Fix missing, blank, wrong, or stale LinkedIn video previews by identifying whether you uploaded a video or shared a URL.
LinkedIn video previews fail for two different reasons: a native video upload is processed by LinkedIn, while a URL post gets its preview image from the website being shared. Identify which workflow you used before changing anything.
For a native upload, check the video file limits, processing status, and custom thumbnail settings. For a URL preview, check the server-delivered Open Graph tags, make sure the image is publicly reachable over HTTPS, then refresh the URL with LinkedIn Post Inspector. A refresh changes new posts only; existing posts keep their old preview.
1. Identify which LinkedIn preview is broken
| What you posted | Who supplies the preview | First checks |
|---|---|---|
| Video uploaded with LinkedIn’s Video control | LinkedIn’s video processor and your optional thumbnail | File limits, encoding, processing, thumbnail upload, safe-area cropping |
| URL pasted into a post | The website’s HTML metadata and LinkedIn’s crawler cache | og:title, og:description, og:image, image reachability, Post Inspector |
LinkedIn also says a post can contain either a URL link or an image, not both. If you paste a URL and then attach an image, the result may not behave like the URL-card workflow you intended. See LinkedIn Help for the platform’s sharing guidance.
2. Native LinkedIn video uploads
Use this path when you selected LinkedIn’s Video control and uploaded a local file. LinkedIn processes the video itself and lets you provide a custom poster image.
Supported limits to verify
| Property | LinkedIn limit |
|---|---|
| File size | Maximum 5 GB |
| Duration | Maximum 15 minutes; minimum 3 seconds on desktop or 2 seconds on mobile |
| Resolution | 256×144 through 4096×2304 |
| Aspect ratio | Between 1:2.4 and 2.4:1 |
| Frame rate | 10–60 fps |
| Bitrate | 192 Kbps–30 Mbps |
For advertising workflows, LinkedIn specifies MP4 video with AAC or MPEG4 audio, recommends 30 fps, and supports 4:5, 9:16, 16:9, and 1:1 ratios. Ad thumbnails can be JPG or PNG, up to 2 MB, and should match the video ratio. These ad specifications are separate from the general organic-upload limits.
Upload a custom thumbnail
- Create the post and choose LinkedIn’s Video control.
- After the video is selected, choose Video thumbnail.
- Upload the intended JPG or PNG poster image.
- Wait for LinkedIn to finish processing before publishing.
Keep faces, logos, and headline text away from the edges. LinkedIn’s controls and responsive crops can cover edge content even when the file itself is valid.
When processing fails
- Export a conventional MP4 with H.264 video and AAC audio.
- Use a supported ratio such as 16:9, 1:1, 4:5, or 9:16.
- Confirm the duration, bitrate, frame rate, resolution, and file size against the table above.
- Try the upload again after the export completes; an interrupted or incomplete upload can look like a thumbnail failure.
These are practical recovery steps, not a guarantee that every encoding issue has the same cause.
3. URL link previews and video cards
When you share a page URL, LinkedIn does not normally extract a frame from the video player. It crawls the shared page and uses its metadata and image. A video can play perfectly in a browser while the LinkedIn card remains blank because the crawler cannot see the same content.
Put metadata in the initial HTML response
Place the tags in the document’s <head> so they are present in the initial HTTP response:
<!doctype html>
<html lang="en">
<head>
<meta property="og:title" content="Product demo video">
<meta property="og:description" content="A concise description of the video page.">
<meta property="og:image" content="https://example.com/social/video-poster.jpg">
<meta property="og:type" content="video.other">
<meta property="og:url" content="https://example.com/videos/demo">
</head>
</html>Do not inject these tags only with client-side JavaScript. Inspect the raw response with curl, “View Source,” or your server-rendered template. A browser’s rendered DOM can contain tags that were absent when LinkedIn fetched the page.
Make the image crawlable
- Use an absolute HTTPS URL, not
/images/poster.jpg. - Return the image without a login, cookie requirement, hotlink challenge, or firewall CAPTCHA.
- Check that the URL returns an image response rather than an HTML error page.
- Keep the poster stable at the same URL while you refresh and publish.
- Use a purpose-built social image instead of assuming LinkedIn will select a video frame.
4. Refresh a stale LinkedIn preview
- Update the Open Graph tags or replace the poster image at its absolute HTTPS URL.
- Open LinkedIn Post Inspector.
- Enter the exact URL you will share and run the inspection.
- Confirm that the title, description, and image shown by the inspector are correct.
- Create a new LinkedIn post with that URL.
Post Inspector refreshes the preview data for new posts. LinkedIn states that existing posts retain the preview they already stored, so editing the page cannot rewrite an old card.
Why the preview can still look old
- You inspected a different URL variant, such as HTTP versus HTTPS, a trailing slash, or a query string.
- The HTML changed in the browser but not in the server response.
- The image URL is unchanged and an intermediate CDN still serves the old bytes.
- The crawler received a redirect, access-denied response, or firewall challenge.
- You are looking at an already-published post, which keeps its original card.
5. A repeatable diagnostic checklist
- Classify the post: native upload or URL share.
- For native uploads: validate every file limit, wait for processing, and upload a custom thumbnail.
- For URL shares: fetch the initial HTML and verify absolute
og:image,og:title, andog:description. - Fetch the image as an unauthenticated client: confirm a successful HTTPS response and an image content type.
- Inspect the exact URL: include the same scheme, host, path, slash, and query parameters used in the post.
- Run Post Inspector: verify the corrected card before publishing.
- Publish a new post: do not expect an existing post to change.
6. Troubleshooting common errors
| Symptom | Likely cause | Fix |
|---|---|---|
| Blank card for a URL | Missing tags, JavaScript-only tags, or an unreachable image | Render tags in initial HTML and expose an absolute HTTPS poster without authentication or bot challenges. |
| Wrong image after a redesign | LinkedIn cached an earlier scrape | Run Post Inspector for the exact URL, then publish a new post. |
| Video upload has no custom poster | Thumbnail was not selected in the Video control | Choose Video thumbnail during upload and provide a supported JPG or PNG. |
| Upload rejected | File exceeds size, duration, ratio, resolution, frame-rate, or bitrate limits | Re-export to supported settings and retry. |
| Poster text is cut off | Interface overlay or responsive crop covers edge content | Move important text and logos into the center safe area. |
| Inspector shows old metadata | Wrong URL variant or stale server/CDN response | Inspect the exact shared URL and verify the response outside the browser. |
| URL and image behave unpredictably together | LinkedIn does not support both as the same post attachment | Choose a URL card or an image post. |
7. Performance, reliability, and cost considerations
Server-rendered metadata avoids waiting for client-side JavaScript and gives crawlers a deterministic response. Host social images on a reliable HTTPS origin, keep dimensions and compression appropriate for fast retrieval, and avoid changing the poster URL during a campaign. For repeated pages, generate the image once and cache it at the edge.
LinkedIn’s preview cache means metadata changes are not instantaneous in every surface. Treat Post Inspector as the verification step, and plan corrections before publishing rather than relying on edits to an existing post.
8. Or skip the browser setup
If your workflow needs dependable page screenshots for social cards, documentation, or video landing pages, ScreenshotNeo returns a clean PNG, JPEG, WebP, or PDF from one GET request. It accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing result.
It also provides an MCP server for AI agents, including Claude and Cursor, with take_screenshot, get_page_info, and capture_pdf. Every plan includes features such as full-page capture, element selectors, dark mode, device presets, custom CSS and JavaScript, waits, request blocking, cookies and headers, caching, signed links, asynchronous jobs, bulk capture, and a usage API.
See the ScreenshotNeo API documentation for all options. The basic request is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/video-page -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/video-page"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/video-page' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);There are 1,000 screenshots per month free with no card. Paid plans start at $5 for 3,000 screenshots. Create a free ScreenshotNeo account.
9. FAQ
Can LinkedIn generate a thumbnail from my video automatically?
For a native upload, LinkedIn processes the video and offers a custom thumbnail control. For a URL share, provide an Open Graph image; do not rely on LinkedIn extracting a frame.
Will changing og:image fix an old post?
No. Post Inspector refreshes data for new posts. Existing posts retain their stored preview.
Why does the page look correct to me but not to LinkedIn?
Your browser may execute JavaScript, send cookies, or pass an authentication check that LinkedIn’s crawler cannot. Verify the initial HTML and unauthenticated image response.
Should I use a video URL in og:image?
No. Use a directly fetchable image URL for the preview poster.
Can I attach a URL and a separate image to force the thumbnail?
LinkedIn documents URL links and images as mutually exclusive post attachments. Control the URL card through the page metadata instead.
