What Size Should an Open Graph Image Be?
1200 by 630 is a good default, but platforms crop differently. Here is how to choose a size and format that holds up.
There is no single Open Graph image size that every platform requires. What exists is a set of common conventions that work well almost everywhere, and a set of platform-specific details that change from time to time. This guide gives you the conventions and explains how to design an image that survives different crops.
The default to start from: 1200 by 630
An image 1200 pixels wide and 630 pixels tall has an aspect ratio of about 1.91:1. Facebook's sharing documentation has long recommended images at least this large, LinkedIn link cards commonly use a similar ratio, and X's large image card is close to 2:1. A single 1200 by 630 image therefore works as a large card on most platforms with only light cropping.
| Use | Common target | Notes |
|---|---|---|
| Large-image cards | 1200 × 630 (about 1.91:1) | The usual default for og:image. |
| Small or summary cards | Square, at least a few hundred pixels | Often shown as a small thumbnail beside the text. |
| Minimum to avoid being ignored | Roughly 200 × 200 or more | Platforms differ; larger is safer. |
| File size | Well under 5 MB | Platforms publish different limits, commonly in the 5 to 8 MB range for some. |
Treat these as recommendations. Each platform documents its own limits and may change them, so verify against current documentation if the details matter to you.
Design for different crops
- Keep text and logos inside a safe area, roughly the central 80 percent, because wide cards and square thumbnails crop the edges differently.
- Use large type and simple composition. Cards are often displayed small, in a feed or a chat bubble.
- Avoid putting key information in the corners, where rounded card shapes and overlays can hide it.
- Do not rely on a thin border or tiny text to carry meaning.
Format and file size
PNG suits graphics and text, JPEG suits photographs. Both are supported everywhere. Animated GIFs generally show a still frame. Some platforms handle WebP, but AVIF, HEIC, SVG, BMP and ICO files are not reliably supported for previews, so keep a PNG or JPEG for og:image even if you serve modern formats elsewhere. Keep the file small enough to download quickly: crawlers have time limits, and very large files may be skipped.
Declare the dimensions
<meta property="og:image" content="https://example.com/images/card.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">These tags help some platforms lay out the card before downloading the image. They must match the file, or they can mislead the layout. The Open Graph & Social Preview Analyzer reads the real dimensions from the file and flags a mismatch with what you declared, and rates the image as recommended, acceptable or potentially problematic rather than passing or failing it.
Twitter/X cards
X uses the card type to choose a layout: summary_large_image shows a wide image, while summary shows a small square. It documents falling back to Open Graph images when twitter:image is not set. See Twitter/X Card tags explained.
One good image beats five variants
Unless you have a reason to tailor images per platform, a single well-composed 1200 by 630 PNG is easier to maintain and gives more consistent results.
Frequently asked questions
- What is the best Open Graph image size?
- A 1200 by 630 pixel image (about 1.91:1) in PNG or JPEG is a widely used default for large-image cards. It is a recommendation, not a requirement, and platforms may crop it differently.
- What is the minimum Open Graph image size?
- It varies by platform and changes over time. Very small images, roughly below 200 pixels on a side, are often ignored, and images under about 600 pixels wide may appear as small thumbnails. Check each platform's current documentation.
- Can I use a square image?
- Yes. Square images suit small summary-style cards, but they are cropped on wide large-image cards, so keep the important content centered.
- What file format should I use?
- PNG or JPEG. WebP is widely supported, while AVIF, SVG, HEIC and BMP are not reliably supported for link previews across platforms.
Try it yourself
The tool that pairs with this guide.
Did this help you untangle your redirects?
If these free developer tools save you time, consider buying me a byte. Your support helps keep DevCraftKit free and growing.
Related articles
What Are Redirect Chains? Causes, Impact and How to Fix Them
Several hops where one would do: how redirect chains form, what they cost, and how to find and fix them.
Published
301 vs 302 vs 307 vs 308 Redirects: Which Status Code to Use
Two questions decide the code: is the move permanent, and must the request method be preserved?
Published
What Is Open Graph and How Does It Work?
The meta tags behind every link card: what Open Graph is, how platforms use it, and how a preview is built from your page.
Published