OG image size guide

What you are seeing: Your image appears cropped, letterboxed with bars, or shrunk into a small square thumbnail beside the text instead of filling the card.

The target is 1200 × 630

1200 × 630 pixels is a 1.91:1 landscape ratio, and it is what Facebook, LinkedIn, X, Discord and Slack all design their large card layouts around. Hitting it exactly means no platform has to crop or pad your image to make it fit.

The pixel count matters as well as the ratio. 1200 wide is enough to stay sharp on high-density displays without pushing the file size up unnecessarily.

OG image sizes by platform

One 1200 × 630 image works everywhere below. The differences are in the minimums, where each platform gives up on the large card, and in file size limits.

File size and format

Use PNG for graphics and text, JPEG for photographs, or WebP if you have checked it renders everywhere you care about. Avoid SVG: none of the major platforms render it as an og:image.

Keep the file under 600 KB, Meta's limit for WhatsApp previews and the strictest of the major platforms; around 300 KB leaves headroom. Serve the image from a public HTTPS URL that returns a 200 status with an image content type.

What goes wrong off-ratio

Too tall and platforms crop the top and bottom to reach 1.91:1. Anything centred vertically survives; anything near the edges is cut. This is how logos and headline text disappear from otherwise fine-looking cards.

Too wide and you get the same crop on the left and right, or letterboxing with grey bars depending on the platform.

Below roughly 600 × 315 the behaviour changes completely: rather than scaling your image up, most platforms abandon the large card and fall back to a small square thumbnail next to the text. That is a much bigger visual downgrade than a crop, and it is the case worth fixing first.

Designing for the crop

Even at the right ratio, assume the outer edges may be trimmed. Keep text and logos inside a safe area roughly 100 pixels in from each edge, and do not put anything load-bearing in a corner.

Test at small sizes. A card that reads well at full width often becomes illegible in a WhatsApp thread or a mobile feed, where it may render under 400 pixels wide. If the headline is not readable there, it is too small.

Declare the dimensions

og:image:width and og:image:height tell platforms the size before they download the image. Facebook uses them to render the card on the first share instead of waiting to fetch the file, so the first person to share your link sees the right layout.

Make sure the values match the real file. Declared dimensions that disagree with the image are worse than none.

Size tags for a 1200 × 630 image

<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 property="og:image:type" content="image/png" />
<meta name="twitter:card" content="summary_large_image" />

Frequently asked

What size should an OG image be?

1200 × 630 pixels, a 1.91:1 landscape ratio, under 600 KB. That single size works for Facebook, X, LinkedIn, Slack, Discord and WhatsApp.

Is the X (Twitter) card image a different size?

Not in practice. X's docs specify 2:1 for summary_large_image, but a 1200 × 630 image displays with only a slight trim at the top and bottom, so one image serves both. Keep text inside the safe area and it survives the crop.

What is the minimum og:image size?

600 × 315 is the practical floor for a large card. Below that, Facebook and LinkedIn switch to a small thumbnail layout. 1200 × 630 is the recommended size and gives you headroom on high-density screens.

Do square images work?

They render, but not well. A 1:1 image gets centre-cropped to 1.91:1 on most platforms, so you lose roughly half the height. If you only have a square asset, place it on a 1200 × 630 canvas with padding rather than letting the platform crop it.