For a website link shared on LinkedIn, make the Open Graph image at least 1200 × 627 pixels, use the recommended 1.91:1 aspect ratio, and keep the file at or below 5 MB. These are LinkedIn’s specifications for the link-sharing module, not a universal requirement for standalone image posts or ads. LinkedIn’s official guidance is available in Make your website shareable on LinkedIn.
The exact LinkedIn link-preview specification
When someone pastes your website URL into a LinkedIn post, LinkedIn retrieves the page’s Open Graph metadata and uses og:image for the preview card. For that use case, LinkedIn lists these requirements:
| Requirement | LinkedIn guidance |
|---|---|
| Minimum dimensions | 1200 × 627 pixels |
| Recommended shape | 1.91:1 aspect ratio |
| Maximum file size | 5 MB |
| Image role | Image fetched from a website link’s Open Graph metadata |
The 1200 × 627 figure is a minimum, not a statement that LinkedIn accepts only that one resolution. The 1.91:1 ratio describes the recommended shape. A 1200 × 630 image is very close to that ratio and is commonly encountered, but LinkedIn’s strongest exact figure for link sharing is 1200 × 627. Do not substitute specifications for another LinkedIn product.
LinkedIn’s help page also says the sharing module has a 5 MB maximum. Keep the size limit attached to this website-link use case; the same page lists separate dimensions, file types and aspect-ratio rules for single-image advertisements.
What “Open Graph image” means on LinkedIn
This topic concerns the image LinkedIn fetches when a post contains a URL. It is normally supplied by an og:image tag in the page’s HTML. It is different from uploading a picture directly as a standalone LinkedIn post and different again from creating an ad.
LinkedIn’s official example identifies four core tags for a shareable page:
og:title— the title shown in the preview.og:image— the image URL LinkedIn should fetch.og:description— the supporting description.og:url— the canonical page URL represented by the card.
These tags belong in the document’s <head>. The image value should point to the actual image resource, not to a page that merely displays it.
Implement the metadata in your page
Basic HTML example
Replace the example values with the title, description, canonical URL and image URL for the page you are publishing:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
<head>
<meta property="og:title" content="Your page title">
<meta property="og:image" content="https://example.com/images/link-preview.jpg">
<meta property="og:description" content="A concise description of the page.">
<meta property="og:url" content="https://example.com/your-page">
</head>Use one deliberate image for each page and make sure the URL in og:image is the file you measured against the 1200 × 627 minimum and 5 MB maximum. If your framework generates metadata server-side, verify the tags in the HTML returned to a fresh request rather than relying only on an editor’s preview.
Content-management systems and templates
Most CMS platforms expose Open Graph fields through an SEO or social-sharing panel. Enter the image there, then inspect the published page source to confirm that the resulting markup contains og:title, og:image, og:description and og:url. If a theme or plugin emits duplicate values, keep the one that represents the intended page and remove conflicting template output where your platform allows it.
Prepare an image that survives the preview card
Start with the required canvas
Create the artwork at 1200 × 627 pixels or larger while preserving the 1.91:1 shape. Designing at the minimum canvas gives you a concrete check against LinkedIn’s stated requirement; designing larger gives you room to export a compliant version later. Regardless of working size, the delivered file must remain no larger than 5 MB for the link-sharing module.
Keep important content inside the central area
LinkedIn controls how the card is displayed in different feeds and interfaces. Keep the page title, logo and any essential words away from the extreme edges so a tighter presentation does not remove the meaning. This is a design precaution, not an additional LinkedIn pixel rule.
Rank #3
Check the delivered file, not only the source design
- Confirm the pixel dimensions of the exported file.
- Confirm the file size is 5 MB or less.
- Open the exact URL used in
og:imagein a normal browser window. - Verify that the URL returns the image without a login, expiring token or directory restriction.
A deployment checklist
- Export a link-preview image at least 1200 × 627 pixels, with the recommended 1.91:1 shape.
- Keep the delivered file at or below 5 MB.
- Add
og:title,og:image,og:descriptionandog:urlto the page head. - Publish the page and inspect its returned HTML to ensure the intended values are present.
- Request the image URL directly from a browser or an unauthenticated network to confirm it is reachable.
- Share the page URL on LinkedIn and check the resulting card. If the image is missing, use the troubleshooting branches below rather than changing dimensions at random.
When LinkedIn does not show the image
The dimensions or file size are wrong
Measure the file that the og:image URL serves. A design document can be 1200 × 627 while the production export is smaller or a different asset is being served. Replace the URL or export, then verify the delivered resource again. Keep the 5 MB limit specific to the link-sharing module.
The metadata is missing or points to another asset
View the page source returned for the public URL and search for each of the four tags. A social plugin may have inserted an old image, or a template may output a different value for a mobile or localized version. Correct the generated HTML so the intended og:image appears in the page head.
The image is protected from LinkedIn’s fetcher
LinkedIn explicitly identifies access restrictions as a possible reason a compliant image does not appear. Protected directories, login requirements and other server rules can prevent retrieval. Test the exact image URL from outside your authenticated session and make it available to LinkedIn’s crawler while keeping any private assets elsewhere.
The URL is not the page you think it is
Check og:url and the URL you paste into LinkedIn. Redirects, canonicalization and localized templates can cause a different document to supply the metadata. Ensure the shared URL resolves to the page whose tags and image you just checked.
You are expecting an undocumented refresh time
LinkedIn’s official material does not specify a crawler cache-refresh interval. Do not rely on a promised number of minutes or hours. First correct the source HTML and image access, then allow LinkedIn to fetch the page again; the available guidance does not establish an exact schedule.
Link previews are not single-image ads
| LinkedIn use case | What the available guidance says | How to apply it |
|---|---|---|
| Website link sharing | Minimum 1200 × 627 pixels, recommended 1.91:1, maximum 5 MB | Use these figures for the page’s og:image. |
| Single-image advertisement | LinkedIn lists separate dimensions, file types and aspect ratios on the same help page; the specific ad values are not the link-preview specification. | Follow the ad-placement requirements for an ad instead of reusing the link-sharing numbers. |
Confusing these two products is a common source of incorrect advice. The official distinction appears on LinkedIn’s help page; an independent 2026 guide also treats 1200 × 627 as the link-sharing figure, but LinkedIn remains the primary authority.
Automate a visual check of the published page
A screenshot can help you confirm that the published page renders the title area, branding and layout you expect, but it does not replace checking the raw Open Graph tags or guarantee that LinkedIn’s crawler will accept the image. Use it as a visual QA step after the metadata and direct image request succeed.
Or skip the browser setup
ScreenshotNeo can capture the public page through one GET request, returning a clean PNG, JPEG or WebP (or a PDF). Its consent handling removes more than 60 known cookie platforms, newsletter popups and chat widgets before capture, and each response identifies whether it was billed. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed. The service also provides an MCP server with take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
See the ScreenshotNeo documentation for all parameters. A minimal capture of your published page is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/your-page -o shot.webpThe same request in Python:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/your-page"}, timeout=90)
open("shot.webp", "wb").write(r.content)And in Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/your-page' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo’s Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots, and every feature is available on every plan. Create a free ScreenshotNeo account to run the check.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability and cost considerations
- Keep the asset reachable: LinkedIn can only build a preview when it can retrieve the image URL. Hosting it behind authentication or a protected directory defeats otherwise correct dimensions.
- Respect the 5 MB ceiling: A smaller delivered file leaves more margin for the sharing module’s stated maximum and usually transfers faster, but do not reduce dimensions below 1200 × 627.
- Validate at the source: The HTML tags and the image response are separate dependencies. Check both; a perfect image cannot compensate for missing metadata, and correct tags cannot compensate for an inaccessible file.
- Separate QA from LinkedIn’s crawler: A local browser or screenshot service shows what a normal request renders. LinkedIn may still omit a card when its fetcher is blocked, so treat access testing as a required step rather than relying on visual appearance alone.
Frequently asked questions
Does LinkedIn’s 5 MB limit apply to every image you upload?
No. The 5 MB figure cited here belongs to LinkedIn’s website link-sharing module. LinkedIn publishes separate specifications for other placements, including single-image ads.
Is 1200 × 627 an exact-size requirement?
No. LinkedIn describes it as the minimum for the sharing module. The page also recommends a 1.91:1 ratio, so larger images should preserve that shape rather than treating 1200 × 627 as the only accepted resolution.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What if my image meets the specification but still does not appear?
Check that LinkedIn can retrieve the exact og:image URL. LinkedIn names protected locations and other access problems as possible causes, so test the asset without relying on an authenticated browser session.
Frequently Asked Questions
Can I use a 1200 × 630 image for a LinkedIn link preview?
It is very close to LinkedIn’s recommended 1.91:1 shape, but the official link-sharing figure to target is 1200 × 627 pixels minimum. Preserve the recommended ratio and keep the delivered file at or below 5 MB.
Where can I confirm the current Open Graph tag guidance?
Use LinkedIn’s official “Make your website shareable on LinkedIn” help page: https://www.linkedin.com/help/recruiter/answer/a521928.
Quick Recap
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.
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 glitches
