Social and share cards
One template, an image per page, with the title and author as variables.
Design once. Generate thousands from data
Store a layout in HTML and CSS, then render it with different variables on every request. Branded images from the data you already hold, without running a rendering worker or rebuilding the design in an image library.
Create a free accountRead the API docs
- 250 free templated images each month
- Stored templates
- Verified QR codes included
- UK-operated infrastructure
One template
The design belongs in one place
Generating images from data usually means one of two bad options: rebuild the layout in a canvas or image library, where fonts and wrapping fight you, or run your own headless browser and keep it alive between launches.
Ironfang Render stores the HTML and CSS and renders it with the variables you send. Change the stored template and every future image follows, with no deployment and nothing to invalidate.
POST /render/v1/image/og-card
Authorization: Bearer if_live_...
{
"vars": {
"title": "Why we own our hardware",
"author": "Ironfang"
},
"format": "png"
}
200 image/pngCapabilities
A design system, not a drawing API
Everything you would expect from HTML, with the storage and substitution that turn one design into many images.
Design in HTML and CSS
Use the layout language you already know, with the fonts, gradients and grid you would use anywhere else. No canvas API, no image library DSL.
Stored templates
Save the design once with placeholders, then render it with different variables per request. The design lives in one place rather than in every call site.
Change the design, not the code
Update the stored template and every future image follows. No deployment, and nothing to purge, because the next render is the new design.
Verified QR codes inside
Send a qr object and the code is generated, checked for scannability and composited into the layout as a variable. QR codes add nothing to what the image counts.
Signed URLs
Mint a URL that renders the template on demand, so the image exists at a URL without your application generating, storing or serving it.
PNG, JPEG or WebP
Choose the format per request from one template, on warm Chromium that Ironfang operates in the UK. Cache hits count nothing, and failed renders are never charged.
Use cases
One design, many images
Anywhere the layout is fixed and the content changes, which is most generated imagery.
Certificates and badges
Personalise per recipient and composite a verified QR code for checking it later.
Product and listing graphics
Generate a branded image per SKU or listing from the data you already hold.
Personalised marketing images
Render a variant per recipient or per campaign without a designer in the loop for each one.
Automated report imagery
Turn a weekly number into a branded graphic for the digest, generated when the digest is built.
Ticket and pass artwork
Combine booking data and a scan-verified code into a single image for the wallet or the email.
Generating Open Graph images?
Social cards are the most common use of this API, and they have their own markup and their own signed-URL flow. There is a page for exactly that job.
Pricing
Priced per generated image
Each image rendered from a template counts once. QR codes inside it add nothing, a failed render counts nothing, and cache hits count nothing. Every account has a free allowance each month, with no card required. Past it, Pay as you go charges the rates below, within the monthly usage limit you set. Prices exclude VAT.
Templated images
Each image rendered from a template.
250 templated images free each month
| Paid units after the free allowance | Rate per 1,000 |
|---|---|
| First 10,000 | £1.00 |
| Next 90,000 | £0.70 |
| Next 900,000 | £0.50 |
| Above 1,000,000 | £0.40 |
Questions
Before you integrate
The details that decide whether this fits, without reading the whole reference first.
- How do templates work?
- You store HTML and CSS once with placeholders in it. Each render posts the variables for that image and gets the bytes back, rendered at the template width and height you defined.
- Can I change the design without changing my application?
- Yes, and it is the point of storing the template. Update the stored HTML and every future render uses it, with no deployment and no change to the code that requests images.
- What formats can I get?
- PNG, JPEG or WebP per request, so the same template can serve a lossless asset in one place and a small one in another.
- Can I include a QR code in the image?
- Yes. Send a qr object with the render and each code is generated, verified for scannability and injected as a variable, so it is composited into the design. QR codes add nothing to what the image counts.
- Do I need to store the finished images?
- Only if you want to. A signed render URL renders on demand at the URL itself, so you can put it straight in a page or an email without generating and hosting the file first.
- Can I render one-off HTML without storing a template?
- Yes. The screenshot endpoint takes HTML directly instead of a URL, which suits a layout that changes every time. Stored templates suit the same design rendered many times.
- What does an image cost?
- Each generated image counts once against the templated image meter, which has a free allowance every month; the rates are under Pricing on this page. Cache hits count nothing, a failed render counts nothing, and paid work that would pass the monthly usage limit you set is refused before it starts.
Less to operate. More to ship.
Render your first template
Create an account, store one design and send the variables. Every account has free templated images each month.
250 free templated images each month, no card required, and no charge for failed renders.