Firebase Pricing: Plans, Free Tier, and Cost Examples (2026)

Pricing overview

Firebase utilizes a tiered pricing structure primarily composed of a free tier, known as the Spark Plan, and a pay-as-you-go tier called the Blaze Plan. This model allows developers to begin building applications without upfront costs and scale their usage as their application grows. The cost for the Blaze Plan is determined by the consumption of various resources across Firebase's integrated services, including Cloud Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Hosting. Specific metrics like database reads, writes, storage capacity, function invocations, and outbound network traffic contribute to the overall billable amount Firebase pricing page.

Many Firebase services, such as Firebase Authentication and Firebase Cloud Messaging, offer significant free allowances even within the paid Blaze Plan, ensuring that foundational app components remain cost-effective. Analytics and Crashlytics are generally free services with no direct associated costs, as they are primarily data collection and reporting tools Firebase documentation overview. Understanding the specific usage metrics for each service is crucial for predicting and managing costs effectively.

Plans and tiers

Firebase offers two main pricing plans: the Spark Plan and the Blaze Plan. Each plan is designed to cater to different stages of application development and scale requirements.

Spark Plan

The Spark Plan is Firebase's free tier, offering a substantial set of features and generous usage limits suitable for development, testing, and small-scale applications. It provides access to most Firebase services, including:

• Cloud Firestore: Provides Free tier limits for document reads, writes, deletions, and stored data. For example, 50k document reads, 20k document writes, 20k document deletions per day, and 1 GB of stored data Cloud Firestore pricing.
• Realtime Database: Includes 10 GB of stored data, 100 simultaneous connections, and 1 GB of network egress per month.
• Authentication: Allows for 10k phone authentications per month. Email/password authentication is free.
• Cloud Functions: Provides 125k invocations per month, 40k GB-seconds, and 20k GHz-seconds computation time.
• Hosting: Includes 10 GB of storage and 360 MB/day data transfer.
• Cloud Storage: Offers 5 GB of stored data, 1 GB/day network egress, and 20k read/50k write operations per day.

The Spark Plan is ideal for individuals, startups, and projects in their initial development phases that need a robust backend without immediate financial commitment.

Blaze Plan

The Blaze Plan is the pay-as-you-go tier, designed for applications that exceed the Spark Plan's free limits or require advanced features not available in the free tier, such as extended network egress, higher database throughput, or Google Cloud services integration. Under the Blaze Plan, costs are calculated based on actual resource consumption, with specific rates for each service. All Spark Plan free limits are still included monthly within the Blaze Plan before any charges apply, providing a buffer for growing applications Firebase Blaze Plan details.

Key services under the Blaze Plan and their typical cost drivers include:

• Cloud Firestore: Charges based on document reads, writes, deletions, and stored data. Prices vary by region. For instance, in us-central1, document reads might be $0.06/100k, writes $0.18/100k, and deletions $0.02/100k beyond free limits Cloud Firestore pricing.
• Realtime Database: Billed by stored data ($5/GB/month), database connections ($0.50/50k concurrent connections/month), and network egress ($1/GB).
• Cloud Functions: Costs are based on the number of invocations, computation time (GB-seconds and GHz-seconds), and outbound network traffic. After the free tier, invocations might be $0.40/million, and computation is calculated based on allocated memory and CPU Google Cloud Functions pricing.
• Cloud Storage: Charges for stored data ($0.026/GB/month in us-central1), network egress, and operations (e.g., $0.004/10k Class A operations).
• Hosting: Beyond free limits, storage is $0.026/GB/month and data transfer is $0.15/GB.

Here's a comparison table of the key features and limits of the two plans:

Free tier and limits

The Firebase Spark Plan serves as a comprehensive free tier that covers a substantial portion of typical development and small-scale application needs. It offers free quotas for most core Firebase services, enabling developers to build and deploy applications without incurring costs until specific usage thresholds are met. These thresholds are reset monthly, providing a consistent free allowance Firebase free tier limits.

Key free limits include:

• Cloud Firestore: 1 GB stored data, 50,000 document reads/day, 20,000 document writes/day, 20,000 document deletions/day.
• Realtime Database: 10 GB stored data, 100 simultaneous connections, 1 GB network egress/month.
• Authentication: 10,000 phone authentications/month. Email/password authentication is always free.
• Cloud Functions: 125,000 invocations/month, 40,000 GB-seconds, 20,000 GHz-seconds of computation time.
• Hosting: 10 GB storage, 360 MB data transfer/day.
• Cloud Storage: 5 GB stored data, 1 GB network egress/day, 20,000 Class A operations/day, 50,000 Class B operations/day.
• Firebase ML: 1,000 text recognition, barcode scanning, and label detection operations/month.
• Test Lab: 10 Android test runs/day, 5 iOS test runs/day.

These limits are designed to support a wide range of projects, from personal portfolios to small business applications, without requiring a credit card initially. Exceeding these limits automatically transitions the project to the Blaze Plan, where usage beyond the free thresholds is billed at the standard pay-as-you-go rates. Users can set budget alerts in the Google Cloud Console to monitor spending and avoid unexpected charges Google Cloud budget alerts documentation.

Real-world cost examples

Understanding Firebase pricing often benefits from concrete examples. Here are a few scenarios illustrating potential costs under the Blaze Plan:

Example 1: Small Social App (Moderate Usage)

Consider a small social application with approximately 1,000 active users daily. Each user might perform 10 database reads and 2 writes on average when interacting with the app. The app also uses Cloud Functions for backend logic (e.g., sending notifications) and Cloud Storage for user profile pictures.

• Cloud Firestore:
  • Reads: 1,000 users * 10 reads/user * 30 days = 300,000 reads/month. (Exceeds free 50k reads/day * 30 days = 1.5M reads/month, so this is within free tier)
  • Writes: 1,000 users * 2 writes/user * 30 days = 60,000 writes/month. (Exceeds free 20k writes/day * 30 days = 600k writes/month, so this is within free tier)
  • Storage: Assume 5 GB for user data. (Exceeds free 1 GB, so 4 GB paid at $0.18/GB/month = $0.72)
• Cloud Functions:
  • Invocations: Assume 500,000 invocations/month (for notifications, data processing). (Exceeds free 125k, so 375k paid at $0.40/million = $0.15)
  • Computation: Assume average 128MB memory, 1 second execution. 500,000 invocations * 128MB * 1s = 64,000 GB-seconds. (Exceeds free 40k GB-seconds, so 24k GB-seconds paid at $0.0000025/GB-second = $0.06)
• Cloud Storage:
  • Stored Data: 20 GB for profile pictures and media. (Exceeds free 5 GB, so 15 GB paid at $0.026/GB/month = $0.39)
  • Network Egress: Assume 50 GB/month. (Exceeds free 1 GB/day * 30 = 30 GB/month, so 20 GB paid at $0.12/GB = $2.40)
• Estimated Monthly Cost: Approximately $0.72 + $0.15 + $0.06 + $0.39 + $2.40 = ~$3.72.

Example 2: E-commerce Backend (High Usage)

An e-commerce application with 10,000 daily active users, frequently updating product inventory, processing orders, and serving images. Users perform 20 reads and 5 writes daily, and the system handles 1 million Cloud Function invocations for order processing and inventory updates. Heavy use of Cloud Storage for product images.

• Cloud Firestore:
  • Reads: 10,000 users * 20 reads/user * 30 days = 6,000,000 reads/month. (Exceeds free 1.5M reads/month. Paid: 4.5M reads at $0.06/100k = $2.70)
  • Writes: 10,000 users * 5 writes/user * 30 days = 1,500,000 writes/month. (Exceeds free 600k writes/month. Paid: 900k writes at $0.18/100k = $1.62)
  • Storage: 50 GB. (Exceeds free 1 GB. Paid: 49 GB at $0.18/GB/month = $8.82)
• Cloud Functions:
  • Invocations: 1,000,000 invocations/month. (Exceeds free 125k. Paid: 875k at $0.40/million = $0.35)
  • Computation: Assume 256MB memory, 2 seconds execution. 1,000,000 invocations * 256MB * 2s = 512,000 GB-seconds. (Exceeds free 40k GB-seconds. Paid: 472k GB-seconds at $0.0000025/GB-second = $1.18)
• Cloud Storage:
  • Stored Data: 500 GB for product images. (Exceeds free 5 GB. Paid: 495 GB at $0.026/GB/month = $12.87)
  • Network Egress: 500 GB/month. (Exceeds free 30 GB. Paid: 470 GB at $0.12/GB = $56.40)
• Estimated Monthly Cost: Approximately $2.70 + $1.62 + $8.82 + $0.35 + $1.18 + $12.87 + $56.40 = ~$83.94.

These examples highlight that while the free tier is generous, scaling applications significantly will lead to increased costs, primarily driven by database operations, storage, and network egress. It's important to monitor usage regularly and optimize database queries and data transfer to manage costs effectively. Google Cloud's pricing calculator can help estimate costs more precisely for specific workloads Google Cloud Pricing Calculator.

How the pricing compares

Firebase's pricing model, particularly its generous free tier and pay-as-you-go structure, positions it competitively against other Backend-as-a-Service (BaaS) and cloud providers. When comparing Firebase to alternatives like AWS Amplify, Supabase, or Azure Mobile Apps, several factors come into play.

AWS Amplify

AWS Amplify, a development platform from Amazon Web Services, also offers a pay-as-you-go model. Its pricing is granular, tied to the underlying AWS services it orchestrates, such as AWS AppSync for GraphQL APIs, Amazon S3 for storage, AWS Lambda for serverless functions, and Amazon Cognito for authentication. AWS provides a free tier for many of these services, similar to Firebase's Spark Plan, but the combined cost can become complex to track across multiple services AWS Amplify pricing details. Firebase often presents a more unified cost structure for its core services, potentially simplifying cost predictions for developers focused solely on mobile and web application backends.

Supabase

Supabase is an open-source Firebase alternative that provides a PostgreSQL database, authentication, instant APIs, and storage. Supabase offers a free plan with limits on database size, number of rows, and API requests, along with a Pro Plan and Enterprise Plan. The Pro Plan starts at a fixed monthly fee (e.g., $25/month) and includes higher limits, with additional usage billed on top Supabase pricing information. This fixed-fee component can offer more predictable costs for some users compared to Firebase's purely usage-based model once free limits are exceeded. However, for smaller projects or those with highly variable usage, Firebase's pay-as-you-go might be more economical up to a certain point.

Microsoft Azure Mobile Apps

Azure Mobile Apps, part of Azure App Service, provides features for building mobile backends, including authentication, push notifications, and offline data sync. Azure's pricing is also pay-as-you-go, based on the App Service plan chosen (e.g., Free, Shared, Basic, Standard, Premium) which dictates compute resources, memory, and storage, plus additional costs for specific services like Azure SQL Database, Azure Notification Hubs, and Azure Storage Azure Mobile Apps pricing. The complexity of Azure's broader ecosystem means developers need to factor in costs from various integrated services, similar to AWS, which can be more intricate than Firebase's more opinionated, consolidated service offerings.

In summary, Firebase generally offers a very accessible entry point with its free Spark Plan and a straightforward pay-as-you-go model for scaling. While alternatives provide competitive features and pricing, Firebase's integrated suite and clear cost drivers for core services often make it a preferred choice for developers prioritizing ease of use and predictable scaling within the Google Cloud ecosystem.