The standard OG image size is 1200×630 pixels, with a 1.91:1 aspect ratio. Use that one size and your link previews will render correctly on Facebook, X (Twitter), LinkedIn, Slack, Discord, WhatsApp and Telegram.
That's the short answer. The rest of this guide covers the details that actually trip people up: per-platform dimensions, the safe zone for text, file-size limits, and the meta tags that tell each platform where your image lives.
The one size that works everywhere
If you only remember one number, make it this:
| Property | Recommended value |
|---|---|
| Dimensions | 1200 × 630 px |
| Aspect ratio | 1.91:1 |
| Format | PNG or JPG |
| File size | Under 1 MB (hard limits are higher, but smaller loads faster) |
| URL | Absolute HTTPS URL |
Every major platform either uses 1.91:1 natively or crops gracefully from it. Designing at exactly 1200×630 means you create one image per page instead of five.
OG image size by platform
Platforms differ slightly in what they prefer and what they enforce:
| Platform | Recommended size | Notes |
|---|---|---|
| 1200 × 630 | Minimum 200×200; images under 600×315 render as a small thumbnail instead of a large card | |
| X (Twitter) | 1200 × 630 | summary_large_image cards crop toward 2:1 — keep critical content centered |
| 1200 × 627 | 1.91:1; effectively the same image as Facebook | |
| Discord | 1200 × 630 | Uses og:image for large link embeds |
| Slack | 1200 × 630 | Unfurls use Open Graph tags directly |
| 1200 × 630 | Keep the file small (aim well under 300 KB) or the preview may not load | |
| Telegram | 1200 × 630 | Reads og:image; caches aggressively |
| 1000 × 1500 | The exception — Pins prefer vertical 2:3, so use Pinterest-specific images there |
The takeaway: outside of Pinterest, one 1200×630 image covers everything.
The safe zone: where your text should live
Different platforms crop differently — X leans toward 2:1, some mobile layouts shave the edges. To keep your title readable everywhere:
- Keep all text and logos inside the central 1120 × 560 area (roughly 5% padding on each side).
- Assume the outer edges may be cropped — never place critical content flush against a border.
- Test with a real title at real size: text that looks fine in a design tool is often too small at feed scale. As a rule of thumb, keep titles at 48px or larger on the 1200×630 canvas.
Our free templates bake these margins in, so anything you type stays inside the safe zone.
File size, format and resolution
- Format: PNG for text-heavy graphics (crisp edges), JPG for photographic backgrounds. WebP works on major platforms now, but PNG/JPG remain the safest for long-tail apps.
- File size: Facebook allows up to 8 MB, X up to 5 MB — but crawlers time out on slow images. Staying under 1 MB (and under 300 KB for WhatsApp reliability) is the practical target.
- Resolution: 1200×630 at 1x is enough. Retina-doubling to 2400×1260 rarely improves feed rendering and doubles your file size.
The meta tags that make it work
Dimensions are only half the job — platforms find your image through Open Graph meta tags in your page's <head>:
<meta property="og:image" content="https://example.com/og/launch.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Launch day: v2.0 — changelog" />
<meta name="twitter:card" content="summary_large_image" />Three details matter more than they look:
og:imagemust be an absolute HTTPS URL — relative paths fail silently on most crawlers.og:image:widthandog:image:heightlet platforms reserve the right space before downloading the image, so the first share renders a full card instead of a blank one.twitter:cardset tosummary_large_imageis what upgrades X previews from a small square to the full-width card.
Common mistakes (and quick fixes)
- The image is smaller than 600×315. Facebook demotes it to a tiny side thumbnail. Export at 1200×630.
- Text hugs the edges. X's crop cuts it off. Keep text in the central safe zone.
- The preview shows an old image. Platforms cache aggressively — see our guide on previewing and refreshing OG images for the fix.
- The URL is relative or behind auth. Crawlers can't fetch
/images/og.pngor anything requiring a login. Use a public absolute URL. - One generic image for the whole site. Pages with specific, relevant OG images consistently earn more clicks than a reused logo card.
Create a correctly sized OG image in seconds
You can set up a 1200×630 artboard, safe-zone guides and export presets yourself — or skip the setup entirely. Our free OG image generator starts from templates already sized to 1200×630 (and 1500×500 for X headers), keeps your text inside the safe zone, and exports an optimized PNG that's ready for your meta tags. No signup, no watermark.
FAQ
What is the best OG image size?
1200×630 pixels (1.91:1 aspect ratio). It renders as a large card on Facebook, X, LinkedIn, Slack, Discord, WhatsApp and Telegram without additional variants.
What is the minimum OG image size?
Facebook accepts images down to 200×200, but anything under 600×315 loses the large-card layout. Treat 600×315 as the practical floor — and 1200×630 as the target.
Should I use a different image for X (Twitter)?
Usually no. A 1200×630 image with centered content works for summary_large_image cards. Only add X-specific images if your design puts critical content near the top or bottom edge.
Does the OG image affect SEO?
Not rankings directly — but it strongly affects click-through when your link is shared, and social distribution feeds discovery. A clear, branded preview is one of the cheapest CTR upgrades available.
