Resize image for Facebook Post (1200×630)
1200×630 (roughly 1.91:1) is the size Facebook uses for shared link previews and the recommended size for in-feed image posts. It's also the standard Open Graph image size used by LinkedIn, X, and most other platforms.
1200×630 pixels (1.91:1) is Facebook's recommended in-feed image size and simultaneously the Open Graph standard used for link previews. Because Facebook, LinkedIn, X, Slack and Discord all read the same og:image tag, a single 1200×630 export becomes the preview card across effectively every platform that unfurls links. Two rules make the difference between a card and a thumbnail: the image must be at least 200×200 to be honoured at all, and below roughly 600 pixels wide most platforms render a small square beside the text instead of a full-width card. Use an absolute URL in the og:image tag, since relative paths are not resolved by every scraper. Text in the image should be large and central, because the card is often displayed at around 500 pixels wide. Facebook also caches previews aggressively, so use the Sharing Debugger to force a refresh after changing the tag.
Drop an image to resize to 1200×630
JPG or PNG
Why does one image control every link preview?
The Open Graph protocol was created at Facebook and later adopted broadly, which is why its recommended dimensions became a de facto cross-platform standard. When any of these services encounters a URL, it fetches the page, reads the og:image meta tag and renders a card at approximately 1.91:1. Setting a 1200×630 image once therefore controls how your page appears in a Facebook post, a LinkedIn share, a Slack unfurl, a Discord embed and an X summary card. The 1200-pixel width is chosen to look crisp on high-density displays where the card renders at around 500 CSS pixels; supplying a smaller image results in visible softness on retina screens. Facebook additionally requires a minimum of 200×200 for the tag to be honoured at all, and images below roughly 600 pixels wide are often rendered as a small square thumbnail beside the text instead of a full-width card.
Cropping, text density and cache behaviour
Anything not already at 1.91:1 is centre-cropped in the preview, so a square image loses its top and bottom. The bigger practical issue is caching: once a platform has fetched and cached a preview image for a URL, changing the file does not update the card. Facebook exposes a Sharing Debugger that forces a re-scrape, and LinkedIn has a Post Inspector, but Slack and Discord cache for extended periods with no user-facing purge. The lesson is to get the image right before the link is first shared widely. Facebook's historical 20%-text rule for ad images no longer causes outright rejection, but image-heavy text still tends to reduce delivery in paid contexts, and dense text is unreadable at the small card size regardless.
Making a card that reads at thumbnail scale
A link preview card is frequently rendered around 500 pixels wide in a desktop feed and smaller in a mobile one, so the design has to survive roughly a 60% reduction. Keep to one short headline and one supporting element. Leave a margin of at least 60 pixels inside all four edges, because different platforms crop the card slightly differently and content flush to the edge occasionally gets clipped. High contrast between text and background matters more than at full size. If the same asset is doubling as an in-feed image post rather than only a link preview, remember the feed post is displayed larger and can carry a little more detail, but building for the smaller case keeps one file working for both. Where a site publishes many pages, generating a consistent template with the page title composited over a branded background gives every share a recognisable look without designing each one by hand.
Facebook Post tip: 1200×630 doubles as your Open Graph image
This same 1200×630 image works as your og:image for websites — set it once and your post looks great whether shared on Facebook, LinkedIn, Slack, or Discord.
Facebook Post size FAQ
Is 1200×630 the same as the Open Graph size?
- Yes. Open Graph recommends 1200×630 and Facebook's in-feed recommendation matches it, which is why one file covers both uses.
Will Facebook crop my image?
- Only if it is not already 1.91:1. Other ratios are centre-cropped in the preview card, so resize first to control the framing.
I changed the image but the old one still shows. Why?
- The platform cached the preview. Facebook's Sharing Debugger and LinkedIn's Post Inspector force a re-scrape; Slack and Discord generally do not offer one.
Does the same size work for LinkedIn?
- Yes. LinkedIn recommends 1200×627, a three-pixel difference that is invisible in practice.
Is there still a 20% text rule?
- It no longer causes rejection, but text-heavy images tend to see reduced delivery in paid placements and are hard to read at card size anyway.
What is the minimum size that works?
- Facebook requires at least 200×200 for the tag to be honoured, but anything under about 600 pixels wide renders as a small square thumbnail rather than a full card.
Should I use JPG or PNG?
- JPG for photographic cards. PNG is better when the card is flat colour with sharp text, since JPEG artefacts show clearly around hard edges.
Does my image get uploaded anywhere?
- No. The resize runs locally in your browser using a canvas element.
Platforms that consume a 1200×630 og:image
| Platform | Card ratio | Cache refresh available |
|---|---|---|
| 1.91:1 | Sharing Debugger | |
| 1.91:1 | Post Inspector | |
| X (Twitter) | 1.91:1 summary_large_image | Re-scrape on new URL |
| Slack | ~1.91:1 | No user-facing purge |
| Discord | ~1.91:1 | No user-facing purge |
Get the image right before a URL is widely shared — several platforms cache previews indefinitely.
Last updated:
References: Open Graph protocol specification; Facebook Sharing best practices and Sharing Debugger documentation; LinkedIn Post Inspector documentation.