For a landscape image that works as a practical starting point across many link previews, create a 1200 × 630-pixel image (about 1.91:1). It is not a universal guarantee: platforms can impose different minimums and file limits, and each service may crop or render the image differently. For LinkedIn, its documented shared-link guidance is more specific: a 1.91:1 frame, 1200 × 627 pixels, a minimum image size of 1200 × 627 pixels, and a 5 MB maximum for its sharing module.
What size should an Open Graph image be?
Start with a 1200 × 630-pixel landscape image if you need one broadly useful asset. That size is a common recommendation in secondary cross-platform guidance, not an official, identical specification for every social network or messaging app. Its aspect ratio is approximately 1.91:1, close to LinkedIn’s documented ratio.
For LinkedIn link sharing, use an image at least 1200 × 627 pixels and no larger than 5 MB. LinkedIn recommends a 1.91:1 ratio for the preview frame. Its help documentation describes that frame as 1.91:1 and 1200 pixels wide by 627 pixels high.
These figures describe different things and should not be treated as interchangeable: pixel dimensions describe the source image, aspect ratio describes its shape, file size is the data limit, and the displayed preview is the platform’s rendering. A compliant source image does not guarantee that every service will show the whole image without cropping.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
How platform requirements compare
| Platform or context | Recommended dimensions and ratio | Minimum dimensions | File-size limit | Metadata or card setup | Evidence and rendering caveat |
|---|---|---|---|---|---|
| LinkedIn shared links | 1200 × 627 pixels; 1.91:1 preview frame | 1200 × 627 pixels for website sharing | 5 MB for the sharing module | Open Graph title, image, description, and URL; LinkedIn also says its share box uses oEmbed and/or Open Graph Protocol | Official LinkedIn Help guidance. The frame specification does not promise identical rendering for every page or placement. |
| Facebook and common Open Graph images | 1200 × 630 pixels is reported as a common recommendation | Not stated in the secondary guidance | Not stated in the secondary guidance | Open Graph image guidance is discussed in secondary technical references | Secondary guidance, not an official current platform specification in the sources cited here. |
| X large-image cards | A large-image card is a distinct card setup; no recommended size is established here | 300 × 157 pixels is reported by a secondary guide | 5 MB is reported by a secondary guide | Large-image card setup is distinct from simply choosing an image size | Secondary guidance only; a current primary X specification is not established here. |
| WhatsApp, Slack, and Discord | No single authoritative universal dimension is established | Not stated in the secondary guidance | Not stated in the secondary guidance | Preview behavior and metadata handling can differ | Secondary guidance covers these services; it reports that Slack and Discord do not publish exact image-dimension specifications. |
The strongest platform-specific figures in this comparison are LinkedIn’s official ones. Treat the other rows as orientation, not proof of current limits. If a platform’s exact requirements matter to a launch, confirm them against that platform’s current documentation rather than applying LinkedIn’s numbers by assumption.
Set Open Graph metadata for a LinkedIn link preview
The image is only one part of a link preview. LinkedIn says its share box relies on oEmbeds and/or Open Graph Protocol data to show the most accurate title, description, and image. Its website-sharing guidance identifies og:title, og:image, og:description, and og:url as relevant fields.
- Create the image. For LinkedIn, make it at least 1200 × 627 pixels, use a 1.91:1 composition, and keep the file within 5 MB.
- Make it publicly retrievable. The value of
og:imageshould point to the image you intend the share preview to use. A crawler that cannot retrieve the page or image may not be able to construct the preview. - Add the metadata in the page head. Set the title, description, image URL, and page URL to match the page being shared.
- Publish and check the actual share preview. A page can still be shared if LinkedIn cannot retrieve a preview image, but the preview may be incomplete or absent.
- Allow for cache refresh. LinkedIn advises allowing up to 48 hours after a tag update for cached content to refresh. A preview that still shows old data immediately after a fix is not conclusive evidence that the new tags are wrong.
A minimal page-head example looks like this:
<head>
<title>Guide to Example</title>
<meta property="og:title" content="Guide to Example">
<meta property="og:description" content="A short description of the page.">
<meta property="og:image" content="https://example.com/images/share-card.jpg">
<meta property="og:url" content="https://example.com/guide">
</head>Replace the example text and URLs with values that belong to your page. This markup demonstrates the fields; it does not establish that a particular file format or URL will be accepted by every platform. The image must also be reachable by the service creating the preview.
Design for the preview, not just the canvas
Matching a ratio is useful, but it is not the same as controlling the rendered crop. Platforms and placements can present link cards differently, and the available evidence does not establish a universal crop rule. Keep the important subject and any essential text comfortably inside the image rather than relying on details at its edges. Check the actual preview on the target service before publishing a high-stakes campaign.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not assume that one image-size number answers every implementation question. Check these separately:
- Aspect ratio: the shape the platform says its preview frame uses.
- Minimum pixel dimensions: the smallest source image explicitly accepted or recommended.
- Maximum file size: the byte limit, where one is documented.
- Metadata: the title, description, image, URL, or card declaration used to identify the preview.
- Rendering: how the service presents or crops the image in a particular interface.
- Cache behavior: how long it may take a changed image or tag to show up after publication.
Troubleshoot a missing or outdated preview
The preview has no image
Check that the page has an og:image value, that the URL points to the intended asset, and that LinkedIn can retrieve the page and image. LinkedIn says a link can still be shared when it cannot retrieve a preview image, so successful link posting alone does not confirm that the image metadata is working.
The preview shows an old image or title
First verify the live page’s Open Graph values. If the tags are correct but the share preview has not changed, allow up to 48 hours for LinkedIn’s cached content to refresh after the update, as LinkedIn advises.
The source image is rejected or does not fit
For LinkedIn website sharing, check both dimensions and file size: its stated minimum is 1200 × 627 pixels and its sharing-module maximum is 5 MB. Do not fix a ratio mismatch by blindly stretching the artwork; prepare a properly composed landscape version instead.
The same asset behaves differently on another service
A 1200 × 630 image is a useful common starting point, not a promise of matching platform rules. The available secondary guidance for Facebook, X, WhatsApp, Slack, and Discord does not establish one set of official dimensions and rendering rules across those services. Check the destination platform’s own current requirements when its behavior is important.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Capture a page image when you need a visual asset
A screenshot can be useful when the desired image is a view of a web page, such as a product screen or published article. It is not automatically a good social preview card: a screenshot may contain browser-scale details, lengthy page content, or text that becomes difficult to read when shown in a small link card. For a branded preview, create a purpose-built image and set the Open Graph metadata. If you do want a page capture, ScreenshotNeo is a website screenshot API and MCP server for developers; its capture options include viewport and full-page images. Use the image it returns as an input to your design workflow, then verify that the final asset meets the destination platform’s requirements.
Or skip the browser setup
One GET request can return a page screenshot as PNG, JPEG, WebP, or PDF. The following cURL call saves a WebP screenshot of the page; replace the example URL and add your API key.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for the request options. Cookie banners are accepted and removed before the shot, along with known newsletter popups and chat widgets; each cleanup step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers say which outcome occurred. An MCP server lets AI agents use the take_screenshot, get_page_info, and capture_pdf tools. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. A screenshot is still only a source visual: prepare and check the social image and page metadata for the platform where you will share it.
Recommended Free Tools
Sign up free for 1,000 screenshots a month, with no card required.
Best Value
Choose a safe default without overstating it
For a general-purpose landscape Open Graph image, 1200 × 630 pixels is a reasonable place to start. For LinkedIn, follow its more exact published guidance: at least 1200 × 627 pixels, a 1.91:1 ratio, and no more than 5 MB for its sharing module. Add the appropriate Open Graph fields, inspect the preview, and account for caching. Treat figures for other platforms as secondary guidance unless their current official specifications confirm them.
Frequently Asked Questions
What is the difference between 1200 × 630 and 1200 × 627?
They are close landscape sizes from different guidance: 1200 × 630 is a common cross-platform recommendation in secondary references, while LinkedIn documents 1200 × 627 and a 1.91:1 frame for shared links.
Can a link be shared if LinkedIn cannot load its preview image?
Yes. LinkedIn says the link can still be shared even when it cannot retrieve a preview image.
Why can an updated Open Graph image take time to appear?
LinkedIn caches content; its guidance says to allow up to 48 hours for cached content to refresh after metadata changes.
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.
