Open Graph Image Size Guide — The Right og:image Dimensions
The recommended og:image size is 1200×630 pixels (1.91:1 aspect ratio). This single dimension works well across Facebook, Twitter/X, LinkedIn, Slack, Discord, and most other platforms that read Open Graph tags.
Get this wrong and your share image will be cropped, blurred, or skipped entirely.
The Correct og:image Dimensions at a Glance
| Platform | Minimum Size | Ideal Size | Max File Size |
|---|---|---|---|
| 200×200 px | 1200×630 px | 8 MB | |
| Twitter/X | 300×157 px | 1200×628 px | 5 MB |
| 200×200 px | 1200×627 px | 5 MB | |
| Slack | 80×80 px | 1200×630 px | — |
| Discord | 80×80 px | 1200×630 px | — |
| 300×200 px | 1200×630 px | — | |
| iMessage | 300×157 px | 1200×630 px | — |
Safe universal recommendation: 1200×630 px, JPEG or PNG, under 1 MB.
Why 1200×630?
The 1.91:1 aspect ratio was standardised by Facebook's Open Graph specification and adopted by nearly every other platform. At 1200×630 px:
- Facebook renders the full image without cropping in link posts
- Twitter/X uses it for
summary_large_imagecards - LinkedIn link posts display it at full width
- Slack and Discord unfurl it without any scaling artefacts
If your image is smaller than 600×315 px, many platforms will fall back to a small thumbnail or no image at all.
How to Set the og:image Tag Correctly
<meta property="og:image" content="https://example.com/preview.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Description of your image" />
Always include og:image:width and og:image:height. Without them, crawlers must download the image to check dimensions — slowing down unfurling and occasionally causing the image to be skipped.
Common og:image Mistakes
Image is too small
Any image below 200×200 px will be ignored by Facebook entirely. Twitter requires at least 300×157 px for summary_large_image. Keep above 1200×630 px for maximum compatibility.
Wrong aspect ratio
A square image (1:1) works on most platforms but will be letterboxed or cropped on Facebook and Twitter. Always use 1.91:1 for link previews.
Image uses a relative URL
The og:image value must be an absolute URL including the protocol:
<!-- ✗ Wrong -->
<meta property="og:image" content="/images/preview.jpg" />
<!-- ✓ Correct -->
<meta property="og:image" content="https://example.com/images/preview.jpg" />
Image is behind a login or returns a redirect
Crawlers cannot access authenticated content. Your og:image URL must be publicly accessible with a direct 200 response.
CORS headers block the image
Some CDNs block cross-origin image loads. The og:image URL needs to allow public reads — no special headers required.
Missing og:image:width / og:image:height
Without explicit dimensions, platform crawlers that time out before the image downloads will skip it.
How to Test Your og:image
The quickest way to verify your image renders correctly is to use TryUnfurl — paste your URL and see exactly how it unfurls on each major platform, including whether the image is picked up, its detected dimensions, and any errors.
You can also use platform-specific debuggers:
- Facebook: Sharing Debugger — also clears the cache
- Twitter/X: Card Validator
- LinkedIn: Post Inspector
See how to test link previews for a step-by-step testing checklist.
Frequently Asked Questions
What is the best og:image size?
1200×630 pixels is the universally recommended size. It satisfies the requirements of Facebook, Twitter/X, LinkedIn, Slack, Discord, and WhatsApp without any cropping or scaling issues.
Does og:image size affect SEO?
Indirectly, yes. Pages without valid og:images get fewer social shares, which reduces traffic and backlinks. Google also reads og:image for rich results in some contexts. The image itself is not a direct ranking factor.
Can og:image be a PNG?
Yes. Both JPEG and PNG are widely supported. JPEG is preferred for photos due to smaller file sizes. PNG works well for logos and graphics with transparency — though note that some platforms will fill transparent backgrounds with white or black.
What happens if og:image is missing?
Platforms will attempt to find an image on the page automatically. This usually results in a random small image being used, or no image at all. Always set og:image explicitly.
Can I use a WebP og:image?
Support varies. Facebook and Twitter support WebP, but some older clients and bots do not. For maximum compatibility, use JPEG or PNG.
How do I update the og:image after changing it?
Platforms cache previews. After updating your image, use the Facebook Sharing Debugger, LinkedIn Post Inspector, or TryUnfurl to force a cache refresh. See how to refresh a link preview for full instructions.