Twitter Card Types Explained: Summary, Summary Large Image, Player, App

The twitter:card meta tag controls which layout X uses to render a link preview. There are four values in active use, and picking the wrong one is a common reason a link looks smaller or plainer on X than it does everywhere else. Here's what each one does, the exact tag to set, and when it's the right call.

summary

A compact card: a small, roughly square image sits to the side of the title and description text. It's the most conservative layout and takes up the least vertical space in a timeline.

• Set with: <meta name="twitter:card" content="summary" />
• Also needs: twitter:title, twitter:description, twitter:image
• Use it for: text-heavy pages where the image is secondary — a profile page, a small utility tool, or content where the title itself carries most of the weight.

summary_large_image

The card almost everyone actually wants. The image renders full-width above the title and description, giving it the same visual prominence you'd see on Facebook, LinkedIn, or Slack. This is the default choice for blog posts, product pages, and anything you want to stop the scroll.

• Set with: <meta name="twitter:card" content="summary_large_image" />
• Also needs: twitter:title, twitter:description, twitter:image (a 1200x630px image displays cleanly without cropping)
• Use it for: blog posts, articles, product and marketing pages — the default for almost any public-facing link.

player

An embedded, playable video or audio card. Instead of a static image, X renders an inline player that plays directly in the timeline without leaving the app. This requires more setup than the image-based cards — you need an embeddable player URL that meets X's player-card requirements, plus fixed dimensions.

• Set with: <meta name="twitter:card" content="player" />
• Also needs: twitter:player (an iframe-embeddable URL), twitter:player:width, twitter:player:height, plus a fallback twitter:image
• Use it for: video posts, podcast episodes, or any content where autoplay-in-timeline meaningfully beats a static thumbnail.

app

A card built to drive mobile app installs. It shows app icon, name, rating, and price alongside a direct install button, pulling the data from the App Store or Play Store listing you point it at rather than from a custom image.

• Set with: <meta name="twitter:card" content="app" />
• Also needs: twitter:app:id:iphone / twitter:app:id:googleplay (store IDs), plus optional twitter:app:name and twitter:app:url fields
• Use it for: linking directly to a mobile app rather than a web page — landing pages whose whole purpose is the install.

Which one should you actually set

If you're not sure, summary_large_image is the right default for nearly any content page — it's the layout that gives your image the most visual real estate and the closest parity with how the same link looks on other platforms. Reach for summary only when a smaller footprint genuinely suits the content, and reserve player and app for the specific cases they're built for. Whichever you pick, confirm it with a link-preview scanner before shipping — a missing required field silently falls back to a plainer card instead of throwing an error.