Keynou Logo

Blog

Tips, tutorials, and insights about online tools

OG Image Size Guide: Exact Dimensions for Every Platform in 2026
2026-06-23Keynou Team

OG Image Size Guide: Exact Dimensions for Every Platform in 2026

One of the most common OG image mistakes is using the wrong dimensions. A 1:1 square image gets pillar-boxed on LinkedIn. An image that's too small gets rejected by Twitter. Text near the edges gets cropped.

This is the definitive reference for OG image sizes across every major platform in 2026.

The Universal Standard: 1200 × 630 pixels

For most websites, 1200 × 630 pixels is the single size you need. It's the recommended dimension for Twitter, Facebook, and LinkedIn — and it scales correctly on WhatsApp, Slack, and Discord.

Aspect ratio: 1.91:1 (roughly 2:1)

Platform-by-Platform Breakdown

Twitter / X

Card type Recommended size Minimum size Aspect ratio
summary_large_image 1200 × 630 300 × 157 2:1
summary (small) 144 × 144 144 × 144 1:1

Use summary_large_image for blog posts and articles — it fills the full width of the tweet card. Add this meta tag:

<meta name="twitter:card" content="summary_large_image" />

Twitter has a 5MB file size limit for OG images and a 3:1 maximum and 1:3 minimum aspect ratio outside of which it falls back to the small card.

LinkedIn

Format Recommended size
Article / blog share 1200 × 627 px
Company page post 1200 × 627 px

LinkedIn's minimum is 200 × 200 for a thumbnail, but anything shared as a link preview needs to be at least 1200 × 627 to display as the large card. Anything smaller renders as a small inline thumbnail on the left.

Facebook

Format Recommended size
Shared link 1200 × 630 px
Minimum (still shows large) 600 × 315 px

Facebook caches OG images aggressively. After changing an image, use the Facebook Sharing Debugger and click "Scrape Again" to force a refresh.

WhatsApp

WhatsApp uses a 1:1 crop of your OG image for the thumbnail in chat previews. This means:

  • Keep your main content centred in the image
  • Don't put critical text or logos in the corners
  • The full 1200×630 image shows when you tap the preview

Slack

Slack renders OG images as a 1200 × 630 card with rounded corners. It respects the og:image tag but limits the preview width to approximately 360px in the sidebar — so text needs to be large enough to read at that size.

Discord

Discord shows link embeds with the og:image as a large card. The image renders at up to 400px wide in the embed. Discord also supports animated GIFs as OG images (unusual, but a fun trick for game sites).

Safe Zone Guidelines

Even at the correct dimensions, text and logos near the edges can get clipped. Follow these safe zone rules:

  • Keep all critical content within the inner 1100 × 530 area (50px inset on all sides)
  • Title text: minimum 36px, ideally 48–64px for readability at thumbnail size
  • Keep logos in the bottom-left or top-left — most platforms preserve the left edge

File Format Recommendations

Format Best for
PNG Designs with text, flat illustrations, logos
JPEG Photography-based images
WebP Modern sites — smaller file, same quality
GIF Animated previews (Discord only, avoid elsewhere)

File size limit across all major platforms: 8MB. In practice, keep it under 300KB for fast loading. A 1200×630 PNG with text and flat colours typically compresses to 30–80KB.

How to Check Your OG Image

Use these free tools to preview and debug your OG image without sharing to a live audience:

  1. OpenGraph.xyz — shows previews for Twitter, LinkedIn, Facebook, Slack
  2. Twitter Card Validator — official Twitter preview tool
  3. Facebook Sharing Debugger — force re-scrape and preview
  4. LinkedIn Post Inspector — official LinkedIn preview

Generate a Correctly-Sized OG Image in Seconds

Keynou's OG Image Generator creates images at exactly 1200 × 630 pixels by default — no guesswork needed. Enter your title and description, choose a category for the accent colour, and download or copy the URL.

Your branding (domain, logo, tagline, colours) saves automatically to your browser so every image you generate is consistent without any re-configuration.

Common Mistakes to Avoid

  • Using a square image (1:1) — renders poorly as a wide card, gets letterboxed
  • Text too small — images render at ~300–400px wide in feeds; 24px body text becomes unreadable
  • Missing alt text — always set og:image:alt for accessibility
  • Relative URLog:image must be an absolute URL (https://...)
  • Forgetting Twitter tags — Facebook reads og:image but Twitter needs twitter:image too (or twitter:card at minimum)

Related Reading

FlowDrive