Open Graph Image Size in 2026: The Complete Guide for Every Platform

The recommended Open Graph image size in 2026 is 1200×630 pixels — a 1.91:1 aspect ratio, kept under about 1 MB. That single dimension renders as a full-width “large” share card on Facebook, X, LinkedIn, Slack, Discord, WhatsApp and iMessage, so it is the one size you should treat as the universal default. Nothing about that core number has changed for years, and it is not changing in 2026 either — what has shifted is how individual platforms crop, compress and fall back when you stray from it.

This guide gives you the exact pixels, the safe zone, the file-size limits, and the meta tags — then the platform-by-platform specifics so your previews look sharp everywhere a link can be pasted.

The one size to remember: 1200×630

If you only take one thing away, make it this: build at 1200×630 pixels. It is the dimension every major platform expects for its large preview card, and it has been the stable standard since responsive share cards became the norm.

1200×630 px — the universal target (1.91:1). Use it unless a specific platform needs something different.
Minimum 600×315 px — below this, platforms downgrade your card to a small thumbnail with the image squeezed off to the side.
Aspect ratio 1.91:1 — matching the ratio matters as much as the raw pixels; an off-ratio image gets cropped, not letterboxed.
File size under ~1 MB — well below the 5 MB ceiling most crawlers enforce. A clean PNG or JPEG is plenty.
Format — PNG for text and flat color, JPEG for photography. Avoid WebP and SVG for og:image; some crawlers still won’t render them.

For crisp rendering on high-density displays you can render at 2x (2400×1260) and let the platform downscale, but keep the file under the size budget. There is rarely a reason to go larger.

The safe zone: where to put text and your logo

Different apps crop the edges of your card differently, and some overlay a play button, avatar or duration badge in a corner. Keep anything that must be readable inside a center safe zone: roughly the middle 1080×600 region, with at least 60 px of breathing room on every edge.

A share card is an advertisement you didn’t pay for — and the image is the headline of that ad. If the headline gets cropped, the ad fails.

Practical rules that survive every crop: headline type at 48 px or larger, no more than two short lines, and your logo set in from the corner rather than flush against it.

The meta tags that control it

Open Graph data lives in <meta> tags in the page’s <head>. For the image specifically, declare the URL plus its dimensions and type so crawlers can reserve space and render the card faster:

<meta property="og:image" content="https://example.com/og/post.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="A short description of the image">
<meta name="twitter:card" content="summary_large_image">

Two non-negotiables: the og:image URL must be absolute (https://…, never a relative path), and twitter:card must be set to summary_large_image or X will shrink your beautiful 1200×630 image into a tiny square thumbnail.

Platform-by-platform sizes in 2026

The 1200×630 default works everywhere, but a few platforms have their own quirks worth knowing.

Facebook, LinkedIn, Slack, Discord, WhatsApp, iMessage

All read standard Open Graph tags and render 1200×630 as a full-width card. This is the bulk of where your links get shared, and the universal size covers all of them with no extra work.

X (Twitter)

X uses its own twitter: namespace but falls back to your Open Graph tags. With twitter:card=summary_large_image set, it shows the same 1200×630 large card. Omit that one tag and you drop to a cramped square thumbnail — the most common “why does my card look broken on X?” cause.

Pinterest is the exception that rewards a vertical image. Pins display best at a 2:3 ratio — 1000×1500 — so if Pinterest traffic matters to you, serve a tall variant via og:image on the pages you expect to be pinned, rather than the horizontal card.

Messaging and link unfurlers

Slack, Discord, WhatsApp and Telegram all unfurl links using Open Graph too. They cache aggressively, so after you change an image you may need to re-share the link or clear the cache before the new version appears.

Common 2026 mistakes that still break previews

Wrong aspect ratio. An 800×800 square or a 16:9 hero photo gets cropped or downgraded to a small card. Match 1.91:1.
Relative image URLs. Crawlers don’t run your JavaScript or reliably resolve relative paths — always use an absolute https:// URL.
Missing twitter:card. Without it, X serves the small summary card.
Stale caches. Platforms cache previews for days. Re-scrape the URL in the platform’s debugger after any change.
One generic image sitewide. A single homepage banner on every page is a missed click. Per-page images consistently out-perform a static logo.
Oversized files. A 4 MB PNG may be silently skipped. Keep it lean.

How to ship the right size for every page

For a handful of pages, hand-making 1200×630 images in a design tool is fine. For a blog, docs site or store with hundreds of URLs, doing it by hand does not scale — and the pages you skip end up with no preview image at all, which is the worst outcome.

The durable approach is to generate Open Graph images programmatically: a template defines the layout, fonts, colors and logo once, and each page’s title fills in the variables automatically. The image is rendered server-side at exactly 1200×630, served behind a single absolute og:image tag, and regenerated whenever the page changes.

That is what Ogwave does. Point it at your sitemap and it discovers every URL, reads each page’s title, and renders an on-brand 1200×630 card for all of them. You can browse ready-made templates across blog, product, docs and event styles — each already built to the correct size and safe zone — or paste any URL into the free preview tool to see how your current tags render across platforms and get a corrected, copy-paste meta block.

The short version

In 2026 the Open Graph image size is still 1200×630 pixels at a 1.91:1 ratio, under ~1 MB, with text inside the center safe zone. Use an absolute image URL, declare the width and height, add twitter:card=summary_large_image, serve a 2:3 vertical version for Pinterest if it matters, and give every page its own image instead of one generic banner. Get those right and your links earn the click they deserve on every platform.