Validate your Twitter card. See how it renders on X.

• summary — small square image on the left, title and description on the right. The default if twitter:card is missing.
• summary_large_image — full-width image above the title. This is what most sites want — it takes up more space in the timeline and gets more clicks.
• player — embeds an iframe (for video or audio). Requirestwitter:player, twitter:player:width, andtwitter:player:height.
• app — renders an app-install card with App Store / Play Store links. Rarely used since Twitter removed the old app card rendering.

You don't need to duplicate every field. X will use og:title iftwitter:title isn't set, og:description iftwitter:description isn't set, and og:image iftwitter:image isn't set.

The exception is twitter:card — there's no OG equivalent, so if you don't set it, X defaults to summary (the small card).

If you want different copy on X vs. Facebook/LinkedIn, set both og:title andtwitter:title separately. Otherwise, just set the og:* tags and add twitter:card.

• Images must be less than 5 MB.
• summary_large_image — minimum 300×157, recommended 1200×630. Aspect ratio 2:1.
• summary — minimum 144×144. Displayed as a square crop.
• Supported formats: JPG, PNG, WebP, GIF (first frame only).
• Images must be served over HTTPS.
• X caches images aggressively — changing the URL (or adding a query param) forces a re-fetch.

X caches card data for up to 7 days. If you updated your tags but the old card still shows:

1. Append a cache-buster query parameter to the URL (e.g. ?v=2).
2. Post the URL with ?v=2 on X — it will fetch fresh metadata.
3. Once the new card renders, you can remove the query parameter.

At scale, managing cache invalidation across thousands of pages is what Linkraft automates.