Blog Content Workflows 6 min read

LinkedIn Post Image Placeholders for Blogs and Docs

Get the correct LinkedIn image size for post links and articles, and set reliable og:image fallbacks so LinkedIn always shows a preview card when content is shared.

linkedin image sizelinkedin og imagesocial preview fallbackopen graphcontent workflows
LinkedIn Post Image Placeholders for Blogs and Docs

LinkedIn link previews pull from og:image. When that tag is missing or the image URL fails, LinkedIn renders a plain link card with no visual — making shared blog posts and docs look unfinished and hurting engagement.

Getting LinkedIn previews right requires the correct dimensions, an absolute URL returning a raster image, and a fallback strategy in your CMS or templating layer for posts that lack a dedicated featured image.

Dimensions

LinkedIn image size for posts and articles

For shared link previews — the kind generated when you paste a URL into a LinkedIn post — the recommended image size is 1200×627 pixels. LinkedIn crops images to approximately 1.91:1 in the card display.

For LinkedIn Articles, the cover image displays at 744×400 in the editor preview, but upload at least 1200×644 for sharp display on high-DPI screens.

PNG and JPEG are the safe choices. WebP works in most cases but has had inconsistent support across LinkedIn's crawler versions. Avoid GIF (only the first frame is used) and avoid SVG entirely.

Implementation text
<meta property="og:image" content="https://fallback.pics/api/v1/1200x627.jpg?text=Your+Post+Title" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="627" />
<meta property="og:image:type" content="image/jpeg" />

CMS workflows

LinkedIn fallbacks in WordPress, Ghost, and headless CMS

In WordPress with Yoast SEO, the Social tab lets you override the OG image per post. For a global fallback, set a default image in SEO > Social > Facebook settings — LinkedIn uses the same og:image tag.

In Ghost, the {{facebook_image}} helper provides the og:image value for social sharing. Wrap it in an #if conditional and substitute a generated URL when no image is set.

In Contentful or a similar headless CMS, query the image field with optional chaining and compute the fallback server-side before rendering the page head.

Debugging

Use LinkedIn Post Inspector to refresh stale previews

LinkedIn caches og:image at first-share time. If you update the image after the URL has already been shared, the cached version persists. LinkedIn's Post Inspector (linkedin.com/post-inspector/) lets you re-fetch the URL and clear the preview cache.

Common reasons a preview fails: the URL returns an HTTP redirect chain before the final image, the image is served with a Cache-Control: no-store header, or the og:image URL is relative rather than absolute.

If the Post Inspector shows the correct image but LinkedIn posts still show a broken card, check whether your page returns a 200 status. A redirect to a login wall or a maintenance page causes the crawler to read the wrong HTML head.

Quick reference

LinkedIn image sizes at a glance

Reference these when setting up LinkedIn og:image templates across different content types.

Shared link preview

1200×627 px, JPEG or PNG, 1.91:1 ratio, under 5 MB.

LinkedIn Article cover

Minimum 1200×644 px for sharp display. 744×400 shown in editor preview.

Company page banner

1128×191 px for the company cover photo — separate from og:image.

Key takeaways

What to standardize before shipping

  • LinkedIn uses og:image exclusively — there is no linkedin-specific image meta tag.
  • Use 1200×627 pixels, JPEG or PNG, for shared link preview cards.
  • Always use an absolute https:// URL; relative paths and SVGs will not render in LinkedIn previews.
  • Substitute a generated fallback URL for posts that lack a dedicated featured image.
  • Use LinkedIn Post Inspector to refresh stale cached previews after an image URL changes.

Production fallback layer

Use fallback.pics anywhere an image URL is accepted.

Start with one deterministic URL and standardize fallback behavior across your design system.

Read the docs