What is TemplatesOn?

This is the first post I'm writing about TemplatesOn, so let me start at the beginning: what it is and why it exists. It began with a chore that kept showing up in my week. Open the design tool. Find last week's file. Change one headline. Swap one photo. Export, rename, download. Then do it again tomorrow with slightly different words.

The design never really changed. Only the content did. But every single time I had to reopen the whole machine — Canva, Figma, Photoshop — just to move a few characters around. TemplatesOn is what I built to kill that loop. In short: it lets you design a template once, then send it text and images to get finished, on-brand graphics and PDFs back automatically.

The idea in one line

Design a template once, then send it text and images to get finished, on-brand graphics and PDFs back — automatically, forever.

That’s the whole thing. You build the layout one time, mark the parts that change as fields, and from then on you never reopen the design software to change a headline or swap an image. The design stays locked. Only the content moves.

The phrase I kept coming back to while building it: one template powers a thousand posts.

How it actually works

Three steps, and that’s deliberate.

1. Build the template once. Lay out your post, poster, or document and mark the dynamic parts — a title, a price, a photo — as fields. Under the hood a template is just an SVG with those fields wired in.
2. Send the new content. Type the new text, drop in the image. From a form, a spreadsheet, your own app, or an automation tool — whatever fits how you already work.
3. Get the finished file. A ready-to-post PNG or a PDF comes back in seconds. On-brand every time, zero design work.

That’s it. Send field values, the platform renders the SVG to a PNG or PDF on demand, you get a file back.

Who keeps reaching for it

The headline audience is simple: people who post a lot. Anyone remaking the same graphic with new words.

• Social posts — daily specials, quotes, announcements. Same layout, new words, every day.
• Event graphics — a new flyer for every show without rebuilding the design.
• Product cards — new drops and price changes turned into on-brand images instantly.
• Certificates and PDFs — personalised documents for every name on a list, generated in bulk.
• Listings — property, job, or marketplace cards that stay consistent at any volume.
• Reports — branded summaries and receipts built straight from your data.

It speaks to your stack

This is the part I cared about most as a builder. TemplatesOn is meant to be triggered from wherever you already are, not from yet another tab you have to remember to open.

• REST API — call it directly at https://templateson.com/api/v1 with an API key. It returns binary PNG/PDF or JSON.
• Zapier — live, published app.
• n8n and Make — native modules rolling out; HTTP nodes work today.
• AI agents — native support via MCP.

Generating an image is one HTTP call with an X-API-Key header. That means a spreadsheet, a cron job, or a five-line script can all produce finished graphics without a human ever opening a canvas.

Giving an AI agent the ability to design

The newest part, and the one I’m most excited about: TemplatesOn has native AI-agent support. No human in the loop required.

There’s an MCP server you connect once at templateson.com/api/mcp. It works with Claude, Cursor, Windsurf, and any MCP-compatible host, and it hands the agent five ready-to-use tools:

• list_templates — discover available templates, yours plus public ones
• get_template_fields — inspect a template’s fields before rendering
• render_image — render any template to PNG, returned inline
• render_pdf — same, as a PDF
• generate_and_save_template — describe a design in plain language and have it saved, ready to render

There’s also a public, no-auth agent manifest at templateson.com/api/agents. An agent fetches it once and gets a complete description of every endpoint, parameter, and example — then acts on its own.

Quick honesty note: the describe-a-design-in-words generation feature is still behind a flag and paused in production, so I treat AI generation as roadmap. The rendering API and the MCP rendering tools are the solid, live core today.

Don’t start from a blank canvas

There’s a public template gallery of community templates you can browse. Clone any public one in a single click, then wire it to your own data. It takes the blank-canvas problem off the table — you don’t have to design from scratch to get value on day one.

Meet Nimo

TemplatesOn has a little astronaut mascot named Nimo who shows up around the site as a guide. His three-line pitch is honestly a tidy summary of the whole product:

• Design once, reuse forever.
• I speak to your stack — API, n8n, Make, Zapier, and AI agents.
• Consistent every time, even when the data changes on every render.

Try it

It’s free to start, no credit card, set up in a couple of minutes. Plans scale on volume, not features — every plan works the same way: build the template, send the data, get the files.

If you post a lot, or you’re wiring up automations and agents that need finished graphics, take a look at templateson.com. Build it once. Generate forever.