Open Graph image size (and why 1200×630 wins)

The size that works

1200×630 pixels at a 1.91:1 ratio is the target for og:image. At this size your image renders at full width on Facebook, LinkedIn, Slack, Discord, and iMessage without upscaling or unexpected cropping.

The ratio matters as much as the resolution. If you supply a square or portrait image, most platforms crop it to a landscape card and you lose control of what shows.

Recommended sizes per platform

| Platform | Recommended size | Preferred ratio | Notes | |---|---|---|---| | Facebook | 1200×630 | 1.91:1 | Smaller images render inline, not as large cards | | LinkedIn | 1200×627 | 1.91:1 | Crops tightly; square images show as small thumbnails | | X (Twitter) | 1200×628 (summary_large_image) | 2:1 | Uses twitter:image; falls back to og:image | | Slack | 200×200 minimum | Any | Displays as thumbnail; larger images show full-width | | WhatsApp | No hard minimum | 1.91:1 | Most reliable when image is under ~300 KB |

These are recommended sizes for the large-card preview. Platforms will still render smaller images, but anything well below these — or not close to the right aspect ratio — may be cropped or shown as a small thumbnail.

For X's summary_large_image card type, the image must be at least 300×157 at a 2:1 ratio. Without twitter:card set, X falls back to og:image but may show a smaller card.

WhatsApp does not publish hard limits, but previews are most reliable when the file is small and fast to fetch. Aim for under 300 KB compressed.

File rules

• Absolute URL only. og:image must start with https://. A path like /og.png fails on every external platform because their crawlers fetch from their own servers.
• Publicly reachable. No auth walls, no IP allowlists, no CDN signed URLs that expire.
• Common formats. JPEG and PNG are universally supported. WebP works on most modern crawlers but may not render on older LinkedIn or Facebook mobile clients.
• File size. Keep it under 1 MB for fast scraping. WhatsApp is most reliable under 300 KB.

Common mistakes

• Supplying a square logo (og:image set to a 1:1 favicon or avatar) — it crops into a narrow strip on large-card layouts.
• Using a relative URL (/images/preview.png) — this is the single most common reason link previews show no image. See og:image is missing.
• Generating the image at 2×/3× resolution and forgetting to compress — 5 MB PNGs cause slow or failed scrapes.
• Setting a different image per-locale but using the same og:url — platforms cache by URL, so only one image wins.

How to check

Paste your URL into the Open Graph Checker. It confirms whether og:image resolves, reports the actual dimensions of the image it fetched, and flags relative URLs or load failures.