One template, many looks — without duplication
Package style and content overrides as reusable mods, group them into named variants, and apply them at render time across your templates.
- Reusable overrides, zero template forks
- Toggle variants per render
- Multiply outputs in bulk jobs
No credit card required · 25 free renders every month
What you get
Mods are named override sets
A mod bundles overrides — colors, copy, layout tweaks — into a single switch you can flip on any render.
Variants group mods
Combine mods into labelled variants like “Dark / DE / Story” and reuse them wherever they fit.
Toggle anywhere
Enable mods on the template use page, in the editor preview, or per API request.
Multiply with bulk generation
Bulk jobs render every row of data against every variant — a 20-row, 5-variant job yields 100 outputs.
No template forks
Stop maintaining near-identical copies of the same design; the base template stays the single source of truth.
Shared across the space
Your team works from the same library, so the same variant means the same thing everywhere.
Questions, answered
What's the difference between a mod and a variant?
A mod bundles overrides — colors, copy, layout tweaks — into one switch. A variant groups mods into a labelled set like "Dark / DE / Story".
Where can I apply variants?
On the template use page, in the editor preview, or per API request — wherever you render the template.
Do I still maintain duplicate templates?
No. The base template stays the single source of truth; variants apply at render time, so there are no near-identical forks to keep in sync.
Keep reading
More from Bannx
One platform for every render. Design once in the templates editor, ship at scale with the API, and compare plans.
