Fix guide · updated 2026-11-15
Supabase "email rate limit exceeded" error
AuthApiError: email rate limit exceeded · over_email_send_rate_limit · 429
You tested your sign-up form a few times and Supabase now answers "email rate limit exceeded". Or your app is live and new users can't sign up or reset their password. Your code isn't broken: Supabase caps how many emails your project sends, and on its built-in email service the cap is 2 an hour for the whole project. Here's what the error means, what counts against the limit, and how to fix it for good.
What the error means
We read the email code in Supabase Auth (internal/api/mail.go). Two different limits answer with HTTP 429 and the same code, over_email_send_rate_limit:
- "email rate limit exceeded" is the limit for the whole project. Your project has sent its allowance of emails for the hour, and Supabase refuses every new one, for every user, until the count goes back down.
- "For security purposes, you can only request this after N seconds." is the limit for one person. The same address asked for the same kind of email too soon. The default wait is 60 seconds, and N is what's left of it.
The first one is the one that hurts: one user, or one afternoon of testing, can use up the hour for everybody.
1. You're still on Supabase's built-in email service
This is the cause almost every time. Until you connect your own email provider, Supabase sends with a built-in service meant for trying things out. It sends only 2 emails an hour for the whole project (Supabase's docs, today's value; they say it can change without notice), and only to members of your Supabase organization. Any other address gets Email address "…" cannot be used as it is not authorized.
Every email Supabase Auth sends counts against those 2: a sign-up confirmation, a magic link or one-time code, a password reset, an invite, an email change. Three test sign-ups in an hour are enough.
The fix is custom SMTP: an email service such as Resend, Postmark, Brevo or Amazon SES, entered under Authentication → SMTP Settings (under Emails). After that, Supabase sends to every address, starting at 30 emails an hour. To raise that, go to Authentication → Rate Limits → Rate limit for sending emails. On the built-in service that field is locked: the dashboard says "The built-in email service has a fixed rate limit." Our guide on "Error sending confirmation email" walks through the SMTP setup step by step.
2. Your app sends more emails than you think
Each of these sends a new email, and each one counts:
- Signing up again with an address that isn't confirmed yet. Supabase doesn't refuse it: it sends the confirmation again (we read
signup.go). A user who signs up again every few minutes because the first email hasn't come uses one more email each time. - A form that submits twice. The first request sends the email. The second usually gets "For security purposes…", and the user sees that error even though the email is on its way.
- A "Resend email" button with no wait. Impatient users press it until something happens.
- An email sent when a page loads. Code that calls
signInWithOtporresetPasswordForEmailin auseEffector on page load sends again on every visit and every reload.
For test accounts, skip the sign-up form. Create them from a server with your service role key (never in browser code). createUser never sends an email, so nothing counts:
import { createClient } from '@supabase/supabase-js';
const admin = createClient(process.env.SUPABASE_URL, process.env.SUPABASE_SERVICE_ROLE_KEY);
await admin.auth.admin.createUser({
email: 'test1@example.com',
password: 'a-long-password',
email_confirm: true, // already confirmed: no email needed
});
3. "For security purposes, you can only request this after N seconds."
This one is about one address, not the whole project. Supabase remembers when it last sent each kind of email to a person and refuses another of the same kind until the wait is over: one timer for the confirmation, one for the email change, and one shared by the password reset and the magic link. So a magic link right after a reset email is refused too.
Nothing is wrong. Show the user a countdown and turn the button back on when it ends. Once you use custom SMTP, you can change the 60 seconds under Authentication → Rate Limits → Minimum interval per user.
4. "Resend" says it worked, but no email arrives
Not a rate limit, but it often comes right after one. supabase.auth.resend({ type: 'signup', email }) answers with success and sends nothing when the address is already confirmed, or when no account uses that address at all (we read resend.go). Answering the same way whether or not the account exists also keeps strangers from using the form to find out who has an account. If the person is already confirmed, they can simply sign in. Our guide on "Email not confirmed" shows how to check an account in the SQL editor.
Turning off "Confirm email" is not the fix
With "Confirm email" off, sign-ups stop sending confirmation emails, so the error goes away for them. Supabase's code even skips the hourly count in that case today, but a comment in that same code says this will be removed. And a live app without confirmation lets anyone sign up with an address they don't own, and still needs email for password resets. Use it for a quick test, then turn it back on and set up custom SMTP.
If an AI tool built your app
Give your AI tool this prompt, so users see a clear message instead of a raw error:
When a Supabase auth call returns the error code over_email_send_rate_limit (HTTP 429), don't retry it automatically. If the message starts with "For security purposes", read the number of seconds in it, show "Please wait N seconds before asking for another email", and disable the button with a countdown until then. Otherwise show "We can't send more emails right now. Please try again in a few minutes." After any email is sent, disable the "Resend" button for 60 seconds with a countdown. Make sure the sign-up, magic link and password reset forms can't be submitted twice while a request is running, and that no email is sent on page load. Don't change anything else.
Then do the dashboard step yourself, since the AI can't: custom SMTP (case 1), and the hourly number under Authentication → Rate Limits.
Not quite your error?
- Emails never arrive and the logs say "not authorized": Supabase "Error sending confirmation email".
- Password resets or magic links fail with "Error sending recovery email" or "Error sending magic link email" (each failed try still counts against the hourly limit): Supabase "Error sending recovery email".
- Supabase refuses the address itself with Email address "x" is invalid: Supabase "Email address is invalid".
- Sign-in answers "Email not confirmed": Supabase "Email not confirmed".
- The link in the email says it's invalid or expired: Supabase "Email link is invalid or has expired".
- Sign-ins or sign-ups answer "Request rate limit reached" (HTTP 429): Supabase "Request rate limit reached".
- Your provider says you can only send testing emails to yourself: Resend "You can only send testing emails to your own email address".
Still stuck?
Open the Auth logs in your Supabase dashboard at the time of the error. Each refused email is there with its 429 and its message, so you can see which limit you hit and which request caused it: a sign-up, a reset, a magic link. If you already use custom SMTP and still see "email rate limit exceeded", compare the number under Authentication → Rate Limits with how many emails your logs show in the last hour. If your email provider itself refuses a message (its own daily limit, an unverified domain), the error is a different one, "Error sending confirmation email" or similar, and the provider's own logs say why.
Other Supabase problems? See Supabase fixes.