Learn about locations for products and resources in your project

There's not a global project-level or app-level setting for location.
Locations are set per product or per resource, and in some cases, per group of products. Usually, though, you set the location for each product and each resource independently from the others.

Note that some Firebase products and resources don't support location selection. Also, you can optionally set anorganization-level location restriction for products and resources that support location selection.

Products or resources that require a location setting

Several products or resources require a location setting.

Product	Default location	Additional information
Firebase AI Logic	ForGemini Developer API: No location selection possible; always global. ForVertex AI Gemini API: If location not set, the default region is`us-central1`.	This location is where you access the model.
Google Analytics	No default location. You must set this location.	This location is theAnalytics reporting location², which represents the country or region of your organization. YourAnalytics reporting location, in turn, sets the currency for revenue reporting.
Firebase App Hosting	No default location. You must set this location for each backend.	This location is whereApp Hosting deployment creates each of your backend resources. Each backend can be in a different location.
Firebase Data Connect	No default location. You must set the location for each instance.	Each instance can be in a different location.
Cloud Firestore¹	No default location. You must set the location for each instance.	Each instance can be in a different location.
Firebase Realtime Database	No default location. You must set the location for each instance.	Each instance can be in a different location.
Cloud Storage for Firebase¹	No default location. You must set the location for each bucket.	Each bucket can be in a different location.
Cloud Functions for Firebase¹	If location not set, the default region is`us-central1`.	Each function can be in a different location.

¹ Depending on when you initially started using these products inyour project, there can be location dependencies between these products. Youmight see this dependency referred to as the"location for defaultGoogle Cloud resources". Learn more about thislocation dependency.

² YourAnalytics reporting location doesnot affect whereGoogle may process and storecustomer data for Firebase.

Set a location for a product or its resources

For a few products, you set the location at the product level. However, for mostproducts, you set the location at the resource level (for example, for eachCloud Storage bucket or each function).

Product	When and how to set the location	Available locations
Firebase AI Logic	ForGemini Developer API: No location selection possible; always global. ForVertex AI Gemini API: When you initialize theVertex AI backend service in your codebase, you can optionally specify a location for where to access the model. If you don't specify a location, the default region is`us-central1`.	Firebase AI Logic locations
Google Analytics	When you enableGoogle Analytics in your Firebase project in theFirebase console, you're prompted to select an Analytics reporting location. You should select a country or region that represents the location of your organization. If you're a project Owner or Editor, you can later edit the time zone and the currency for your Analytics reporting location; go to yourGoogle Analytics settings, then go to theReporting pane.	See list in theGoogle Analytics settings >Reporting pane.
Firebase App Hosting	When you create anApp Hosting backend, you're prompted to select a location. You can use theFirebase console, REST API, orFirebase CLI to create a backend.	App Hosting locations
Firebase Data Connect	When you provision aData Connect service instance, you set its locations. You also set the location of the associatedGoogle Cloud SQL instance. You can use theFirebase console orFirebase CLI to provision an instance.	Data Connect service andCloud SQL instance locations
Cloud Firestore¹	When you provision aCloud Firestore database instance, you set its location. You can use theFirebase console, REST API,Firebase CLI, or Terraform to provision an instance.	Cloud Firestore locations
Firebase Realtime Database	When you provision theRealtime Database instance, you set its location. You can use theFirebase console, REST API,Firebase CLI, or Terraform to provision an instance.	Realtime Database locations
Cloud Storage for Firebase¹	When you provision theCloud Storage bucket, you set its location. You can use theFirebase console, REST API, or Terraform to provision a bucket.	Cloud Storage for Firebase locations
Cloud Functions for Firebase¹	When you write a function, you can optionally set its region. If you don't specify a location, the default region is`us-central1`.	Cloud Functions for Firebase locations

View location settings

Product	Where to view the location setting
Firebase AI Logic	ForGemini Developer API: No location selection possible; always global. ForVertex AI Gemini API: In your codebase, look for the initialization of theVertex AI backend service. If a location isn't specified, then the default location is`us-central1`.
Google Analytics	In theFirebase console, go to settingsProject settings >Integrations >Google Analytics. Click the account number to open yourGoogle Analytics account, and then go to theAdmin panel to find your account's location information.
Firebase App Hosting	In theFirebase console, go to theApp Hosting page to view the list of your backends and their locations. To view the location for a specific backend, you can use theFirebase CLI command`firebase apphosting:backends:get --projectPROJECT_IDBACKEND_ID`
Firebase Data Connect	In theFirebase console, go to theData Connect page to view the list of your database instances and their locations.
Cloud Firestore	In theFirebase console, go to theCloud FirestoreData tab to view the list of your database instances and their locations.
Firebase Realtime Database	In theFirebase console, go to theRealtime DatabaseData tab to view the list of your database instances and their locations.
Cloud Storage for Firebase	In theFirebase console, go to theCloud StorageFiles tab to view the list of your buckets and their locations.
Cloud Functions for Firebase	Scheduled functions: In theGoogle Cloud console, go toCloud 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: In your function's source code, look for a`region` parameter. If a region isn't specified, then the default location is`us-central1`.

Possible location dependencies due to "location for default Google Cloud resources"

The "location for defaultGoogle Cloud resources" is the location settingfor any project resources associated with GoogleApp Engine, including thefollowing:

defaultCloud Firestore database instance
defaultCloud Storage for Firebase bucket with the name format of*.appspot.com
GoogleCloud Scheduler used specifically with 1st gen scheduled functions

Note: None of the other resources in your project share this locationdependency, including the following: Realtime Database instances,non-defaultCloud Firestore instances, non-defaultCloud Storage buckets,defaultCloud Storage buckets with the name format of*.firebasestorage.app, non-scheduled functions,and 2nd gen scheduled functions.

This "location for defaultGoogle Cloud resources" is an immutablesetting. Also, when you set the location for one of the associated resources,you indirectly set the location for all of them due to their common associationwithApp Engine.

However, with many changes to the Firebase andGoogle Cloud ecosystem overthe years, the associations of resources toApp Engine have beenchanging. Most notably, startingOctober 30, 2024, all newly provisioneddefaultCloud Storage for Firebase buckets have the name format*.firebasestorage.app, and they arenot associatedwithApp Engine.

Key Point: StartingOctober 30, 2024,provisioning the defaultCloud Storage for Firebase bucket does not set the"location for defaultGoogle Cloud resources" (like the location for theproject's defaultCloud Firestore instance). Also, provisioning thedefaultCloud Firestore instance no longer sets the location for a newdefaultCloud Storage for Firebase bucket (with name format of*.firebasestorage.app).

Here are the details of what changed in the possiblelocation dependencies:

StartingOctober 30, 2024,if thedefaultCloud Firestore instance and thedefaultCloud Storage for Firebase bucket arenot yet provisioned:
- Provisioning the defaultCloud Firestore instance sets the locationfor any futureApp Engine app provisioned in the project.However, it doesnot dictate the location of the futuredefaultCloud Storage bucket.
- Provisioning the defaultCloud Storage bucketno longer provisionsanApp Engine app. Thus, the location of thedefaultCloud Storage bucket doesnot dictate the location of thefuture defaultCloud Firestore instance.
StartingOctober 30, 2024,if the defaultCloud Firestore instance hasalready been provisioned, but thedefaultCloud Storage for Firebase bucket hasnot been provisioned:
- The existing defaultCloud Firestore instance doesnot dictate thelocation of the future defaultCloud Storage bucket(*.firebasestorage.app).
StartingOctober 30, 2024,if thedefaultCloud Storage for Firebase bucket hasalready beenprovisioned (specifically, the*.appspot.com bucket), but thedefaultCloud Firestore instance hasnot been provisioned:
- Back when the defaultCloud Storage bucket(*.appspot.com) was provisioned,anApp Engine app wasalso provisioned, and thus the locationof the future defaultCloud Firestore instance was set at that time.Even if you delete the*.appspot.com bucket, youcan't delete theApp Engine app, so the location setting of thefuture defaultCloud Firestore instance is already set.

If you used1st gen scheduled functions, then their location is set to thelocation for defaultGoogle Cloud resources. This is becauseCloud Scheduler andApp Engine previously had an association witheach other. Also, if you set up 1st gen scheduled functionsbeforeprovisioning other resources that shared this location setting, then you settheir location, too.

Next steps

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

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-03 UTC.

Movatterモバイル変換