Twitter / X card types explained — summary vs summary_large_image

Quick frame: X (Twitter) supports four card types — summary, summary_large_image, app, player. For 99% of marketing content, summary_large_image wins on engagement. Pick summary only when the image is genuinely weak or you want a compact link-list feel.

The four types, ranked by use case

summary_large_image (default for marketing)

Wide hero image (1200×675, 1.91:1) above the text. Stops the scroll. Engagement typically 2–3× higher than the small thumbnail variant.

summary (compact text-first)

Small square thumbnail (144×144 minimum) next to the text. Use only when:

• The image is genuinely weak (text-only podcast, document).
• You want a compact link-list feel (e.g., a thread of multiple links).

app (mobile app deep-link)

Promotes an iOS / Android app with the app store badge. Mostly for app launches.

player (video / audio embed)

Embedded media player. Audio podcasts, video creators. Requires HTTPS and a hosted player URL.

The validation workflow

X caches card metadata for ~7 days. After publishing changes, force a fresh fetch at cards-dev.twitter.com/validator. This is essential before any campaign — don't assume tweets will pick up new tags.

Use the Twitter card preview to mock the visual first, then the Twitter card generator for the actual tag block.

Open Graph as fallback

X reads Open Graph tags as a fallback if twitter:* tags are missing. So you can ship just OG and get a passable card. But explicit twitter:* tags give you full control — different image for X vs Facebook, X-specific handles credited in the card, image alt text optimised for X's audience.

Required vs nice-to-have

Required: twitter:card, twitter:title, twitter:description, twitter:image. Recommended: twitter:site (your @handle), twitter:creator (author @), twitter:image:alt.

For the full Open Graph parallel, read Open Graph tags checklist for 2026.

FAQ

Q. Does Twitter still call them "Twitter cards" after the rebrand? A. Internally the API and tags retain the twitter:* prefix. The product is now "X cards" in user-facing copy.

Q. Image dimensions for summary_large_image — 1200×630 or 1200×675? A. X recommends 1200×675 (16:9). 1200×630 (Facebook's 1.91:1) still renders but with mild side-cropping. If you serve one image for both, 1200×675 is the safer bet.

Q. Does X verify the image is accessible? A. Yes. Hosting behind authentication or geo-restricted URLs breaks card rendering.