Open Graph image sizes 2026
Last updated: 2026-05-14
Every platform reads og:image differently. This is the current reference, platform-by-platform, for the social cards people actually see in 2026. If you only ship one size, ship 1200 × 630 px.
Master reference table
| Platform | Recommended | Aspect | OG tag | Notes |
|---|---|---|---|---|
1200 × 630 | 1.91:1 | og:image | Minimum 600×315. Anything smaller is rendered as a tiny thumbnail. | |
| X (Twitter) | 1200 × 600 | 2:1 | twitter:image (card=summary_large_image) | X scales og:image but accepts twitter:image for an exact-fit card. |
1200 × 627 | 1.91:1 | og:image | Slight aspect tweak vs Facebook; safer to ship both. | |
| Discord | 1200 × 630 | 1.91:1 | og:image | Embed cards honor og:image directly. PNG and JPG both fine. |
| Slack | 1200 × 630 | 1.91:1 | og:image | Cached by Slackbot; force refresh with a query string change. |
1200 × 630 | 1.91:1 | og:image | Limit total image weight to ~300 KB; WhatsApp aborts large images. | |
| iMessage | 1200 × 630 | 1.91:1 | og:image | Apple Link Preview prefers og:image; static images only. |
| Bluesky | 1200 × 630 | 1.91:1 | og:image | Standard OG protocol; no Bluesky-specific tag. |
| Threads | 1200 × 630 | 1.91:1 | og:image | Same OG protocol as Meta family. |
| Mastodon | 1200 × 630 | 1.91:1 | og:image | Most instances honor og:image; image is fetched once and cached. |
The 1200 × 630 default
1200 × 630 (1.91:1) is the safe default. Facebook codified it, LinkedIn accepts a near-identical 1200 × 627, Discord/Slack/WhatsApp inherit Facebook's spec, and Bluesky/Threads/Mastodon honor the Open Graph protocol with the same expectations. A single 1200 × 630 PNG covers ~90% of share surfaces.
When to ship multiple variants
- X (Twitter): ship a 1200 × 600 (2:1)
twitter:imagefor pixel-exact summary_large_image cards. - LinkedIn: 1200 × 627 if you want zero crop. 1200 × 630 also works.
Common mistakes
- Shipping an image larger than ~5 MB (most crawlers refuse).
- Forgetting
og:image:widthandog:image:heighthints - Facebook caches faster when both are set. - Using a transparent PNG over white text - dark-mode clients render unreadable cards.
- Putting critical text inside the bottom 80px - some clients overlay UI controls there.
- Hosting the image on a slow origin - WhatsApp and iMessage time out around 1-2 seconds.
Recommended OG tag set
<meta property="og:type" content="website" />
<meta property="og:url" content="https://example.com/post" />
<meta property="og:title" content="Your title here" />
<meta property="og:description" content="One-line summary." />
<meta property="og:image" content="https://cdn.example.com/og.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:image" content="https://cdn.example.com/twitter.png" />FAQ
What size should an OG image be in 2026?
1200 × 630 pixels (1.91:1 aspect ratio) is the canonical Open Graph image size and works across Facebook, LinkedIn, Discord, Slack, WhatsApp, iMessage, Threads, Bluesky and Mastodon. Ship a separate 1200 × 600 (2:1) for X with twitter:image, and 1200 × 627 for LinkedIn if you want pixel-exact.
What is the minimum OG image size?
Facebook will accept down to 600 × 315 but renders it as a small card. Below that, platforms typically suppress the image entirely.
Does Twitter still use og:image?
Yes - X falls back to og:image when twitter:image is not present, and renders it as a summary card. For the larger 2:1 layout, set twitter:card to summary_large_image and provide twitter:image at 1200 × 600.
Why does WhatsApp not show my OG image?
WhatsApp has a strict size budget (around 300 KB) and a short fetch timeout. Compress your image and keep the og:image URL fast to respond.
How do I force Slack or LinkedIn to refresh a cached OG image?
Change the og:image URL (e.g. append a version query string). LinkedIn also offers the Post Inspector; Slack uses Slackbot which caches aggressively.
Want the right-size image without thinking about any of this? Generate one with OGImagen - every generation outputs all three native formats (1200×630, 1200×600, 1200×627) and gives you the meta tags pre-filled. Or check an existing URL with our OG checker.