Locations for Cloud Storage for Firebase

When you provision a Cloud Storage bucket, you must choose a location for the bucket. To reduce latency and increase availability, store your data close to the users and services that need it.

For *.firebasestorage.app default buckets as well as any additional buckets in your project, you can choose from all available Cloud Storage locations.

Note: At this time, Cloud Storage for Firebase does not support configurable dual-regions.

Be aware that once you provision a bucket, you cannot change its location setting.

Buckets in US-CENTRAL1, US-EAST1, and US-WEST1 can take advantage of the "Always Free" tier for Google Cloud Storage. Buckets in all other locations follow Google Cloud Storage pricing and usage.

You can optionally create multiple buckets in your project, each with its own location setting. For details, see the Cloud Storage getting started guide for your platform ( iOS+ | Android+ | Web | Flutter | Unity | C++ ).

Legacy project considerations

If your project has a legacy *.appspot.com default bucket, note the following about its location:

• Google App Engine locations: Its location is one of the available Google App Engine locations.

• Location dependency: Its location has a dependency on the "location for default Google Cloud resources". When you provisioned that default bucket, the location might have already been set, either during project creation or when setting up another service that shares this location dependency.

Default buckets with the name format of *.firebasestorage.app do not share this dependency and can be provisioned in any supported Cloud Storage location.