Write one HTML template and let anything fill it — your code, a spreadsheet, a webhook, an agent. Out comes PNG, JPG, PDF, GIF or MP4.
Nobody opened a design tool. Here's a slice of what came out.
5,000 rendered · 4m 12s · 0 failed
One template and a spreadsheet did all of that.
Then anything that can supply those values produces a file. Same template, same contract, whoever is calling.
The template you write
<div class="badge">
<img src={{photo}}>
<h1>{{name}}</h1>
<p>{{role}}</p>
</div>Plain HTML and CSS — flexbox, Google Fonts, anything you already know. No proprietary editor, no design file to keep in sync.
The contract it declares
Typed and validated, so a bad row fails before it renders.
POST a row of JSON and get a URL back. Most renders arrive this way.
POST /v1/render 
Upload a CSV, map columns to variables. Every row renders.
Point any service at a URL. Event in, file out, unattended.
Three fields and a render button. No code anywhere.
Every other caller fills a contract someone already wrote. An agent can write the template first, read back the variables, then render it — start to finish, unattended.
How that works ↓
A video template declares variables exactly like an image one, and the same five callers fill them. An MP4 comes back instead of a PNG.
Your year at Northwind
Priya shipped 1,284 times.
More than 96% of the team. Nice one.
Total ships
1,284
Every one of them, across the year.
Percentile
Top 4%.
Nice one, Priya.
The row that filled it
rendered 11.4s · 1080p · 15s
No timeline was opened to make this one.
Drag scenes, bind any layer to a variable.
Scenes as data, kept in version control.
Describe the film. It writes the template and declares the variables.
If it can do the film, the PNG is not the hard part.
The file arrives as four different problems, depending on what triggers it. All four are the same render.
01 One per user
Wrapped-style recaps, milestone cards, streaks, certificates. Every product with users gets asked for this, usually by a founder in December.
consumer apps · fitness · learning · fintech · communities · games
02 One per item
An OG image for every listing, product, property and profile — regenerated when the data changes, not when someone remembers.
marketplaces · e-commerce · real estate · job boards · travel · publishers
03 One per period
Statements, invoices, weekly digests, board reports. The output isn't a dashboard — it's a thing someone forwards, files or prints.
fintech · analytics · billing · agencies · ops teams
04 One per event
Agents and pipelines that have to emit something real — a PDF, an image, a deck — not another block of text.
AI products · automation builders · internal tooling
Four problems. One integration.
Three ways in. Pick whichever already matches your stack.
npm i @pictify/sdk
pip install pictify
POST /v1/render { template, variables } → https://media.pictify.io/…Official Node and Python SDKs, so you're not writing a fetch wrapper on day one. Or plain REST from anything that sends JSON.
Drop a render step into a flow you've already built.
npm i @pictify/mcp-server Four tools. Enough for an agent to author a template and run it.
One API key covers all three.
Pictify Campaigns · private pilot
For customer success and lifecycle teams who want to show each customer what they got this month — without a designer, and sending from the tool they already use.
| # | Account ID | Company | Workflows | Hours saved |
|---|---|---|---|---|
| 42 | 00042 | Contoso Freight | 1,284 | 312.4 |
Email card
Contoso Freight
Sample data · up to 250 customers per send · you send from your own tool
Write one template, point something at it, and stop making files by hand.