Images
X Card image sizes: the 2026 cheat sheet
Every X Card image rule in one place: 2:1 and 1:1 ratios, minimum and maximum pixels, the 5 MB limit and formats, plus Open Graph sizes for other platforms.
Short answer
For summary_large_image use a 2:1 image between 300x157 and 4096x4096 pixels (1200x600 is a good choice); for summary use a square of at least 144x144; every card image must be under 5 MB and a JPG, PNG, WEBP or GIF, never SVG.
Key takeaways
- Large image cards: 2:1, minimum 300x157, maximum 4096x4096.
- Summary cards: 1:1, minimum 144x144.
- All cards: under 5 MB; JPG, PNG, WEBP, GIF (first frame only); no SVG.
- One 1200x630 image works almost everywhere, with a slight crop on X.
Image rules are the part of card markup people look up most, and the numbers are scattered across several pages of X's documentation. Here they are together, with the sizes other platforms want, as of November 2026.
What size should an X card image be?
1200x600 for a large image card, 600x600 for a summary card, and under 5 MB in JPG, PNG, WEBP or GIF. Those are comfortable sizes inside X's limits:
| Card type | Ratio | Minimum | Maximum | Good default |
|---|---|---|---|---|
summary_large_image |
2:1 | 300x157 | 4096x4096 | 1200x600 |
summary |
1:1 | 144x144 | 4096x4096 | 600x600 |
player (poster) |
match the player | 68,600 pixels total | 4096x4096 | 1280x720 |
app |
taken from the store | n/a | n/a | n/a |
Every card image shares the file rules: under 5 MB, in JPG, PNG, WEBP or GIF. For an animated GIF only the first frame is used. SVG is not supported at all, and an SVG in twitter:image simply gives you no image.
The odd-looking 157 in the large image minimum is X's own figure; 300x157 is a hair over 1.91:1. Do not design at the minimum. Cards are shown at full post width on desktop and on high-density phone screens, so anything under about 1000 pixels wide looks soft.
Should I use 1200x600 or 1200x630?
Use 1200x630 if you want one image everywhere; use 1200x600 if X is the platform that matters most. 1200x630 is the size Meta recommends for link shares, at about 1.91:1, and it has become the default for Open Graph images in general. On X it is cropped to 2:1, which removes 15 pixels from the top and 15 from the bottom at full size. That is invisible unless you put text or a logo right at the edge.
If your design has a tight frame or text near the top and bottom, export a 1200x600 version and use it for twitter:image while og:image keeps the 1200x630 version. The image checker can produce both from one source.
What about other platforms?
Most of them are happy with the same 1200x630 image; the differences are in minimums and file size.
| Platform | What it reads | Size guidance |
|---|---|---|
og:image |
1200x630 recommended; 600x315 minimum for the large layout; 200x200 absolute minimum; files up to 8 MB | |
og:image |
about 1.91:1; 1200x627 is the commonly cited size | |
| Apple Messages | og:image |
at least 900 pixels wide; under 150 pixels wide may be treated as an icon |
| Discord | og:image or twitter:image |
uses declared width and height if present; large layout with summary_large_image |
| Slack | oEmbed, Twitter Card and Open Graph tags | fetches the image to validate it |
Apple's technote also suggests avoiding text in preview images because they are shown at varying sizes. That advice fits Messages; on X a large, short title on the image generally helps people decide to click. A few big words satisfy both.
How heavy can the file be?
Under 5 MB for X, but aim for 100 to 400 KB. The limit is a ceiling, not a target. A 1200x630 JPG at quality 80 to 85 is usually 80 to 250 KB. PNG is better for flat colors and text but can be several times larger for photos. WEBP is typically the smallest for both and is on X's supported list. Smaller files are fetched faster by every crawler and stay well clear of other platforms' limits.
Where should the important part of the image go?
In the middle, away from the bottom-left corner and the very edges. On current X apps the page title is laid over the lower-left of large image cards, so faces and text there get covered. Summary cards crop to a center square. Some apps round the corners. A safe working area is the central 80% of the width and the top two thirds of the height.
Quick checks before you ship
- Open the image URL in a private window: it should load without a login.
- Confirm the URL in
og:imageis absolute and uses https. - Check the size and format with the image checker.
- Add
og:image:width,og:image:heightand alt text. See alt text for card images. - If you are replacing an image X has already seen, give it a new file name, because images are cached by URL.
If you do not have an image at all, the OG image maker will draw a clean title card at any of the three common sizes.
Questions
Is 1200x630 OK for X?
Yes. It is slightly taller than 2:1, so X trims a few pixels from the top and bottom. If nothing important sits at the very edges you will not notice.
Does X support WEBP card images?
Yes. X's documentation lists JPG, PNG, WEBP and GIF. AVIF is not on the list, so convert AVIF images before using them in cards.
Can I use an animated GIF?
You can, but only the first frame is shown in the card. Make sure that frame works as a still image.
What size should a player card poster be?
Match your player's aspect ratio, usually 16:9, and keep it above 68,600 pixels in total. Below that, X says the card will not render; 1280x720 is a comfortable size.