Social Media Preview Image Size Guide for Every Platform

Every social platform has its own requirements for link preview images. Use an image that is too small and you get a thumbnail instead of a full-width card. Use the wrong aspect ratio and the platform crops off the important parts. Use a format the scraper cannot read and the image does not appear at all.

This guide has the exact dimensions for every major platform and a single image size that works reasonably well on all of them — so you can create one og:image and move on.

The Universal OG Image Size

If you want one image size that works acceptably on every major platform without needing separate images per platform, use:

• Dimensions: 1200 x 630 pixels
• Aspect ratio: 1.91:1
• Format: JPG (for photos) or PNG (for graphics with text)
• File size: under 1MB

This is the Facebook-specified recommended size. LinkedIn uses the same dimensions. Twitter's large card prefers 1200x600 (2:1) but accepts 1200x630 without cropping the center. Discord and WhatsApp scale it down to fit their card formats without awkward cropping.

Design the safe zone

Keep important content (logo, headline, key visual) in the center 900x470 area. Platforms that use slightly different aspect ratios crop from the edges. Anything in the safe zone will appear on every platform.

Facebook OG Image Size Requirements

Facebook has two card formats, and which one your link gets depends on your og:image dimensions.

Large card (full-width image in the feed)

• Recommended: 1200x630 pixels at 1.91:1 ratio
• Minimum: 600x314 pixels for the large card format
• The image spans the full width of the post card above the title and description

Small card (thumbnail beside text)

• If your image is below 600x314 but above 200x200, Facebook shows a square thumbnail on the left with the title and description on the right
• Below 200x200: no image displayed at all

Other Facebook requirements

• Maximum file size: 8MB
• Formats: JPG, PNG, GIF (animated GIFs may show as static in previews)
• URL: must be absolute HTTPS
• Declare dimensions in og:image:width and og:image:height to help Facebook show the right format immediately without fetching the image first

Sell Custom Apparel — We Handle Printing & Free Shipping

LinkedIn OG Image Size Requirements

LinkedIn uses the same Open Graph tags as Facebook with very similar size requirements.

Standard link post card

• Recommended: 1200x627 pixels (matches Facebook's 1.91:1 ratio)
• Minimum for large card display: LinkedIn recommends at least 1200px wide; smaller images may render as a smaller card or not at all

LinkedIn article and newsletter

• Header image for articles: 1200x644 pixels
• Newsletter cover image: 1080x1080 pixels (square format)

Important note about LinkedIn

LinkedIn can be stricter than Facebook about image size thresholds. An image that Facebook shows in the small card format may not appear at all on LinkedIn. If LinkedIn is not showing your image, check that your og:image is at least 1200px wide. Also declare og:image:width and og:image:height so LinkedIn does not need to fetch the image to determine its format.

Twitter / X OG Image Size Requirements

Twitter has two card formats controlled by the twitter:card meta tag.

summary_large_image (full-width image card)

• Recommended: 1200x600 pixels at 2:1 ratio
• Minimum: 300x157 pixels
• Maximum file size: 5MB for PNG or GIF, 15MB for JPEG
• Formats: JPG, PNG, GIF (WebP also works)
• Twitter crops to a 2:1 ratio centered on the image

summary (small square thumbnail card)

• Recommended: 144x144 pixels minimum
• Shows a square thumbnail on the left with the title and description on the right
• Default if twitter:card tag is absent or set to "summary"

Setting the card type

Add this tag to get the large image card format:

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

Twitter falls back to og:image if no twitter:image is specified. Your 1200x630 og:image will work for Twitter's large card — Twitter crops the center to the 2:1 ratio, which is why keeping content in the center safe zone matters.

Discord, WhatsApp, Slack, and iMessage

These platforms read standard og: tags but display them in different formats.

Discord

• Shows a compact embed with a thumbnail version of og:image
• Image: no strict minimum, but images below 400px wide may not display
• Discord sometimes displays images in a square crop or a wider horizontal format depending on the channel context
• 1200x630 renders cleanly in Discord's embed format

WhatsApp

• Minimum: 300x200 pixels for the thumbnail to appear
• WhatsApp always shows a small thumbnail beside the link text; there is no full-width card format
• The thumbnail is cropped to a rectangular format from the center of your image

Slack

• Slack shows the og:image as a thumbnail in the unfurl card
• Minimum: 100x100 pixels
• Recommended: any size above 400px wide
• Slack may additionally show metadata it fetches directly from known platforms (GitHub stars, YouTube view counts)

iMessage (iOS)

• Uses og:image, falls back to apple-touch-icon
• Shows a compact link preview card with a thumbnail
• 1200x630 scales down cleanly to iMessage's card format

Frequently Asked Questions

Should I use JPG or PNG for my og:image?

JPG is better for photographs and images with many colors — smaller file size at equivalent quality. PNG is better for graphics with text, logos, or sharp edges where JPG compression artifacts would be visible. Both formats are supported by all major platforms. Avoid WebP as og:image since not all platform scrapers support it.

Can I use the same og:image for every page on my site or does each page need a unique image?

Using the same og:image on every page is technically valid but not ideal. When all your links show the same thumbnail in someone's feed, individual posts are harder to distinguish. For high-value pages (home page, major landing pages, blog posts), create page-specific images. For lower-traffic pages a site-wide fallback is acceptable.

What is og:image:width and og:image:height and should I add them?

These tags declare the image dimensions to the platform scraper so it does not have to fetch and decode the image to determine its size. Facebook uses them to decide which card format to show before fetching the image. They are not required but they improve rendering speed and consistency. Add them whenever you know the image dimensions.