What is the best Open Graph image size for 2026?
Use 1200 x 630 pixels, an aspect ratio of about 1.91:1. Meta recommends at least 1200 x 630, LinkedIn asks for at least 1200 x 627, and X's large card uses a 2:1 ratio, which at most trims 15 pixels from the top and bottom. Keep the headline and logo in the middle, save a JPG or PNG well under 5 MB, and declare the size with og:image:width and og:image:height. To bring an existing image to that size, the Image Resizer has a 1200 × 630 preset that crops or pads it to fit.
Platform requirements side by side
| Platform | Size guidance | Aspect ratio | Max file size | Formats in the docs |
|---|---|---|---|---|
| Facebook and other Meta apps | At least 1200 x 630 recommended; 600 x 315 for the large preview; 200 x 200 absolute minimum | As close to 1.91:1 as possible | 8 MB | Not listed |
| Minimum 1200 x 627 | 1.91:1 | 5 MB | Not listed for link previews | |
| X, summary_large_image card | Minimum 300 x 157, maximum 4096 x 4096 | 2:1 | Under 5 MB | JPG, PNG, WEBP, GIF (first frame only); no SVG |
| X, summary card | Minimum 144 x 144, maximum 4096 x 4096 | 1:1, always cropped to a square | Under 5 MB | Same as the large card |
Figures from Meta's images in link shares guide, LinkedIn's shareable website help page and X's Cards documentation. One 1200 x 630 file satisfies every row, so a single Open Graph image size covers all four.
Where the edges get cut
I've seen plenty of sites put the logo in the top-right corner of the OG image, only for it to be trimmed off in a cropped mobile preview, which is why I recommend a center-heavy design. No platform publishes an official safe zone, but the crops follow from the ratios. On a 1200 x 630 canvas, assuming a centered crop:
- X's 2:1 large card works out to 1200 x 600, so a crop to that ratio takes 15 pixels from the top and 15 from the bottom.
- LinkedIn's 1.91:1 works out to 1200 x 628, a 2-pixel difference nobody will see.
- A square crop, which X applies whenever a page uses the smaller summary card, keeps the central 630 x 630 and drops 285 pixels from each side.
The area that survives all three runs from x = 285 to x = 915 and from y = 15 to y = 615. Put the headline and logo inside it and let the background run to the edges. One caveat from Meta's sharing FAQ: it tries to center crops on faces it detects, so photos of people can crop differently.
File format and file size
X documents JPG, PNG, WEBP and GIF. Meta's and LinkedIn's link-preview docs list no formats at all, so WebP there is something you'd have to test. I still use a high-quality JPG for photos and PNG for flat graphics with text; it's the one place where I'll accept a few extra KB to skip that testing.
Open Graph image size also has a ceiling in megabytes: 8 MB for Meta and 5 MB for LinkedIn and X. Meta's FAQ lists an image that is too big or slow to fetch as a cause of a blank white preview, so as a rule of thumb I keep OG images to a few hundred KB. The Image Compressor shows the original and compressed sizes, with a quality slider and JPEG, PNG or WebP output. How to compress images without losing quality covers which format and quality setting to pick.
Open Graph image dimensions and resolution
1200 x 630 is 756,000 pixels, and its exact ratio is 1.905:1, close enough to the 1.91:1 that Meta and LinkedIn name. LinkedIn's 1200 x 627 works out to 1.914:1, so the two sizes differ by 3 pixels of height and nobody can tell them apart in a feed.
The OG image size Meta asks for is at least 1200 x 630 "for the best display on high resolution devices", so a larger file at the same shape is allowed. If your design tool exports at 2x, the Open Graph image size becomes 2400 x 1260: four times the pixels (3,024,000) and usually a much heavier file, while X still caps images at 4096 x 4096 and 5 MB. To scale while keeping the shape, divide the width by 1.905: 1800 wide gives 945 high, and 1600 wide gives 840. A canvas with another ratio gets cropped to fit, and the crop math in the section above stops applying.
The image tags to add
The full tag set (title, description, type and URL) is covered in Open Graph tags explained. For the image, this is the block I use:
<meta property="og:image" content="https://example.com/og/spring-sale-1200x630.jpg">
<meta property="og:image:type" content="image/jpeg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Spring sale banner with the shop logo on a green background">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:image:alt" content="Spring sale banner with the shop logo on a green background">- Use an absolute URL. Meta's FAQ says all URLs must be absolute so it can attribute shares and cache images properly.
- og:image:width and og:image:height let Meta render the image on the first share; without them, the first person to share may see no image.
- The Open Graph protocol says a page that sets og:image should also set og:image:alt, a description of the image rather than a caption. X's twitter:image:alt allows up to 420 characters.
- twitter:image is optional, because X falls back to og:image. twitter:card has no Open Graph equivalent, and without it X may show the small summary card instead of the large one.
The Meta Tag Generator writes og:image, twitter:card and twitter:image for you; add the type, width, height and alt lines by hand.
Making a 1200 x 630 image with the site's tools
- In the Image Resizer, add your image and open the Social sizes tab.
- Pick "Facebook & link preview 1200 × 630".
- Under "When the shape changes", choose Crop to fill (trims the overflow equally from both sides) or Fit inside (keeps the whole picture on a background colour you pick).
- Set the format to JPG or PNG, click Resize images and download. If the file is heavy, run it through the Image Compressor.
- Upload it, put its absolute URL in og:image, and paste the page URL into the OG Checker. It previews the card in Facebook / LinkedIn, Twitter / X and Slack tabs, shows the declared width and height, and warns about missing og:image, og:title or twitter:card tags.
The checker turns a relative og:image path into a full URL to draw the preview, so confirm in your page source that the tag itself is absolute. It fetches your page from the site's server, so the URL has to be public; a page behind a login or on localhost can't be checked, and the same goes for Facebook's and LinkedIn's crawlers.
Common og:image mistakes
- A relative path such as
/images/og.jpgin og:image. Meta's FAQ requires absolute URLs, and the OG Checker filling in the domain for its preview can hide the problem. - An SVG file. X's card documentation does not accept SVG, and Meta and LinkedIn list no formats at all, so a JPG or PNG is the safe export.
- A file between 5 MB and 8 MB. Meta accepts it, but it is over the LinkedIn and X limits.
- Saving the new design over the old file name. Meta caches by URL, so the old preview keeps showing; the next section covers the fix.
- A headline or logo outside the x = 285 to 915 band. A square crop on X's summary card removes it.
- No twitter:card tag, which can leave X showing the small card with its square crop instead of the large image.
- og:image:width and og:image:height that don't match the real file. Meta reads them to show the image on the first share, before its crawler has processed the file, so give the true pixel size.
The OG Checker also flags text around the image: it warns when og:title is over 60 characters or og:description is over 160. The guides to writing title tags and the meta description character limit cover how to write both to length.
When the preview still shows the old image
Meta caches images by URL, so replacing the file at the same address changes nothing. Upload the new image under a new file name, update og:image and run the page through the Sharing Debugger; left alone, Meta refreshes link data every 30 days. Keep the old image online, because existing posts still point at it and show a white box if it disappears.
LinkedIn's Post Inspector refreshes LinkedIn's stored copy, and X's documentation says its crawler re-reads card tags roughly every seven days. Refreshes only reach new posts: LinkedIn leaves existing previews as they were, and on Facebook you choose "Refresh share attachment" on the post itself.
Frequently asked questions
How do I test my OG image?
Use the Facebook Sharing Debugger or the LinkedIn Post Inspector. These tools show how your image will appear before you publish your post. The OG Checker gives Facebook / LinkedIn, X and Slack style previews from a single URL, along with the image dimensions the page declares.
Can I use one OG image for the whole site?
As a fallback, yes. X's card documentation asks for an image that represents the specific page and says not to use a generic image such as a site logo or author photo, so give your important pages their own artwork.
What happens if my image is smaller than 1200 x 630?
On Facebook, an image under 600 x 315 still appears, but as a small square beside the text. Below 200 x 200 it falls under Meta's minimum.
