> ## Documentation Index > Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt > Use this file to discover all available pages before exploring further. # Send branded emails from your own domain > Send branded emails, including authentication emails and custom app emails, from your own email domain with automatic DNS, SPF, DKIM, and DMARC setup to improve deliverability, protect your domain reputation, and strengthen brand trust. ## Overview Emails allow your Lovable Cloud app to send **authentication emails** and custom **app emails** from your own email domain. For example: `noreply@notify.yourdomain.com` or `noreply@yourdomain.com` Using a dedicated sending subdomain helps protect your root domain's reputation while keeping your branding consistent. You can customize: * Which email domain your project uses * The sender subdomain configuration * Email branding and visual style * Email templates and subject lines Lovable handles domain verification, DNS configuration, email authentication (SPF, DKIM, and DMARC), and delivery infrastructure. No external email provider accounts or API keys are required. ## Supported email types You can send authentication emails and custom app emails. ### Authentication emails Authentication emails are a type of transactional email related to account access and identity verification. They are automatically triggered by Cloud Auth when users perform specific security-related actions. Lovable provides six built-in templates you can use: * **Confirm signup**\ Sent when a user creates an account and email confirmation is enabled. Verifies that the user owns the email address before activating the account. * **Password reset**\ Sent when a user requests to reset their password. Allows secure password recovery. * **Magic link**\ Sent when passwordless login is enabled and a user requests a login link. Authenticates the user without requiring a password. You can ask Lovable to enable magic link authentication if it is not already configured. * **Invite**\ Sent when you invite a user to join your project (from Cloud → Users). Grants account access through a secure invitation link. * **Email change**\ Sent when a user updates their email address. Confirms ownership of the new address before applying the change. * **Reauthentication**\ Sent when a user must verify their identity before performing a sensitive action, such as changing a password. Typically includes a short-lived verification code. You can ask Lovable to enable reauthentication if it is not already configured. See [Generate and customize email templates](#generate-and-customize-email-templates) for more information. ### App emails App emails are a type of transactional email sent in response to user activity or events in your app. They are triggered by your application logic when something happens, like a purchase or update. There are no built-in templates, you decide when to send them and what they contain. Ask Lovable to add the required functionality, such as shipping notifications, order confirmations, purchase receipts, and other updates, and it will generate the templates for you. Lovable also handles unsubscribe automatically by adding an unsubscribe link to the email footer. See [Generate and customize email templates](#generate-and-customize-email-templates) for more information. ## Availability and usage * Emails are available on **paid plans**. * Each paid workspace includes **50,000 transactional emails per month** at no additional cost. Usage is calculated across the entire workspace. Additional emails are billed at \$1 per 1,000 emails and deducted from your [Cloud and AI balance](/integrations/cloud#usage-based-cloud-and-ai-pricing). * Emails are rate limited to **100 emails per hour per workspace** to protect deliverability and system stability. If you need a higher limit, contact [Lovable Support](https://lovable.dev/support). ## Why use emails * **Better deliverability:** Emails sent from your own domain are more likely to reach the inbox instead of spam. * **More trust:** Users see your domain in the `From` address, reinforcing credibility. * **Consistent branding:** Emails match your product identity. * **Managed setup:** Lovable verifies your domain and configures the required DNS records. * **Authenticated sending:** Lovable automatically sets up [SPF, DKIM, and DMARC](#what-are-spf-dkim-and-dmarc-and-do-i-need-to-configure-them) to authenticate your emails and improve inbox placement. * **Continuous monitoring:** Lovable alerts you if DNS changes could impact email delivery. ## Prerequisites To use emails: * [Lovable Cloud](/integrations/cloud) must be enabled for your project. * Your workspace must be on a paid plan. * You must own a domain and have access to manage its DNS settings. * You must be a workspace admin or owner to add, delete, or verify domains. ## How emails work When you configure an email domain, Lovable: * Creates a transactional sender subdomain under your root domain, such as `notify.yourdomain.com` * Guides you through DNS configuration using an automated setup flow * Verifies your domain by checking required DNS records * Provides six built-in branded authentication email templates that you can generate and customize * Generates custom app email templates based on the functionality you request, such as confirmations, notifications, and updates * Activates email delivery once DNS verification completes After domain verification, emails are sent from your domain. ### Email domain scope and usage Email domains are provisioned at the workspace level. * A workspace can have multiple email domains * A verified domain can be used across multiple projects * Each project selects which verified domain it uses * Only one email domain can be active per project at a time * Only domains with status **Verified** can send emails * Emails can be enabled or disabled per project ## Add an email domain Select the domain you want to use for sending emails. This will be the domain your users see in their inbox. There are two ways to start: * **From the chat**: Ask Lovable to set up emails and it will present a setup button. For example: ```text theme={null} I want to send password reset emails from my domain. ``` * **From Cloud settings**: Go to **Cloud → Emails** and click **Get started**. This takes you to the email setup flow. - Choose an existing workspace domain from the dropdown, or select **Add a new email domain**, then enter your root domain or subdomain, for example `yourdomain.com`. Domains can have up to 5 levels, for example `a.b.c.example.com`. - Click **Continue**. Configure the subdomain prefix that will be used for sending emails. The right-side preview shows a simulated inbox with example emails from your configured domain. * By default, Lovable creates a `notify` subdomain for delivery, for example `noreply@notify.yourdomain.com`, but you can change the subdomain. * Optionally, enable **Show as sent from @yourdomain.com** so recipients see emails from `@yourdomain.com` in their inbox, while your transactional sender subdomain handles delivery behind the scenes. * Click **Set up domain**. After clicking **Set up domain**, Lovable launches an **automated DNS configuration flow** (powered by Entri) that guides you through setting up the required `NS` zone delegation for your domain. If your DNS provider is not listed or you prefer manual control, you can configure DNS records yourself. Scroll to the bottom of the **Select your domain provider** Entri modal and choose **Go to our manual setup**. Both the automated and manual methods require verifying ownership of your domain. Lovable will provision your domain and generate the required DNS records. Follow the on-screen prompts to log in to your DNS provider and authorize Entri to update your DNS records. 1. Copy the displayed DNS records. * `TXT` record for domain verification * `NS` records pointing to Lovable's nameservers 2. Track your progress with the **I have copied X/Y records** counter. 3. Add the copied DNS records directly into your domain registrar or DNS provider. You can also forward these instructions to a colleague if someone else manages your DNS. After DNS is configured, you're taken back to the **Emails** page in your project. A progress panel shows the current state of your domain setup and a countdown timer for each setup step. See [Email domain statuses](#email-domain-statuses) to learn what each status means. DNS changes typically propagate within a few hours, but may take up to 48 hours. While DNS verification is in progress, you can start setting up your authentication and app email templates. See [Generate and customize email templates](#generate-and-customize-email-templates) for more information. Lovable automatically detects when DNS verification completes and activates your domain. Once the domain status changes to **Verified**, emails begin sending from your domain. Newly provisioned domains start with a neutral reputation. Initial deliverability may fluctuate while your domain builds trust with inbox providers through consistent, legitimate sending. See [Email deliverability best practices](#email-deliverability-best-practices) for more information. ## Email domain statuses Email domains can move through the following statuses: | Status | Meaning | | :-------------------- | :-------------------------------------------------------------- | | **Pending** | Setup has started and DNS configuration is in progress | | **Verifying** | DNS records have been detected and verification is in progress | | **Setting up** | Domain provisioning in progress | | **Verified (Active)** | Domain is ready and can be used to send emails | | **Offline** | Required DNS records were changed or removed after verification | | **Failed** | Verification or provisioning failed | | **Domain removed** | The domain was deleted from the workspace | Domains are continuously monitored. If required DNS records drift, are removed, or expire, the domain may move to an inactive state until re-verified. ## Generate and customize email templates The **Emails** page includes two tabs, **Auth emails** and **App emails**, where you can preview the generated templates for your app. Email templates are not generated automatically. To generate email templates: * **Auth email templates**\ Go to the **Auth emails** tab and click **Customize auth emails**. Lovable generates six built-in branded templates. * **App email templates**\ Ask Lovable to add the required functionality, such as notifications, confirmations, or receipts. It will generate the corresponding email templates for you. For example: ```text wrap theme={null} Add order confirmation emails to my app. When an order is placed, send a confirmation email to the customer. ``` Each template shows: * **From** address * **Subject** line * **Live preview** of the email template rendered in an iframe * **Send test** options, including sending a test email to your account or to a custom address. Emails sent from newly configured domains may initially land in spam while reputation builds. ### Automatic branding When generating the email templates, Lovable applies your app's branding automatically by: * Extracting CSS variables from `src/index.css` (primary colors, fonts, border radius) * Detecting logo files in `public/` and `src/assets/` * Uploading a detected logo to a dedicated email assets storage bucket * Adapting email copy to match your app's tone and language The outer email body background is always `#ffffff` to ensure consistent rendering across email clients. Inner components can use your brand colors. ### What you can customize You can ask Lovable to update: * Copy and tone * Brand colors * Layout and structure * Images and logo placement * Subject lines The outer email body background must remain white (`#ffffff`) to ensure consistent rendering across email clients. Inner components can use your brand colors. For example: ```wrap theme={null} Match the emails to my brand by using #2563eb for buttons and headings, add my logo at the top, remove emojis, make the tone professional but friendly, move the button higher in the layout, add a footer with support@myapp.com, and update subject lines to start with my app name. ``` Lovable updates templates while preserving required information, such as authentication variables, secure callback links, and the unsubscribe footer. ### Edit templates manually If you prefer to edit code directly: * **Authentication emails** * Templates are located at `supabase/functions/_shared/email-templates/` * The sending logic is located at `supabase/functions/auth-email-hook/` Required authentication variables and callback links must remain intact, or authentication flows will break. * **App emails** * Templates are located at `supabase/functions/_shared/transactional-email-templates/` * The sending logic is located at `supabase/functions/send-transactional-email/` The unsubscribe footer in app email templates must remain intact. Removing it violates email sending requirements and will affect deliverability. Templates use React Email components with inline styles (email clients do not support external CSS). After editing template files or subject lines, you must ask Lovable to redeploy for changes to take effect. For example: ```text theme={null} Redeploy my email templates ``` ## Managing email domains In **Cloud → Emails**, use the domain dropdown to access: * **Analytics and logs**: View delivery metrics for the email domain and email activity for the current project using that domain. * **Manage domains**: View all workspace email domains and their status badges, inspect and copy DNS records, switch which domain the current project uses, manually verify a domain, add a domain, or delete a domain. Deleting a domain is a **workspace-wide action**. This will stop sending emails from that domain. Any project using that domain will automatically fall back to default authentication emails and other app emails will stop sending. * **Add a new domain:** Add a new workspace email domain. * **Disable emails**: Enable or disable emails for the current project. When disabled, authentication emails continue sending using the default Cloud Auth sender instead of your custom email domain and templates, and other app emails stop sending. ### Analytics and logs The analytics and logs view shows delivery metrics for the connected domain over 7, 30, or 90 days, and a log of recent emails sent for the current project. * **Metrics cards**: * **Sent**: Emails accepted and queued for delivery * **Delivered**: Emails successfully delivered to recipient inboxes * **Bounced**: Emails rejected by the recipient mail server * **Delivery chart**: Delivered (blue) vs. failed (red) emails for the email domain. Hover over any point to see the exact counts for that hour. * **Email activity log**: An expandable list of recent emails sent for the current project, showing recipient, status (completed, failed, pending), type (auth email, app email, or test email), timestamps, and detailed execution traces with error messages for failures. ## Email deliverability best practices When sending emails from a new domain, inbox placement may take time to stabilize. Inbox providers evaluate sender reputation over time based on engagement, authentication, and sending patterns. Follow these practices to improve deliverability and build a strong sender reputation. New email domains have no sending history. Inbox providers treat them cautiously because spammers often use fresh domains and abandon them quickly. Initial deliverability may fluctuate during the first few days or weeks. This is normal. Your domain's reputation builds gradually as real users engage with emails. This includes: * Authentication emails: Signups, password resets, email verifications * App emails: Order confirmations, shipping notifications, account updates Both email types contribute to your overall domain reputation. Using a dedicated transactional subdomain helps isolate authentication traffic and protect your primary domain reputation. **Typical timeline** * First few days: Test emails may land in spam * First few weeks: Deliverability improves as legitimate traffic builds reputation * First few months: Reputation stabilizes with consistent, engaged sending **What helps:** * Start sending with normal authentication traffic (user signups, password resets) * Let volume grow naturally as your user base expands * Add app emails gradually as transaction volume grows * Maintain consistent sending patterns over weeks and months * Ensure emails are expected and triggered by real user actions * Mark legitimate emails as “Not spam” in your inbox **What hurts:** * Sudden large spikes in email volume from a brand-new domain * Sending bulk test emails immediately after setup * Inconsistent sending (long gaps followed by sudden bursts) * Panic-driven changes to domains or sender identity Reputation builds automatically with consistent, legitimate sending behavior over time. Authentication must pass for emails to reach the inbox. Lovable automatically configures `SPF`, `DKIM`, and `DMARC` when you set up your email domain. If DNS records are modified or misconfigured, authentication can fail and emails may land in spam. Always confirm the domain status is **Verified** in **Cloud → Emails**. Authentication emails should only be triggered by real user actions, such as signing up or resetting a password. App emails should only be sent when directly related to user activity, for example: * Order confirmations: Only to the customer who placed the order * Shipping notifications: Only to customers with active shipments * Account updates: Only to users who made changes or need to be notified Avoid generating artificial traffic for testing or automation purposes. Unnatural traffic patterns can negatively affect domain reputation. Don't send to: * Email addresses that previously bounced * Users who unsubscribed from non-essential notifications * Inactive or closed accounts Authentication emails should clearly match the user's recent action and explain why the email was sent. App emails should focus on information relevant to the specific transaction or event. **Good practices**: * Use straightforward subject lines ("Reset your password", "Verify your email") * Include all necessary details (order numbers, tracking links, amounts, dates) * Clearly explain what the user needs to do * Match the email to the action the user took **Avoid**: * Adding marketing content or upsells to auth emails * Misleading or clickbait subject lines * Promotional language in authentication emails Mixing promotional content into transactional emails can trigger spam filters and reduce trust. Use a consistent: * From address * Sender name * Domain Frequent changes to sender identity reduce trust signals with inbox providers. Authentication emails (password resets, email verification, magic links) don't require unsubscribe links as they're necessary for service functionality. Lovable automatically adds unsubscribe functionality to all app email templates. When a user unsubscribes, their email is added to a suppression list and future app emails to that address are blocked automatically before sending. Don't remove the unsubscribe footer as this violates email sending requirements and will affect deliverability. When customizing email templates: **Do**: * Use clear, descriptive subject lines ("Your order has shipped", "Reset your password") * Keep formatting simple and clean * Use a balanced text-to-image ratio * Include your brand name and a recognizable sender address * Ensure links in the email match your sending domain whenever possible **Don't**: * Use ALL CAPS in subject lines * Add excessive punctuation (!!!) * Create misleading subject lines * Use image-heavy layouts * Link to unrelated or mismatched domains Inbox providers look for consistency between the sender domain and the domains used in links. If your email is sent from `yourdomain.com`, links inside the email should ideally point to `yourdomain.com` or its subdomains. Mismatched domains are commonly used in phishing attacks and may trigger spam filtering. Clear, predictable formatting and domain alignment improve trust and engagement. High bounce rates damage sender reputation. Use **Analytics and logs** to monitor: * Sent * Delivered * Bounced Hard bounces caused by invalid or mistyped addresses are especially harmful. Repeatedly sending to invalid addresses can reduce inbox placement. If bounce rates increase: * Review how email addresses are collected * Validate inputs at signup * Avoid retrying failed deliveries repeatedly Spam complaints also negatively affect reputation. Both authentication and app emails should always be expected and clearly explained. The **Send test** option in **Cloud → Emails** is useful for validation, but limit your testing. **Why this matters**: * Inbox providers evaluate engagement signals from all emails you send * Repeated test emails to the same address create artificial traffic patterns * Bouncing test emails to fake addresses damages your reputation **Better approach**: * Send a few test emails to yourself or your team * Use real email addresses you control * Avoid sending large batches of test emails If authentication emails are marked as spam: 1. Confirm the domain status is **Verified** 2. Ensure DNS records are correctly configured 3. Review subject lines and content 4. Check bounce rates in **Analytics and logs** 5. Reduce sudden spikes in sending volume 6. Be patient. New domains need time to build trust with inbox providers Deliverability improves with consistent, legitimate sending behavior over time. Inbox providers consider engagement when evaluating sender reputation. Authentication emails naturally generate positive signals when users: * Open the email * Click the verification or reset link * Complete the intended action App emails generate positive signals when users: * Open order confirmations to check details * Click tracking links in shipping notifications * Interact with account update information Clear messaging and expected flows increase engagement and improve long-term inbox placement. Gmail clips emails larger than 102 KB. Keep your total email size under 100 KB to ensure your content displays fully. **Best practices:** * Optimize images before embedding them in app emails * Avoid large embedded images in receipts or order confirmations * Keep order details and transaction information concise * Consider linking to images hosted on your domain instead of embedding large files Lovable includes plain text versions of emails automatically for accessibility and as a fallback for email clients that don't support HTML. While link tracking and open tracking can be useful for measuring engagement with marketing emails, they can hurt deliverability for transactional emails. Why this matters: When a shipping notification or order confirmation link doesn't lead directly to your domain, it can make the email look suspicious to inbox providers. Recommendation: For app emails like order confirmations and shipping notifications, use direct links to your domain rather than tracking redirects whenever possible. Inbox providers don't share their spam filtering criteria publicly (to prevent spammers from gaming the system). However, they generally evaluate: * **Sender authentication**: Are `SPF`, `DKIM`, and `DMARC` configured correctly? (Lovable handles this automatically) * **Sender reputation**: What's your history of bounces, complaints, and engagement? * **Content quality**: Are subject lines clear? Is formatting clean? Do links match your domain? * **Engagement signals**: Do users open emails? Click links? Reply? Or mark them as spam * **Sending patterns**: Are you sending consistently? Or in sudden bursts? Think: "What would a phisher do?" Then do the opposite. Inbox providers want to protect their users, so demonstrate at every step that you're a legitimate sender with no malicious intent. ## Troubleshooting Possible causes: * DNS records not fully propagated * `NS` delegation incorrect * `TXT` verification record missing * DNS configured on wrong domain level **What to do:** * Recheck the exact DNS records shown in **Cloud → Emails** * Confirm records were added to the correct root domain * Wait up to 48 hours for propagation * Retry verification This means required DNS records were changed, removed, or expired after verification. **What to do:** * Review DNS records in **Cloud → Emails** * Restore missing `NS` or `TXT` records * Re-verify the domain The domain was deleted while this project was still using it. Go to **Cloud → Emails → Manage domains**, connect a different verified domain to this project, or add and verify a new one. Check: * Email domain is linked to your project * Domain status is **Verified** * Emails are enabled for the project * For authentication emails: Cloud Auth is enabled, and you are triggering a supported auth event type * The correct edge function is deployed * Emails are rate limited to **100 emails per hour per workspace** to protect deliverability and system stability. If you need a higher limit, contact [**Lovable Support**](https://lovable.dev/support). Use **Send test** on a template tab and check **Analytics and logs** for delivery failures or bounces. Common causes: * Invalid email addresses * Typos during signup * Repeated retries to invalid addresses Validate email input at signup and avoid retrying hard bounces. This is common for newly provisioned domains. Avoid sending large volumes of internal test emails. Allow organic user-triggered emails to build reputation over time. If you edited template files but users are still receiving old versions: * Ensure the corresponding edge function was redeployed * Ask Lovable to redeploy your email templates Template changes only take effect after redeployment. If emails are consistently landing in spam or being rejected, you can use the following tools for deeper diagnostics. These tools are optional and most useful for higher-volume senders. * [Google Postmaster Tools](https://postmaster.google.com/)\ View sender reputation, spam rates, and authentication alignment for Gmail recipients. * [Yahoo Sender Hub](https://senders.yahooinc.com/)\ Monitor complaint rates and sender reputation for Yahoo inboxes. * [Spamhaus blocklist lookup](https://check.spamhaus.org/)\ Check whether your domain, IP address, or email URLs appear on major blocklists. * [Google Safe Browsing](https://transparencyreport.google.com/safe-browsing/search)\ Test links used in your emails to ensure they are not flagged as unsafe. These tools help diagnose reputation or blocklist issues that may impact inbox placement. ## FAQ **Authentication emails** are a type of transactional email related to account access and identity verification. They are automatically triggered by Cloud Auth when users perform specific security-related actions, such as sign up, reset a password, or accept an invite. Lovable provides six built-in templates that you can generate when needed. **App emails** are a type of transactional email sent in response to user activity or events in your app. They are triggered by your application logic when something happens, like a purchase or update. There are no built-in templates, you decide when to send them and what they contain. Ask Lovable to add the functionality, such as notifications, confirmations, receipts, and other updates, and it will generate the templates for you. No. Both email types use the same custom domain and the same setup process. No. Only transactional emails are supported, such as signup confirmations, password resets, order confirmations, and shipping notifications. Marketing emails, such as newsletters, promotional emails, product announcements, and similar messages are not supported. Yes. Emails require Lovable Cloud and integrate with Cloud Auth to send authentication emails. No. Your web custom domain controls where your app is hosted. A custom email domain controls which domain your emails are sent from. These are separate configurations because web hosting and email delivery use different DNS records and infrastructure. You can use a completely different root domain for email sending as long as you control its DNS. However, using a domain that aligns with your product brand is recommended for user trust and deliverability. Hosting your app on a custom domain does not automatically configure email sending. Yes. Lovable automatically creates a transactional subdomain such as `notify.yourdomain.com` for delivery. You can optionally display emails as coming from your root domain while delivery happens through the subdomain behind the scenes. Using a dedicated email subdomain is recommended because it helps protect your root domain's reputation. No. Lovable manages domain verification, DNS configuration, authentication records such as `SPF`, `DKIM`, and `DMARC`, and delivery infrastructure. You do not need to manage API keys or third-party email provider accounts. `SPF`, `DKIM`, and `DMARC` are email authentication standards that help inbox providers verify that your emails are legitimate and not spoofed. When you send an email, providers such as Gmail or Outlook check that: * The email is authorized to be sent from your domain * The message has not been altered in transit * The domain owner has defined a policy for handling suspicious emails If authentication fails, emails may be marked as spam, rejected, or damage your domain reputation. Lovable automatically configures and maintains: * **SPF (Sender Policy Framework):** Authorizes which servers can send email for your domain * **DKIM (DomainKeys Identified Mail):** Cryptographically signs emails to prevent tampering * **DMARC (Domain-based Message Authentication, Reporting, and Conformance):** Defines how providers handle failed authentication and protects against spoofing You do not need to manually configure these records. Lovable sets them up during domain verification and continuously monitors them. If authentication records are modified, removed, or expire, you are notified so they can be restored. Each paid workspace includes **50,000 transactional emails per month** at no additional cost. Usage is calculated across the entire workspace. Additional emails are billed at **\$1 per 1,000 emails** and deducted from your [Cloud and AI balance](/integrations/cloud#usage-based-cloud-and-ai-pricing). No. Emails are available on **paid plans only**. Free plans use the default Lovable Cloud Auth sender. DNS changes typically propagate within a few hours, but can take up to 48 hours. You can check the domain status in **Cloud → Emails**. The status updates automatically once verification completes. New email domains start with no sending reputation. If emails land in spam: • Confirm the domain status is **Verified**\ • Ensure DNS records have not changed\ • Avoid sudden spikes in sending volume\ • Avoid spam-trigger formatting\ • Check bounce rates in **Analytics and logs** Deliverability improves over time with consistent, legitimate user activity. Yes. You can customize: * Copy and tone * Brand colors * Layout and structure * Logos and images * Subject lines You can ask Lovable to update the templates or edit them directly in `supabase/functions/_shared/`. Required authentication variables and callback links must remain intact in auth emails, as well as the unsubscribe footer in app email templates. The outer email body background must remain white (`#ffffff`) to ensure consistent rendering across email clients. Inner components can use your brand colors. If emails are disabled for a project, authentication emails continue sending using the default Lovable Cloud Auth sender instead of your branded templates. App emails stop sending. Deleting an email domain is a **workspace-wide action**. All projects using that domain will immediately fall back to the default Lovable Cloud Auth sender and app emails will stop sending.