OG Image Size Guide: Every Platform in 2026
You designed a beautiful OG image, deployed it, and shared the link: only to see it cropped, stretched, or blurry on half the platforms your audience uses. The problem is that every social network and messaging app has different display dimensions, aspect ratios, and file-size limits.
This guide gives you the exact specifications for every major platform in 2026 so you can create one image that looks great everywhere.
The Universal Safe Size
If you only remember one number, make it this: 1200 × 630 pixels. This 1.91:1 aspect ratio is the de facto standard adopted by Facebook, X, LinkedIn, and most messaging apps. It is the single best size to target if you want one image that works everywhere. Learn more in our complete OG tags guide.
Platform-by-Platform Breakdown
| Platform | Recommended Size | Aspect Ratio | Min Size | Max File Size | Notes |
|---|---|---|---|---|---|
| 1200 × 630 | 1.91:1 | 200 × 200 | 8 MB | Below 600px wide, renders as small thumbnail. Check your Facebook preview | |
| X (Twitter) | 1200 × 628 | 1.91:1 | 300 × 157 | 5 MB | Requires twitter:card tag for large image. Check your Twitter preview |
| 1200 × 627 | 1.91:1 | 200 × 200 | 5 MB | Shared posts crop to ~1.91:1; articles may differ. Check your LinkedIn preview | |
| Slack | 1200 × 630 | 1.91:1 | No strict min | — | Unfurl respects OG tags; small images render inline |
| Discord | 1200 × 630 | 1.91:1 | No strict min | 8 MB | Embeds show large preview if image is wide enough |
| 1200 × 630 | 1.91:1 | 300 × 200 | — | Preview appears below message bubble | |
| iMessage | 1200 × 630 | 1.91:1 | No strict min | — | Rich link bubble; very small images get tiny thumbnail |
| Telegram | 1200 × 630 | 1.91:1 | No strict min | — | Instant View may override OG image |
| 1000 × 1500 | 2:3 | 600 × 900 | 20 MB | Vertical format; not ideal for standard OG image |
Why 1200 × 630?
The 1.91:1 ratio was popularized by Facebook's original link preview design and has since been adopted by virtually every other platform. At 1200 px wide the image has enough resolution to look sharp on high-DPI mobile screens (which render the card at roughly 600 CSS pixels). Going larger than 1200 px provides no visible benefit and just increases file size and load time.
File Format Recommendations
- PNG: Best for text-heavy images, screenshots, and graphics with sharp edges. Larger file size but no compression artifacts.
- JPEG: Best for photographic images. Use quality 80-85 for a good balance of size and clarity.
- WebP: Smaller file sizes than PNG/JPEG. Widely supported as of 2026. All major platforms (Facebook, X, LinkedIn, Discord) accept WebP.
- SVG: Not supported as an OG image by any platform. Always use a rasterized format.
- GIF: Technically works on some platforms but will display as a static frame on most. Not recommended.
The Safe Zone
Even though the full canvas is 1200 × 630, different platforms crop slightly differently. Keep all critical content (text, logos, CTAs) within a safe zone of roughly 1080 × 565 pixels, centered in the canvas. That gives you about 60 px of breathing room on each side.
This is especially important for LinkedIn, which occasionally clips a few pixels off the edges, and for WhatsApp, which rounds the corners of the preview card.
Common Image Size Mistakes
- Using a square image. A 1200 × 1200 image will be center-cropped to landscape on Facebook and X, cutting off the top and bottom. Always design for 1.91:1.
- Image too small. Anything under 600 px wide will render as a tiny thumbnail on Facebook or not display at all on X.
- Enormous file size. A 4000 × 2100 px PNG might be 10+ MB. Crawlers have timeouts: if the image takes too long to download, the preview will be blank.
- Text too close to edges. Critical text placed at the very edge of the image gets cropped on mobile previews.
- Low contrast text. The image needs to be legible at small sizes on mobile. Use high-contrast text and large font sizes.
Test Your Image
After creating your OG image, run your URL through Rediate's free audit tool to see exactly how it will render across X, LinkedIn, and Slack: along with a score and specific recommendations to improve it.