Generate the twitter:card meta tags that control how your page looks when shared on Twitter/X, with a live card preview across all four card types — Summary, Summary Large Image, App, and Player.
Full-width image above the title and description.
When a link is posted in a tweet, Twitter/X's crawler fetches the page and scans its <head> for twitter: meta tags, using twitter:card specifically to decide which of the four supported layouts to render. For any twitter: field it doesn't find set explicitly, it falls back to checking for the equivalent Open Graph (og:) tag before giving up and rendering no card at all — which is why sites that already have solid Open Graph tags in place often only need to add twitter:card itself, plus twitter:site and twitter:creator for proper attribution, to get a fully working Twitter Card.
summary_large_image is the default, most visually prominent choice for the vast majority of shared content — articles, blog posts, product pages, and general web content — since its large image draws attention in a fast-scrolling timeline. summary suits cases with a smaller or less critical image, or where the text content matters more than a large visual. app and player are narrow, purpose-built types: app links directly to an installable mobile application in the App Store or Google Play, and player embeds a directly playable video or audio clip inline in the tweet itself, both requiring additional platform-specific setup beyond the basic tags this tool generates.
Twitter/X enforces real minimum dimensions per card type and will silently fail to display an image (or reject the card layout entirely) if your image doesn't meet them — a minimum of 300×157 pixels for summary_large_image, though 1200×630 is the safer target for a crisp result across devices, and a much smaller square minimum for the summary card's compact thumbnail. As with Open Graph images, the URL in twitter:image must be a complete, absolute HTTPS address, never a relative path, since Twitter/X's crawler fetches it independently with no browsing context of its own.
twitter:site attributes the shared content to the publication or brand's Twitter/X account, while twitter:creator attributes it to the specific individual who wrote or created that particular piece — the two are commonly different accounts (a company's official handle versus an individual staff writer's personal handle), and including both, when applicable, gives credit more precisely than either field alone. Neither is required for a card to render at all, but their absence means Twitter/X has no attribution to display alongside the card, missing a small but real opportunity for either the brand or the individual creator to be recognized.
Twitter/X caches card data per URL after the first time it's crawled, so changes to your meta tags won't automatically appear on a link that's already been shared before — use Twitter/X's Card Validator to force a fresh scrape and confirm your current tags produce the card you expect, including checking that the correct image, title, and description are all being picked up. This is a much more reliable check than simply reading your generated HTML and assuming it will render exactly as intended, since a subtle issue with the page's actual served HTML (a missing closing tag elsewhere, for instance) can sometimes prevent Twitter/X's crawler from parsing the meta tags correctly even when they look right in your source.
Twitter Card Generator focuses specifically on Twitter/X's own card format. These related tools cover the other social and search metadata a page typically needs.