OG Image Size: 1200×630 Explained
The standard Open Graph image size is 1200×630 pixels (a 1.91:1 aspect ratio). It is the size Facebook, X, LinkedIn, WhatsApp, Slack, and Discord recommend and render correctly, so building every og:image at 1200×630 is the safe default for social sharing.
Why 1200×630?
Social platforms crop and scale the shared preview. 1200×630 is wide enough to stay sharp on high-density screens while keeping the ratio (1.91:1) that all major platforms render without cropping the headline or branding. Smaller images get upscaled and look blurry; larger ones are downscaled or rejected.
The rules to follow
| Property | Recommended |
|---|---|
| Width | 1200 px |
| Height | 630 px |
| Aspect ratio | 1.91:1 |
| Max file size | Under 5 MB (8 MB is the hard cap) |
| Format | PNG (crisp text) or JPG (photos) |
Where the safe area is
Platforms sometimes crop the top and bottom or a vertical strip. Keep headline text and your logo inside the middle ~50% of the card so important content survives most crops.
Why some previews come out as a small thumbnail
A correct 1200×630 image can still render as a small square thumbnail beside the text instead of a wide card. That decision belongs to the platform, and it is not driven by the image dimensions alone — LinkedIn, Slack and WhatsApp each pick a layout from the page and the image together, and none of them exposes a setting to force the large card.
Two things are in your control and are worth checking first, because a broken one produces the small card every time:
- The image has to be fetchable when the crawler asks. A thumbnail is what platforms fall back to when they cannot read or parse the image. Our own diagnostic reports this per platform, including the cases where a crawler gives up: an animated image and an image over its fetch budget (WhatsApp's is 600 KB in our configuration) both share as text with no picture at all rather than as a small card.
/trymeasures the real bytes, format and animation and states the verdict per platform. - The declared dimensions have to match the real file.
og:image:widthandog:image:heightthat disagree with the image are a common cause of a degraded card; a template render always declares what it actually produced.
What you cannot do is force the wide card where a platform prefers the thumbnail. No tool can, which is why we do not sell it: see WhatsApp Link Preview Not Showing? for the causes that are actually fixable, and the cache guide for why an image you changed may not be the one being read.
How FastOG handles size
FastOG renders every template at exactly 1200×630, so you never have to think about size or ratio — the output is ready for og:image and twitter:image out of the box.
<meta property="og:image" content="https://fastog.com/api/v1/og?template=default&title=My+Post&key=sk_...&s=...">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
The API also accepts an explicit width, height and format (png, jpeg or webp) when a surface needs something other than the default — X profile headers are the shipped example, at 1500×500 via the xheader template.
FAQ
Is 1200×630 still the right size in 2025?
Yes. It remains the widely recommended default across Facebook, X, LinkedIn, WhatsApp, Slack, and Discord.
What if I use a different size?
It usually still works but may be cropped or blurred. If you must deviate, keep the 1.91:1 ratio and stay under 5 MB.
Does FastOG let me set a custom size?
Yes. The default is 1200×630, which is what the platforms expect, but the API accepts width, height and format (png, jpeg, webp) when you need a different canvas — for example a 1500×500 X profile header.