Independent publishing
Give essays, blogs, and newsletters a recognizable website card.
Website card images for Bluesky
Use one HCTI og:image pattern across your site. Each page supplies its own metadata, and HCTI keeps the matching Bluesky image current without a separate image-generation request.
HCTI @example.com · 2h
A small addition to your page head can keep every link card fresh.
htmlcsstoimage.com
One Open Graph image URL for every page
HCTI reads the page’s meta tags and returns the matching cached image.
12 replies · 38 reposts · 219 likes
A card for the open web
Bluesky website cards put the linked page directly beneath a short post. Use the image to establish the topic quickly without repeating the post text.
Give essays, blogs, and newsletters a recognizable website card.
Make changelogs and release posts easier to spot in a timeline.
Show the project, feature, or release instead of a generic repository image.
Metadata recipe
Point og:image at the HCTI URL for the current path, then use hcti:selector on that page to choose the element HCTI captures.
<meta property="og:image" content="https://hcti.io/v1/og/{YOUR_DOMAIN_ID}/product-launch">
<meta property="hcti:selector" content="#social-card">
<head> before a crawler loads it.If your firewall filters bots, allow requests whose user agent contains Bluesky Cardyb.
See the image and text Bluesky can use when someone shares your page.
How it works
The public URL stays simple while HCTI reads the page, creates the image, and reuses it until the inputs change.
Use your HCTI domain ID and append the current page path. No API key or per-page image URL needs to be published.
On refresh, HCTI fetches the requested page and reads its hcti: screenshot options or html:tv: template values.
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
HCTI checks page metadata separately from generating the image. Unchanged screenshot or template inputs reuse the existing render; changed inputs create the next image.
Choose how often HCTI may check each page for updated meta tags. Origin cache headers and ETags can avoid unnecessary work.
HCTI hashes the resolved screenshot or template inputs so unchanged pages return the image that already exists.
Use one image everywhere, fit one render into recognized preview sizes, or render with a platform-specific viewport.
Link preview platforms
The same Open Graph image URL can serve many crawlers. Explore focused guidance and recommended preview dimensions for common platforms.
Ready for better link previews?
Add one stable OG image URL pattern, keep the supported meta tags on each page, and let HCTI handle rendering and reuse.
Related features
Learn about related options for image and PDF generation, storage, security, and team access.