Twitter Card types explained: summary, summary_large_image, player, and app cards
Use summary_large_image for content pages and summary for utility or reference pages. Use an App Card when the page promotes a mobile app and includes its App Store or Google Play identifiers and deep links. A paid campaign may need an X Ads account, but normal App Card metadata does not.
Twitter Cards control how your URL appears when shared on X (formerly Twitter). The four types are summary (small square thumbnail + title + description), summary_large_image (full-width hero image + text below), player (embedded video or audio), and app (direct app install link). Most websites need only summary_large_image for articles and summary for everything else.
By TechCompare · Updated
How this is calculated
summary_large_image is the best choice for blog posts, product pages, and landing pages. It shows a prominent 1.91:1 image above the title and description, taking up roughly 30% more vertical space in the timeline than a summary card. The summary card is useful for pages where the image is secondary, such as documentation, API references, and list pages. An App Card is ordinary page metadata, not a paid-ad feature: set twitter:card to app and provide the relevant twitter:app:name, twitter:app:id, and optional deep-link URL fields for each mobile platform. Under X's card policy, the shared post must explicitly promote or refer to the app. Ads Manager has separate requirements only when you run a paid campaign.
Verdict
summary_large_image puts the 1.91:1 hero above the title and adds about 30% more timeline height, which is why it fits blog posts and product pages. The summary card is the better pick for docs and reference pages where the image is secondary to the title. A player card needs valid player metadata and a reachable HTTPS player, but this is not a general Twitter whitelisting workflow. Each card pulls its own twitter:title, twitter:description, and twitter:image tags.