Open Graph Image Size Guide (2026): Facebook, X, LinkedIn, and More

If you have searched for open graph image size, you already know the pain: one platform crops your text, another compresses your image, and the third shows a random thumbnail.

This guide gives you one workflow that works across the major platforms and keeps your previews clean.

Why this keyword keeps coming up

The phrase open graph image size appears with variants like:

• open graph image size recommendation
• facebook open graph image size
• whatsapp open graph image size
• twitter open graph image size

The reason is simple: teams want one reusable asset that survives different crawlers, aspect ratios, and cache behavior.

Default size that works in most cases

Start with 1200 x 630 (roughly 1.91:1) for your base share image.

Why this default works:

• It is widely compatible with Open Graph previews.
• It gives enough resolution for desktop and retina screens.
• It maps cleanly to many social preview layouts.

If your workflow can only support one export size, this should usually be it.

How X (Twitter) differs

For summary_large_image, X documents a 2:1 image ratio with a minimum of 300x157.

That does not always match the 1200 x 630 Open Graph default perfectly. If X traffic matters a lot for you, create a second image variant in 2:1 and test both cards.

Safe design rules to avoid ugly crops

Use a safe-area approach:

• Keep key text away from edges (roughly 8-10% inner padding).
• Avoid putting logos in the bottom-right corner only.
• Keep headline length short enough for mobile previews.
• Prefer one focal visual, not a busy collage.

Think of your design as a flexible billboard, not a pixel-perfect poster.

Metadata setup checklist

On each article page, keep your metadata predictable:

• og:title
• og:description
• og:image
• og:type
• twitter:card set to summary_large_image
• twitter:image (optional but recommended for explicit control)

Also use absolute image URLs and make sure your preview image is crawlable without login.

Common reasons previews fail

When previews look wrong, these are the usual causes:

• Old cache from social crawler fetches
• Relative image URL instead of absolute URL
• Wrong image dimensions or oversized file
• Slow image endpoint timing out crawler requests
• Dynamic metadata not available server-side

After updates, re-scrape with platform validators/debuggers to refresh cache.

Production export settings

For reliable share previews at scale:

• Export JPG for photo-heavy covers and PNG for text-heavy graphics.
• Keep file size reasonable so crawlers fetch quickly.
• Use consistent templates by content category.
• Version filenames when you need forced cache refreshes.

Example naming:

• og-seo-checklist-v1.jpg
• og-seo-checklist-v2.jpg

Quick answer

If you only remember one thing:

• Create your primary image at 1200 x 630
• Keep text in a generous safe area
• Add summary_large_image and Open Graph tags
• Validate on at least one real URL per platform

That single process solves most open graph image size issues before publish day.