Guides / Firebase test numbers

Firebase test phone numbers vs a mock SMS inbox

Updated October 8, 2026
Short answer

If your app signs users in with Firebase Phone Authentication, Firebase sends the SMS itself, so use its fictional test numbers or the Firebase Auth emulator; otpmock cannot intercept those messages. If your app sends codes through an SMS provider such as Twilio, Vonage or AWS SNS, Firebase's tools don't apply, and a mock inbox like otpmock does.

What Firebase offers

Both are designed for Firebase Phone Authentication, where Firebase generates and delivers the code.

Where otpmock fits

Many apps don't use Firebase for phone verification. They generate a code themselves or call a Verify API, and send it through an SMS provider. For those apps, otpmock stands in for the provider: the SDK talks to otpmock in test environments, and tests read the code over HTTP.

Side by side

Firebase test numbers / emulatorotpmock
Applies toFirebase Phone AuthenticationApps sending via SMS provider APIs
CodeFixed per number, or emulator-generatedGenerated by your app or the emulated Verify API
Any phone number per testEmulator: yes. Console test numbers: a fixed listYes
Shared staging environmentConsole test numbers: yes. Emulator: localYes
CostFreeFree up to 100 messages a month

Using both

Some apps use Firebase for sign-in and an SMS provider for other texts, such as transaction confirmations. Use Firebase's tools for the first and otpmock for the second.

FAQ

Can otpmock receive Firebase Phone Auth codes?

No. Firebase delivers those messages itself, so there is no SDK option to redirect them. Use Firebase's test numbers or emulator.

Is otpmock affiliated with Firebase or Google?

No.

Product names are trademarks of their owners; otpmock is not affiliated with them. Descriptions of other products reflect their public documentation as of October 2026.

Try it on your own suite

The free plan includes 100 messages a month. No card required.

Get a free API key

Related guides