SnapFrame STUDIO

Social and Open Graph images: the 2026 numbers

Guide 02 · sizes, crops, safe areas · Updated 16 November 2026

A link preview is a thumbnail and a headline competing with a dozen others in a feed. The image either earns the click or wastes the space. The technical part is small and knowable: one baseline size, a handful of crops, and a few rules about where text can safely sit.

The baseline: 1200 × 630

1200×630 is a 1.91:1 ratio and remains the safest single Open Graph image: it fills the preview card on Facebook, LinkedIn, Slack, Discord, WhatsApp, Telegram, Notion and most link-unfurlers without letterboxing.

Design at 1200×630, export at 2x (2400×1260) when the file size allows, and let each platform downscale. Downscaling is always kinder than upscaling.

Per-platform reference

SurfaceRatioRecommended pixelsNotes
Open Graph (default)1.91:11200×630Used by Facebook, LinkedIn, Slack, Discord, iMessage and most others.
X / Twitter large card2:1 (1.91:1 accepted)1200×600 – 1200×675A 1200×630 image is cropped slightly top and bottom.
LinkedIn feed1.91:11200×6271.91:1 matches the card exactly; 1200×630 is fine.
Instagram feed4:51080×13504:5 occupies the most vertical space in the feed.
Instagram / TikTok story9:161080×1920Keep content clear of the top 250px and bottom 340px.
YouTube thumbnail16:91280×720Text must remain readable at 210×118.
Pinterest2:31000×1500Tall pins get more feed height.
Blog hero (inline)16:91600×900Doubles as a good OG image if you accept minor cropping.

Safe areas

Platforms crop link previews differently, and a few overlay UI on top of the image. Keep the essentials inside the middle:

Text on a preview image

Link cards already show the title and description next to the image, so the image does not have to repeat them. When it does carry text:

The tags that get read

<meta property="og:title" content="…">
<meta property="og:description" content="…">
<meta property="og:image" content="https://example.com/og.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta name="twitter:card" content="summary_large_image">

Use an absolute URL. Some crawlers resolve relative paths, many do not. State the width and height so the first render is not a guess. Keep the image under ~300KB: some platforms skip images that take too long to fetch, and WebP is accepted by every major crawler in 2026.

Testing before you publish

Caches are the usual reason a new image "does not show up". Most debuggers have a re-scrape button; without one, appending ?v=2 to the URL resets the cache.

Common mistakes

The studio exports 1200-friendly ratios directly — pick 16:9 for a 1600×900 hero, or 1:1 and 4:5 for feed posts — and every export is rendered at 2x, so the same composition works for a link card and a print deck.

Keep reading

Try it on your own screenshot

Free, no sign-up, and the image never leaves your browser.

Open the studio