If you just want one number to memorize, it is 1200x630. Bookmark this page for everything else. Below is a scannable cheat sheet of the current Open Graph and social image dimensions for every major platform, the aspect ratios behind them, and the practical rules that keep your previews looking sharp instead of cropped, blurry, or blank.

The cheat sheet

| Platform | Recommended size | Aspect ratio | | --- | --- | --- | | Open Graph (default) | 1200x630 | 1.91:1 | | Facebook | 1200x630 | 1.91:1 | | X / Twitter (summary_large_image) | up to 1600x900 (1200x675 also valid) | 16:9 | | LinkedIn | 1200x627 | ~1.91:1 | | Square (Instagram-style, some feeds) | 1080x1080 | 1:1 |

A few things to notice. Open Graph, Facebook, and LinkedIn all land on essentially the same 1.91:1 landscape rectangle, which is exactly why a single 1200x630 image covers most of your needs. X uses a true 16:9 frame for its large summary card, and squares show up when a platform crops to a 1:1 cell.

Why 1200x630 is the safe default

The og:image tag is read by Facebook, LinkedIn, Slack, Discord, WhatsApp, iMessage, and almost every other service that unfurls a link. They all expect a landscape image around 1.91:1, and 1200x630 is the size those platforms officially recommend. Ship that one image and your link will look correct in the overwhelming majority of places it gets shared.

It is also large enough to stay crisp on high-density displays without being so heavy that it slows down the scrape. If you only make one image per page, make it this one.

<meta property="og:image" content="https://example.com/og/post-title.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />

X has its own tags. If you want a tailored 16:9 card, add the Twitter-specific markup; otherwise X will fall back to your Open Graph image.

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:image" content="https://example.com/og/post-title.png" />

Aspect ratios, in plain terms

1.91:1 is the wide landscape rectangle used by Open Graph, Facebook, and LinkedIn (1200x630 / 1200x627). This is the workhorse.
16:9 is X's large card (1200x675 up to 1600x900). It is slightly taller than 1.91:1, so a design built only for 1200x630 may get nudged a little when shown as 16:9.
1:1 is the square (1080x1080) used by Instagram-style feeds and some in-app crops.

If you design for the wide 1.91:1 frame and keep your content centered, it survives the move to 16:9 and even a square crop reasonably well. That is the whole logic behind a safe area.

Safe-area tips

Different platforms crop differently, and some overlay UI (an avatar, a domain label, a play button) on top of the image. Protect yourself with a few habits:

Keep critical content in the center. Treat the outer ~10% on every edge as a danger zone that might get trimmed in a square or 16:9 crop.
Do not put text near the edges. Logos and headlines pushed to a corner are the first thing to disappear.
Mind the bottom edge. Some unfurls drop a domain or title bar over the lower portion of the image.
Use big, high-contrast type. OG images are often viewed small, in a busy feed, on a phone. If the headline is not readable as a thumbnail, it is not doing its job.

File size and format

Format: PNG or JPG. Use PNG for crisp text, flat colors, and sharp logos; use JPG for photographic backgrounds where a smaller file matters more than perfect edges.
File size: keep it under 5 MB. Smaller is better, because scrapers will sometimes skip or fail on oversized images, and a heavy file slows down the first unfurl.
Absolute URLs only. og:image must be an absolute URL (https://example.com/og/...), not a relative path. Relative paths are the single most common reason a preview shows up blank.
Export at 2x for crispness. Designing at the target dimensions and exporting at 2x gives you sharp results on retina and high-DPI screens. FreeOGImage exports at 2x automatically, so a 1200x630 design comes out at 2400x1260.

A quick workflow

Start from the 1200x630 default and design with everything important in the center.
Export it (2x) and wire it into your og:image plus width and height tags using an absolute URL.
If X traffic matters, add the summary_large_image tags. Otherwise your OG image is the fallback and you are done.
Validate by pasting the live URL into a platform's debugger or simply sharing it into a Slack or Discord channel to confirm the unfurl.

Everything here runs client-side in FreeOGImage: no signup, no watermark, and nothing you make is uploaded anywhere. Browse the ready-made layouts on the templates page, or read more guides on the blog.

Ready to ship a clean 1200x630 image in a minute? Open the editor and start from the minimal type template.

Open Graph image sizes in 2026 (the cheat sheet)