To request a large-image preview when someone shares a page on X (formerly Twitter), put twitter:card with the exact value summary_large_image in that page’s HTML <head>. Add an absolute image URL and page-specific title and description; then check the metadata and image on the live page.
HTML tags for a large-image card
Add these tags inside the page’s <head>, replacing the sample text and image URL with values for the page being shared:
As an Amazon Associate I earn from qualifying purchases.
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="A useful page title">
<meta name="twitter:description" content="A concise description of this page.">
<meta name="twitter:image" content="https://example.com/images/page-preview.jpg">The value summary_large_image selects the large-image card layout. The image must be given as a complete, absolute URL, not a relative path such as /images/page-preview.jpg. Twitter Card examples use name="twitter:..." attributes; Open Graph tags use property="og:...".
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUse page-specific metadata for every URL you want to share. If you use a site template or content-management system, make sure it emits the relevant values for each page rather than repeating a generic image and description across the whole site.
Choose between Twitter-specific tags and Open Graph metadata
Twitter-specific tags give you direct control over the preview intended for X. Open Graph tags are a separate metadata convention commonly used for social previews. The SEO Framework says summary and large-image summary cards can fall back to corresponding Open Graph values for title, description, and image; this is secondary technical guidance, so verify what the live page actually produces. The SEO Framework’s Twitter Cards guidance describes that fallback.
- Use Twitter-specific fields when you want explicit X metadata or a different X image, title, or description from other platforms.
- Rely on Open Graph values as fallbacks when the same preview is appropriate everywhere and the page already has suitable
og:title,og:description, andog:imagetags. In that case, an explicittwitter:carddeclaration may be all you add, but confirm the resulting card rather than assuming the fallback works. - Avoid conflicting duplicate values across the two sets of tags until you have checked which image and text appear in the preview.
For the tag syntax and layout, see the secondary implementation guides from og-image.org and OpenGraphImage. They are not current first-party X specifications.
Check the page and image before sharing
- Inspect the page’s returned HTML. Confirm the card tags are in the document head and that the card value is exactly
summary_large_image. Look for malformed tags or duplicate metadata with competing values. - Open the image URL directly. Make sure it resolves to the intended image rather than an error, redirect loop, or unrelated content. The available guidance does not settle every current X fetch rule or access restriction, so direct reachability is a practical check, not a guarantee of platform acceptance.
- Check the rendered preview. Use an available card preview or validator if one is accessible, and compare its image and text with the tags you intended. Current official validator availability and the precise way to force a cached preview to refresh are not established by the available sources.
If a framework inserts metadata in the browser with JavaScript, inspect the HTML available to a crawler as well as the browser’s final DOM. A tag visible only after client-side rendering may not be present in the response a page fetcher sees.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesImage dimensions and platform limits: what is not settled
Do not treat commonly repeated image dimensions, file-size ceilings, or format lists as guaranteed X requirements without a current primary specification. The secondary sources disagree on recommended aspect ratios, including 1200×600 and 1200×630, and no current first-party X specification was available to settle the matter. Choose a clear image that suits the intended preview, then validate the actual result rather than relying on an unverified pixel target.
Troubleshoot a missing or incorrect image
- The preview is not using the large-image layout: check that
twitter:cardis present in the page head and its content is exactlysummary_large_image. - No image appears: confirm
twitter:imagecontains the intended absolute URL, load that URL directly, and inspect the page’s returned HTML for missing or malformed tags. - The wrong image appears: check for duplicate
twitter:imageorog:imagevalues and make them consistent unless you intentionally want different platform previews. - The text or image differs from what you set: inspect both Twitter-specific and Open Graph tags, since secondary guidance describes Open Graph fallback behavior for summary card fields.
- The browser shows tags but the preview does not: verify whether the tags are in the server-returned HTML, not only added after client-side JavaScript runs.
- A preview tool is unavailable or appears stale: try another accessible preview mechanism and recheck the live HTML and image URL. No cache lifetime or guaranteed cache-refresh procedure is established here.
Or skip the browser setup
If you need a screenshot of the page itself in addition to setting up its social metadata, ScreenshotNeo can return a PNG, JPEG, WebP, or PDF from one GET request. For the card image, still choose an image URL that is appropriate for your page’s metadata.
Example cURL request (replace the target URL and API key):
Quick Recap
Best Value
Rank #4
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for free.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
