Reference

Social Media Image Sizes for Link Previews: A Sourced Reference (2026)

Link-preview image sizes and limits from Meta, LinkedIn, Slack, Open Graph, Pinterest and YouTube docs, with check dates and unverified specs marked.

Asad AliDecember 22, 20258 min read

This is a reference for the images that appear when a link to your site is shared: the og:image and card images that platforms pull from your page's meta tags. Every number below comes from the platform's own documentation, and we say where we couldn't verify something.

Last checked: 13 November 2026. Platforms change these rules without notice. If a number matters to a launch, click through to the source.

If you want to generate these images automatically, see the dynamic OG image guide. If you're building previews for links your users paste into your own app, see link preview generation.

The short answer

A 1200 × 630 PNG or JPEG under 5 MB, referenced with absolute URLs in og:image, og:image:width, og:image:height and og:image:alt, meets every link-preview requirement documented below.

Platform Documented size guidance Ratio Max file size Source
Meta (Facebook) At least 1200 × 630 recommended; 600 × 315 minimum for larger display; 200 × 200 smallest allowed Close to 1.91:1 8 MB Meta: Images in link shares
LinkedIn Minimum 1200 × 627; under 401 px wide shows as a thumbnail 1.91:1 recommended 5 MB LinkedIn: Make your website shareable
Slack No size documented; classic unfurls read Open Graph and X Card metadata Not stated Not stated Slack: Unfurling links
X Not verified (docs unavailable when checked) Not verified Not verified X developer docs
Open Graph protocol No size requirement; defines the tags — — ogp.me

Open Graph protocol: the tags

The Open Graph protocol defines the tags that most platforms read. It doesn't set image sizes. It lists four required properties for every page: og:title, og:type, og:image and og:url. Optional image properties include:

  • og:image:secure_url: an alternate URL if the page requires HTTPS
  • og:image:type: the image's MIME type
  • og:image:width and og:image:height: size in pixels
  • og:image:alt: a description of the image. The spec says a page that specifies og:image should specify og:image:alt.
<meta property="og:title" content="Pricing that scales with you">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/pricing">
<meta property="og:image" content="https://cdn.example.com/og/pricing-v4.png">
<meta property="og:image:type" content="image/png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Three pricing tiers with monthly prices">
<meta name="twitter:card" content="summary_large_image">

Meta (Facebook)

From Meta's link-share image guide and webmaster sharing guide:

  • Size. Use images at least 1200 × 630 for the best display on high-resolution devices. Use at least 600 × 315 to get the larger link-preview layout. The smallest allowed image is 200 × 200.
  • Ratio. Keep images as close to 1.91:1 as possible to avoid cropping in Feed.
  • File size. Up to 8 MB.
  • Type. og:image:type is documented as one of image/jpeg, image/gif or image/png.
  • Width and height tags. Meta recommends setting og:image:width and og:image:height so the image loads correctly the first time a link is shared.
  • Caching. The crawler scrapes and caches metadata the first time a URL is shared. Images are cached by URL, so to change an image, use a new image URL. Updating the image doesn't update the preview on posts that already exist.
  • Encoding. The crawler only accepts gzip and deflate content encodings.
  • Debugging. The Sharing Debugger (Facebook login required) shows the tags it scraped and triggers a fresh scrape.

LinkedIn

From LinkedIn's help pages on making a website shareable and refreshing with Post Inspector. Both pages said "Last updated: 3 years ago" when we checked.

  • Required tags. og:title, og:image, og:description and og:url.
  • Size. Minimum 1200 × 627. Images less than 401 pixels wide display as a small thumbnail instead of a large image.
  • Ratio. 1.91:1 recommended.
  • File size. Up to 5 MB.
  • Refreshing. The Post Inspector refreshes a cached preview. LinkedIn notes the change only affects new posts that include the URL.

X (Twitter)

X reads its own twitter: card tags, and twitter:card set to summary_large_image requests the large-image card. When we tried to load X's card documentation on 13 November 2026, the developer pages returned errors (HTTP 402 and 404), so we have not verified X's current image dimensions, file size limit, or whether X falls back to Open Graph tags.

Rather than repeat figures from other sites, we suggest:

  • Set twitter:card to summary_large_image and twitter:image to the same 1200 × 630 image you use for og:image.
  • Check X's current developer documentation for card image limits before relying on a specific number.

Slack

Slack's link unfurling documentation says that when no Slack app handles a domain, Slack falls back to classic unfurling: it crawls the URL and looks for common Open Graph and X Card metadata. The page doesn't document image sizes or cache duration. A standard 1200 × 630 og:image is what Slack's classic unfurl will look for.

Discord

Discord's developer documentation describes the embed object that bots and webhooks send (title, description, URL, image, thumbnail). It doesn't document how Discord scrapes Open Graph tags from shared links or what image sizes it prefers, so we don't state Discord-specific rules. Test by pasting the link into a private server.

Pinterest

  • Rich Pins. Pinterest's Rich Pins guide says article and product Rich Pins use Open Graph or schema.org markup in the page <head>.
  • Image ratio. Pinterest's ad specifications recommend a 2:3 aspect ratio, or 1000 × 1500 pixels, for standard image ads. That is an ad spec; the Rich Pins guide doesn't state a size for organic Pins.

If Pinterest matters to you, a separate 1000 × 1500 portrait image (for example, offered through a "Pin it" button) avoids squeezing a landscape og:image into a tall Pin.

YouTube thumbnails

Not a link preview, but often generated by the same pipeline. YouTube's custom thumbnail guidance recommends:

  • Resolution: 3840 × 2160 for videos (2160 × 3840 for Shorts), with a minimum width of 640 pixels for videos
  • Ratio: 16:9 for videos, 9:16 for Shorts
  • Formats: image formats such as JPG or PNG
  • File size: 2 MB on mobile for video thumbnails; 50 MB on desktop

YouTube presents these as recommendations rather than hard limits.

What we left out, and why

  • Instagram, TikTok and in-feed post sizes. These platforms don't build link previews from your og:image, and we couldn't load Instagram's official help pages for post dimensions when we checked. We'd rather leave the numbers out than repeat unverified ones.
  • Profile pictures, banners and cover photos. These change often and aren't part of link sharing.
  • Third-party "safe zone" percentages. None of the official pages above publish crop safe zones. Keep important text away from the edges with generous padding, and check the preview in each platform's tool.

Generating each size from one template

If you render social images from HTML, render each size at its exact pixel dimensions rather than resizing one image. Text reflows properly and nothing gets stretched. With the Screenshotly API, set width and height to the target size and deviceScaleFactor to 1:

{
  "url": "https://example.com/og/pricing?size=link",
  "width": 1200,
  "height": 630,
  "deviceScaleFactor": 1,
  "format": "png"
}

width and height accept 320–3840 and 240–3840 CSS pixels. For outputs bigger than that, multiply with deviceScaleFactor (up to 3). A YouTube-style 3840 × 2160 thumbnail, for example, is a 1920 × 1080 template at deviceScaleFactor: 2:

import { writeFile } from 'node:fs/promises';

// Each target is rendered from the same template at its own layout size.
const TARGETS = {
  link: { width: 1200, height: 630, deviceScaleFactor: 1 }, // og:image / twitter:image
  pin: { width: 1000, height: 1500, deviceScaleFactor: 1 }, // Pinterest 2:3
  youtube: { width: 1920, height: 1080, deviceScaleFactor: 2 }, // 3840×2160 output
};

for (const [size, dimensions] of Object.entries(TARGETS)) {
  const res = await fetch('https://screenshotly.app/api/screenshot', {
    method: 'POST',
    headers: {
      'x-api-key': process.env.SCREENSHOTLY_API_KEY,
      'content-type': 'application/json',
    },
    body: JSON.stringify({
      url: `https://example.com/og/pricing?size=${size}`,
      format: 'png',
      ...dimensions,
    }),
  });
  if (!res.ok) throw new Error(`${size}: capture failed (${res.status}): ${await res.text()}`);
  await writeFile(`pricing-${size}.png`, Buffer.from(await res.arrayBuffer()));
}

Your template page reads size and switches its layout. These fields work on every plan, including Free. Run this on a server; the API key must never reach the browser. Upload the results to public storage with a versioned file name, as described in the OG image guide, because the API returns image bytes rather than a permanent public URL.

Pre-launch checklist

  • Image is 1200 × 630, PNG or JPEG, under 5 MB
  • og:image is an absolute, public URL that loads in a private window
  • og:image:width, og:image:height and og:image:alt are set
  • twitter:card is summary_large_image
  • Image file name changes whenever the image changes
  • Checked in Meta's Sharing Debugger and LinkedIn's Post Inspector
  • Pasted into Slack and Discord test channels

Render a 1200 × 630 card in the playground, or start free with 100 captures.

social media
image sizes
open graph
og image

About the Author

Asad Ali

Asad Ali

CTO at ZTABS and the developer behind Screenshotly. Writes about screenshot automation, API design, and building reliable SaaS backends with Next.js, Node.js, and TypeScript.

Credentials: CTO at ZTABS, full-stack developer, builder and maintainer of Screenshotly and its official JavaScript and Python clients

Frequently Asked Questions

What single size works for link previews?

1200×630 pixels. Meta recommends images of at least 1200×630 at close to 1.91:1, and LinkedIn's documented minimum is 1200×627 at a recommended 1.91:1. Keep the file in PNG or JPEG and under 5 MB, LinkedIn's limit, which is lower than Meta's 8 MB.

Can I use WebP for og:image?

Meta's documentation lists image/jpeg, image/gif and image/png as values for og:image:type. Since WebP isn't listed there, PNG or JPEG is the safer choice for link previews.

What size does X (Twitter) need for summary_large_image cards?

We couldn't retrieve X's developer documentation when we checked on 13 November 2026, so this page doesn't state X-specific limits. Set twitter:card to summary_large_image, use the same 1200×630 image, and check X's current card documentation.

Why doesn't my new image show up when I share the link again?

Platforms cache link previews. Meta caches images by URL and says to use a new URL for a new image. LinkedIn's Post Inspector refreshes its preview, but the change only applies to new posts. Put a version or content hash in the image file name.

Why aren't Instagram post sizes on this page?

Instagram doesn't use link-preview images from your site, and we couldn't load Instagram's official help pages for post dimensions when we checked. Rather than repeat numbers we couldn't verify, we left them out.

Ready to capture your first screenshot?

Get started with 100 free screenshots. No credit card required.

Related Articles