Blog
Notes from the press floor.
How teams turn one design into thousands of finished images — dynamic previews, bulk runs, localization, and agents that render their own work.
- ·Playbook5 min →
QR codes that belong on the design, not stickered over it
Most bulk QR workflows produce a naked code you still have to place on artwork. Put the code inside the template and the finished asset comes out in one render.
- ·Playbook5 min →
A thumbnail for every video, without opening a design tool
Channels win on consistency. A templated 1280×720 with a variable title and photo turns thumbnail production from a per-video chore into a render.
- ·Engineering5 min →
PNG, JPEG, WebP or AVIF: picking formats for generated images
The right answer changes with the destination — an ad network, an email, a web page, a printer. The wrong answer is baking one choice into the pipeline.
- ·Playbook5 min →
Automating image generation with Zapier and Make
If your data already flows through Zapier or Make, finished artwork is one HTTP step away — no designer, no deploy, no code.
- ·Engineering6 min →
Dynamic Open Graph images, without a screenshot service
Every shared link deserves its own preview card. Here is how to render them on demand from one design — no Puppeteer, no screenshot farm.
- ·Playbook5 min →
From a spreadsheet to ten thousand finished images
A product catalogue, an event roster, a list of winners — if it fits in a spreadsheet, it can come out the other side as finished artwork.
- ·Playbook5 min →
One design, every language: localized creative at scale
Translation is usually where creative production stalls. It does not have to be a separate project — it can be a parameter on the render.
- ·Engineering6 min →
Giving an AI agent its own printing press (via MCP)
Agents are good at deciding what to make. Give them a deterministic press and a free preview, and they can make it — and check their own work before spending.