Select locations for products and resources in your project

Several Firebase products require a location setting:

Google Analytics — If you enable Google Analytics in your Firebase project, you're prompted to select an Analytics reporting location. This location represents the country or region of your organization. Your Analytics location, in turn, sets the currency for revenue reporting.

Note: Your Analytics reporting location does not affect where Google may process and store customer data for Firebase. It also does not affect the options for your default Google Cloud Platform (GCP) resource location.
Cloud Firestore and Cloud Storage — If you start using either of these products, you're prompted to select your project's default Google Cloud Platform (GCP) resource location (if it wasn't already selected when setting up another service).
Cloud Functions for Firebase (scheduled functions only) — If you run scheduled functions, Cloud Scheduler requires an App Engine app; during its setup you're prompted to select your project's default Google Cloud Platform (GCP) resource location (if it wasn't already selected when setting up another service).

To learn more about location settings for non-scheduled functions, visit Cloud Functions Locations.
Realtime Database — If you create a Realtime Database instance, you're prompted to select the location of the instance, and each instance can be in a different location. Note that the locations of your Realtime Database instances do not affect the options for your default GCP resource location.

Select a location setting for a product or group of products

For most use-cases, you select a location setting in the Firebase console as part of setting up a specific product. Note that in some cases (as described in this section), setting the location for one product may set the location for other products due to dependencies.

Analytics

If you enable Google Analytics in your Firebase project in the Firebase console, you're prompted to select an Analytics reporting location. Select a country or region that represents the location of your organization.

If you're a project Owner or Editor, you can edit the time zone and the currency for your Analytics reporting location; go to your Google Analytics settings, then go to the Reporting pane.

Cloud Firestore, Cloud Storage, and scheduled functions

Cloud Firestore, Cloud Storage, and scheduled functions all share the same location setting, called the default GCP resource location (learn the specifics about this location setting below). Note that this location might have been previously set, either during project creation or when setting up another service that uses this location setting.

If you set up Cloud Firestore or Cloud Storage, you're prompted to select your project's default GCP resource location in the Firebase console workflow.

For Cloud Storage, your default GCP resource location only applies to your default bucket. If you're on the Blaze plan, you can create multiple buckets, each with its own location.
If you run scheduled functions, Cloud Scheduler requires an App Engine app. During its setup, you're prompted to select your project's default GCP resource location.
You can programmatically set your default GCP resource location by calling the defaultLocation.finalize endpoint for your Firebase project.

Realtime Database locations

If you create a new Realtime Database instance, you need to specify the location for that instance. Each Realtime Database instance in your project can be located in a different location. In the following table, find the supported locations for Realtime Database instances along with their associated database URL schemes.

Note that the locations of your Realtime Database instances do not affect the options for your default GCP resource location.

Region name	Region description	Database URL scheme
`us-central1`	Iowa	`DATABASE_NAME`.firebaseio.com
`europe-west1`	Belgium	`DATABASE_NAME`.europe-west1.firebasedatabase.app
`asia-southeast1`	Singapore	`DATABASE_NAME`.asia-southeast1.firebasedatabase.app

View location settings

Analytics — In the Firebase console, go to Project settings > Integrations > Google Analytics. Click the account number to open your Google Analytics account, and then go to the Admin panel to find your account's location.
Realtime Database — In the Firebase console, view the list of your database instances and their locations in the Realtime Database Data tab.
Cloud Firestore — In the Firebase console, view the list of your database instances and their locations in the Cloud Firestore Data tab.
Cloud Storage — In the Firebase console, view the list of your buckets and their locations in the Cloud Storage Files tab
Scheduled functions — In the Google Cloud console, go to Cloud Scheduler to view the list of topics for each job and function. The location is the last segment in the name of the topic.
Non-scheduled functions — By default, functions run in the us-central1 region. However, if the location has been explicitly set, you can find the location in your function's source code.

Learn about the default GCP resource location

Several services available for your app require a location setting that's 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:

Cloud Firestore
Note that your default GCP resource location does not apply to Firebase Realtime Database.
Cloud Storage
Note that your default GCP resource location only applies to your default Cloud Storage bucket. If you're on the Blaze plan, you can create multiple buckets, each with its own location.
App Engine app (for example, for scheduled functions)
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.

You can select either a multi-region location or a regional location as your default GCP resource location. Note that if you already have an App Engine app with a location of either us-central or europe-west, any GCP service that uses this location setting 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.

Firebase supports the following multi-region GCP resource 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.

Firebase supports the following regional GCP resource locations:

	Region Name	Region Description
North America
	`us-west1`	Oregon
	`us-west2`	Los Angeles
	`us-west3`	Salt Lake City
	`us-west4`	Las Vegas
	`us-central1`	Iowa
	`northamerica-northeast1`	Montréal
	`northamerica-northeast2`	Toronto
	`us-east1`	South Carolina
	`us-east4`	Northern Virginia
	`us-east5` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Columbus
	`us-south1` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Dallas
South America
	`southamerica-west1` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Santiago
	`southamerica-east1`	São Paulo
Europe
	`europe-west2`	London
	`europe-west1`	Belgium
	`europe-west4`	Netherlands
	`europe-west8` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Milan
	`europe-southwest1` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Madrid
	`europe-west9`	Paris
	`europe-west12` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Turin
	`europe-west10` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Berlin
	`europe-west3`	Frankfurt
	`europe-north1` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Finland
	`europe-central2`	Warsaw
	`europe-west6`	Zürich
Middle East
	`me-central1`	Doha
	`me-central2`	Dammam
	`me-west1`	Tel Aviv
Asia
	`asia-south1`	Mumbai
	`asia-south2` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Delhi
	`asia-southeast1`	Singapore
	`asia-southeast2`	Jakarta
	`asia-east2`	Hong Kong
	`asia-east1`	Taiwan
	`asia-northeast1`	Tokyo
	`asia-northeast2`	Osaka
	`asia-northeast3`	Seoul
Australia
	`australia-southeast1`	Sydney
	`australia-southeast2` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Melbourne
Africa
	`africa-south1` This location does not support Cloud Storage for Firebase. If you plan to use Cloud Storage for Firebase, you should choose a different location.	Johannesburg

Next steps

To create a Cloud Firestore database in a specific location, visit Get started with Cloud Firestore.
To create a Cloud Storage bucket, visit the Get Started page for your platform.
To run scheduled functions with Cloud Functions for Firebase, visit the setup guide.
For more information about building applications to meet your latency, availability, and durability requirements, refer to Geography and Regions.