Free tools

Twitter/X Card Generator & Preview

Set the card type, fill in your title, description, image URL, and site handle, then get a live X card preview and the ready-to-paste twitter: meta tags. Free, no sign-up.

Card type

Live preview

No image set

Your title

Approximates the X card layout. Actual rendering may vary by client.

Generated meta tags

<meta name="twitter:card" content="summary_large_image">

Paste inside the <head> of your page. Check a live URL with the Open Graph Checker.

Free, no sign-up. Live preview updates as you type.

01 ·  How it works

01

Choose your card type

Pick summary_large_image for a big edge-to-edge photo above the text, or summary for a small square thumbnail beside it. Most blog posts and landing pages want summary_large_image.

02

Fill in the fields

Enter your title, description, image URL, and optional site and creator handles. The live preview updates as you type so you can see exactly how your card will look on X.

03

Copy and paste

Hit Copy and paste the generated tags inside the &lt;head&gt; of your page. Then paste your live URL into an X draft post to confirm the card resolves correctly.

What is a Twitter card?

A Twitter card (now an X card) is a rich link preview that appears when someone shares a URL on X. Instead of a bare link, X reads a set of <code>twitter:</code> meta tags from your page and displays a formatted card with a title, description, and image. The result looks more like a news article preview than a plain URL, which drives significantly more clicks.

The system works by X's crawler fetching your page when a link is posted, reading the tags from the server-rendered <code>&lt;head&gt;</code>, and caching the result for future shares. This tool generates the correct tags and shows a live preview so you can confirm everything looks right before adding them to your site.

Twitter card types: summary vs summary_large_image

There are two card types in common use. <strong>summary</strong> shows a small square thumbnail to the left of the title and description. <strong>summary_large_image</strong> shows a large, edge-to-edge image above the title and description, taking up much more visual space in the feed.

For most content — blog posts, landing pages, product pages, and documentation — summary_large_image is the stronger choice. It commands more attention in a scrolling feed and gives you space to communicate your brand visually. Use summary for pages where you have a small logo or icon-sized image and the text carries the weight.

The complete Twitter card meta tags reference

All Twitter card tags use the <code>name</code> attribute, not <code>property</code> like Open Graph. They sit in the <code>&lt;head&gt;</code> of your page. Here are all the tags and what they control:

  • <strong>twitter:card</strong> (required): the card layout. Set to <code>summary</code> or <code>summary_large_image</code>.
  • <strong>twitter:title</strong>: the card headline. Falls back to <code>og:title</code> if omitted. Keep it under 70 characters.
  • <strong>twitter:description</strong>: the card summary text. Falls back to <code>og:description</code> if omitted.
  • <strong>twitter:image</strong>: the card image. Must be an absolute HTTPS URL. Falls back to <code>og:image</code> if omitted.
  • <strong>twitter:image:alt</strong>: alternative text for the image, for accessibility and screen readers.
  • <strong>twitter:site</strong>: the @handle of the website or brand, for example <code>@screenshotrender</code>. Optional but recommended.
  • <strong>twitter:creator</strong>: the @handle of the individual author. Optional; mainly used for article bylines.

Twitter card image size and requirements

The image requirements differ by card type. For <strong>summary_large_image</strong>, the recommended size is <strong>1200x628 pixels</strong> (roughly a 1.91:1 ratio). The minimum is 280x150 and the maximum file size is 5 MB. For <strong>summary</strong>, the image is cropped to a square, so center your subject. Minimum size is 144x144 px.

All images must be served over HTTPS. Supported formats are PNG, JPG, WebP, and GIF (static only for cards). If the image URL redirects, X may not follow it correctly, so use a direct final URL.

If you need a correctly sized 1200x628 card image for every page, ScreenshotRender can render one from a URL or an HTML template on demand, returning a PNG you can serve directly as your <code>twitter:image</code>.

How to add Twitter cards to your website

Add the tags inside the <code>&lt;head&gt;</code> element of each page. A minimal setup for a blog post looks like this:

  • <code>&lt;meta name="twitter:card" content="summary_large_image"&gt;</code>
  • <code>&lt;meta name="twitter:title" content="Your post title"&gt;</code>
  • <code>&lt;meta name="twitter:description" content="A short summary"&gt;</code>
  • <code>&lt;meta name="twitter:image" content="https://yoursite.com/og.png"&gt;</code>
  • <code>&lt;meta name="twitter:site" content="@yourhandle"&gt;</code>

How to preview and test your Twitter card

The official Twitter Card Validator was shut down in 2022. The current way to preview a card is to paste the URL into a draft post on X (you do not need to publish it) and see how it unfurls. X reads the live page each time, so changes you make to the tags are reflected immediately in a fresh draft.

Use the generator above to preview the card before your page is even live, so you can confirm title truncation, description, and image composition look right. Once the page is published with the tags, paste the live URL in an X draft to do a final check.

Twitter card validator: what to check

A twitter: tag audit covers more than just whether the tags are present. Here is a checklist of what to verify:

  • <strong>twitter:card</strong> is present, spelled correctly, and set to a valid value.
  • <strong>twitter:image</strong> (or <code>og:image</code> as fallback) is an absolute HTTPS URL that resolves to a real image.
  • Image dimensions meet the minimums for the chosen card type (1200x628 is the safe target for summary_large_image).
  • Image file size is under 5 MB.
  • <strong>twitter:title</strong> (or <code>og:title</code>) is present and not truncating at an awkward point.
  • The tags are in the server-rendered HTML source, not inserted by client-side JavaScript after page load.

Twitter cards vs Open Graph tags

Open Graph (<code>og:</code>) and Twitter cards (<code>twitter:</code>) are two overlapping standards. Open Graph is the broader one, read by Facebook, LinkedIn, Slack, Discord, WhatsApp, and many others. Twitter cards are X's own format layered on top.

The key relationship: X reads <code>og:title</code>, <code>og:description</code>, and <code>og:image</code> as fallbacks when the corresponding <code>twitter:</code> tags are missing. If you already have full Open Graph tags on your page, the only new tag you need is <code>twitter:card</code> to specify the layout.

You can audit the full set of tags on any live URL with the <a href="/tools/open-graph-preview" class="text-orange-600 hover:underline font-medium">Open Graph Preview &amp; Checker</a>, which shows how both OG and twitter: tags resolve and flags anything missing.

How to fix a broken Twitter card

If your card is not appearing or is showing incorrectly, work through these common causes in order:

  • <strong>Missing twitter:card</strong>: X will not show any card without this tag. Add it even if you have full OG tags.
  • <strong>Non-HTTPS image</strong>: X rejects images served over HTTP. Make sure the URL starts with <code>https://</code>.
  • <strong>Image too large</strong>: files over 5 MB are silently ignored. Compress and re-test.
  • <strong>Image URL redirects</strong>: use the direct final URL, not one that 301s to the real image.
  • <strong>Tags added by JavaScript</strong>: X reads the raw server-rendered HTML. Tags injected by a client-side script after page load are not picked up.
  • <strong>Stale cache</strong>: after fixing the tags, paste the URL in a fresh draft tweet. X re-fetches live pages for draft previews, so you should see the update right away.

How to generate a Twitter card image with ScreenshotRender

Your <code>twitter:image</code> should be a pixel-perfect 1200x628 image that represents the page content. One approach is to render a screenshot of the page itself at those dimensions. Another is to render a custom HTML template with the title, description, and brand colors baked in, giving every page a unique social image.

ScreenshotRender does both: point its API at a URL and it returns a PNG at whatever viewport size you specify, which you can serve directly as your <code>twitter:image</code>. The <a href="/tools/og-image-generator" class="text-orange-600 hover:underline font-medium">OG Image Generator</a> tool on this site also lets you design and download a 1200x630 card image for free, which you can then host and reference in your twitter:image tag.

More free tools

FAQ

Common questions

Everything about the Twitter/X Card Generator & Preview.

Common questions

A Twitter card is a rich link preview that appears when a URL is shared on X (formerly Twitter). Instead of a plain link, X reads twitter: meta tags from your page and displays a formatted card with a title, description, and image. There are two common layouts: summary (small square thumbnail beside the text) and summary_large_image (large image above the text).

The two types in active use are summary and summary_large_image. Summary shows a small square thumbnail to the left of the title and description, and works well for news, short updates, or brand logos. Summary_large_image shows a large, edge-to-edge image above the text and is best for articles, landing pages, and image-forward content. App and player cards exist for app installs and video embeds but are rarely needed for standard web pages.

summary_large_image is the value to set for twitter:card when you want a large, full-width image to appear above your title and description on X. It commands more attention in a feed than the small-thumbnail summary layout. Use it whenever you have a good 1200x628 image and want maximum visual impact, which covers most blog posts, marketing pages, and product pages.

A summary card is triggered by setting twitter:card to summary. It shows a small square thumbnail image to the left of the title and description. It is compact and works well for news articles, short posts, and pages where a logo or icon represents the content. For most image-forward pages, summary_large_image is the better choice.

For summary_large_image the recommended size is 1200x628 pixels at roughly a 1.91:1 aspect ratio, with a maximum file size of 5 MB. For the summary card the image is cropped to a square, so the minimum is 144x144 px. All images must be served over HTTPS. Supported formats are PNG, JPG, WebP, and static GIF. You can generate a correctly sized 1200x628 image from any URL using ScreenshotRender.

The only truly required tag is twitter:card, which sets the card type. Without it X will not show a card at all. In practice you also need twitter:title and twitter:image to display useful content, though X falls back to og:title and og:image if the twitter: versions are absent. Add twitter:description for the summary text and twitter:site for your brand handle. This generator produces all of them at once.

Mostly no, but there is one exception. X reads og:title, og:description, and og:image as fallbacks when the twitter: equivalents are absent. But you still need twitter:card to specify the layout. Without it, X may not show any card. So the minimum addition to a page that already has full Open Graph tags is one line: a meta tag with name twitter:card and content summary_large_image.

twitter:site is the @handle of the website or publisher, for example @screenshotrender. It appears in some card layouts and is used by X for analytics attribution. It does not affect whether a card appears, but it is good practice to include it for any page you want associated with your brand on X.

twitter:creator is the @handle of the individual author of the content. It matters most on article pages where you want byline attribution. If you do not have a per-author handle or the page is not author-specific, you can omit this tag or set it to the same value as twitter:site.

Use the generator above to preview the card before your page is live. Once the page is published with the tags, paste the live URL into a draft post on X to see exactly how the card unfurls. You do not need to publish the draft. X dropped its dedicated Card Validator in 2022, so a draft post or this generator is the best option available.

Check in this order: twitter:card is present and spelled correctly; twitter:image is an absolute HTTPS URL that resolves; the image is under 5 MB; your page returns HTTP 200; and the tags are in the server-rendered HTML source, not added by JavaScript after page load. X reads the raw HTML from the server, so any tag injected by a client-side script after the initial render is invisible to its crawler.

The most common reasons are: the image URL is not HTTPS, the file exceeds 5 MB, the URL returns a 404 or redirect, or the image dimensions are below the minimum for the chosen card type. Also confirm the URL in twitter:image or og:image is absolute, not a relative path such as /images/og.png. After fixing, paste the URL in a fresh X draft to confirm the updated image loads.

Yes. Despite the rebrand from Twitter to X, the twitter: meta tag prefix and the card system remain fully active as of 2026. You do not need to rename existing tags to x: or anything else. The same tags, the same card types, and the same image requirements all continue to work unchanged.

Install an SEO plugin such as Yoast SEO, Rank Math, or The SEO Framework. All three have a Social section where you can enable Twitter cards and set the default card type. They generate the correct twitter: tags automatically from your post title, excerpt, and featured image. You can also set per-post overrides from the post editor.

A Twitter card generator is a tool where you fill in your page details and it produces the HTML meta tag snippet ready to paste into your site. This generator also shows a live preview so you can see how the card will look in a feed before you add the tags. It covers both card types, the image, title, description, and site handle in one place.

Yes. ScreenshotRender captures a screenshot of any URL at a custom viewport size and returns a PNG. Set the viewport to 1200x628 and point the resulting image URL at twitter:image and og:image. You can also render an HTML template designed specifically for social cards, giving every page a unique, on-brand image without designing each one manually.

[ CAPTURE ][ RENDER ][ API ]

Get Started

Need to generate og:images at scale?

ScreenshotRender renders pixel-perfect 1200×630 social images from any URL or HTML template. Start free with 100 screenshots, no credit card.

Want to integrate via API? Get your key here