LinkedIn builds link previews from your page’s Open Graph tags. The image that appears in the feed is whatever og:image points at—subject to LinkedIn’s crop, minimums, and cache. This platform guide covers recommended LinkedIn OG image size (~1200×627 / 1.91:1), file and URL requirements, safe text margins, Post Inspector refresh, and how LinkedIn differs from Facebook and WhatsApp.
Pixel tables for LinkedIn surfaces also live on LinkedIn social image sizes. Cross-network habits: OG image best practices. Cache refresh walkthrough: LinkedIn link preview not updating.
Recommended dimensions
| Guidance | Value |
|---|---|
| Practical LinkedIn share image | ~1200×627 (about 1.91:1) |
| Cross-network master many teams use | 1200×630 with safe margins |
| Often-cited minimum | Around 200×200 (produces a small thumbnail—avoid for campaigns) |
Treat 1200×627 as the LinkedIn-oriented target and 1200×630 as a fine shared master if you leave padding so either crop still reads. Confirm general Open Graph sizing on OG image size.
Aspect ratio matters more than one exact pixel
LinkedIn may letterbox or crop depending on surface (feed vs detail). Designing at 1.91:1 with an inset safe zone beats chasing a single magic width every quarter when docs shift by a few pixels.
Safe text margins
LinkedIn crops edges on some layouts. Keep headlines, CTAs, and logos inside an inset of roughly 10% from each side. Background color or photography can bleed; type should not.
Bad habits:
- Edge-to-edge headlines
- Tiny UI screenshots as the entire card
- Low-contrast gray on gray
- Five-line paragraphs of on-image text
Good habits:
- Three to six word headline
- One logo mark
- High contrast
- Optional short subtitle that still fits inside the safe zone
Build readable cards in the OG Image Generator. Preview crops with the Social Preview Simulator.
File tips
- PNG for flat graphics and sharp type; JPG for photographs.
- Keep files lean—oversized assets slow scrapes and stress messengers (WhatsApp is especially sensitive; see Facebook works, WhatsApp does not).
- Prefer widely supported formats for the tagged URL; do not rely on WebP-only as the sole
og:image(formats guide). - When artwork changes, upload a new filename. Overwriting
og.pngin place is a common reason Post Inspector still shows the old picture. - Optional but useful tags:
<meta property="og:image" content="https://example.com/og/article-v2.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="627" />
<meta property="og:image:alt" content="Article cover with title on brand background" />
Generate a full snippet with the Meta Tag Generator.
Absolute HTTPS URL (required)
LinkedInBot must fetch the image without your cookies.
<!-- Bad -->
<meta property="og:image" content="/media/og.png" />
<!-- Good -->
<meta property="og:image" content="https://example.com/media/og.png" />
Also ensure:
- The page is public (no soft login gate for anonymous visitors)
- The image opens in a private window
- CDN hotlink rules or bot blocks are not rejecting LinkedInBot
- Signed URLs do not expire before the next scrape
If the image fails on every network, start with og:image not showing.
Wire the rest of the card
LinkedIn reads more than the image:
| Tag | Role |
|---|---|
og:title |
Headline on the card |
og:description |
Supporting text (may truncate) |
og:image |
Visual |
og:url |
Canonical URL / cache key preference |
og:type |
Usually website or article |
Keep one pipeline for tags—duplicate SEO plugins create conflicting titles and images. Verify with View Source, then the Link Preview Checker.
Refresh with Post Inspector
After HTML and the file are correct:
- Open LinkedIn’s Post Inspector (overview: LinkedIn Post Inspector).
- Sign in.
- Paste the exact share URL and Inspect.
- Compare title, description, and image to View Source.
Inspecting refreshes LinkedIn’s stored data for that URL string, which helps new shares. An existing post may keep the card it was created with—delete and re-share if the old card must go. Full troubleshooting: LinkedIn link preview not updating.
Inspect the same string you put in og:url when possible. UTM parameters can create separate cache entries.
LinkedIn vs Facebook vs WhatsApp
| Concern | |||
|---|---|---|---|
| Primary tags | Open Graph | Open Graph | Open Graph |
| Typical large card size | ~1200×627 | ~1200×630 | Same art, stricter weight |
| Official refresh tool | Post Inspector | Sharing Debugger | No public debugger |
| Existing posts | Often keep old card | Often keep old card | Chats may keep old unfurl |
| Common failure | Cache + small/square image | Cache + relative URL | Heavy/exotic files |
Facebook refresh notes: Facebook Sharing Debugger and Facebook link preview not updating. WhatsApp: WhatsApp link preview not working.
Practical takeaway: one well-made 1.91:1 asset usually serves all three, but you must re-scrape LinkedIn and Facebook separately and re-test WhatsApp on a device after file-weight fixes.
CMS and framework notes
- WordPress: featured images are often cropped square or medium—override with a dedicated OG field or plugin setting pointed at a 1200×627 file (WordPress guide).
- Next.js: set absolute images via
metadataBase/openGraph.imagesoropengraph-image(Next.js guide). - Dynamic titles: generate per-post cards, but cache the PNG URL LinkedIn fetches (dynamic OG images).
Whatever the CMS, View Source on production is the source of truth—not the editor preview pane.
Campaign checklist for LinkedIn shares
Before a company-page post or employee amplification:
- Export ~1200×627 (or 1200×630 with safe margins).
- Upload under a versioned path.
- Confirm absolute
og:imagein View Source. - Private-window image load.
- Link Preview Checker.
- Post Inspector on the canonical URL.
- Share a test post from a draft/test context if you can; know that production posts may stick.
If you change only the bitmap and keep the same URL, expect pain—change the path.
Design details that read well on LinkedIn
LinkedIn audiences skim professional feeds. Cards that look like noisy consumer ads underperform even when tags are perfect. Prefer:
- Clear product or article framing
- Legible sans headlines (avoid hairline scripts)
- Brand color blocks instead of busy stock collage
- Honest alt text via
og:image:alt
Use LinkedIn size reference when you also create native upload sizes (personal posts, cover images). Those native upload dimensions are not the same problem as og:image for shared links—do not confuse “image I uploaded into the composer” with “image LinkedIn scraped from my URL.”
Checklist
- ~1200×627 (1.91:1) or 1200×630 with safe margins
- Lean PNG/JPG; absolute https
og:image - Text inside safe zone; strong contrast
- View Source + Link Preview Checker clean
- Post Inspector run after changes (tool page)
- New filename when art changes
- Separate WhatsApp/Facebook checks if those channels matter
LinkedIn OG images succeed when the file is large enough, the URL is public, the HTML is consistent, and the cache is refreshed on purpose. Size is the starting point—1200×627 / 1.91:1—but verification and Post Inspector close the loop. Ship that combination and your link cards stay readable when someone pastes your URL into the feed.
Frequently asked questions
Short answers from this guide.
What LinkedIn OG image size should I use?
About 1200×627 pixels (roughly 1.91:1). A 1200×630 master with safe margins also works well across LinkedIn and other networks.
Why is my LinkedIn preview showing a tiny thumbnail?
The image is often too small, too square, or failing to load. Use a large 1.91:1 asset, absolute https, and confirm the file opens logged out.
How do I refresh a LinkedIn link preview?
Fix og tags in View Source first, then run the exact URL through LinkedIn Post Inspector. See the LinkedIn preview troubleshooting guide for stuck posts.
Does LinkedIn use the same image as Facebook?
Usually the same og:image works. Crops and caches differ. WhatsApp adds stricter file-weight sensitivity. Test each network after changes.
Should important text touch the edges?
No. Keep headlines and logos inside a generous inner margin so LinkedIn crops do not clip them.
PNG or JPG for LinkedIn?
Either works when the file is lean and public. PNG for sharp graphics; JPG for photos. Avoid exotic formats as the only tagged file.