Twitter Card Generator
Give links to your page a proper card on X. Choose the card type, enter the title, description and image, add your @username, and copy the twitter: meta tags. The generator validates usernames and addresses, warns when text will be cut off, and can produce the short form for pages that already have Open Graph tags.
- Runs in your browser
- No sign-up
- Free to use
Card preview
An approximation of the card on X. The image is fetched from its address only when you select “Load image”.
How to use Twitter Card Generator
- Choose the card type; “Summary with large image” suits most pages.
- Enter the title, description and image address.
- Add the site’s and the author’s @usernames.
- Copy the tags into the head of your page and post the link to check it.
Twitter Card Generator features
Four card types
Summary, summary with large image, player and app.
Username validation
Accepts @name, name or a profile link and checks the 15-character rule.
Length warnings
Flags titles over 70 and descriptions over 200 characters.
Open Graph fallback
Outputs only the tags X needs when the page already has og: tags.
Player and app fields
Player address and size, App Store and Google Play identifiers.
Preview
Shows the large or small card layout; the image loads only on request.
When to use Twitter Card Generator
- Making blog posts share with a large image on X.
- Adding card tags to a site template.
- Setting up an app card with store links.
- Checking why a link shows without a card.
Twitter Card Generator FAQ
What is a Twitter Card?
A preview that X attaches to a post containing a link: an image, a title and the domain. It is built from meta tags in the page whose names begin with “twitter:”.
Which card type should I use?
“summary_large_image” for articles, products and landing pages, because the large image draws attention. “summary” shows a small square image beside the text. “player” embeds video or audio and needs approval. “app” links to app stores.
What image size works best?
For the large card, a 2:1 shape such as 1200 × 628 pixels; for the small summary card, a square of at least 144 × 144. Files must be under 5 MB in JPG, PNG, WEBP or GIF format.
Do I need these tags if I have Open Graph tags?
X falls back to og:title, og:description and og:image. You still need twitter:card to select the layout, and twitter:site is recommended. Tick the fallback box to get just those.
Is twitter:site required?
It is required for player and app cards and recommended for the others, since it attributes the card to your account.
How do I test a card?
Start composing a post containing the link; the card preview appears in the composer. X caches cards for about a week, so changes to an already-shared address take time to appear.
How X builds a card from your page
When a post contains a link, X’s crawler requests the page and looks in its head for card tags. If it finds twitter:card, it knows which layout to use and reads the title, description and image to fill it. If it finds none, the link appears as plain text, and a plain link gets far less attention than a card with a picture.
The tags are few. twitter:card names the layout. twitter:title, twitter:description and twitter:image supply the content, and twitter:image:alt describes the image for people who cannot see it. twitter:site and twitter:creator name the accounts of the publication and the author. For each of the three content tags the crawler falls back to the Open Graph equivalent, so a page with complete og: tags needs only the card type.
The two summary cards differ only in the image. The large version shows a wide image above the text and suits anything visual. The small version shows a square thumbnail beside the text and suits pages where the image is incidental, such as documentation. Player cards embed media from a dedicated https page and must pass a review; app cards show a name, an icon and a store link taken from the app’s store listing.
Practical problems are usually simple. The image address is relative or blocked by robots.txt, the file is too large, or the page needs a login. The crawler must be able to fetch both the page and the image without authentication. After a fix, remember that cards are cached for several days; adding a query string to the shared address forces a fresh fetch.