FREE TOOL
Supabase “email rate limit exceeded” checker: which limit did you hit?
Updated
Paste the error your app got. The checker tells you which Supabase email or request limit it is, and links the fix. It runs in your browser; nothing is sent.
1. Paste the error or response
2. Two questions
Read more
- Supabase: Rate limits
- Supabase: Send emails with custom SMTP
- Supabase: Auth error codes
- “email rate limit exceeded”: which limit you hit and how to fix it
FAQ
Why do I hit the limit after only a few test sign-ups?
This was asked in Supabase discussion #15880, where the answer was that the built-in sender is for basic testing only and you need your own SMTP. Supabase's current documentation gives the built-in limit as 2 emails per hour for the project.
Can I raise the built-in limit of 2 emails per hour?
Only by moving off it: Supabase says that limit can only be changed by using your own SMTP or a Send Email hook, after which you adjust the email limit on the Rate Limits page.
How can I test sign-up without burning the limit?
Supabase suggests an email testing tool such as Mailtrap while testing, and a real SMTP provider for production. You can also develop against local Supabase and read the emails in Mailpit.
Is what I paste sent to VibeFix?
No. The checker runs in your browser with a script on this page. Nothing you paste is sent or stored.
Fixed in your code, then tested live.
App broke after you published it? Our AI agent fixes it in your code, then tests your live app again so you see the result yourself. The first check is free.
The numbers are Supabase’s documented defaults as of 1 November 2026. Supabase’s docs say the built-in limit can change without notice, so check the current pages before relying on them.
VibeFix is independent. Supabase, Mailpit and Mailtrap are trademarks of their owners.