Renderwolf · Rendering API

Pixels on demand

Screenshots, PDFs and social images from a URL or raw HTML - one API, served by a warm Chromium fleet on our own UK hardware.

In development

Being built in the open, launching soon

The API, dashboard and n8n node are under construction right now. Want early access, or an opinion on what the API should do? We'd genuinely like to hear it.

Request early access

The API

Three jobs, one endpoint away

Everything is the same engine underneath: send HTML or a URL, get pixels or pages back, fast.

  • Screenshot API

    Pixel-perfect captures of any URL or raw HTML, from a Chromium fleet that is already warmed up.

    • Full-page, viewport or element-by-selector
    • Device presets, dark mode & custom viewports
    • PNG, JPEG or WebP out
    • Ad, cookie-banner & tracker blocking
  • PDF API

    Invoices, reports and documents from the same HTML and CSS you already write.

    • URL or raw HTML in, print-quality PDF out
    • Page sizes, margins & landscape
    • Header & footer templates
    • Full background & web-font rendering
  • Image API

    Templated social and OG images, defined in code - not a drag-and-drop editor.

    • HTML/CSS templates with variables
    • Store once, render with fresh data every time
    • Signed URLs drop straight into og:image tags
    • Edge-cached, so repeat fetches are free

Why Renderwolf

Small API, strong opinions

  • No cold starts

    The Chromium fleet is always warm. Renders start in milliseconds, not the 20-second cold boots some screenshot APIs are known for.

  • Embed-ready URLs

    Signed GET URLs mean a render can live directly in an og:image tag, an email or an n8n flow - no server-side glue required.

  • Hard caps, honest bills

    Plans have fixed render quotas. When you hit the cap we tell you - we never silently bill overage.

  • Our own UK metal

    Renderwolf runs on Ironfang's own EPYC and NVMe infrastructure - which is why generous quotas don't need venture-scale prices.

Pricing

Simple plans, hard caps

Launch pricing - locked in for early-access users. Every plan is self-service and cancels in one click.

  • Free

    $0/month

    100 renders/mo

    Kick the tyres. No card required.

  • Hobby

    $9/month

    5,000 renders/mo

    Side projects and automation flows.

  • Scale

    $49/month

    50,000 renders/mo

    High-volume rendering, still hard-capped.

PDF renders count as two. Prices exclude VAT where applicable. Hitting a cap pauses renders - it never bills overage.

Questions

The short answers

When does Renderwolf launch?
It's in active development now. The API, dashboard and n8n node are being built together and will launch together. Ask for early access and you'll be first through the door.
What counts as a render?
One successful screenshot or image is one render. PDFs are heavier, so they count as two. Failed renders don't count, and repeated identical requests within the cache window are served from cache without touching your quota.
What happens when I hit my cap?
We email you at 80%, and at 100% the API returns a clear error instead of quietly billing you. Upgrade in the dashboard whenever you like - it takes effect immediately.
Where does it run?
On Ironfang's own hardware in the UK, behind Cloudflare's global edge. Rendered assets are cached at the edge, so they're fast everywhere.
Will it work with n8n, Make or Zapier?
A verified n8n community node ships at launch - search "Renderwolf" in the editor. Make and Zapier integrations follow. The API is plain HTTPS + JSON, so anything that can make a request can use it today.

Want in early?

Early-access users get launch pricing for life and a direct line to the people building it.

Request early access