OG image size: 1200×630 pixels

Use 1200×630 pixels (a 1.91:1 ratio), JPG or PNG, under 1 MB, with anything important kept in the centre square. That one file looks right on Facebook, LinkedIn, X, Slack, Discord and WhatsApp.

Open Graph image dimensions by platform

Platform	Recommended	Ratio	Minimum	Max file size
Facebook	1200 × 630	1.91:1	600 × 315 for large card; 200 × 200 absolute	8 MB
LinkedIn	1200 × 627	1.91:1	200 × 200 (smaller than ~400 wide shows as thumbnail)	5 MB
X (summary_large_image)	1200 × 628	~1.91:1, displayed at 2:1	300 × 157	5 MB
X (summary)	240 × 240 or larger square	1:1	144 × 144	5 MB
Slack	1200 × 630	1.91:1 (shown up to ~360px wide)	No published minimum	No published limit; keep small
Discord	1200 × 630	1.91:1 with summary_large_image	No published minimum	No published limit; keep small
WhatsApp	1200 × 630	1.91:1 or square thumbnail	~300 px wide for the large layout	~300–600 KB (reported)
iMessage	1200 × 630	1.91:1	No published minimum	Keep small

Sources: Meta Sharing best practices, X Developer docs (Cards markup), LinkedIn Help (“Make your website shareable”). Slack, Discord and WhatsApp don’t publish limits; figures are observed behaviour.

See what gets cropped

Every platform centre-crops your image to its own shape. Pick a platform to see the part that survives. Try your own image: it never leaves your device.

Use my image Show centre safe zoneYour image: 1200×630 (1.90:1)

Facebook / LinkedIn large card: keeps the bright area and 0% of your image is cut off.

The dashed square is the centre-safe zone (the middle 630×630 of a 1200×630 image). Anything inside survives every crop, so put logos and key words there.

Why the centre matters

No platform shows your image exactly as you made it. Facebook and LinkedIn crop to 1.91:1, X crops large cards to 2:1, and small layouts crop to a square. The crop is always taken from the centre.

So a 1200×630 image has a 630×630 “safe zone” in the middle. Put the logo and the few words that matter there and they survive every layout. Text hugging the left edge is the most common casualty.

Drop your own image into the tester to see the loss for each shape.

The tags to declare with your image

<meta property="og:image" content="https://example.com/og/launch.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Dashboard showing deploy time dropping from 14 to 6 minutes" />
<meta name="twitter:card" content="summary_large_image" />

Checklist

Absolute https:// URL, publicly reachable, not blocked by robots.txt or bot protection.
JPG, PNG or WebP. Not SVG, not AVIF.
Under 1 MB (300 KB is a good target for WhatsApp).
A new file name when you change it, so caches pick up the new version.

Need an image? The OG image generator exports exactly 1200×630. Already have one? Check it live to see its real pixel size and weight.

Frequently asked questions

What is the best OG image size?

1200×630 pixels. It is the 1.91:1 ratio Facebook and LinkedIn use for large cards, it displays well on X, Slack and Discord, and it is sharp on high-density screens.

What is the minimum og:image size?

Facebook ignores images under 200×200 and shows images under 600×315 as small thumbnails. X needs at least 300×157 for summary_large_image. Stay at 1200×630 and you clear every minimum.

What file size should an OG image be?

Keep it under 1 MB, ideally 100–300 KB. Hard limits are 8 MB on Facebook and 5 MB on X and LinkedIn, but WhatsApp and Slack give up on large files much sooner.

PNG or JPG for og:image?

PNG for text, flat colours and logos (crisp edges), JPG for photos (smaller files). WebP is supported by the major platforms but some smaller apps still don’t read it. Avoid SVG: it isn’t supported.

Should I declare og:image:width and og:image:height?

Yes. Facebook processes images asynchronously; declaring the dimensions lets it render the large card on the very first share instead of after the image is processed.