Menu
Sign up
Reference · checked 2026-11-02

OG image size: 1200×630, and what each platform documents

Use 1200×630 pixels (1.91:1), saved as JPEG or PNG under 600 KB. That one file meets every minimum size and file-size limit that Facebook, LinkedIn, X, WhatsApp and iMessage publish, and Facebook's and LinkedIn's 1.91:1 ratio. X's large card is 2:1 — 30 pixels shorter.

Slack, Discord and Telegram publish no pixel size at all, and several platforms publish no file formats. Where a platform is silent, the table says so instead of repeating a number from a blog post.

Share image sizes by platform

Every value below comes from the platform's own documentation, checked on 2026-11-02. "Not documented" means the platform publishes nothing for that column.

Platform Recommended Aspect ratio Minimum Max file size Formats Crop and small images
Facebook 1200×630 or larger, for high-resolution displays 1.91:1 600×315 for the large card; 200×200 is the smallest allowed 8 MB Not documented Meta asks for a ratio close to 1.91:1 "to display the full image in Feed without any cropping". Below 600×315 the image is shown much smaller.
X (summary_large_image) Not documented 2:1 300×157 (max 4096×4096) 5 MB JPG, PNG, WebP, GIF (first GIF frame only; no SVG) How X crops other ratios is not documented. 1200×630 is 1.905:1, close to 2:1.
X (summary) Not documented 1:1 144×144 (max 4096×4096) 5 MB JPG, PNG, WebP, GIF (first GIF frame only; no SVG) "The image will be cropped to a square on all platforms."
LinkedIn Not documented 1.91:1 1200×627 5 MB Not documented (the JPG/PNG/GIF list on the same help page is for ads) Images narrower than 401 pixels show as a small thumbnail.
Slack Not documented Not documented Not documented Not documented Not documented Reads Open Graph, Twitter Card and oEmbed tags. No size published.
Discord Not documented Not documented Not documented Not documented PNG, GIF, JPG, WebP, AVIF Small image beside the text unless twitter:card is summary_large_image; up to four og:image tags make a gallery.
WhatsApp Not documented ≤ 4:1 300 px wide 600 KB Not documented The <head> with the tags must be within the first 300 KB of the HTML.
iMessage Not documented Not documented 900 px wide 10 MB (icons, images and video together; the page itself: 1 MB) Not documented Images under 150 px wide may be ignored or shown as an icon. Apple advises against text in preview images.
Telegram Not documented Not documented Not documented Not documented Not documented Telegram publishes no requirements for link-preview images.
Pinterest 1000×1500 for Pins (ad specs) 2:3 Not documented 20 MB (desktop upload, ad specs) PNG, JPEG (ad specs) Pins taller than 2:3 may be cut off in feeds. Rich Pins read up to six og:image tags; no size is given for them.
Mastodon Not documented Not documented Not documented 8 MB (from the source code) JPEG, PNG, GIF, WebP (from the source code) Each server fetches the page itself and stores the image downscaled to at most 230,400 pixels (640×360).

Safe zone: what survives a crop

X documents 2:1 for summary_large_image and a square crop for summary, but not where it cuts. If a platform trims from the centre, a 1200×630 image keeps the middle 1200×600 at 2:1 and the middle 630×630 as a square. Keep the title and logo inside those areas, away from the edges. Apple also advises against text in preview images, because Messages shows them at different sizes on different devices — large type survives that, body-size text does not.

Check your image

Paste the URL of your og:image. Your browser loads it (not our server) and shows its size, ratio, the 2:1 and square areas, and which documented minimums it meets.

A browser cannot read the file size of an image on another domain. To check the size in bytes and the page's tags, use the OG Checker below.

Check the whole page

Paste the page URL: the OG Checker fetches it like a crawler, lists missing or broken tags and previews the card on X, LinkedIn, Facebook, Slack and Discord.

When the old image keeps showing

Every platform caches the preview. Fixing the tag does not change a card that was already fetched:

Generating images at this size

Shareglint renders 1200×630 cards from 153 built-in templates or from your own HTML and CSS. The default scale: 2 gives a 2400×1260 file for high-density screens; scale: 1 gives exactly 1200×630. Ask for "format": "jpeg" when the file must stay small for WhatsApp. The same template renders square, pinterest (1000×1500) and other sizes from one request. The Free plan has 100 images a month.

Browse the templates Sizes in the API docs Get a free API key

Background: what an Open Graph image is and how platforms read it · og:image not showing?

FAQ

What is the best OG image size?

1200×630 pixels, a 1.91:1 ratio, as a JPEG or PNG under 600 KB. It meets Facebook's recommendation, LinkedIn's 1200×627 minimum, X's card limits and WhatsApp's 600 KB limit.

Is 1200×627 or 1200×630 right for LinkedIn?

Both work. LinkedIn's help page gives 1200×627 as the minimum and 1.91:1 as the recommended ratio; 1200×630 is three pixels taller, meets that minimum and is the size Facebook recommends.

What size is the X (Twitter) card image?

For summary_large_image: a 2:1 ratio, at least 300×157 and at most 4096×4096 pixels, under 5 MB, as JPG, PNG, WebP or GIF (first frame only). For summary: 1:1, at least 144×144, cropped to a square. X's card pages have moved off its developer site; these values are from the archived copies.

Can I use WebP for og:image?

X and Discord list WebP, and Mastodon's source code accepts it, but Facebook, LinkedIn and WhatsApp document no formats at all. JPEG or PNG is the safe choice for og:image.

What happens if the og:image is too small?

Facebook shows an image under 600×315 much smaller and does not allow one under 200×200. LinkedIn shows an image narrower than 401 pixels as a small thumbnail. Messages may ignore an image under 150 pixels wide or show it as an icon.

Why does the old image still show after I changed it?

Platforms cache previews. Facebook caches images by URL, so give the new image a new URL and re-scrape in the Sharing Debugger; LinkedIn's Post Inspector refreshes its preview; Slack and Discord keep a preview for about 30 minutes.

Sources

Checked on 2026-11-02. X's card documentation moved off developer.x.com and is not on docs.x.com, so the X links are Internet Archive copies. Mastodon's documentation gives no limits; its row is read from the source code. Telegram publishes no link-preview requirements.