---
title: "Test Firebase Auth emails: verification, reset, email link · Proxy Mail QA"
description: "Test Firebase Authentication's verification, password reset and email-link sign-in emails on the web, and the daily limits: 5 sign-in links on Spark."
url: https://proxymail.qa/auth/firebase
---

1. [Home](https://proxymail.qa/)
2. [Auth providers](https://proxymail.qa/auth)

# Test Firebase Authentication emails

Firebase Authentication emails a link to verify an address, reset a password, change an address and sign in without a password. To test them, sign up with a fresh Proxy Mail QA address and the link shows up on its row. Watch the daily limits: on the free Spark plan, Firebase sends only 5 email sign-in links a day.

Updated October 17, 2026

Limits below are from Firebase’s Authentication limits page on 17 October 2026\. Check it for current details.

## What Firebase sends

| Email                | Sent by                 | Daily limit, Spark | Daily limit, Blaze |
| -------------------- | ----------------------- | ------------------ | ------------------ |
| Address verification | sendEmailVerification   | 1,000              | 100,000            |
| Password reset       | sendPasswordResetEmail  | 150                | 10,000             |
| Address change       | verifyBeforeUpdateEmail | 1,000              | 10,000             |
| Email-link sign-in   | sendSignInLinkToEmail   | 5                  | 25,000             |

Each is a link. The 5-a-day limit on email-link sign-in catches most teams testing passwordless sign-in on the free plan: after five, the emails stop until the next day.

## Test it by hand

1. Create an address in Proxy Mail QA.
2. Sign up in your app with it, or request an email sign-in link.
3. The link appears on the address’s row within seconds. Open it in the browser where you started, as email-link sign-in expects.

Check the link lands on your app, not `localhost`: the continue URL comes from your code, and its domain must be in Authentication → Settings → Authorized domains.

## Automate it

signup.spec.ts

```ts
import { test, expect } from 'proxymail-qa/playwright';

test('Firebase sign-up verifies the address', async ({ page, qa }) => {
  const { address, password } = await qa.createAddress({ password: true });
  const submitted = new Date();
  await page.goto('/signup');
  await page.getByLabel('Email').fill(address);
  await page.getByLabel('Password').fill(password);
  await page.getByRole('button', { name: 'Create account' }).click();

  const { value: link } = await qa.waitForLink(address, { type: 'verify', since: submitted });
  await page.goto(link);
  await expect(page.getByText('Your email has been verified')).toBeVisible();
});

```

For mobile apps, see [Firebase email-link sign-in for mobile apps](https://proxymail.qa/mobile/firebase-email-link). Built with Antigravity? Its [guide](https://proxymail.qa/built-with/antigravity) covers the Firebase settings it sets up. More in [Test sign-up emails in Playwright](https://proxymail.qa/solve/playwright-email-tests).

## 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)

## Questions

### Why did Firebase stop sending email sign-in links?

Firebase's limits page lists 5 email-link sign-in emails a day on the Spark plan (25,000 on Blaze), and says to add a billing account to send more. Verification emails allow 1,000 a day on Spark and password resets 150.

### Where do Firebase Auth emails come from?

From noreply@ on your project's firebaseapp.com domain unless you set your own in the console's templates. The links go to Firebase's action handler, then to the continue URL you pass, whose domain must be in the Authorized domains list.

### What about email-link sign-in in a mobile app?

That needs the link to open your app, which has its own setup after Dynamic Links shut down. See Firebase email-link sign-in for mobile apps.

## Related guides

- [Supabase AuthConfirmation, magic-link, code and reset emails, and why the default sender won't email your test addresses.](https://proxymail.qa/auth/supabase)
- [ClerkVerification codes, email links and resets, when test-mode addresses aren't enough, and the development email cap.](https://proxymail.qa/auth/clerk)
- [Auth0Verification links, passwordless codes and resets, and the built-in email provider's limits.](https://proxymail.qa/auth/auth0)
- [Auth.js (NextAuth)Magic-link sign-in through your own email provider, its expiry, and what stops the email arriving.](https://proxymail.qa/auth/authjs)
- [Better AuthVerification, reset, magic-link and email OTP emails through your own provider, and their short expiry.](https://proxymail.qa/auth/better-auth)

[See every email testing problem we solve](https://proxymail.qa/solve)

Firebase is a trademark of Google LLC. Proxy Mail QA is independent and isn't affiliated with or endorsed by them.