Saved Templates
Persist reusable text templates with merge fields.
Overview
Save reusable text templates with merge fields you fill in later. Drop placeholders like {{name}}, {{date}}, or {{order_id}} inside the template body, then plug in values from a quick form to produce the final text. Templates are stored locally and survive across sessions.
Customer support reps using boilerplate email replies, freelancers reusing proposal language, contract drafters generating standard NDAs, and developers building stub responses for testing all reach for a template library. It's faster and more accurate than copy-pasting from a notes file.
How it works
Each template has a name, a body containing one or more {{placeholder}} tags, optional descriptions for each placeholder, and tags for organization. When you render the template, the tool lists each placeholder in a form, you fill the values, and it substitutes them back into the body. Storage is browser-local; nothing is sent to a server.
Some implementations support default values, type hints (date, number, multi-line), and chained templates that include each other.
Examples
Template name: Welcome email
Body:
Hi {{name}},
Thanks for signing up for {{product}} on {{date}}.
Your account ID is {{account_id}}.
Best,
The Team
Values: name=Alice, product=ToolBelt, date=2026-05-18, account_id=A-1234
Output:
Hi Alice,
Thanks for signing up for ToolBelt on 2026-05-18.
Your account ID is A-1234.
Best,
The Team
FAQ
Where are my templates stored?
In your browser's local storage. The data doesn't leave your device. Export it as JSON to back up or share.
Can placeholders have default values?
Yes. Defaults appear pre-filled in the form so you can override only the values that change.
Are templates limited to email replies?
No. Any reusable text works — meeting agendas, code review comments, shell commands, JSON payloads. Treat the tool as a generic text macro store.