OG Image Sizes: The 2026 Guide for X, Facebook & LinkedIn

When you paste a link into X, Facebook, or LinkedIn, the platform pulls a preview card: a title, a short description, and — if you’ve set it up — a large image. That image is controlled by Open Graph meta tags, and getting its size right is the difference between a sharp, professional preview and an awkwardly cropped thumbnail.

This guide covers the exact dimensions that work across the major platforms in 2026, the safe-area rules that keep your text readable everywhere, and how to generate a correct-size image in about a minute.

The only sizes you need

For link previews, one size covers nearly every case:

Platform	Recommended size	Aspect ratio	Notes
Facebook / Open Graph	1200 × 630 px	1.91 : 1	The og:image standard; Meta documents 1200 × 630 as the ideal size
LinkedIn	1200 × 627 px	1.91 : 1	LinkedIn’s own guidance for link-share images
X (Twitter)	1200 × 630 px	~2 : 1	summary_large_image cards display at roughly 2:1; 1200 × 630 renders cleanly

The practical takeaway: design at 1200 × 630 and you are covered on all three platforms. The tiny difference between 630 and 627 pixels tall is invisible in practice — no platform will reject or visibly distort your image over three pixels.

A few technical details worth knowing:

• Minimum size: Facebook will not show a preview image smaller than 200 × 200 px. Always stay well above that floor.
• File formats: JPG and PNG both work everywhere. Use PNG for graphics with text or flat colors, JPG for photographic backgrounds.
• File weight: keep the file under ~1 MB. Larger files still work, but they slow down the first scrape and can delay the preview appearing.
• The tags that matter: og:title, og:description, og:image, plus twitter:card set to summary_large_image so X renders the large format instead of the small thumbnail.

Safe-area rules: design for the crop

Every platform crops slightly differently — X trims the top and bottom a touch more aggressively than Facebook, and mobile apps crop differently from desktop. Design defensively:

1. Keep text inside the middle 80%. Leave roughly 60 px of breathing room on every edge at 1200 × 630. Anything near the border risks being cut on some client.
2. One headline, max. A preview card is glanced at for a second. A short title in a large, bold font beats a paragraph every time.
3. High contrast wins. Cards appear at small sizes in busy feeds. Dark text on light backgrounds (or the reverse) with a strong contrast ratio stays legible when scaled down.
4. Test the actual card. After publishing, paste your URL into each platform once and look at the real render. X and Facebook both cache previews aggressively — if you change the image later, use Facebook’s Sharing Debugger to force a re-scrape.

Common mistakes

• Using a square or portrait image. A 1080 × 1080 Instagram-style square gets center-cropped into a wide banner, usually decapitating the headline. Design wide from the start.
• Tiny text. If your title is unreadable at 300 px wide, it fails. Preview cards on mobile are small — err on the side of bigger type.
• No image at all. Without og:image, platforms fall back to a text-only card (or grab a random image from the page). A text-only card in a visual feed is easy to scroll past.
• Forgetting twitter:card. Without summary_large_image, X renders the small right-aligned thumbnail variant, wasting most of the card’s visual space.

Make yours in a minute with PicForge

You don’t need a design tool account or a template subscription. PicForge’s OG Image Generator renders at exactly 1200 × 630, entirely in your browser:

1. Open the generator and pick one of the six built-in styles.
2. Type your headline, subtext, and site name.
3. Download the PNG — no sign-up, no watermark, nothing uploaded to a server.

Because rendering happens locally with the same pipeline on every visit, what you see in the live preview is exactly what gets downloaded. Pair it with the size table above and your link previews will look deliberate on every platform.

Quick FAQ

Do I need different images for each platform? No. A single 1200 × 630 image works across Facebook, LinkedIn, and X. Only create variants if you want platform-specific branding.

Why does my new image not show up when I share the link? Platform caches. Facebook’s Sharing Debugger and X’s Card Validator both let you force a fresh scrape of your URL.

PNG or JPG? PNG for text-heavy graphics (sharper edges), JPG for photographic backgrounds (smaller files). Both are accepted everywhere.

What about the og:image:width and og:image:height tags? Including them (1200 and 630) helps crawlers reserve layout space before the image loads. They’re optional but recommended.

---

Last updated October 2026. Platform specs change slowly, but if you spot an outdated dimension, let us know and we’ll fix it.