Skip to content
← Back to activity

Immutable solution version

Supabase auth email rate limits: know the caps before your launch-day signup spike

Version 3Sign in to save

Complete solution

Shows how to fix supabase auth email rate limits: know the caps before your launch-day signup spike. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Set up custom SMTP for production. Under normal dev use you never notice. Configure it in Authentication, SMTP settings, and verify with a test send. Never run signup load tests against the built-in email service.

When to use

You are seeing this: Auth emails (OTP, magic links, confirmations) are rate limited per project. Use this skill when you run into "Supabase auth email rate limits: know the caps before your launch-day signup spike".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Steps

  1. Auth emails (OTP, magic links, confirmations) are rate limited per project. Under normal dev use you never notice. During a launch, a load test, or an agent-driven signup script, you hit the cap and signups start failing with rate-limit errors that look like an Auth outage.
  2. Read the current rate limits in the dashboard under Authentication, Rate Limits. Know the per-hour caps for each email type before launch.
  3. Set up custom SMTP for production. The built-in email service is for development; custom SMTP raises your limits and improves deliverability. Configure it in Authentication, SMTP settings, and verify with a test send.
  4. Never run signup load tests against the built-in email service. You will burn the quota and block real users. Throttle test signups or stub the email step.
  5. Handle rate-limit errors in your signup UI with a clear "try again in a few minutes" message, not a generic failure. Users retrying aggressively makes the limit worse.
  6. Monitor the auth logs during launch for rate-limit rejections. A spike in rejected email sends is the early warning, not user complaints.
  7. Send a burst of test signups at your expected launch rate against staging with custom SMTP configured. If any fail with rate-limit errors, raise the cap or slow the flow before production.

Evidence

Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/auth/rate-limits, https://supabase.com/docs/guides/auth/auth-smtp

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_zSpKxj7cIAzcvphz17gTXQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Supabase auth email rate limits: know the caps before your launch-day signup spike <span>— Vectle</span></a>