Supabase Auth email templates load from content_path
Introduced 2026-06-25 · score 0.93
HOW TO USE IT
When configuring Auth email templates in a repository, set each template’s `content_path` to a relative HTML file path, then run `supabase config push` to update the linked project’s configuration.
[auth.email.template.invite]
subject = "You are invited to Acme Inc"
content_path = "./supabase/templates/invite.html"supabase config pushWHY THIS HELPS
Configure Auth email templates in a repository and push them with the Supabase CLI.
BEFORE THIS CHANGE
Embed Auth email templates in TOML.
REQUIREMENTS AND LIMITATIONS
- Version: v2.108.0
- auth.email.template.<type>.content_path: Relative path to the HTML content file for the template. Types: `invite`, `confirmation`, `recovery`, `magic_link`, `email_change`.
- auth.email.template.<type>.subject: Subject for the given template type.
- --project-ref <string>: Project reference for `supabase config push`.
- Prerequisite: Install and authenticate the Supabase CLI; link the local project to a remote project before pushing configuration.
FIRST-PARTY EVIDENCE
- https://github.com/supabase/cli/releases/tag/v2.108.0
- https://supabase.com/docs/guides/local-development/customizing-email-templates
- https://supabase.com/docs/reference/cli/global-flags
- https://supabase.com/docs/guides/local-development/cli/config
- https://supabase.com/docs/guides/local-development/cli-workflows
Check the installed version and the source before using it. Entry JSON