---
id: 'customizing-email-templates'
title: 'Customizing email templates'
description: 'Customizing local email templates using config.toml.'
subtitle: 'Customizing local email templates using config.toml.'
---
You can customize the email templates for local development [using the `config.toml` settings](/docs/guides/cli/config#auth-config).
## Configuring templates
You should provide a relative URL to the `content_path` parameter, pointing to an HTML file which contains the template. For example
Confirm your signup
```
Click here to confirm: {{ .ConfirmationURL }}
``` ### Token Contains a 6-digit One-Time-Password (OTP) that can be used instead of the `ConfirmationURL`. **Usage** ```htmlHere is your one time password: {{ .Token }}
``` ### TokenHash Contains a hashed version of the `Token`. This is useful for constructing your own email link in the email template. **Usage** ```htmlFollow this link to confirm your user:
``` ### SiteURL Contains your application's Site URL. This can be configured in your project's [authentication settings](/dashboard/project/_/auth/url-configuration). **Usage** ```htmlVisit here to log in.
``` ### Email Contains the user's email address. **Usage** ```htmlA recovery request was sent to {{ .Email }}.
``` ### NewEmail Contains the new user's email address. This is only available in the `email_change` email template. **Usage** ```htmlYou are requesting to update your email address to {{ .NewEmail }}.
``` ## Deploying email templates These settings are for local development. To apply the changes locally, stop and restart the Supabase containers: ```sh supabase stop && supabase start ``` For hosted projects managed by Supabase, copy the templates into the [Email Templates](/dashboard/project/_/auth/templates) section of the Dashboard.