Resize image for LinkedIn Post (1200×627)
LinkedIn recommends 1200×627 (1.91:1) for both in-feed image posts and shared link previews. It's essentially the same as Facebook's preview size — a single image at this ratio works across all major business platforms.
LinkedIn recommends 1200×627 pixels (1.91:1) for in-feed images and shared link previews. It is three pixels shorter than the 1200×630 Open Graph standard, a difference with no practical consequence — one export serves LinkedIn, Facebook and every other platform that reads og:image. The feed column is narrow, rendering that file at roughly 550 CSS pixels on desktop and around 400 on a phone, so small type in a chart or screenshot becomes unreadable. Use PNG for anything containing text. LinkedIn caches link previews aggressively, and the Post Inspector is the only reliable way to force a refresh after changing a page's og:image. Note that carousels and document posts use 1:1 or 4:5 instead, so a 1.91:1 asset is the wrong shape for those. LinkedIn does not crop 1.91:1 images in the feed, but it does centre-crop anything else, so a square graphic shared as a link preview loses its top and bottom.
Drop an image to resize to 1200×627
JPG or PNG
What is the difference between a LinkedIn feed image and a link preview?
LinkedIn treats these as two different objects that happen to share dimensions. A native image post uploads the file directly and displays it at up to the full column width, roughly 550 CSS pixels on desktop. A link preview is generated by fetching the destination page and reading its og:image tag, then rendering a card with the headline and domain beneath. Native image posts are shown larger and more prominently; link previews are smaller and carry the text overlay. This matters because the same 1200×627 file will be seen at noticeably different sizes depending on which route it takes into the feed. LinkedIn caches link previews aggressively, and the Post Inspector tool is the only reliable way to force a refresh after changing a page's og:image. For native uploads there is no cache issue — deleting and reposting simply uses the new file.
Column width, mobile rendering and document posts
The LinkedIn feed column is narrow, and on mobile it is narrower still. A 1200-pixel-wide image rendered at around 400 CSS pixels on a phone loses roughly two-thirds of its linear detail, which means small type in a chart or screenshot becomes unreadable. Link preview cards compound this by shrinking the image further and placing the headline text below it. LinkedIn does not crop 1.91:1 images in the feed, but it does centre-crop anything else, so a square image posted as a link preview loses its top and bottom. Document and carousel posts follow different rules entirely — those are uploaded as PDFs or multi-page files and displayed at 1:1 or 4:5 — so a 1.91:1 asset is the wrong shape for a carousel. Native video has its own specification again.
Designing for a professional feed at small scale
The practical constraint on LinkedIn is that the image is small and surrounded by dense text, so it has to earn attention in a fraction of a second. A single idea, high contrast and generous type work; detailed infographics do not. If you are sharing data, extract the one number that matters and make it the image rather than posting the full chart. Keep a margin of at least 60 pixels inside the edges so nothing is clipped by the card border. Where the same image is being used both as a native post and as the og:image for an article, build for the smaller link-preview case and it will hold up in both. For a series of posts, a consistent visual template makes the set recognisable in the feed, which matters more on LinkedIn than on platforms where content is discovered through search rather than through a follow graph.
LinkedIn Post tip: use bold contrast for the small feed preview
On LinkedIn, posts with images get roughly 2× the engagement of text-only posts. Use bold contrast and minimal text so your image is readable in the small in-feed preview.
LinkedIn Post size FAQ
Is 1200×627 the same as the Open Graph size?
- Effectively yes. Open Graph specifies 1200×630 and the three-pixel difference is invisible, so one file works for both.
Does LinkedIn crop other aspect ratios?
- Anything that is not 1.91:1 is centre-cropped in the preview card. Native image posts have a little more latitude but still favour 1.91:1.
Why does the old preview image keep showing?
- LinkedIn caches link previews. Run the URL through LinkedIn's Post Inspector to force a re-scrape after changing the og:image.
Is there a different size for carousel posts?
- Yes. Document and carousel posts use 1080×1080 or 1080×1350. A 1.91:1 asset is the wrong shape for those.
Why is my chart unreadable in the feed?
- The image renders around 400 CSS pixels wide on mobile. Extract the single number that matters instead of posting a full chart.
Do native image posts perform differently from link previews?
- They are displayed larger and without the headline overlay, so the image itself carries more weight. The dimensions are the same either way.
Should I use JPG or PNG?
- JPG for photographs, PNG for flat designs with sharp text where JPEG artefacts would show around the type.
Does the file leave my browser?
- No. The resize runs locally on a canvas and nothing is transmitted.
LinkedIn post formats and their shapes
| Post type | Recommended size | Ratio |
|---|---|---|
| Native image post | 1200 × 627 | 1.91:1 |
| Link preview card | 1200 × 627 via og:image | 1.91:1 |
| Document / carousel | 1080 × 1080 or 1080 × 1350 | 1:1 or 4:5 |
| Profile banner | 1584 × 396 | 4:1 |
1200×627 and the 1200×630 Open Graph size are interchangeable in practice.
Last updated:
References: LinkedIn Help image specifications for shares and posts; Open Graph protocol specification; LinkedIn Post Inspector documentation for preview cache refresh.