fanfarly / supabase email errors · updated 2026-11-21 · markdown

Supabase over_email_send_rate_limit (email rate limit exceeded)

You call signUp, signInWithOtp, resetPasswordForEmail or resend, and Supabase Auth answers with HTTP 429 and the error code over_email_send_rate_limit (older clients show email rate limit exceeded). No email goes out.

Short answer

There are two different limits behind this error. Find out which one you hit:

LimitDefaultWhere it appliesHow to change it
Project-wide email limit2 emails per hour with the built-in mailer; 30 per hour right after you switch to custom SMTPall auth emails of the projectAuthentication → Rate Limits, only after custom SMTP (or the Send Email Hook) is set up
Per-address windowone email per address every 60 seconds for magic link / OTP, signup confirmation and password resetone user clicking "send again"Authentication → Rate Limits (customizable), or debounce the button in your UI

If several different users hit the error within an hour, it is the project-wide limit. If one user hits it after clicking twice, it is the per-address window.

Why the built-in mailer runs out so fast

The email service that ships with every Supabase project is meant for trying things out. It sends at most 2 emails per hour and only to members of your organization's team. Real users need a custom SMTP provider. Sources: Supabase: custom SMTP, Supabase: rate limits.

Fix, step by step

1. Set up custom SMTP

Dashboard: Authentication → Emails → SMTP Settings (path /dashboard/project/<ref>/auth/smtp). You need from your provider:

The same settings through the Management API:

curl -X PATCH "https://api.supabase.com/v1/projects/$PROJECT_REF/config/auth" \
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "external_email_enabled": true,
    "smtp_host": "smtp.example.com",
    "smtp_port": "465",
    "smtp_user": "your-smtp-user",
    "smtp_pass": "your-smtp-password",
    "smtp_admin_email": "no-reply@yourapp.com",
    "smtp_sender_name": "Your App"
  }'

2. Raise the project limit

Right after custom SMTP is enabled, Supabase applies 30 emails per hour. Raise it in Authentication → Rate Limits, or:

curl -X PATCH "https://api.supabase.com/v1/projects/$PROJECT_REF/config/auth" \
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "rate_limit_email_sent": 300 }'

Pick a number your SMTP provider allows. Free plans of most providers cap you per day as well.

3. Stop double sends in the UI

Disable the "send again" button for 60 seconds after a send, and show the user a countdown. This removes most per-address errors.

4. In local development, do not send real email

supabase start runs a local mail catcher (Mailpit, previously Inbucket) and shows every auth email in the browser, with no limits. Use it instead of the hosted project while you build.

Which provider?

Any SMTP provider works. A few common choices:

ProviderFree tierNotes
Resend3,000 / month, 100 / daySMTP and API, official Supabase integration
Amazon SESnone since 07.2026, about $0.10 per 1,000cheapest at volume; new accounts start in a sandbox and must request production access
Brevo300 / dayEU company, SMTP and API
Fanfarly (early access)3,000 / month, 100 / daysets SMTP, the rate limit and auth templates with npx fanfarly supabase; not available yet

Disclosure: Fanfarly is built by the author of this page.

Still failing?