Twitter Card types explained: summary, summary_large_image, player, and app cards

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.

Platform or focus
Platforms
Social media and messaging apps
Topic detail
Twitter Card types
twitter-cards

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 (documentation, API references, list pages). The player card requires Twitter whitelisting and is mainly used by YouTube, Vimeo, and major media publishers. The app card is for mobile app install campaigns and requires a Twitter Ads account. Each card type needs specific meta tags: twitter:card, twitter:title, twitter:description, twitter:image, and optionally twitter:site and twitter:creator.

Verdict

Use summary_large_image for content pages. Use summary for utility and reference pages. Skip player and app cards unless you work at a company with a Twitter Ads account and a whitelisted domain.

More OG scenarios

Frequently asked questions

What are Open Graph meta tags?
Open Graph meta tags are snippets of code in your website's <head> that control how your page appears when shared on social media. They allow you to define a specific title, description, and image that platforms like Facebook, Discord, and LinkedIn will display.
Why do I need a separate twitter:card tag?
While many platforms fallback to Open Graph (og:) tags, Twitter uses its own specific meta tags (twitter:card, twitter:image, etc.) to format link previews. Providing both ensures maximum compatibility across all platforms.
What is the best image size for Open Graph?
The recommended size for an Open Graph image is 1200x630 pixels. This creates a 1.91:1 aspect ratio, which is the standard size used by almost all major social platforms for large preview cards.
How do I test if my tags are working live?
Once deployed, you can use official debuggers like the Facebook Sharing Debugger or the Twitter Card Validator. This visualizer tool helps you preview and generate the tags locally before you deploy them.