# Templates

Save reusable designs, manage versions and publish templates for transactional sends.

Save an email as a template to reuse its design across campaigns and journeys. Keep templates for recurring messages such as newsletters, announcements and receipts, then edit the content for each use.

## Save a template

1. Go to **Templates** and start a new design, or open an existing one. See [Design an email](/docs/guides/email-designer/design-an-email).
2. Give it a name in the bar at the top.
3. Choose **Save**. The bar shows **All changes saved** once it's stored.

From the **Templates** list you can search by name, filter by kind, duplicate a template or delete it.

## Use a template in a campaign or journey

When you write a campaign's email, choose **Start from a template** and pick one of yours. Journey emails work the same way. Kirora copies the design into that message.

Because each campaign gets its own copy, editing a template later never changes a campaign that has already used it, and deleting a template is always safe.

## Template kinds

In the designer's **Settings** tab, **Template kind** can be **Campaign**, **Journey** or **Transactional**. For campaign and journey templates, the kind only helps you sort your library. It doesn't change who can receive the email, consent rules, which merge tags work, or the required footer.

Transactional templates behave differently.

## Transactional templates

Transactional emails are the ones your website or app sends for a single person, such as an order confirmation, a password reset or a booking reminder. They're sent by your developers through the API, using the template's ID or alias.

Transactional templates have a few extras:

- **Publish and versions.** Saving changes the draft only. Choose **Publish** to make the draft live: it becomes version 1, then version 2, and so on. Sends start using it straight away. Open **Versions** to view an older version or restore it. Restoring publishes that version again as the newest one.
- **Alias.** In **Settings**, you can give the template a readable alias, such as `order-receipt`, that your developers can send by instead of its ID.
- **Subject and sender.** A transactional template keeps its own subject, preview text and sender, and they go live when you publish.
- **Custom HTML block.** Only transactional templates can use **Custom HTML**.
- **Repeating lists.** Use a **Repeating list** block for the order's lines, with `{{ item.name }}` and similar tags inside it. See [Merge tags and personalisation](/docs/guides/email-designer/merge-tags-and-personalisation).

Once a transactional template is saved, the **Settings** tab shows an example of sending it, which you can pass to your developer. For the developer side, see the [API quickstart](/docs/api/quickstart).

## Shared blocks

A shared block is a block you keep once and place in many emails, such as a promotion banner or a product card. Update it once and every email that places it shows the change.

1. In the designer, select the block and choose **Save as shared block**.
2. Give it a name.
3. In other emails, add it from the **Shared blocks** group in the block library.

Manage them from **Templates › Shared blocks**, where you can rename or delete them. You can't delete a shared block while an email still uses it.

## Start from a sample

**Start from a sample** offers finished emails for common jobs. Pick one, change the words, colours and images, and save it as your own template.

## Next steps

- [Create a campaign](/docs/guides/campaigns/create-a-campaign) — send a template to an audience once
- [Build a journey](/docs/guides/journeys/build-a-journey) — send it automatically when something happens