Private beta— the API is live and free to use. Paid plans are coming soon.
RenderHelm.

URL or HTML in → pixels out

Render any page to a screenshot, PDF, or social image.

One key, three endpoints, and your first render in under a minute. Five hundred a month are on the house — no watermark, no card.

POST /v1/screenshotPOST /v1/pdfPOST /v1/renderGET /v1/og/blog-header.png

A title card reading “RenderHelm — screenshot, PDF, social image,” produced by the RenderHelm API.
LIVE made by RenderHelm · HTML → PNG · 1200×630

          

Real renders, straight from the live API — no key needed to look.

01 / API

Two ways in: capture a live page, or compose your own.

Capture points RenderHelm at a URL and hands back a screenshot or a PDF of the page. Compose takes your own HTML — or a reusable template — and renders it to an image, a PDF, or a social card. One key covers all four, and on a paid plan identical requests come back from your cache for free.

Capture · Screenshot

Pixel-perfect captures

Full-page or viewport screenshots of any URL — PNG or JPEG, any device size.

POST /v1/screenshot
Capture · PDF

Any page to a PDF

Turn a live page into a clean, paginated document — invoices, receipts, reports — in one call.

POST /v1/pdf
Compose · Render

Your HTML or a template

Send HTML — or a template with {{ vars }} and {% for %} — and get an image or PDF back.

POST /v1/render
Compose · Open Graph

Signed social images

Reusable Open Graph (OG) templates you embed with one signed link — no secret in the URL.

GET /v1/og/blog-header.png
02 / QUICKSTART

Your first render in under a minute.

Send a URL with your key. Get image bytes back. That's it.

# a screenshot of any page, as image/png
curl -X POST https://renderhelm.keelhelm.com/v1/screenshot \
  -H "Authorization: Bearer sk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","full_page":true}' \
  --output shot.png
03 / WHY RENDERHELM

Made to get out of your way.

A free tier you can actually build on

Five hundred renders a month, free — not the usual fifty. No watermark, no credit card, enough headroom to take something real to launch.

Transparent pricing

Flat monthly plans and an overage you opt into — never a surprise bill. The number on the pricing page is the number you pay: no per-seat math, no metered dashboard to decode, no asterisks. On paid plans, repeat renders come back from your cache for free.

A cache you control

On paid plans every result is fingerprinted and kept in your own cache — ask for the same render again and it's back in milliseconds, free and uncounted. Pin the ones you never want to lose; the rest roll off on their own.

Drops into any stack

It's plain HTTP, with copy-and-go examples for curl, Next.js, and Astro. Social images embed with one signed link — no SDK, no build step, no lock-in.

04 / PRICING

Start free. Move up only when you outgrow it.

Free covers 500 renders a month. Paid plans add PDF and Compose renders, higher limits and burst, and — on Pro and Scale — private CSS for your brand styles.

Free
$0
500 renders / mo
  • Screenshots + social images
  • 5/min · 50/day
  • No render cache
  • No watermark
Get a key
Starter
$9/mo
5,000 renders / mo
  • Adds PDF + full-page
  • 30/min
  • 50 MB render cache
  • Optional overage
Join the waitlist
Pro
$29/mo
20,000 renders / mo
  • Everything in Starter
  • 60/min
  • 250 MB cache · Private CSS
  • Priority rendering
Join the waitlist
Scale
$79/mo
60,000 renders / mo
  • Everything in Pro
  • 120/min
  • 500 MB cache · Private CSS
  • Highest burst
Join the waitlist
05 / FAQ

Good questions, straight answers.

What does RenderHelm do?

It turns any URL or raw HTML into a screenshot, PDF, or Open Graph image with a single API call. One key, three endpoints, nothing to install.

Is the free tier really free?

Completely. Five hundred renders a month with an email-verified key — no credit card, and nothing watermarked on the way out.

How does pricing work?

Three flat monthly plans — $9, $29, and $79 — plus a metered overage you can switch on if you want it. Repeat renders served from cache are never counted.

What counts as a render?

A screenshot or social image counts as one; a full-page capture or a PDF counts as two. Anything answered from cache is free.