Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
For a website link shared on LinkedIn, use an Open Graph image that is at least 1200 × 627 pixels, follows the recommended 1.91:1 aspect ratio, and is no larger than 5 MB. Those are LinkedIn’s link-sharing specifications—not the requirements for a standalone image post or a single-image ad. [LinkedIn Help]
What size should a LinkedIn Open Graph image be?
For a website page preview, LinkedIn’s sharing-module guidance sets 1200 × 627 pixels as the minimum, recommends a 1.91:1 ratio, and sets a 5 MB maximum file size. The guidance is for the image LinkedIn fetches when someone shares a page link. It does not say that 1200 × 627 is the only accepted resolution. [LinkedIn Help]
The ratio explains why these dimensions fit: 1200 divided by 627 is approximately 1.914, which rounds to 1.91. A 1200 × 630 image is close in shape, but LinkedIn’s stated minimum is 1200 × 627, so use that exact figure when you want to match the published guidance rather than substitute a common cross-platform size.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Keep the image within all three constraints
- Dimensions: at least 1200 × 627 pixels.
- Shape: 1.91:1 recommended.
- File size: no more than 5 MB.
These numbers describe LinkedIn link previews. The official English help page is undated; its specifications are cited here as LinkedIn’s published guidance, not as a newly announced 2026 change.
Which LinkedIn image use case is this for?
An Open Graph image is the picture associated with a webpage URL. When someone shares that URL, LinkedIn can read the page’s metadata and use it to build a link preview. The image is commonly specified by the page’s og:image tag.
| Use case | What the guidance says | How to apply it |
|---|---|---|
| Website link-sharing image | Minimum 1200 × 627 px; recommended 1.91:1 ratio; maximum 5 MB. | Use these figures for the webpage image represented by og:image. |
| Single-image ad | LinkedIn lists separate ad specifications, including dimensions, file types, and aspect ratios. | Do not apply link-preview numbers to an ad creative; consult the ad-specific requirements on LinkedIn’s help page. |
| Standalone image post | The cited sharing-module guidance is about images fetched for website link sharing, not a general specification for uploaded image posts. | Do not assume the Open Graph dimensions answer upload requirements for every post format. |
LinkedIn’s help page presents sharing-module and ad requirements separately. Keep the use case straight before choosing dimensions: an image that meets the link-sharing guidance is not thereby confirmed to meet every ad or post format’s requirements. [LinkedIn Help]
Set the Open Graph image on your webpage
Add the Open Graph tags to the page’s HTML head, using an absolute URL for the image that LinkedIn should fetch. LinkedIn names og:title, og:image, og:description, and og:url among the tags that should exist for sharing. [LinkedIn Help]
Recommended Free Tools
<head>
<meta property="og:title" content="A clear page title">
<meta property="og:description" content="A concise description of the page.">
<meta property="og:url" content="https://www.example.com/article">
<meta property="og:image" content="https://www.example.com/images/link-preview.jpg">
</head>Replace the example page and image URLs with your canonical page address and the public URL of the intended image. The Open Graph example on LinkedIn’s help page uses an image URL for og:image. The tag identifies the image resource; the image itself must still meet the dimensions and file-size guidance and be retrievable by LinkedIn. [LinkedIn Help] [LinkedIn Help, German-language page]
Rank #3
Choose and prepare the image
- Export a link-preview image at 1200 × 627 pixels or larger, aiming for a 1.91:1 aspect ratio.
- Check the exported file’s size; LinkedIn’s stated maximum for the sharing module is 5 MB.
- Put the image at a stable, publicly retrievable URL rather than a location that requires a sign-in or other protected access.
- Set that URL in
og:imagein the HTML head of the page being shared. - Publish the page and check that the live page source contains the intended Open Graph values.
For a crop that differs from your design canvas, inspect the final exported image at its actual dimensions. As a practical design precaution, keep essential text and logos away from the extreme edges so they remain legible if a preview is displayed with a slightly different crop. This is a layout precaution, not a separate LinkedIn size requirement.
Why a correctly sized image may not appear
Dimensions alone do not guarantee a preview image. LinkedIn notes that an image can be absent if its fetcher cannot retrieve it, including when the image is in a protected directory or on a protected site. [LinkedIn Help]
- Check the image URL directly. Open the exact URL from
og:imagein a browser where you are not relying on a logged-in session. Confirm that it resolves to the intended image rather than a sign-in page or an error. - Check access controls. Review whether authentication, directory protection, or site rules prevent LinkedIn from retrieving the asset. LinkedIn explicitly identifies protected locations as a possible cause.
- Check the live page metadata. Make sure the shared page’s published HTML has the correct
og:image, not just a draft, template, or different page’s value. - Check the asset against the published limits. Confirm it is at least 1200 × 627 pixels, uses the recommended shape, and does not exceed 5 MB.
- Allow for uncertainty about refresh timing. LinkedIn’s cited help guidance does not state a crawler cache-refresh interval. Do not assume that changing a tag causes an immediate preview update.
Do-it-yourself checks and troubleshooting
Start with the page URL that is actually being shared, then inspect its rendered or published source for the four Open Graph tags LinkedIn identifies. Check that og:image points to the intended asset and that the asset is reachable without protected access. If the image still does not appear, change one issue at a time—metadata, access, dimensions, or file size—so you can tell which correction mattered.
| Symptom | Likely check | What to do |
|---|---|---|
| No preview image | The image URL may be inaccessible, or the asset may be in a protected location. | Verify the exact image URL and remove access barriers that prevent LinkedIn from fetching it. |
| Wrong image appears | The live page may expose a different og:image value than intended. |
Inspect the shared page’s published HTML and correct the metadata there. |
| Image does not match the size guidance | Exported dimensions or file size may be outside the sharing-module specifications. | Export at least 1200 × 627 pixels, aim for 1.91:1, and stay within 5 MB. |
| Preview does not seem to change after an edit | The available LinkedIn guidance does not establish a cache-refresh interval. | Verify the live page and image first; avoid relying on an unverified refresh-time promise. |
LinkedIn’s English help page does not publish a precise refresh schedule in the guidance cited here. That means a delayed change cannot, from that source alone, be diagnosed as a particular cache duration. [LinkedIn Help]
Check the published page visually
A browser screenshot can help you see whether the live webpage loads and whether the intended image asset is present in the page as rendered. It does not prove that LinkedIn’s fetcher can access the page, that LinkedIn has refreshed a preview, or that a social preview will be rendered identically. Treat visual inspection as one check alongside inspecting the live Open Graph tags and image access.
For a direct browser-based check, open the published page and inspect its source or developer tools for og:title, og:description, og:url, and og:image. Then open the image URL independently and verify the asset. Those checks address the metadata and retrieval issues LinkedIn calls out; a screenshot is supplementary.
Or skip the browser setup
ScreenshotNeo can capture a webpage by URL with one API request. Its screenshot is a visual check of the page, not a LinkedIn preview validator; still inspect the Open Graph tags and ensure LinkedIn can retrieve the image. The API offers PNG, JPEG, WebP, or PDF output, and its response identifies page verdict and billing status. See the ScreenshotNeo API documentation.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace the target URL with your published page URL. ScreenshotNeo removes known consent banners, newsletter popups, and chat widgets before capture; those cleanup steps can each be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Its MCP server provides screenshot tools for AI agents, and the free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is available on every plan. See ScreenshotNeo for product details, or sign up free for 1,000 screenshots a month with no card.
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.
