Open Graph Image Size Guide
The exact Open Graph image dimensions and file size requirements for Facebook, LinkedIn, Twitter, Discord, WhatsApp, Slack, and Telegram.
The preview image is the most visible element of any Open Graph card. Using the wrong dimensions causes awkward cropping, pixelation, or blank placeholders — killing click-through rates.
This guide provides the exact image specifications required by every major platform in 2026.
Universal Recommended Size
For maximum compatibility across all platforms, create your Open Graph images at:
- Width: 1200 pixels
- Height: 630 pixels
- Aspect ratio: 1.91:1
- File format: PNG or JPEG (WebP support is inconsistent)
- File size: Under 5 MB (under 1 MB recommended)
This single image size renders correctly on Facebook, LinkedIn, Twitter/X, Discord, WhatsApp, Slack, and Telegram without cropping.
Platform-Specific Requirements
| Platform | Minimum Size | Recommended Size | Aspect Ratio | Max File Size |
|---|---|---|---|---|
| 200×200 px | 1200×630 px | 1.91:1 | 8 MB | |
| 200×200 px | 1200×627 px | 1.91:1 | 5 MB | |
| Twitter/X (large card) | 300×157 px | 1200×628 px | 1.91:1 | 5 MB |
| Twitter/X (summary) | 144×144 px | 800×800 px | 1:1 | 5 MB |
| Discord | 200×200 px | 1200×630 px | 1.91:1 | 8 MB |
| 300×200 px | 1200×630 px | 1.91:1 | 5 MB | |
| Slack | 200×200 px | 1200×630 px | 1.91:1 | 5 MB |
| Telegram | 200×200 px | 1200×630 px | 1.91:1 | 5 MB |
For a deeper breakdown of all social image dimensions including profile photos and story formats, see our Social Media Image Dimensions Guide.
How to Specify Image Dimensions in HTML
Always declare explicit dimensions using structured OG properties:
<meta property="og:image" content="https://example.com/og-banner.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:type" content="image/png" />
<meta property="og:image:alt" content="Open Graph Image Size Guide banner" />Specifying width and height allows platforms to render the card layout immediately without downloading the full image first. This improves perceived load speed in feeds and chat windows.
Common Image Mistakes
1. Using Relative URLs
Social crawlers fetch your page from their own servers. /images/og.png resolves to nothing on their domain. Always use fully-qualified HTTPS URLs.
2. Oversized Files
If your image exceeds the platform’s file size limit, the crawler times out and displays no image. Compress your PNGs with tools like TinyPNG or Squoosh.
3. Important Content at the Edges
Different platforms crop images differently. Place your key text, logo, and visual focus in the center 80% of the image to avoid clipping on any platform.
4. Text-Heavy Images
Some platforms (particularly Facebook) historically penalized images with more than 20% text coverage in advertising contexts. Keep text minimal and high-contrast.
Generating Custom OG Images
For sites with many pages, manually designing images in Figma is impractical. Consider:
- Dynamic OG Image APIs — Render HTML/CSS to PNG at request time. See our Dynamic Open Graph Images: Complete Guide.
- Template-Based Generators — Use our OG Image Builder to create branded social cards with text overlays.
- Framework-Specific Solutions — Next.js
@vercel/og, Astro@astro-community/og, and similar libraries. See Dynamic OG Image Automation.
Twitter Card Image Sizes
Twitter/X has its own image requirements that differ slightly from Open Graph. For the full specification, see Twitter Card Image Size.
Test how your images render across all platforms simultaneously with the Social Preview Simulator.