Understand App Hosting costs

bookmark_border Stay organized with collections Save and categorize content based on your preferences.

App Hosting requires a project with the Firebase Blaze pricing plan enabled. This plan has the following no-cost limits for Google Cloud products invoked by App Hosting:

 

No-cost usage is aggregated across projects by billing account and resets every month; you are billed only for usage past the limits.

Calculate costs

Starting June 14, 2025, you begin incurring costs for your Firebase App Hosting project once you exceed the pay-as-you-go Blaze pricing plan allowances. You will be charged for the following Firebase App Hosting line items:

• Uncached Outgoing Bandwidth refers to the data transferred directly from the origin servers of the Firebase App Hosting service to fulfill user requests. Origin servers are located between an App Hosting backend's Cloud Run service and Cloud CDN. This occurs when the requested content is not already stored in the Cloud CDN cache (that is, it's uncached). Consequently, the origin server must fetch the data and send it to the user.

  This process incurs costs for two primary reasons:

  1. Populating Cloud CDN caches: When a user requests uncached content, it triggers a process to fetch that data from the origin server and store a copy in the Cloud CDN cache for future requests. This initial transfer of data from the origin to the CDN contributes to the overall cost.
  2. Transferring data to the end user: Once the content is available (either directly from the origin or from the CDN after the initial cache population), it must be transmitted to the end user's device at the requested destination. This data transfer also contributes to the cost.

• Cached Outgoing Bandwidth refers to the data transferred in gibibytes from Cloud CDN's caches to the end user's device at the requested destination.

You will also be charged for the usage of the underlying Google Cloud products that your backend uses:

• Cloud Run
• Cloud Build
• Artifact Registry
• Secret Manager
• Cloud Logging

The exact price points for these line items can be viewed on our pricing page.

Billing examples

The cost of running a dynamic Web app on App Hosting can vary widely depending on factors like traffic, storage, and specific services used. The examples in this section are provided as a general guide, but your actual costs may differ.

Costs in our example are based on these assumptions about the configuration and usage of the Web app:

Example cost calculations assume that each visit to the Web app has these characteristics:

With these assumptions, we can extrapolate the following costs for this example scenario. At a level of 10k visits there are virtually no costs, with costs of any significance beginning to accrue at the 1M visit level.