SupabaseEmailError Fix2026 Updated

Supabase Email Confirmation Not Sending— Custom SMTP Fix [2026]

Also covers: free tier rate limits · Resend SMTP · SendGrid · spam folders · resend email · template customisation

January 20266 min readSupabase · Resend · SendGrid · SMTP

⚡ The Problem

Error
// signUp() returns no error — but user never receives email
const { error } = await supabase.auth.signUp({ email, password })
console.log(error)  // null

// Common causes:
// 1. Free tier rate limit (2 emails/hour) — most common
// 2. Email landed in spam
// 3. No custom SMTP configured for production

✅ Fix — configure custom SMTP (Resend recommended)

Supabase Dashboard → Project Settings → Authentication → SMTP
SMTP Host:       smtp.resend.com
SMTP Port:       465
SMTP Username:   resend
SMTP Password:   re_your_api_key_here
Sender Email:    noreply@yourdomain.com
Sender Name:     Your App Name

Why Supabase Confirmation Emails Don't Arrive

Supabase's built-in email service has a strict rate limit of 2 emails per hour on the free plan. If you sign up, test password reset, and sign up again in the same hour, you may have exhausted the limit. The emails appear to be sent (no error returned) but are silently queued and dropped.

For production, the built-in service also sends from a shared domain with lower deliverability. Custom SMTP with your own verified domain is essential for emails to reliably reach inboxes.

1

Check the Rate Limit — Free Tier Sends Only 2 Emails/Hour

Most common cause during development
1 min

If you have been testing signups and password resets in the same hour, you have likely hit the limit. Wait 1 hour and try again, or immediately configure custom SMTP to remove the limit entirely.

Quick test — check if rate limit is the issue
// If this returns no error but email never arrives → rate limit hit
const { data, error } = await supabase.auth.signUp({
  email: "test@example.com",
  password: "password123",
})

// Solution: configure custom SMTP (see Fix 2 below)
// or temporarily disable email confirmation for development:
// Supabase Dashboard → Authentication → Providers → Email
//   → toggle OFF "Confirm email"

During development, disable email confirmation entirely. Supabase Dashboard → Authentication → Providers → Email → turn off 'Confirm email'. Re-enable before going to production.

2

Configure Custom SMTP with Resend

Recommended — free tier, excellent deliverability
10 min

Resend offers 3,000 emails/month free, has excellent deliverability, and integrates with Supabase in minutes. This removes the 2-email/hour limit completely.

Step 1 — Set up Resend
# 1. Create account at resend.com
# 2. Add and verify your domain (follow their DNS guide)
# 3. Create an API key at resend.com/api-keys
# 4. Copy the API key (starts with "re_")
Step 2 — Configure in Supabase Dashboard
# Supabase Dashboard → Project Settings → Authentication → SMTP Settings

Enable Custom SMTP:  ✅ toggle ON

SMTP Host:           smtp.resend.com
SMTP Port:           465
SMTP Username:       resend
SMTP Password:       re_xxxxxxxxxxxxxxxxxxxx  (your Resend API key)
Sender Email:        noreply@yourdomain.com   (must be your verified domain)
Sender Name:         Your App Name

# Click "Save" — then test with a signup
Step 3 — Test the SMTP setup
# Supabase Dashboard has a "Send test email" button in SMTP settings
# Or test via your app signup flow
# Emails should now arrive immediately with no rate limit
3

Configure Custom SMTP with SendGrid

Alternative — enterprise-grade deliverability
10 min
SendGrid SMTP settings for Supabase
# 1. Create account at sendgrid.com
# 2. Settings → Sender Authentication → Domain Authentication
#    (verify your sending domain — required for production)
# 3. Settings → API Keys → Create API Key (Full Access or Mail Send only)

# Supabase Dashboard → Project Settings → Authentication → SMTP Settings:
SMTP Host:           smtp.sendgrid.net
SMTP Port:           587
SMTP Username:       apikey                    (literal string "apikey")
SMTP Password:       SG.xxxxxxxxxxxxxxxxxx     (your SendGrid API key)
Sender Email:        noreply@yourdomain.com
Sender Name:         Your App Name
4

Fix Emails Landing in Spam

Emails sending but not reaching inbox
15 min

If emails send but land in spam, the issue is deliverability — your sending domain lacks proper DNS authentication records.

Required DNS records for email deliverability
# Add these DNS records at your domain registrar
# (Resend / SendGrid provide exact values in their dashboard)

# 1. SPF — authorises your SMTP provider to send on your behalf
TXT  @    "v=spf1 include:_spf.resend.com ~all"

# 2. DKIM — cryptographically signs outgoing emails
CNAME  resend._domainkey  resend._domainkey.yourdomain.com.dkim.resend.com

# 3. DMARC — tells mail servers what to do with failed SPF/DKIM
TXT  _dmarc  "v=DMARC1; p=quarantine; rua=mailto:admin@yourdomain.com"

# After adding DNS records, allow 24-48 hours for propagation
# Then verify at: mail-tester.com or mxtoolbox.com

Always test your email deliverability score at mail-tester.com before going to production. A score below 8/10 means emails will frequently land in spam.

5

Resend Confirmation Email Programmatically

'Resend confirmation email' button for users
2 min

Add a resend button to your 'check your email' page so users who didn't receive the email can request a new one.

components/resend-confirmation.tsx
"use client"

import { createClient } from "@/lib/supabase/client"
import { useState } from "react"

export function ResendConfirmationButton({ email }: { email: string }) {
  const supabase = createClient()
  const [status, setStatus] = useState<"idle" | "sending" | "sent" | "error">("idle")

  async function handleResend() {
    setStatus("sending")

    const { error } = await supabase.auth.resend({
      type: "signup",
      email,
      options: {
        emailRedirectTo: `${window.location.origin}/auth/callback`,
      },
    })

    setStatus(error ? "error" : "sent")
  }

  return (
    <div>
      <button onClick={handleResend} disabled={status === "sending" || status === "sent"}>
        {status === "idle" && "Resend confirmation email"}
        {status === "sending" && "Sending..."}
        {status === "sent" && "Email sent! Check your inbox"}
        {status === "error" && "Failed — try again"}
      </button>
      {status === "sent" && <p>Also check your spam folder.</p>}
    </div>
  )
}

Prevention

Frequently Asked Questions

Why is Supabase not sending confirmation emails?+
The most common cause on the free plan is the built-in rate limit — Supabase only sends 2 emails per hour on the free tier. If you have tested signup multiple times, you may have hit this limit. The fix is to configure a custom SMTP provider like Resend or SendGrid, which removes this restriction.
What is the Supabase email rate limit on the free plan?+
Supabase free tier allows 2 emails per hour using the built-in email service. For production or any serious development, you must connect a custom SMTP provider. The Pro plan increases this but custom SMTP is still recommended for reliability and deliverability.
Which SMTP providers work well with Supabase?+
Resend is the most popular choice because it has a generous free tier (3,000 emails/month), excellent deliverability, and a simple API. SendGrid, Mailgun, Postmark, and AWS SES also work well. All are configured the same way in Supabase Dashboard → Project Settings → Authentication → SMTP Settings.
How do I resend a confirmation email in Supabase?+
Call supabase.auth.resend({ type: 'signup', email: userEmail }) in your client code. This resends the confirmation email to the specified address. You can expose this as a button on your 'check your email' page for users who didn't receive it.
Can I customise the Supabase confirmation email template?+
Yes. Go to Supabase Dashboard → Authentication → Email Templates. You can customise the HTML and subject line for confirmation emails, magic links, password reset, and invite emails. Use the {{ .ConfirmationURL }} variable to insert the confirmation link.
Why do Supabase emails go to spam?+
Supabase's built-in email service sends from a shared domain (mail.supabase.io) with lower deliverability than a custom domain. Emails from shared sending domains are more likely to be marked as spam. Use a custom SMTP provider with your own domain and configure SPF, DKIM, and DMARC DNS records to improve deliverability.

Need Expert Help?

We Set Up Supabase Email for Production

Softplix engineers configure Supabase with custom SMTP, domain verification, and email templates — ready for production from day one. Let us help.

Talk to an Engineer