What size should an og:image be?
A 1200 × 630 pixel image (about 1.91:1), saved as JPEG or PNG and ideally under 600 KB, meets the minimums we found documented. There is no single official size: Facebook recommends at least 1200 × 630 and allows 8 MB, LinkedIn asks for 1200 × 627 and 5 MB, and WhatsApp asks for under 600 KB.
The short version
- Use an absolute URL and put the tag in the
<head>:<meta property="og:image" content="https://…">. - The Open Graph protocol itself sets no size, no file-size limit and no format list: those come from each app.
- Facebook says images under 600 × 315 pixels (but over 200 × 200) are shown as a small square, and 200 × 200 is the minimum it allows.
- Specify
og:image:widthandog:image:heightso Facebook can render the image the first time a link is shared. - Slack documents no size at all, and Facebook's tag reference lists only JPEG, GIF and PNG, so JPEG or PNG is the least risky choice (our reading).
What each app documents
| App | Size and shape | File size and format |
|---|---|---|
| Minimum 200 × 200. “At least 1200 x 630 pixels for the best display on high resolution devices”; 600 × 315 is the minimum for the larger image. Keep close to 1.91:1 to avoid cropping. | Must not exceed 8 MB. og:image:type lists image/jpeg, image/gif or image/png. | |
| Minimum 1200 × 627, recommended ratio 1.91:1. Images under 401 pixels wide display as a thumbnail. | Maximum 5 MB. | |
| 300 px or more wide, with a width-to-height ratio of 4:1 or less. The tags must be in the first 300 KB of the HTML. | “Under 600KB”, as an absolute URL. | |
| X (large image card) | Ratio 2:1, minimum 300 × 157, maximum 4096 × 4096. Documented on pages X has since removed (archived copy, 2024). | Under 5 MB. JPG, PNG, WEBP and GIF; SVG not supported. |
| Slack | Reads Open Graph and Twitter Card tags. No size is documented. | No limit documented. Previews are cached for around 30 minutes. |
| Google Discover | At least 1200 px wide, more than 300,000 total pixels, 16:9 recommended, with max-image-preview:large. Google says a large image in og:image can influence the thumbnail. | Not stated for og:image. |
These sources disagree on shape (1.91:1, 2:1, 16:9), which is why 1200 × 630 is a compromise rather than a rule. Apple, Discord, Telegram and Pinterest publish no og:image size that we could find.
See what your page declares
Paste the page address. The checker fetches your og:image, reports its status, type, file size and real pixel size, and rates it.
What we tested
On 2026-10-13 we ran the live Open Graph Checker on eleven test pages, each pointing its og:image at a different image we made. The test pages are a preview that search engines are told not to index, not part of this site.
| The image | What the checker reported for it | Rating |
|---|---|---|
| 1200 × 630 PNG (5 KB) | “og:image loads (1200×630 px)” | Passed |
| 1200 × 630 JPEG, and the same as WebP | “og:image loads (1200×630 px)” | Passed |
| 150 × 150 | “og:image is only 150×150 px” | Fix before publishing |
| 400 × 210 | “loads (400×210 px) but may be cropped or shown small” | Review |
| 1000 × 1000 (square) | The same “may be cropped or shown small” | Review |
| 800 × 1200 (portrait) | The same “may be cropped or shown small” | Review |
| 1700 × 1700 PNG, 8.7 MB | “og:image is larger than 5 MB”; its pixel size was not read | Review |
A relative URL (/og/…png) to a good image | The image passed, and a separate “og:image is a relative URL” item asked for the absolute URL | Passed, plus Review |
| A URL that does not exist | “og:image returns 404” | Fix before publishing |
| A web page used as the image | “og:image is not an image (text/html; charset=utf-8)” | Fix before publishing |
The checker's own thresholds: under 200 pixels on a side is a problem to fix, and an image narrower than 600 pixels or outside roughly 1.7:1 to 2.1:1 is something to review. The 200 and 600 pixel lines follow Facebook's documented numbers; the ratio range is our own.
What it does not do, and what these tests show:
- It passed the WebP image because a browser can decode it. It cannot say whether a given app accepts WebP: Facebook's
og:image:typelist does not include it, while X's archived page lists it. - It does not check
og:image:widthorog:image:height. - It cannot tell you how an app will crop or cache the result. If the preview still looks wrong after the checker passes, the cause is more likely the cache: see Open Graph image not showing.
What this can't tell you
Sizes change. The Facebook FAQ page we read is dated 2018 and X's card pages are gone, so treat the figures as what each operator documented on the day we read them. Before a launch, share the link once privately in the apps that matter to you.
Related: website launch checklist.
Sources
We read these official pages on 2026-10-13.
- Images in Link Shares - Meta for Developers
- Link Sharing FAQ - Meta for Developers (page dated 2018-05-18)
- A Guide to Sharing for Webmasters - Meta for Developers (page dated 2026-06-30)
- Link Previews - WhatsApp, Meta for Developers (page dated 2026-05-21)
- Make your website shareable on LinkedIn - LinkedIn Help
- Summary with large image - Twitter Developer Platform (archived copy of 2024-05-13; X has since removed these pages)
- Slack Robots
- Get on Discover (page dated 2026-03-09)
- Image SEO Best Practices (page dated 2026-03-02)
- The Open Graph protocol
Fixed this one? Before you send people to the page, run the full pre-publish check for everything else: indexing signals, link preview, broken links, alt text, structured data and HTTPS in one pass.