Open Graph Image Size: The Right Dimensions for Every Platform (2026) — share-preview.com

Why Open Graph Image Size Matters

You've written a great piece of content. You share it on social media. And then you watch in frustration as Twitter crops your image to a bizarre aspect ratio, Facebook shows a tiny blurry thumbnail, and LinkedIn strips the image entirely. The culprit is almost always Open Graph image dimensions.

The og:image tag tells social networks which image to use as the visual preview when someone shares your URL. But each platform has its own rules about image dimensions, aspect ratios, and minimum sizes. A single image that works perfectly on Facebook can look terrible on Twitter.

The stakes are real: studies consistently show that social posts with images receive 2–3× more engagement than text-only posts. A broken or cropped image doesn't just look unprofessional — it actively reduces clicks and shares.

Recommended Dimensions by Platform

Quick Reference Table

What Happens with Wrong Image Sizes

Using the wrong dimensions doesn't just look bad — it can cause the image to not display at all. Here are the most common failure modes:

Too Small → No Image Shown

LinkedIn has a hard minimum of 1200×627px. If your image is smaller, LinkedIn simply will not show it — your link will render as text-only. Facebook won't show images under 200×200px. Twitter won't render a large card for images under 300×157px.

Wrong Aspect Ratio → Cropping

If your image is the right pixel count but the wrong shape, platforms crop it to fit their expected ratio. A square image on Twitter's large card will have the sides brutally cut off. A portrait image on Facebook will be center-cropped to landscape. Text or logos near the edges will disappear.

Oversized File → Slow Load / Not Cached

Large image files load slowly in social card previews. WhatsApp in particular struggles with images over 300KB and may show a placeholder or skip the image entirely on slow mobile connections. Aim for under 200KB for WhatsApp-shared URLs.

HTTP Instead of HTTPS → Blocked

All major platforms block HTTP images in social previews. If your og:image URL starts with http://, no platform will display it. Always use HTTPS.

The One Size That Works Everywhere

If you can only create one OG image size, make it 1200 × 630 pixels. Here's why this is the universal sweet spot:

• ✅ Meets Facebook's recommended dimensions exactly
• ✅ Exceeds LinkedIn's 1200×627 minimum (with 3px to spare)
• ✅ Works on Twitter large cards (2:1 ratio is close enough, Twitter will scale)
• ✅ Renders well on WhatsApp, Slack, and Discord
• ✅ The 1.9:1 aspect ratio is close enough to Twitter's 2:1 that minimal cropping occurs

The Proper OG Image Tag

<!-- Always set all three: URL, width, and height -->
<meta property="og:image" content="https://yoursite.com/og-image.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Descriptive text for the image">
<meta property="og:image:type" content="image/jpeg">

Setting og:image:width and og:image:height is technically optional, but it helps Facebook and LinkedIn lay out the page correctly before the image loads, reducing the chance of rendering issues.

Design Tips for the Universal 1200×630 Image

• Keep the safe zone: Important content should stay within a 1100×544 rectangle centered in the image
• Contrast matters: Your image will appear as a small thumbnail on mobile — use high-contrast designs that are readable at 300px wide
• Brand prominently: Put your logo in the safe zone — it's free brand exposure every time someone shares your link
• Minimal text: 6–8 words maximum in the image itself. Let the og:title and og:description carry the message
• Optimize file size: Use JPG at 80–85% quality or PNG with compression. Target under 200KB for best performance across all platforms

Pre-Publish OG Image Checklist

How to Test Your OG Image

The only way to know for certain how your OG image will appear is to test it. Each platform renders previews slightly differently — what looks perfect on Facebook may be cropped on Twitter, and LinkedIn may show nothing at all if your image doesn't meet its strict minimums.

Platform-Specific Validators

• Facebook: developers.facebook.com/tools/debug — Facebook's official debugger. Paste your URL to see the preview and force a cache refresh.
• Twitter / X: cards-dev.twitter.com/validator — Shows how your Twitter Card renders and logs any errors.
• LinkedIn: linkedin.com/post-inspector — LinkedIn's official post inspector. Note that LinkedIn caches aggressively; changes may take hours to appear.

The Problem with Testing Each Platform Separately

Using three separate validators is slow and error-prone. You might fix Facebook and break Twitter without realizing it. The better approach is to use a tool that shows all platform previews simultaneously.