Mendlark / Guides

Supabase "email rate limit exceeded": how to fix it

Sign-up, a magic link or a password reset fails with AuthApiError: email rate limit exceeded (HTTP 429, code over_email_send_rate_limit). Often the third person to sign up in an hour hits it, or you hit it yourself while testing. It is a limit on how many auth emails your project may send, not a bug in your form.

Stuck on this? Get it fixed for €49.

Fixed in 48 hours or you don't pay. Launch deal for the first 5 customers (normally €79). You get the tested fix as a pull request, so nothing changes until you merge it.

Get it fixed for €49

1. You are still on Supabase's built-in email sender

Every new project sends auth emails through a built-in sender meant for testing. Supabase currently caps it at about 2 emails per hour for the whole project (the number has changed before and can change without notice), and it only delivers to members of your Supabase team. Every confirmation, magic link, invite and reset counts, including your own tests. If your app has real users, this is almost always the cause.

2. Connect custom SMTP (the real fix)

In the Supabase dashboard open Authentication → Emails → SMTP settings and switch on custom SMTP with a provider such as Resend, Postmark, SendGrid or Amazon SES. Use a sender address on a domain you have verified with that provider (SPF and DKIM set up), or the emails will land in spam even after the error goes away. Lovable and Bolt apps use the same Supabase settings, so nothing changes in your app code.

3. Raise the limit after switching on SMTP

When you save custom SMTP, Supabase starts you at a low limit (around 30 emails per hour) to protect a new sending domain. If you still see the error after a launch or a busy hour, open Authentication → Rate Limits and set the email limit to your busiest real hour plus room for a launch. Don't set a huge number "just in case": a bot hammering your reset form could then send thousands of emails from your domain.

4. "You can only request this after N seconds"

The same 429 and code can also mean a per-person cooldown: Supabase makes one email address wait about 60 seconds between sign-up, magic-link or reset emails. Custom SMTP does not remove this, and it is there on purpose. Disable the button for a minute after a click and show "Check your inbox, you can resend in 60 seconds" instead of letting people tap again.

5. Show a friendly message instead of a raw error

const { error } = await supabase.auth.signInWithOtp({ email });
if (error?.code === 'over_email_send_rate_limit') {
  showMessage('Too many emails just now. Please wait a minute and try again.');
} else if (error) {
  showMessage('Something went wrong. Please try again.');
}

6. Local development with the Supabase CLI

If you only see it locally, the CLI has its own limit. Raise email_sent under [auth.rate_limit] in supabase/config.toml and restart, or open the local Inbucket/Mailpit inbox to check emails are actually going out.

Quick checklist

  • Custom SMTP switched on with a verified sending domain
  • Email limit on the Rate Limits page matches your real busiest hour
  • Resend button waits 60 seconds between clicks
  • Friendly message for over_email_send_rate_limit
  • Test emails arrive in the inbox, not spam

Stuck on this? Get it fixed for €49.

Fixed in 48 hours or you don't pay. Launch deal for the first 5 customers (normally €79). You get the tested fix as a pull request, so nothing changes until you merge it.

Get it fixed for €49

Still stuck?

Mendlark fixes this kind of problem for a fixed €49 (launch price, normally €79). We agree the problem first, test the fix and send it as a pull request, so nothing changes in your app until you merge it. If we can't fix it, you don't pay. Get the €49 fix, or start with a free scan.

Not sure what else is wrong? Paste your app link into the free instant check and get a plain-English list of problems in seconds.