Every figure on this page was read off firebase.google.com/pricing and the Google Cloud Firestore rate card on 1 September 2026. Firebase has only two plans, and neither of them is the reason your bill moves. The metered operations underneath are.
# free plan · no credit card required
Rates verified first-party today. No estimates, no third-party figures.
Firebase pricing has two plans: Spark at $0 a month and Blaze, which is pay as you go. Blaze has no monthly fee at all. You keep the entire Spark free allowance and pay only for usage above it, so a quiet app on Blaze can still bill $0. The cost comes from metered operations: Firestore document reads at $0.03 per 100,000, writes at $0.09 per 100,000, Cloud Functions at $0.40 per million invocations after 2 million free, and Hosting transfer at $0.15 per GB after 360 MB a day. Because nothing caps those meters, the practical risk on Firebase is a runaway bill rather than a high subscription.
Last updated September 2026
This is the line that surprises people. Firestore bills per document read, not per query, so one screen that pulls a 200 document list is 200 reads every time it loads. The free tier is 50,000 reads a day, then $0.03 per 100,000 in us-central1. Writes cost three times as much at $0.09 per 100,000 and deletes are $0.01. A chatty mobile client with a real-time listener left open is the usual reason a $0 project becomes a $60 one.
Google publishes Firestore storage as an hourly rate, which hides how it accumulates. At 730 hours in a billing month that works out to about $0.15 per GiB a month, and the first 1 GiB is free. Point in time recovery data is billed at the same rate again, so turning PITR on roughly doubles your storage line. Backup data is cheaper at $0.000041096 per GiB hour, about $0.03 per GiB a month, and restore or clone operations are $0.20 per GiB each time you run one.
The first 2 million invocations a month are free, then $0.40 per million. Invocations are rarely the expensive part. Compute is billed separately as GB seconds (400,000 free a month) and CPU seconds (200,000 free), outbound networking is $0.12 per GB after 5 GB, and every deploy burns Cloud Build minutes at $0.003 a minute after 120 free minutes a day. A function that fans out on every database write multiplies all four meters at once.
Firebase Hosting gives you 10 GB of storage and 360 MB of transfer a day at no cost, with custom domains and SSL included on both plans. Past that it is $0.026 per GB stored and $0.15 per GB transferred. The 360 MB daily allowance is the tight one: a single 2 MB hero image served 200 times exhausts it before lunch, and the meter is daily rather than monthly so a traffic spike cannot be absorbed by a quiet week.
Email, Google, Apple and the other standard sign in methods are genuinely free. Identity Platform charges nothing up to 50,000 monthly active users, then falls back to Google Cloud pricing, and SAML or OIDC federation is free only to 50 monthly active users, which is a much lower bar than most teams expect. Phone authentication is the real cost: it is billed per SMS sent at rates that vary by country, so Firebase publishes no single figure and neither will we.
Firebase now has two storage billing paths and they are not the same. Legacy *.appspot.com buckets bill as App Engine: 5 GB free, then $0.026 per GB stored, $0.12 per GB downloaded, $0.05 per 10,000 uploads and $0.004 per 10,000 downloads. Newer *.firebasestorage.app buckets bill as Cloud Storage instead, and their free quota exists only in us-central1, us-west1 and us-east1. Create a bucket in the wrong region and you pay from the first byte.
Spark costs $0 and includes 50,000 Firestore reads a day, 20,000 writes, 1 GiB stored, 10 GB of Hosting storage, 360 MB of daily transfer, unlimited Analytics, Crashlytics, Cloud Messaging, App Check, Remote Config and A/B Testing. What Spark does not give you is Cloud Functions or any paid Google Cloud service. For a large share of side projects the missing piece is Functions, not capacity.
Blaze has no plan fee. It carries the entire Spark allowance forward and charges only for usage above it, which means upgrading does not by itself cost you anything. Google also offers $300 in free credit to eligible new accounts. The one thing Blaze changes is that your ceiling disappears: on Spark an over-quota app stops working, on Blaze it keeps working and keeps billing.
Firebase does not offer a hard spending cap. Cloud Billing budgets send an alert when you cross a threshold, but an alert is a notification and not a brake, so the recommended pattern is a budget alert wired to a Pub/Sub topic and a function that disables billing on the project. That is genuinely the documented approach, and the fact that it takes a function to build a spending limit tells you how the platform is designed.
Once an app has predictable traffic, per-operation billing stops being an advantage. A 2 GB DigitalOcean droplet is $12 a month flat, runs Postgres, your API and your background jobs together, and does not charge per read. The work that made Firebase attractive, provisioning and deployment, is the part DeployManage handles, so the comparison is between a metered invoice and a fixed one.
These are the allowances and rates Google publishes on its own pricing page, not our estimates. Blaze includes the whole Spark column at no cost and bills only above it. Where Firebase defers to Google Cloud rates rather than publishing a figure, this table says so rather than inventing one.
swipe to see all columns →
| Spark (free) | Blaze (pay as you go) | |
|---|---|---|
| Monthly plan fee | $0 | $0, usage billed on top |
| Firestore document reads | 50,000 per day | $0.03 per 100,000 after the free tier |
| Firestore document writes | 20,000 per day | $0.09 per 100,000 |
| Firestore document deletes | 20,000 per day | $0.01 per 100,000 |
| Firestore stored data | 1 GiB | $0.000205479 per GiB hour, about $0.15 per GiB month |
| Firestore network egress | 10 GiB per month | 10 GiB free, then Google Cloud rates |
| Cloud Functions invocations | Not available | 2 million free per month, then $0.40 per million |
| Cloud Functions outbound data | Not available | 5 GB free, then $0.12 per GB |
| Cloud Build minutes | Not available | 120 minutes a day free, then $0.003 per minute |
| Hosting storage | 10 GB | $0.026 per GB above 10 GB |
| Hosting data transfer | 360 MB per day | $0.15 per GB above 360 MB a day |
| Custom domain and SSL | Included | Included |
| Realtime Database stored | 1 GB | $5 per GB |
| Realtime Database downloaded | 360 MB per day | $1 per GB |
| Realtime Database connections | 100 | 200,000 per database instance |
| Storage, legacy appspot bucket | 5 GB stored, 1 GB per day out | $0.026 per GB stored, $0.12 per GB out |
| Authentication, standard providers | Included | Included |
| Identity Platform monthly active users | 50,000 | 50,000 free, then Google Cloud rates |
| SAML or OIDC monthly active users | 50 | 50 free, then Google Cloud rates |
| Phone authentication | Not available | Billed per SMS sent, rate varies by country |
| Cloud Messaging, Analytics, Crashlytics | No cost | No cost |
| Test Lab, virtual devices | 10 tests per day | 60 minutes a day free, then $1 per device hour |
| Test Lab, physical devices | 5 tests per day | 30 minutes a day free, then $5 per device hour |
| Paid Google Cloud services | Not available | Available |
| Hard spending cap | Quota stops the app | None, budget alerts only |
Spark is a genuinely good free tier and this is the case it serves well. You get 50,000 Firestore reads a day, hosting with SSL on a custom domain, authentication, analytics and crash reporting without a payment method on file. The wall you hit is Cloud Functions, which Spark does not include at all, so the moment you need server side logic you are on Blaze whether or not your usage grew.
Per-operation billing suits this shape. If your app is quiet for three weeks and busy for one, you pay for the busy week and nothing for the quiet ones, which a fixed monthly server cannot match. The risk to manage is the daily Hosting transfer allowance of 360 MB, which does not roll over, and a Firestore listener pattern that turns one active user into thousands of reads an hour.
This is where metered pricing stops paying. If you serve a predictable few hundred business users every weekday, you are buying the same capacity every month and paying a per-read premium for flexibility you never use. A single $12 to $24 server running Postgres and your application usually costs less than the Firestore line alone at that scale, and the invoice does not move.
The common story is not a price rise, it is a code change: a new screen that reads a collection instead of a document, a listener that never detaches, or a function that triggers on every write and calls itself. Because Firebase has no hard cap, the first signal is the invoice. If you have reached this point, the fix is usually query shape first, and a fixed cost platform second.
Firebase costs $0 a month on the Spark plan and $0 a month in plan fees on the Blaze plan, because Blaze is pay as you go and has no subscription at all. What you pay on Blaze is usage above the free allowance, which Blaze carries over from Spark in full. An app on Blaze that stays inside the free limits genuinely bills nothing.
That structure is why the question is hard to answer with one number. There is no seat price, no tier to outgrow and no annual commitment. The invoice is the sum of six or seven metered lines, and the two that dominate for most teams are Firestore operations and Cloud Functions compute. A small production app typically lands somewhere between $0 and $25 a month. An app with an inefficient read pattern can land in the hundreds on the same amount of traffic, which is the part that makes Firebase costs feel unpredictable.
Google also gives eligible new accounts $300 in free credit, which masks the real run rate for the first few months. Check what your usage looks like once that credit is gone rather than budgeting from your first invoice.
Yes, Firebase has a free tier that does not expire and does not require a payment method. The Spark plan costs $0 and includes 50,000 Firestore document reads a day, 20,000 writes, 20,000 deletes, 1 GiB of stored data, 10 GiB of monthly egress, 10 GB of Hosting storage and 360 MB of daily Hosting transfer.
Several Firebase products are free on both plans with no usage cap worth worrying about: Cloud Messaging, Google Analytics, Crashlytics, Performance Monitoring, A/B Testing, App Distribution, In-App Messaging and Remote Config. Authentication with standard providers such as email, Google and Apple is also free.
The honest limitation is Cloud Functions. Spark does not include it, and it does not include any paid Google Cloud service either. Since most applications need server side logic eventually, the free plan tends to end for architectural reasons rather than because a project got popular. When it does, note that moving to Blaze does not cost anything on its own.
Blaze is Firebase's pay as you go plan: no monthly fee, the full Spark free tier included, and metered charges for anything above it. Upgrading to Blaze requires a billing account but does not create a bill by itself.
Blaze changes three things. It unlocks Cloud Functions and the paid Google Cloud products behind Firebase, it raises several ceilings (Realtime Database goes from 100 simultaneous connections to 200,000 per database instance), and it removes the quota wall. On Spark, an app that exceeds its allowance stops serving until the quota resets at midnight. On Blaze, it keeps serving and keeps billing.
That last difference is the whole risk profile of the plan. Spark fails closed and Blaze fails open. Teams who care more about a predictable invoice than about staying online through a spike often find that neither option is what they wanted, which is the reason a fixed monthly server keeps coming up in this comparison.
Firestore costs $0.03 per 100,000 document reads in us-central1, after a free allowance of 50,000 reads a day. Writes are $0.09 per 100,000, deletes are $0.01 per 100,000, and TTL deletes are billed at the delete rate.
The unit matters more than the rate. Firestore bills per document returned, not per query issued, so cost scales with how much data your screens pull rather than how often users tap. A dashboard that loads a 500 document collection on every visit costs 500 reads per visit. The same dashboard backed by a single pre-aggregated summary document costs one.
Storage is quoted hourly at $0.000205479 per GiB, which is roughly $0.15 per GiB a month over a 730 hour month, with the first 1 GiB free. Point in time recovery data bills at that same rate, so enabling PITR approximately doubles the storage line. Backups are cheaper at $0.000041096 per GiB hour, about $0.03 per GiB a month, while restore and clone operations cost $0.20 per GiB each.
One detail almost no third-party page mentions: Firestore operations are eligible for committed use discounts. A one year commitment cuts reads to $0.024 and writes to $0.072 per 100,000, and a three year commitment takes them to $0.018 and $0.054. If your read volume is steady, that is a 20 to 40 percent reduction on the largest line of the bill.
Almost always because of read volume, not price changes. Firebase rates are low per operation, so a large bill means a very large number of operations, and that usually traces to one of a handful of code patterns rather than to growth in users.
The four that account for most surprise invoices:
Enable the Firestore usage view in the console and look at reads per day before assuming the pricing model is at fault. If reads per active user are in the thousands, the query shape is the problem and no platform change will fix it. If reads per user are reasonable and the bill is still uncomfortable, then the pricing model genuinely does not fit your workload.
Firebase does not offer a hard spending cap. Cloud Billing budgets let you set a monthly threshold and receive an alert at chosen percentages of it, but an alert is a notification, not a brake. Usage continues and billing continues after it fires.
The documented way to build an actual limit is to route the budget alert to a Pub/Sub topic and subscribe a Cloud Function that calls the Cloud Billing API to disable billing on the project. That works, and it is genuinely what Google recommends, but it is worth being clear about what it means: you are writing and maintaining a small piece of infrastructure whose job is to switch your product off, and when it fires your application stops rather than degrades.
For a lot of teams that trade is the deciding factor. A fixed monthly server has a spending limit by construction, because the invoice is the same whether you serve one request or a million. You trade elastic scale for a number you already know, and for a steady workload that is usually the better trade.
Firebase Hosting is free up to 10 GB of storage and 360 MB of data transfer a day, then $0.026 per GB stored and $0.15 per GB transferred. Custom domains and SSL certificates are included on both Spark and Blaze at no charge, and you can host multiple sites in one project.
The daily transfer allowance is the constraint worth planning around, because it does not roll over. Ten quiet days do not bank capacity for a busy one. In practical terms 360 MB is around 180 page loads of a 2 MB page, which a modest launch day passes easily.
Firebase App Hosting, the newer product for server rendered apps, is priced separately: outgoing bandwidth is free to 10 GiB a month and then $0.20 per GiB uncached or $0.15 per GiB cached, with storage free to 5 GB and $0.10 per GB after that. If you are comparing static hosting costs across platforms, our Netlify pricing breakdown and Vercel pricing breakdown use the same first-party method on the two most common alternatives.
Firebase Authentication is free for standard sign in methods, and free up to 50,000 monthly active users once Identity Platform is enabled. Email and password, Google, Apple, Facebook and the other common providers cost nothing regardless of user count on the classic Authentication product.
Two things are billed. Above 50,000 monthly active users, Identity Platform falls back to Google Cloud rates. And SAML or OIDC federation, the enterprise single sign on path, is free only up to 50 monthly active users, which is a far lower threshold than the headline 50,000 and catches teams selling into enterprises earlier than they expect.
Phone authentication is the line that costs real money. It is billed per SMS sent, and because carrier rates differ enormously by country Google publishes no single figure. We are not going to quote one either, since any number we invented would be wrong for most readers. If phone sign in is central to your product, price it against your actual user geography before committing, and treat it as a per-message cost rather than a platform cost.
The honest comparison is not feature for feature, because Firebase gives you managed authentication, a real-time database, push messaging and analytics in one console and a bare server gives you none of that. What a server gives you instead is a fixed number.
| Cost line | Firebase Blaze | Your own server |
|---|---|---|
| Monthly fee | $0 plus usage | $12 to $48 depending on size |
| Database reads | $0.03 per 100,000 | Included |
| Database writes | $0.09 per 100,000 | Included |
| Bandwidth | $0.15 per GB after 360 MB a day | 1 to 5 TB included |
| Background jobs | $0.40 per million invocations plus compute | Included |
| Invoice predictability | Varies with traffic and code | Identical every month |
| Scales to zero | Yes | No |
| Scales up automatically | Yes | Only if you resize |
Read that table in both directions. If your traffic is genuinely spiky or you are pre-launch, scale to zero is worth real money and Firebase wins. If your traffic is steady, you are paying a per-operation premium every month for elasticity you are not using, and a $12 droplet running Postgres will handle a workload that costs considerably more in Firestore reads.
The reason teams stay on metered platforms past that crossover is usually not price, it is that nobody wants to own server setup, TLS renewal, deploys and rollbacks. That is the specific job DeployManage does: it provisions the server on your own cloud account, configures nginx, PHP or Node, databases and certificates, and deploys from git with atomic zero downtime releases. You get the fixed invoice without taking on the sysadmin work that normally comes with it. If you are weighing the same decision against a Postgres backend specifically, our Supabase pricing breakdown covers the closest open source alternative to Firebase, including what self hosting it actually requires.
Ready to stop managing servers by hand? DeployManage provisions, deploys and monitors your fleet from one dashboard.
$ get started freeFirebase costs $0 a month on Spark and $0 in plan fees on Blaze, since Blaze is pay as you go with no subscription. You pay only for usage above the free tier, which Blaze includes in full. Small production apps commonly land between $0 and $25 a month, driven mostly by Firestore reads and Cloud Functions compute.
Yes. The Spark plan is free with no expiry and no payment method required. It includes 50,000 Firestore reads a day, 20,000 writes, 1 GiB stored, 10 GB of Hosting storage and 360 MB of daily transfer, plus free Analytics, Crashlytics and Cloud Messaging. It does not include Cloud Functions.
Spark is free and fails closed: exceed a quota and your app stops until midnight. Blaze has no plan fee, includes the entire Spark allowance, unlocks Cloud Functions and paid Google Cloud services, and fails open: it keeps serving and keeps billing. Blaze also raises Realtime Database connections from 100 to 200,000.
Firestore charges $0.03 per 100,000 document reads in us-central1 after 50,000 free reads a day. Writes are $0.09 per 100,000 and deletes are $0.01. Billing is per document returned rather than per query, so a query returning 200 documents costs 200 reads.
No. Firebase offers budget alerts through Cloud Billing but no hard cap. To create a real limit you route a budget alert to a Pub/Sub topic and run a Cloud Function that disables billing on the project. That stops the application entirely rather than throttling it, so it is a circuit breaker and not a spending control.
Usually a code change rather than a price change. The four common causes are reading a whole collection where one document would do, real-time listeners that never detach, Cloud Functions triggered by their own writes, and queries that fetch wide result sets to filter client side. Check reads per day in the Firestore usage view first.
Firebase Hosting is free up to 10 GB stored and 360 MB of transfer a day, then $0.026 per GB stored and $0.15 per GB transferred. Custom domains and SSL are included on both plans. The daily transfer allowance does not roll over, so quiet days do not bank capacity for busy ones.
Standard providers such as email, Google and Apple are free at any user count. With Identity Platform enabled, the first 50,000 monthly active users are free, then Google Cloud rates apply. SAML and OIDC federation is free only to 50 monthly active users. Phone authentication is billed per SMS at country-specific rates.
The first 2 million invocations a month are free, then $0.40 per million. Compute is billed separately with 400,000 GB seconds and 200,000 CPU seconds free monthly, outbound networking is $0.12 per GB after 5 GB, and deploys consume Cloud Build minutes at $0.003 a minute after 120 free minutes a day.
The Realtime Database is a separate product from Firestore with different pricing: $5 per GB stored and $1 per GB downloaded on Blaze, with 1 GB stored and roughly 10 GB monthly download free. Blaze allows 200,000 simultaneous connections per database instance against 100 on Spark.
Google provides the Cloud Pricing Calculator, which covers Firebase's underlying services since most Blaze charges are Google Cloud charges. It is accurate for storage and compute but hard to use for Firestore, because it needs a reads-per-month figure that depends on your query shape. Measuring reads in the console for a week gives a better estimate.
No. Firebase is a proprietary Google service and cannot be run on your own infrastructure. The Local Emulator Suite runs locally for development only. Teams who want Firebase-style features on their own servers generally move to an open source alternative such as Supabase or Appwrite, or to a conventional application server with Postgres.
It depends on traffic shape. Firebase scales to zero, so it is cheaper for spiky or pre-launch workloads. For steady traffic a $12 to $24 server usually costs less than the Firestore line alone, because per-operation billing charges a premium for elasticity a predictable workload never uses.
Yes, through committed use discounts, which most pricing summaries omit. A one year commitment reduces reads to $0.024 and writes to $0.072 per 100,000, and a three year commitment takes them to $0.018 and $0.054. That is a 20 to 40 percent saving on the largest line for teams with steady read volume.
Provision a server on your own DigitalOcean, Hetzner, AWS or Vultr account, run Postgres and your application on it, and deploy from git with atomic zero downtime releases. Fixed monthly cost, no per-read billing, no budget alert wired to a kill switch.
# free plan · no credit card required