Open Graph image size and tags: the complete guide
When someone shares your link, the card that appears, with its image, headline and line of text, comes from Open Graph tags in the page's <head>. Get the image size and a handful of tags right once, and every platform shows a proper card.
The image size to use
1200 × 630 pixels, a 1.91:1 ratio, as a JPG or PNG under about 1 MB. That one image works on Facebook, LinkedIn, Slack, Discord and messaging apps, and is close enough to X's large card that it displays well there too.
Larger is fine as long as the ratio holds; 2400 × 1260 looks sharper on high-resolution screens. Smaller images still work down to a point, but Facebook, for one, shows images under 600 × 315 much smaller than a full-width card.
What each platform asks for
| Platform | What it documents |
|---|---|
| At least 1200 × 630 for the best display, 600 × 315 minimum for a large image, 200 × 200 absolute minimum, ratio as close to 1.91:1 as possible, file no bigger than 8 MB. | |
| At least 1200 × 627, ratio 1.91:1, file no bigger than 5 MB. | |
| X (Twitter) | Large image cards use a 2:1 ratio, from 300 × 157 up to 4096 × 4096, under 5 MB. Set twitter:card to summary_large_image or X shows a small square card. |
| WhatsApp, iMessage, Slack, Discord | No published size. They read og:image, and 1200 × 630 displays well in all of them. Keep the file small, because these apps fetch the image while the message is being sent. |
The difference between 1.91:1 and 2:1 is a few pixels top and bottom. X crops a 1200 × 630 image very slightly, which is why the important content belongs in the middle.
The tags every page needs
Open Graph is defined at ogp.me. Its four required properties are og:title, og:type, og:image and og:url; a description and image dimensions make the card better and faster:
<meta property="og:title" content="Trail Runner 2 Waterproof Shoe"> <meta property="og:description" content="Lightweight waterproof trail shoe with a 6 mm drop. Free returns."> <meta property="og:type" content="website"> <meta property="og:url" content="https://example.com/shoes/trail-runner-2/"> <meta property="og:image" content="https://example.com/img/share/trail-runner-2.jpg"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="630"> <meta property="og:image:alt" content="The Trail Runner 2 shoe on a muddy path"> <meta property="og:site_name" content="Example"> <meta name="twitter:card" content="summary_large_image">
og:imagemust be an absolute URL, starting withhttps://. A relative path such as/img/share.jpgis ignored by several platforms.og:image:widthandog:image:heightlet Facebook render the image the first time the link is shared, before it has downloaded and measured the file.og:typeiswebsitefor most pages andarticlefor posts.- X reads Open Graph tags for the title, description and image when its own
twitter:tags are missing, sotwitter:cardis the only X tag most sites need.
If a page has no Open Graph tags, platforms guess from the title tag, meta description and the first large image they find, which is often a logo or an icon. Setting the tags yourself removes the guessing.
Designing an image that survives cropping
- Keep text and faces in the middle. Some apps crop the card to a square or a narrower shape on phones. A safe area of about 630 × 630 in the centre is shown everywhere.
- Use few words, set large. The card is often seen at 300–500 pixels wide on a phone. A headline that's readable at 1200 pixels may be a blur at that size.
- Don't repeat the title. The headline is already printed under the image. Use the image for a product photo, a chart or a strong visual instead.
- Use a JPG for photos and PNG for flat graphics, and compress both. These two formats are read by every platform and app.
Why the preview doesn't update
Every platform caches share cards, and Facebook caches images by URL. If you change the tags or replace the image but keep the same file name, people keep seeing the old card.
- Give a changed image a new URL, for example
share-v2.jpg, and updateog:image. Facebook recommends not deleting the old file, because existing posts still point to it. - Ask each platform to fetch the page again: Facebook's Sharing Debugger ("Scrape Again") and LinkedIn's Post Inspector. X and the messaging apps refresh on their own over time.
- Check the image is reachable for crawlers: not behind a login, not blocked in robots.txt, and not served only to browsers that run JavaScript.
Posts that were shared before the fix keep their old card. The refresh only affects new shares.
How to check a page
A checker reads the page as platforms do, lists every og: and twitter: tag, loads the image to measure its real size and ratio, and shows the card as Facebook, LinkedIn and X will draw it:
To check share tags across a whole site, the website SEO audit flags pages with no og:title or og:image, which usually points to a template that's missing them.
Questions
What is the best og:image size for WhatsApp?
WhatsApp doesn't publish one. It reads the page's og:image, and the standard 1200 × 630 image displays well. Keep the file small, ideally a compressed JPG of a few hundred kilobytes, since the preview is fetched as the message is sent.
What size should the Facebook og:image be?
At least 1200 × 630 pixels, at a 1.91:1 ratio. Facebook shows images from 600 × 315 as large cards and ignores images smaller than 200 × 200. The file must be under 8 MB.
Can I use a square image?
You can, but most platforms will crop it to a wide card or show it as a small thumbnail. A 1.91:1 image is shown as intended almost everywhere.
Do Open Graph tags affect SEO?
Not directly; Google doesn't rank pages on them. They decide how your links look when shared, which affects how often they're clicked. Google can use og:title as one of the sources for a result's title.
Why does the wrong image show when I share my link?
Either the page has no og:image, so the platform picked one, or the platform is showing a cached card. Add the tag with an absolute URL, then refresh the cache with the Sharing Debugger or Post Inspector.