Images for Twitter Cards

Generate Twitter link preview images for every page

Use one HCTI og:image pattern across your site. Each page supplies its own metadata, and HCTI keeps the matching Twitter image current without a separate image-generation request.

  • 1200 × 600 images for tweets
  • Updates when preview inputs change
  • No extra code per page

HCTI @example · 1h

New: dynamic preview images that stay in sync with every page.

Make every share look intentional

htmlcsstoimage.com

Make every share look intentional

Generate the right Twitter Card image from each page's metadata.

24 replies · 81 reposts · 406 likes

Built for fast timelines

Make the card carry context when the post stays short

Twitter Cards combine a compact post with a wide preview. Use the image and card title to explain the linked page without turning the post itself into a summary.

1

Launch threads

Give the main announcement a clear image that remains attached to reposts.

2

News and analysis

Pair current headlines with a preview created from the latest page content.

3

Developer updates

Make releases, documentation, and technical posts easy to distinguish.

Metadata recipe

Set up the Twitter image

Point twitter:image at the HCTI URL for the current path, then use hcti:selector on that page to choose the element HCTI captures.

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

<meta name="twitter:image" content="https://hcti.io/v1/og/{YOUR_DOMAIN_ID}/product-launch">

<meta property="hcti:selector" content="#social-card">

What if the Twitter preview does not update?

Check the page first

  • Confirm the metadata is in the page’s <head> before a crawler loads it.
  • Open the HCTI image URL directly and make sure it returns the expected image.
  • Remember that Twitter may keep its own cached preview after the image changes.

Allow the Twitter crawler

If your firewall filters bots, allow requests whose user agent contains Twitterbot.

Twitterbot/1.0
Read Twitter’s preview documentation

Preview your page on Twitter

See the image and text Twitter can use when someone shares your page.

Query parameters are ignored unless you’re signed in.

Public pages only

We’ll read the page’s link-preview tags and image. Some sites may block automated checks.

How it works

The public URL stays simple while HCTI reads the page, creates the image, and reuses it until the inputs change.

  1. Add one twitter:image pattern

    Use your HCTI domain ID and append the current page path. No API key or per-page image URL needs to be published.

  2. HCTI reads the page head

    On refresh, HCTI fetches the requested page and reads its hcti: screenshot options or html:tv: template values.

  3. Serve the matching image

    HCTI creates the image when the resolved screenshot or template inputs change, then caches and serves it to link-preview crawlers.

Fresh when it matters

Update previews without rendering on every share

HCTI checks page metadata separately from generating the image. Unchanged screenshot or template inputs reuse the existing render; changed inputs create the next image.

Controlled refreshes

Choose how often HCTI may check each page for updated meta tags. Origin cache headers and ETags can avoid unnecessary work.

Content-based reuse

HCTI hashes the resolved screenshot or template inputs so unchanged pages return the image that already exists.

Preview-aware sizing

Use one image everywhere, fit one render into recognized preview sizes, or render with a platform-specific viewport.

Ready for better link previews?

Give every page an image worth sharing

Add one stable OG image URL pattern, keep the supported meta tags on each page, and let HCTI handle rendering and reuse.