Cheat sheet

OG image size for every major share card

One landscape file — 1200×630 — covers almost every link preview. Compare recommended size, aspect ratio, minimums and file limits, then test the live URL. Last checked: October 2026.

  • 1200 × 630Default canvas
  • 1.91:1Aspect
  • < 1 MBTarget weight
  • 200-400 KBWhatsApp aim

Platform table

Recommended sizes by network

Scroll horizontally on phones. Sticky first column keeps the platform name in view.

Recommended Open Graph image sizes by platform
PlatformRecommended sizeAspect ratioMin sizeMax file size
Facebook1200 × 630 px1.91:1200×200 absolute; 600×315 large card8 MB
Twitter / Xsummary_large_image1200 × 628 px≈2:1300×1575 MB
LinkedIn1200 × 627 px1.91:1200×2005 MB
WhatsApp1200 × 630 px1.91:1Uses Open GraphPractical max ~600 KB; aim 200-400 KB
Discord1200 × 630 px1.91:1Uses Open GraphUnder 1 MB recommended
Slack1200 × 630 px1.91:1Uses Open GraphUnder 1 MB recommended (5 MB hard)
Telegram1200 × 630 px1.91:1200×200~5 MB

Facebook, X and LinkedIn figures follow official docs. WhatsApp, Discord, Slack and Telegram sizes are recommended — based on how these apps render Open Graph images; no official spec is published. Export one 1200×630 PNG or JPG under 1 MB (WhatsApp: practical max about 600 KB; aim for 200-400 KB.). Host it at a stable absolute HTTPS URL and set og:image:width /og:image:height.

Related guides:Facebook Sharing Debugger·LinkedIn Post Inspector·Link Preview Checker.

Live check

Paste a public URL into the Link Preview Checker to see the title, description and image crawlers are likely to use.

Common mistakes

What breaks previews on each platform

Short notes — cropping, cache, and file limits — so you fix the right thing first.

FacebookCrop + cache

Facebook

Meta crops edges and may letterbox odd ratios. Keep the headline inside a ~10% inset. After you replace an image at the same URL, scrape again or the cache keeps the old file.

Twitter / XEdge crop

Twitter / X

Use twitter:card=summary_large_image with a landscape file. A 1200×630 image is cropped slightly toward 2:1 — don’t put critical text on the top or bottom edge.

LinkedInDocumented size

LinkedIn

LinkedIn’s recommended link image is 1200×627 (minimum 200×200). Narrower images often collapse to a tiny thumbnail. Prefer one absolute HTTPS og:image and re-run Post Inspector after deploy.

WhatsAppFile weight

WhatsApp

WhatsApp: practical max about 600 KB; aim for 200-400 KB. Use a stable absolute URL. Previews cache hard — change the image path when artwork changes.

DiscordSmall embed

Discord

Without a clear landscape image (and often twitter:card=summary_large_image), embeds fall back to a small square. PNG or JPG is the safe default for og:image.

SlackSlow omit

Slack

No separate pixel spec. Oversized files or slow hosts simply omit the image. Keep the file small and the image URL publicly fetchable.

TelegramAbsolute URL

Telegram

Relative paths and hotlink blocks are common failures. Serve PNG or JPG over HTTPS with a full absolute og:image URL.

Related pages

Frequently asked questions

Quick answers about the best og:image size, missing previews, minimums and whether you need one file per network.

What is the best og:image size?

Use 1200×630 pixels (about 1.91:1) as the default. That single canvas works for Facebook, LinkedIn, WhatsApp, Discord, Slack and Telegram, and is acceptable on X with a light crop for summary_large_image.

Why is my og:image not showing?

Usually the tag is missing from the raw HTML, the URL is relative, the file returns an error to anonymous GET, or a platform still caches an older image. Confirm View Source, use an absolute https URL, then rescrape.

What is the minimum og:image size?

Facebook: 200×200 absolute minimum; 600×315 for a large card. LinkedIn’s minimum is 200×200 (recommended 1200×627). X summary_large_image needs at least 300×157. Designing at 1200×630 clears every published minimum.

What file size should my OG image be?

Vendor caps (5–8 MB) are not targets. Aim under 1 MB. For WhatsApp, practical max about 600 KB; aim for 200-400 KB. Prefer JPG for photos and PNG for flat title cards.

Do I need a different image for every platform?

No. Ship one 1200×630 file for og:image and usually twitter:image. Add a second file only when the crop is truly different (for example a 2:3 Pinterest pin).

Should og:image be an absolute URL?

Yes. Paths like /og.jpg fail in most crawlers. Use a full https URL, return 200 with image/png or image/jpeg, and avoid expiring signed URLs or hotlink protection that blocks bots.