What is TemplatesOn?

This is the clean version as of July 2026: TemplatesOn is a way to turn reusable designs into generated files. You build a template once, mark the parts that change, and then send data to get finished images, PDFs, videos, carousels, certificates, reports, or social assets back automatically.

The original itch is still the same. I was tired of reopening Canva, Figma, or Photoshop just to change one headline, swap one photo, export the file, rename it, and do it again the next day. The design did not change. Only the content did.

TemplatesOn kills that loop. The layout stays locked. The data moves.

The idea in one line

Design a template once, then send it text, images, rows, links, or structured data to generate finished files automatically.

That can mean a single PNG, a PDF document, a multi-page PDF, a set of carousel slides, a bulk batch of personalized files, or an MP4 video. The workflow is the same: one reusable template, many outputs.

The phrase I still come back to is simple: one template powers a thousand files.

How it works

The core flow is deliberately small.

1. Build the template once. Lay out the invoice, certificate, social graphic, report, carousel, or document. Mark the dynamic parts as fields.
2. Send the data. It can come from the dashboard, a form, Zapier, n8n, Make, your backend, a spreadsheet, or an AI agent.
3. Get the finished output. The render engine fills the template and returns the file or delivers it where it needs to go.

Under the hood, templates are SVG-based layouts with dynamic text, image, repeat, conditional, QR, barcode, and verification directives. You do not need to care about that to use it, but it is why the same template can serve a lot of different workflows.

What it can do today

TemplatesOn started as image and PDF generation, but the current app is broader than that.

• Image and PDF renders - generate PNGs or PDFs from a saved template, or make a simple direct image without a template.
• Bulk rendering - send up to 1,000 records and get one file per record. It meters as one bulk job, not one request per row.
• Multi-page PDFs - design documents with multiple pages and render them as one stitched PDF.
• Carousels - render a multi-page template as a set of numbered slide images for social platforms.
• Video rendering - turn a template into an MP4, either as a slideshow or a motion render.
• Render destinations - send finished files to hosted storage, Google Drive, email, or a signed webhook instead of downloading and re-uploading them.
• Async webhooks - queue renders and let TemplatesOn call your webhook when the result is ready.
• Imports - bring in SVG, Figma frames, and Canva exports instead of rebuilding every design by hand.
• Custom fonts - upload the real brand typeface and use it in generated images and PDFs.
• Conditional and repeat fields - one invoice template can handle three line items or thirty, with sections that show only when the data says they should.
• QR codes, barcodes, and verification - generate tracked QR codes, standard barcodes, and public verification pages for certificates or documents.
• Free previews and versioning - preview while editing without spending render allowance, and roll a template back when a save goes wrong.
• OG images - use a stable TemplatesOn URL as a dynamic link-preview image that reflects the current params.

Where it fits

The best use cases are still the ones where the design repeats and the data changes.

• Invoices and receipts - order data in, finished PDF out.
• Certificates and personalized documents - one verified document per recipient, with public proof it is genuine.
• Social graphics and ads - product drops, sale posts, announcements, event flyers, and daily content at volume.
• Reports and summaries - branded output generated from fresh data, not copied into a design tool.
• Listings and catalogs - property cards, job posts, product images, or marketplace visuals that stay consistent.

How you connect to it

TemplatesOn is meant to run from the tools you already use, not from another tab you have to remember to open.

• REST API - call https://templateson.com/api/v1 with an API key. The API supports image, PDF, bulk, carousel, video, preview, template, key, and async render flows.
• Automation tools - Zapier is published, and the app has dedicated docs for n8n and Make. HTTP nodes work for anything the native helpers do not cover yet.
• Dashboard - manage templates, API keys, bulk renders, QR tracking, subscriptions, and profile settings from the app.
• AI agents - connect an MCP-compatible client to https://templateson.com/api/mcp and let the agent inspect templates and render real files.

The AI-agent layer

The current MCP server is more than a simple render wrapper. It gives an agent tools to discover templates, inspect fields, render outputs, read the template DSL, preview a generated design, create or update templates, bulk render, render carousels and videos, and manage template revisions.

The tool set currently includes list_templates, get_template_fields, render_image, render_pdf, get_dsl_schema, preview_template, create_template, update_template, bulk_render, render_carousel, render_video, list_revisions, and restore_revision.

That matters because an agent can do the whole practical flow: find the right template, learn what data it needs, generate or preview a layout, create or update the template if needed, render the final file, and roll back if a template revision goes wrong.

A useful boundary: TemplatesOn is the render layer. You bring the AI client and your own API key. TemplatesOn turns the agent's structured request into real output.

Pricing and limits

There is still a free start. The public pricing page now keeps the message simple: one render is one render, with no credit math. Paid plans add throughput and plan-gated capabilities such as bulk, video, destinations, MCP access, premium imports, custom fonts, QR/barcode/verification, carousels, and multi-page PDFs.

Some core authoring features are treated as the foundation rather than upsells: SVG import, conditional and repeat fields, template versioning, free preview renders, and OG images are available as core workflow pieces.

The simplest way to think about it

TemplatesOn is not another design tool you live inside. It is the rendering layer behind your design system, automations, app, or AI agent.

If you are manually exporting the same kind of asset over and over, the template should probably exist once and be driven by data after that.

Build it once. Generate forever.

Ready to try it? Start building with TemplatesOn at templateson.com.