Skip to main content
Customize the transactional auth emails your users receive from your app — signup confirmations, password resets, magic links, and more. These are the emails sent by your Supabase Auth layer, not marketing emails.
Before you start: Set up user authentication so your project has an auth database. Auth email templates only apply once auth is enabled.

​
Where to Find Templates

In your project, go to Database > Auth > Templates tab. You’ll see six templates you can customize, each with its own subject line, HTML body, and plain-text fallback.

​
Edit a Template

1

Open the Templates tab

Go to Database > Auth > Templates and click the template you want to edit.
2

Update the subject line

The subject is what users see in their inbox list. Keep it short and specific — “Confirm your email for Acme” beats “Email confirmation”.
3

Edit the HTML body

Write or paste HTML with inline CSS. External stylesheets won’t load in most email clients. Use Supabase template variables to insert dynamic values (see below).
4

Add a plain-text version

Recommended. Some email clients default to plain text, and spam filters like it when both are present. Include the same action link in plain form.
5

Preview

Click Preview to see the rendered HTML with example data. Fix any layout issues before saving.
6

Save

Click Save. The new template takes effect for the next email sent.

​
Template Variables

Supabase uses Go-style template syntax. The most common variables:
Use the exact syntax {{ .VariableName }} with the leading dot. If your emails arrive showing literal {{ .ConfirmationURL }} text, you’re missing the dot or a space.

​
Example: Branded Confirmation Email

Keep templates under 100KB. Email clients clip longer messages, and users won’t see the action link.

​
SMTP Is Required

Auth emails only send once SMTP is configured. You have two options on the SMTP tab of the same Auth page:
  • Hiveku Email — use your project’s built-in email service (easiest, no setup)
  • Custom SMTP — bring your own provider (SendGrid, Postmark, your own SMTP server)
If SMTP isn’t configured, templates will save but no emails go out.

​
Verify Your Changes

1

Sign up as a test user

Use an email address you control (a +test alias is handy).
2

Check the inbox

Confirm the new subject, branding, and content show correctly.
3

Click the action link

Verify the link works — it should confirm the account, reset the password, or whatever that template is for.

​
Troubleshooting

SMTP isn’t configured yet. Go to the SMTP tab and either enable Hiveku Email or add your provider’s credentials. Without SMTP, auth emails are queued but never sent.
Use exact Go template syntax — {{ .ConfirmationURL }} with a leading dot and spaces around the variable. A missing dot or a typo in the variable name means it’s rendered as literal text.
Your sending domain isn’t verified. See Email domains to add SPF, DKIM, and DMARC records. Unverified domains get filtered aggressively.
Email clients strip external CSS. Use only inline styles. Avoid flexbox and grid — use tables for layout. Test with the Preview button and with real test emails across clients.

​
What’s Next?

Set Up User Authentication

Enable signup, login, and password reset flows

Email Domains

Verify your sending domain so emails land in the inbox