Skip to content
SCREENSHOT · USE CASE

Social Card Generator API

Produce per-platform social cards — X, LinkedIn, Facebook, Slack unfurls — from one HTML template rendered at each platform's aspect ratio.

Produce per-platform social cards — X, LinkedIn, Facebook, Slack unfurls — from one HTML template rendered at each platform's aspect ratio.

Why render from HTML at all

Every network crops differently, so a single 1200×630 export gets letterboxed somewhere. Rendering from HTML makes the variants nearly free: keep one template, pass the platform as a query parameter, and capture it at each viewport. The alternative — exporting a design file per platform per post — is the step that quietly stops happening around month two.

The request

POSTscreenshot.sh
curl https://api.renderkit.tech/v1/screenshot \
  -H "x-api-key: $RENDERKIT_API_KEY" \
  -H "content-type: application/json" \
  -d '{ "url": "https://example.com", "full_page": true, "block_ads": true }'

Options that matter here

  • One template, many viewports: 1200×630, 1200×1200, 1600×900
  • Query-parameter props, so the same route renders any post
  • Real CSS layout, so long titles wrap instead of overflowing the card
  • Signed URLs you can hand straight to a meta tag or a scheduling tool

More

Full screenshot API reference · API docs · compare RenderKit vs ScreenshotOne.

Common questions

Yes — call /v1/screenshot once per size against the same HTML route, varying only the viewport. CSS handles the reflow, so you maintain one template rather than one per platform.

Yes. Both read standard og:image tags, so pointing that tag at the rendered image is all that is required — there is no platform-specific format.

RenderKit starts at $9/mo with 500 free renders, and screenshots, PDFs, and markdown extraction all draw from the same meter — there is no separate per-primitive plan.

Ship your first render in 60 seconds.

500 free renders to start. No card. Cancel by ignoring it.

Get your free key$npm i renderkit-sdk