---
title: "Email limits in Supabase, Firebase, Auth0 and Clerk testing · Proxy Mail QA"
description: "Auth providers cap the emails they send for you while you build. The limits in Supabase, Firebase, Auth0 and Clerk, and how to get past them for testing."
url: https://proxymail.qa/solve/auth-email-limits
---

1. [Home](https://proxymail.qa/)
2. [What we solve](https://proxymail.qa/solve)

# Email limits in auth providers, and how to test past them

Your sign-up test passes twice, then the third run waits for an email that never comes. The app said "Check your email", the logs show nothing wrong, and the provider has quietly stopped sending. Most auth providers cap the emails they send for you, and the caps are small.

Updated 13 November 2026

These are the limits on the email each provider sends for you, from their documentation on 13 November 2026\. Check each provider’s docs for current details.

| Provider | What the built-in sender allows                                                                                  |
| -------- | ---------------------------------------------------------------------------------------------------------------- |
| Supabase | 2 emails an hour, and only to members of the project’s team                                                      |
| Firebase | Per day on the free Spark plan: 1,000 address verifications, 150 password resets, 5 email-link sign-ins          |
| Auth0    | 10 emails a minute of any type; not for production                                                               |
| Clerk    | 100 emails a month per development instance, and up to 100 recipients a day per workspace (50 in its first week) |

Each section below says how to get past the limit.

## Supabase

The built-in sender is for trying Supabase out. It sends at most 2 emails an hour, and only to addresses on your project’s team; anyone else gets “Email address not authorized”.

1. Set up custom SMTP with a provider such as Resend, Amazon SES or Postmark: in the dashboard under **Authentication → Emails**, on its SMTP settings.
2. Supabase then allows 30 emails an hour until you change it under **Authentication → Rate Limits**. Raise it for staging if your tests send more.
3. Check your SMTP provider isn’t in its own sandbox: a new Resend account without a verified domain, or Amazon SES before production access, sends only to your own addresses.

More in [Supabase sign-up problems](https://proxymail.qa/solve/supabase-auth-problems).

## Firebase

Firebase sends its own emails, with daily limits per project. On the free Spark plan, email-link sign-in stops after 5 emails a day, so a passwordless test suite runs out on its first morning. The limits are much higher on the Blaze plan (pay as you go).

Firebase’s docs don’t describe sending these emails through your own SMTP server. To send them yourself, create the link with the Admin SDK (`generateEmailVerificationLink`, `generatePasswordResetLink` or `generateSignInWithEmailLink`) and send it with your own email provider.

More in [Firebase sign-up problems](https://proxymail.qa/solve/firebase-auth-problems).

## Auth0

Auth0’s built-in email provider is for testing only: it sends at most 10 emails a minute, of any type, with no custom templates or sender address. A test suite running in parallel can pass that in seconds.

Set up your own under **Branding → Email Provider**: switch on **Use my own email provider**, then pick SMTP or one of the listed providers.

More in [the Auth0 guide](https://proxymail.qa/auth/auth0).

## Clerk

Development instances can send 100 emails a month, and each workspace has a daily cap on recipients across its development instances (50 a day for the first 7 days, then 100). Over it, sign-ups that need an email fail with `dev_daily_email_recipient_limit_exceeded`.

Test mode lets `+clerk_test` addresses verify with the code `424242` without an email, and they don’t count towards the caps. Since late October 2026, Clerk sends no email at all to those addresses in test mode, so tests that need the real email (a sign-in link, an invitation) use a normal address and count towards the cap.

Clerk has no SMTP setting. To send through your own provider, switch off **Delivered by Clerk** on a template and send the email from the `email.created` webhook.

More in [the Clerk guide](https://proxymail.qa/auth/clerk).

## Use the allowance well

- **One address per test.** A new Proxy Mail QA address each run means a retry never waits for an email that went to a reused address, and every email you pay for is one you check.
- **Read the delivery check before retrying.** If nothing reached the address, the provider didn’t send it: retrying only uses more of the allowance.
- **Keep the provider’s test shortcuts for unit tests.** Fixed codes and test modes skip the email. Keep a few end-to-end tests that receive the real one, so you know your users get it.

## Automating this?

When a wait finds nothing, check\_delivery (MCP) or the address's delivery check in the app says whether anything reached the address at all. Nothing at all usually means the email never left the provider.

[Node.js client](https://proxymail.qa/docs/node) [Python](https://proxymail.qa/docs/python) [Set up your coding agent](https://proxymail.qa/docs/api#agent-setup)

## Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

[Create a free account](https://app.proxymail.qa/?mode=signup&from=site-solve-auth-email-limits)

## Questions

### Do failed sign-ups count towards the limit?

Usually yes: the limit counts emails sent, so every attempt that sends a code or link uses one, whether or not the test passed. Retries in a failing test suite use the allowance fastest.

### Why does it work for me but not for my testers?

In Supabase, the built-in sender only emails members of your project's team. You're on the team, so your test works; a tester's address, or a Proxy Mail QA address, gets "Email address not authorized".

### Can I raise the built-in limit instead?

In Supabase, the email limit can be changed only once you use your own sender (custom SMTP or a Send Email hook). Firebase's daily limits go up on the Blaze plan. For Auth0 and Clerk, send through your own provider.

### Where are these numbers from?

From each provider's documentation on 13 November 2026\. They change without much notice, so check the linked pages before you rely on them.

## Related guides

- [Test sign-up and email verification](https://proxymail.qa/solve/email-verification-testing): A fresh, private address for every sign-up test, with the verification link or code ready the moment it lands.
- [Test OTP and one-time login codes](https://proxymail.qa/solve/otp-code-testing): Codes pulled out of the email with a Copy button and a countdown when the email says how long they last.
- [Test magic links and passwordless sign-in](https://proxymail.qa/solve/magic-link-testing): Single-use links that are never opened or prefetched on our side, so they still work when you click them.
- [Test password reset emails](https://proxymail.qa/solve/password-reset-testing): Request, receive and use reset links, and keep the new password saved next to the test account.
- [Stop sharing one Gmail inbox for QA](https://proxymail.qa/solve/shared-test-inbox): Private, disposable addresses for every tester instead of one shared mailbox and a pile of plus-addresses.
- [Stop using Gmail for test codes](https://proxymail.qa/solve/gmail-test-inbox): Why reading codes from Gmail over its API or IMAP keeps breaking your tests, and how one address per test removes the inbox from the problem.
- [Let test addresses through a disposable-email block](https://proxymail.qa/solve/disposable-email-blocks): Keep the block for real users and let your test domains through in development and staging, with one setting you can't ship by mistake.
- [CAPTCHA, Google and Apple sign-in in tests](https://proxymail.qa/solve/captcha-and-social-sign-in-tests): Published test keys for reCAPTCHA, hCaptcha and Turnstile, and what to test instead of automating Google and Apple sign-in.
- [Take QA notes by voice with Wispr Flow](https://proxymail.qa/solve/voice-notes-wispr-flow): Dictate what each test account is for, its state and what you found, straight into its notes, in seconds.
- [Test phone-first sign-up without real SMS](https://proxymail.qa/solve/phone-first-sign-up-testing): Test numbers with fixed codes, a test-mode code kept out of release builds, and why virtual numbers usually fail.
- [Test sign-up for people in China](https://proxymail.qa/solve/china-sign-up-testing): Real-name rules, a 姓名 field and province menus, a safe test code, and 身份证 numbers that can't be anyone's.
- [Test sign-up for people in Japan](https://proxymail.qa/solve/japan-sign-up-testing): Furigana fields, 全角 and 半角, postcode lookups and LINE sign-in, with test accounts that have Japanese names.
- [Made-up test accounts, not masked production data](https://proxymail.qa/solve/synthetic-test-data): A masked copy of production still holds real people. Test sign-up with made-up accounts that no one owns instead.
- [Test sign-up for people in India](https://proxymail.qa/solve/india-sign-up-testing): Test accounts with one name, PIN codes that agree with the city, phone-first sign-up, Hindi labels, ID fields and card mandates.
- [Test sign-up for people in Pakistan](https://proxymail.qa/solve/pakistan-sign-up-testing): Test accounts with Pakistani names in both scripts, CNIC fields that never hold a real number, and phone-first sign-up.
- [Fill phone and ID fields safely](https://proxymail.qa/solve/phone-id-and-tax-number-fields): Numbers set aside for fiction, your app's own test numbers, ID values that never match a real person, and KYC sandbox values, filled the same way by agents and tests.
- [Verification link points to localhost:3000](https://proxymail.qa/solve/localhost-links): Why emails from staging link to localhost, how to fix it in Supabase, Firebase and other stacks, and how we flag it.
- [Common Supabase sign-up and login problems](https://proxymail.qa/solve/supabase-auth-problems): Emails that never arrive, links that expire or sign nobody in, and sign-ups that fail, with the fix for each.
- [Common Firebase sign-up and login problems](https://proxymail.qa/solve/firebase-auth-problems): Missing verification and reset emails, verified users who still look unverified, failing links and sign-up limits, with the fix for each.
- [Sign-up and login problems in vibe-coded apps](https://proxymail.qa/solve/vibe-coded-login-problems): The login bugs AI-built apps usually ship with: emails only you receive, links to the preview, missing pages, and what to ask the builder.
- [Check that one user can't see another's data](https://proxymail.qa/solve/vibe-coded-app-data-leaks): A curl with the anon key for tables anyone can read, and two signed-up accounts for policies that let every user read every row.
- [Triage sign-up and login bug reports with an agent](https://proxymail.qa/solve/bug-report-triage): An agent signs up with a new test address, watches the inbox, and answers replicated, not replicated or inconclusive, with the evidence.
- [A self-improvement loop for agents that build sign-up](https://proxymail.qa/solve/agent-self-improvement-loop): The agent builds, signs up with a test address, reads what the email did, fixes its own work and runs again. Proxy Mail QA is the tool it checks with.
- [Test sign-up emails in Playwright](https://proxymail.qa/solve/playwright-email-tests): A complete Playwright test for sign-up codes and links, from a fresh inbox to the report on the pull request.
- [Test sign-ups over several screens](https://proxymail.qa/solve/multi-step-sign-up-testing): One test account across every screen of the sign-up, with your form's own questions filled the same way each time.
- [Test sign-up emails in Cypress](https://proxymail.qa/solve/cypress-email-tests): A complete Cypress test for sign-up links and codes, with the email waits running as Cypress tasks.
- [Test sign-up emails with pytest](https://proxymail.qa/solve/pytest-email-tests): A complete pytest test for sign-up codes and links, with Playwright for Python or Selenium and a one-file helper.
- [Test coupon codes and welcome offers](https://proxymail.qa/solve/coupon-code-testing): The coupon with its discount, end date and arrival time, what checkout did with it, and a failure when an expired or reused one is accepted.
- [Test unsubscribe links and one-click unsubscribe](https://proxymail.qa/solve/unsubscribe-testing): The unsubscribe headers and link checked on every marketing email, and a watch that flags any marketing after unsubscribing, with no time limit.
- [Test that a welcome offer can't be claimed twice](https://proxymail.qa/solve/welcome-offer-abuse): Versions of one address that reach the same inbox, and a check that fails when the same person got the offer more than once.
- [AI sign-up page review](https://proxymail.qa/solve/ai-sign-up-page-review): Let an agent check the sign-up through to the email: delivery, the link, how it was sent, and that only one arrives.
- [AI registration page review](https://proxymail.qa/solve/ai-registration-page-review): An agent tries every field with values made for it, then finishes the registration through the email.
- [Review a sign-up page by hand](https://proxymail.qa/solve/how-to-review-my-sign-up-page): A checklist for your browser and phone, in the order that finds the most problems.
- [Review a simple sign-up form](https://proxymail.qa/solve/review-a-simple-sign-up-form): 12 checks for a form with an email, a password and perhaps a name.
- [Review a multi-page sign-up form](https://proxymail.qa/solve/review-a-multi-page-sign-up-form): One test account across every screen, and the verification email wherever it comes.
- [Review a financial sign-up form](https://proxymail.qa/solve/review-a-financial-website-sign-up-form): The emails, age and country rules and awkward values in a financial sign-up, and what needs other tools.
- [An email address for testing registration](https://proxymail.qa/solve/email-for-checking-my-registration-form): A new, real address for every registration try, with the code or link ready to use.
- [An email address for testing sign-in](https://proxymail.qa/solve/email-for-checking-my-sign-in-form): Test accounts with saved passwords and an inbox for codes, magic links and resets.
- [How long should a password be?](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be): NIST's numbers for password length and rules, and test passwords to check yours.
- [No error for a password that breaks the rules](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors): The eight usual causes of a silent password field, and how to tell which one it is.
- [Help me check my website](https://proxymail.qa/solve/help-me-check-my-website): A whole-site check in an afternoon, in the order that finds the costliest problems first.
- [Tools to build and check a website](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website): A toolkit by area, most of it free and none of it ours, except for account emails.
- [What tools do I need for a website?](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website): The full list, then which parts a simple site can skip.

[Built your app with an AI tool? Pick yours](https://proxymail.qa/built-with)
