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


Before you use Firestore, you must choose a location for your database. To reduce latency and increase availability, store your data close to the users and services that need it. This location setting is your project's default Google Cloud Platform (GCP) resource location.

Note that your default GCP resource location might have been previously set, either during project creation or when setting up another service that requires a location setting (see below).

Default GCP resource location

Several services available for your app require a location setting, called your project's default Google Cloud Platform (GCP) resource location. This location is where your data is stored for GCP services that require a location setting.

The following products share the same default GCP resource location:

  • Firestore

  • Cloud Storage
    Note that your default GCP resource location only applies to your default Cloud Storage bucket. You can create multiple buckets, each with their own location.

  • Google App Engine (GAE) app
    If you set up an App Engine app, its location shares your default GCP resource location. Note that if you use Cloud Scheduler (for example, to run scheduled functions), you're required to have an App Engine app in your project.

Types of locations

You can store your Firestore data in a multi-region location or a regional location.

Note that if you already have an App Engine app with a location of either us-central or europe-west, your Firestore database will be considered multi-regional.

Multi-region locations

Select a multi-region location to maximize the availability and durability of your database.

A multi-region location consists of a defined set of regions where multiple replicas of the database are stored. Each replica is either a read-write replica which contains all of the data in the database or a witness replica which does not maintain a full set of data but participates in replication.

By replicating the data between multiple regions, data can continue to be served even with the loss of an entire region. Within a region, data is replicated across zones so that data can continue to be served within that region even with the loss of a zone.

Firestore supports the following multi-region locations:
Multi-Region Name Multi-Region Description Read-Write Regions Witness Region
eur3 Europe europe-west1 (Belgium), europe-west4 (Netherlands) europe-north1 (Finland)
nam5 United States us-central1 (Iowa), us-central2 (Oklahoma—private GCP region) us-east1 (South Carolina)

Regional locations

A regional location is a specific geographic place, such as South Carolina. Data in a regional location is replicated in multiple zones within a region. All regional locations are separated from other regional locations by at least 100 miles.

Select a regional location for lower costs, for lower write latency if your application is sensitive to latency, or for co-location with other GCP resources.

Firestore supports the following regional GCP resource locations:
Region NameRegion Description
North America
us-west2Los Angeles
us-west3Salt Lake City
us-west4Las Vegas
us-east1South Carolina
us-east4Northern Virginia
South America
southamerica-east1São Paulo
asia-east2Hong Kong


This location does not support App Engine. If you plan to use App Engine, you should choose a different location.


Location SLA

Your Firestore location type determines the Service Level Agreement (SLA) uptime percentage:

Covered Service Monthly Uptime Percentage
Firestore Multi-Region >= 99.999%
Firestore Regional >= 99.99%

Location Pricing

Your Firestore location determines the cost of database operations.

For a comprehensive explanation of pricing per region and per region type, see Understand Firestore billing.

View your project's location settings

Use one of the following methods to view the location setting for your project:

  • Run the gcloud app describe command.

  • If you have an active App Engine app, open the App Engine Dashboard in the Google Cloud console. The location information is in the upper right-hand corner of the dashboard, and it applies to both App Engine and Firestore.

    Screenshot of the previously chosen location

  • In the Firebase console, go to your Project settings.

Next steps

  • For more information about building applications to meet your latency, availability, and durability requirements, refer to Geography and Regions.