Skip to content

Open Graph image dimensions

Recommended pixel dimensions and aspect ratio for the `og:image` meta tag. Facebook/LinkedIn render shares using a 1.91:1 aspect ratio (~1200×630); Twitter's `summary_large_image` card uses 2:1. Wrong dimensions cause ugly cropping in shares.

Open Graph image dimensions determine how the page's preview image appears when shared on Facebook, LinkedIn, Slack, Discord, and any other Open-Graph-aware platform. Each platform crops to its own aspect ratio when the source image doesn't match its expected ratio, so getting the dimensions right at the source avoids unpredictable cropping.

Recommended dimensions per platform:

  • Facebook: 1200×630 (1.91:1). Minimum: 200×200. Below 600×315 falls back to a square thumb.
  • LinkedIn: same as Facebook -- 1200×627 (essentially 1.91:1).
  • Twitter summary_large_image: 2:1 ratio, minimum 300×157, optimal 1200×600.
  • Twitter summary: square, minimum 144×144, optimal 360×360.
  • Slack/Discord: respect og:image dimensions; use Facebook's spec for safety.

Common dimension bugs:

  1. Square image on summary_large_image card: 600×600 OG image declared, Twitter card type is summary_large_image. Twitter expects 2:1; it crops the square to fit the wide format and the result usually clips important content. Either provide a wider image or change the card type to summary.

  2. Image too small (<200×200): Facebook treats sub-200 images as too small to display. The image is silently ignored and shares fall back to no preview. Use at least 200×200; optimal 1200×630.

  3. Aspect ratio outside 1.5-2.4: panoramic (e.g. 3000×500, 6:1) or portrait (e.g. 400×800, 1:2) images get center-cropped by Facebook to fit 1.91:1. Important content at the top, bottom, or sides of the source image gets clipped.

  4. No og:image:width / og:image:height declared: Facebook must download and measure the image to compute the preview, slowing first-share renders. Declaring the dimensions in the OG tags lets the platform reserve the correct aspect-ratio space immediately.

The BeaverCheck OG depth analyzer evaluates declared dimensions against these thresholds when both og:image:width and og:image:height meta tags are present. It does NOT fetch the image to measure actual file dimensions -- that would require a per-scan additional HTTP request.

The cleanest authoring approach: generate a single 1200×630 image, set both width and height meta tags explicitly, and use summary_large_image for the Twitter card.

Further reading

Send Feedback