OG image sizes for every platform (2026)

The Open Graph image is the single most-clicked element of a shared link: it is the difference between a bare URL and a card with a headline and a face. Getting sizes right is unglamorous and worth thirty minutes of your life, because the same PNG serves every platform if you respect a few crops. This is the 2026 state of play, verified against current platform docs and behavior.

The one size that works everywhere

1200 × 630 pixels remains the safe universal choice. Facebook, LinkedIn, WhatsApp, Discord, Telegram, Slack and most unfurlers display it at roughly 1.91:1, which is exactly this ratio. X (Twitter) prefers 16:9 and will show 1200 × 630 with a minor top-and-bottom crop in its large-card layout — a fair trade for maintaining a single image. Design with that crop in mind and one file covers every platform you realistically care about. Instagram and TikTok do not use Open Graph cards for in-app links the way the rest of the web does, so ignore them for og:image purposes and size for the link-unfurling platforms instead.

Safe margins and text rules

Every platform crops slightly differently and some (WhatsApp in particular) crop harder in certain views, so treat the outer 10 percent of every edge as sacrificial. Keep logos, headlines and faces inside a centered 1000 × 500 comfort zone, and set body text at no smaller than 40 pixels at 1200 width — image cards render small on phones, and text that was legible on your monitor becomes a smear at 380 CSS pixels. High contrast matters more than beauty: a washed-out image with crisp text outperforms an exquisite one that cannot be read in a feed.

The tags that must ship with og:image

An image alone does not make a card. The minimum viable set is five tags, and the commonest debugging failures are a relative og:image URL or a missing og:title:

• og:title — the headline the card shows; keep under ~60 characters.
• og:description — one supporting line; under ~110 characters keeps it unclipped in most views.
• og:image — an absolute URL starting with https, publicly reachable, no redirects or login.
• og:url — the canonical URL of the page being shared.
• twitter:card — set to summary_large_image, or X shows a tiny square instead of the big card.

After changing tags, re-scrape the URL with the platform's own debugger (Facebook's Sharing Debugger, X's card validator, LinkedIn's Post Inspector) — platforms cache aggressively, and the debugger is the reliable cache-buster. Our SERP & Social Preview tool shows the Google snippet and the social cards side by side before you ship.

File size and format

Use PNG for anything with text or flat color, JPEG for photographs, and keep the file under 1 megabyte — large files load slowly, some platforms compress them into ugliness, and a few reject images beyond roughly 5 MB. WebP is increasingly accepted but not yet universal enough to bet a launch on. Name the file something stable; renaming it later without changing the URL in your tags is a classic way to break cards that used to work. Finally, keep one canonical copy of the image at a permanent URL even if you redesign the site around it — platforms remember and re-serve the URL they first scraped, sometimes for months.

A quick word on dark mode: most feed environments render dark backgrounds around cards, which makes dark-on-dark edges disappear. Give your image a subtle border or a slightly lighter frame so the card reads as a card in both light and dark UIs. It is a two-minute design decision that pays off every single share.

Make one in a minute

The ToolFolio OG Image Generator builds 1200 × 630 previews from templates with your brand colors, entirely in your browser — no upload of your design to anyone's server, no sign-up, free. Pair it with the SERP & Social Preview tool to see the finished card exactly as each platform will render it before you deploy.

Questions people ask