⚡ TL;DR (Updated July 2026)
The one image to make: 1200x630 pixels, JPG or PNG, ideally under 1MB
Facebook: 1200x630 (1.91:1)
X (Twitter): 1200x675 large card (16:9), 800x418 small card
LinkedIn: 1200x627 (1.91:1)
Discord, Slack, WhatsApp, iMessage: 1200x630 works everywhere
Keep your headline and faces inside the center 1080x600 safe zone
Test before you share with the Meta Sharing Debugger and LinkedIn Post Inspector
The optimal Open Graph image size in 2026 is 1200x630 pixels. That single dimension works across Facebook, X (Twitter's large card), LinkedIn, Slack, Discord, WhatsApp, iMessage, and almost every other platform that builds a link preview. If you only make one OG image per page, make it 1200x630 with a 1.91:1 aspect ratio, save it as JPG or PNG (ideally under 1MB, 8MB max), and keep your headline and any faces inside the center 1080x600 safe zone.
This guide covers the exact open graph image size for every major platform, a quick-reference table you can bookmark, the 2026 spec changes you might have missed, the most common reasons OG images don't show up when you share a link, and the free tools you can use to check any URL before you post.
Open Graph Image Size Quick Reference (2026)
Here are the recommended Open Graph dimensions for every major platform. When in doubt, 1200x630 is the safe default that renders cleanly almost everywhere.
| Platform | Recommended size | Aspect ratio | Notes |
|---|---|---|---|
| Universal (one image to rule them all) | 1200 x 630 | 1.91:1 | Safe default for Facebook, Slack, Discord, WhatsApp, iMessage |
| 1200 x 630 | 1.91:1 | Minimum 600 x 315; file under 8MB | |
| X (Twitter) - large card | 1200 x 675 | 16:9 | summary_large_image; 1200 x 630 also renders fine |
| X (Twitter) - small card | 800 x 418 | 1.91:1 | summary card; thumbnail beside the text |
| 1200 x 627 | 1.91:1 | Near-identical to Facebook | |
| Discord | 1200 x 630 | 1.91:1 | Reads standard og:image tags |
| Slack | 1200 x 630 | 1.91:1 | Reads standard og:image tags |
| 1200 x 630 | 1.91:1 | Compresses hard; keep source file under 300KB | |
| 1000 x 1500 | 2:3 | Reads og:image but portrait performs far better | |
| Instagram (DM link previews) | 1200 x 630 | 1.91:1 | Feed posts ignore OG; only DM previews use it |
What Is an Open Graph Image?
An Open Graph image is the picture that appears in the preview card when someone shares a link to your page on social media. It is pulled from your site through Open Graph meta tags, small pieces of code in your page's <head> that tell platforms exactly what to display.
The image is set with a single tag:
<meta property="og:image" content="https://yoursite.com/og-image.jpg" />
The Open Graph protocol was introduced by Facebook in 2010, and today nearly every platform reads the same tags. If you want the full breakdown of which tags to write and how, see our companion guide on how to write OG meta tags. This guide focuses on the image itself: the dimensions, the specs, and getting it to show up correctly.
Why the Open Graph Image Matters
The og:image is the first thing the eye lands on in a shared link, often before the headline. A strong one can lift social click-through dramatically, while a missing or broken one quietly kills it. Getting it right means you:
- Earn more clicks: previews with a clear, well-sized image consistently out-click text-only links.
- Control the narrative: without an og:image, platforms grab whatever picture they find on the page, which is often your logo or a random thumbnail.
- Look professional and on-brand: a consistent, well-designed preview makes your content instantly recognizable in a crowded feed.
Best Open Graph Image Sizes for Each Platform
The recommended open graph image size that works across nearly every platform is 1200 x 630 pixels. That said, a few platforms have their own quirks worth knowing.
Facebook OG Image Size
For Facebook, the recommended OG image size is 1200 x 630 pixels at a 1.91:1 aspect ratio. This fills the news-feed preview without cropping. The minimum Facebook will display is 600 x 315, and anything below 200 x 200 gets rejected. Keep the file under 8MB, though under 1MB loads faster and survives compression better. This same Facebook open graph image size carries over cleanly to Messenger and Instagram DM previews.
LinkedIn uses 1200 x 627 pixels (1.91:1), which is functionally identical to Facebook's spec. One image at 1200x630 covers both with no visible difference. LinkedIn caches previews aggressively, so if you update an image after a link has already been shared, you will need to force a refresh with the Post Inspector (covered below).
X (Twitter)
X uses two card types for displaying link previews:
- Summary Card with Large Image: the full-width preview, recommended at 1200 x 675 pixels (16:9). This is the format set by
twitter:cardvaluesummary_large_image. A 1200x630 image also renders correctly here. - Summary Card with Small Image: a compact thumbnail beside the text, recommended at 800 x 418 pixels (1.91:1).
Center your key elements (text, logo, faces) so nothing important is lost if the card is resized on different devices.
Discord, Slack, WhatsApp, and iMessage
These messaging platforms all read standard og:image tags and render at roughly 1.91:1, so 1200 x 630 is ideal across the board. WhatsApp is the one to watch: it compresses preview images aggressively, so keep your source file under 300KB to preserve detail. iMessage and Discord both display a clean large preview with no special tags required.
Pinterest and Other Platforms
Pinterest will read your og:image, but it is built for portrait images at a 2:3 ratio (1000 x 1500 is the sweet spot). A landscape 1200x630 image will display but underperform in the feed. If Pinterest is a primary channel for you, create a separate portrait image. For everywhere else, sticking with 1200x630 is the reliable default.
For sizes beyond link previews (feed posts, stories, reels, banners, profile photos), see our full social media image sizes guide.
What Changed for 2026
Open Graph specs are stable by design, but a few things are worth updating in your head for 2026:
- 1200x630 is now the firm cross-platform standard. Older guides recommending 1200x627 or 600x315 are not wrong, but 1200x630 is the cleanest single size that satisfies every platform at once.
- X retired its standalone card validator. Card validation now lives inside the X developer portal, so most teams rely on third-party preview tools or the Meta and LinkedIn debuggers to confirm rendering.
- File-weight matters more than ever. With WhatsApp and mobile sharing dominating, a source file under 1MB (and under 300KB for WhatsApp) renders faster and cleaner than a heavy 5MB+ PNG.
- Dynamic og:images are mainstream. Many sites now auto-generate a unique 1200x630 image per page at build time, so every post gets a custom preview instead of one shared default.
Best Practices for Open Graph Images
1. Use the Right File Format and Weight
Save OG images as JPEG (best for photos, smaller files) or PNG (sharper for text and logos). Keep the file under 8MB to satisfy Facebook's hard limit, but aim for under 1MB so it loads instantly and survives platform compression.
2. Respect the Safe Zone
Different platforms crop slightly differently. Keep your headline, logo, and any faces within the center 1080 x 600 area so nothing critical gets clipped when a platform trims the edges.
3. Keep Text Minimal and Readable at Thumbnail Size
Your image is often viewed at a fraction of its real size on a phone. Use bold, high-contrast type at 36pt or larger (at source resolution), and resist cramming in more than one message.
4. Stay On-Brand and Use Unique Images Per Page
Consistent colors, fonts, and layout make your previews instantly recognizable. Where you can, give each important page its own tailored og:image rather than reusing one site-wide default.
How to Create Open Graph Images
You do not need design skills to produce a clean 1200x630 image. The fastest route is an AI design tool like Krumzi, where you describe what you want and get a perfectly sized, on-brand og:image back in seconds, fully editable. For a 50-post blog, that turns hours of templating into minutes.
If you would rather work from scratch, any design tool that lets you set a custom 1200x630 canvas will do, just keep the safe zone and file-weight guidance above in mind. For a deeper walkthrough, see our guide on how to create social media graphics with AI.
Why Your OG Image Isn't Showing (and How to Fix It)
If you share a link and the image is missing, broken, or wrong, it is almost always one of these:
- The platform cached an old version. This is the most common cause. Platforms scrape your page once and remember it. After you update the image, force a re-scrape with the Sharing Debugger or Post Inspector.
- The og:image URL is relative, not absolute. It must be a full, absolute
https://URL, not/images/og.jpg. - The image is too small or too large. Below 200x200 gets rejected; above the platform file limit fails to load. Stay at 1200x630 and under 8MB.
- The image sits behind a login or is blocked to crawlers. It must be publicly accessible to the platform's scraper, with no authentication and not disallowed in robots.txt.
- The tag is injected by client-side JavaScript. Most social scrapers do not run JS, so the og:image tag has to be in the server-rendered HTML.
- Missing og:image:width and og:image:height. Without them, the very first share sometimes renders blank while the platform fetches the image. Add both tags to avoid it.
Tools to Test Your Open Graph Image
Never ship a high-stakes link without previewing it first. Bookmark these:
- Meta Sharing Debugger: paste any URL to see the Facebook and Messenger preview, and force a re-scrape after you update tags.
- LinkedIn Post Inspector: shows the LinkedIn preview and clears LinkedIn's cache for that URL.
- X (Twitter) Card Validator: confirms how your card renders on X.
Run your URL through all three before announcing a launch. A 30-second check prevents a broken preview from going out to thousands of people.
Frequently Asked Questions
What is the best Open Graph image size?
The best Open Graph image size is 1200 x 630 pixels at a 1.91:1 aspect ratio. This single size renders cleanly on Facebook, X, LinkedIn, Discord, Slack, WhatsApp, and iMessage, so if you make only one og:image, make it 1200x630.
What is the og:image size for Facebook?
The recommended og:image size for Facebook is 1200 x 630 pixels (1.91:1). The minimum that displays is 600 x 315, anything under 200 x 200 is rejected, and the file should stay under 8MB.
What are the correct Open Graph dimensions for Twitter (X)?
X recommends 1200 x 675 pixels (16:9) for the large summary card and 800 x 418 pixels for the small card. A standard 1200x630 image also renders correctly on the large card.
Why is my Open Graph image not showing up?
Usually the platform cached an older version of your page. Run the URL through the Meta Sharing Debugger or LinkedIn Post Inspector to force a re-scrape. Also confirm the og:image uses an absolute https URL, is publicly accessible, and is at least 200 x 200 pixels.
Do I need different OG images for each platform?
No. A single 1200x630 image works everywhere except Pinterest, which favors a 2:3 portrait image. Make the one 1200x630 version first, then add a portrait variant only if Pinterest is a priority channel.
Final Thoughts
Getting your Open Graph image size right is one of the simplest, highest-leverage wins in social marketing. Make one 1200x630 image, keep it on-brand and under 1MB, place your key content inside the center safe zone, and test it with the debuggers before you share. Do that and every link you post shows up looking sharp, professional, and ready to earn the click.
Want the design half handled in seconds? Krumzi generates a custom 1200x630 og:image from a short prompt, on-brand and fully editable.
Related reading:
Facebook
X
LinkedIn
