This page describes how to create, update, and deleteCloud Firestoredatabases. You can create multipleCloud Firestore databases perproject. You can use multiple databases to set up production and testingenvironments, to isolate customer data, and for data regionalization.

Free tier usage

Cloud Firestore offersfree tierthat lets you get started at no cost.

The free tier applies to only oneCloud Firestore database per project. Thefirst database that is created in a project without a free tier database willget the free tier. If the database with the free tier applied is deleted, thenext database created will receive the free tier.

Before you begin

You must complete the following before creating a database:

1. If you haven't already, create a Firebase project: In theFirebase console, clickAdd project, thenfollow the on-screen instructions to create a Firebase project or to addFirebase services to an existingGoogle Cloud project.

2. Assign appropriate Identity and Access Management roles as described in the next section.

Required roles

To create and manage databases, you need theOwner orDatastore OwnerIdentity and Access Management role. These roles grant the required permissions.

Required permissions

To manage databases, you need the following permissions:

• Create a database:datastore.databases.create
• Read database configuration:datastore.databases.getMetadata
• Configure a database:datastore.databases.update
• Delete a database:datastore.databases.delete
• Clone a database:datastore.databases.clone

Create a database

To create aCloud Firestore database, use one of the following methods:

firebase firestore:databases:create --editionEDITIONDATABASE_ID \--location=LOCATION

gcloud firestore databases create \--database=DATABASE_ID \--location=LOCATION \--edition=enterprise \--enable-mongodb-compatible-data-access

gcloud firestore databases create \--database=DATABASE_ID \--location=LOCATION \--edition=enterprise \--delete-protection

resource"google_firestore_database""database"{name="DATABASE_ID"location_id="LOCATION"type="FIRESTORE_NATIVE"database_edition="ENTERPRISE"  // Optionaldelete_protection_state="DELETE_PROTECTION_STATE"}

Database ID

Valid database IDs include IDs that conform to thefollowing:

• Includes only letters, numbers, and hyphen (-) characters.
• Letters must be lowercase.
• The first character must be a letter.
• The last character must be a letter or number.
• Minimum of 4 characters.
• Maximum of 63 characters.
• Must not be a UUID or resemble a UUID. For example, don't use an ID likef47ac10b-58cc-0372-8567-0e02b2c3d479.

If you delete a database, you cannot immediately re-use the database ID until after 5 minutes.

Delete protection

Use delete protection to prevent accidental deletion of a database.Delete protection works in the following way:

• You cannot delete a database with delete protection enabled until you disabledelete protection.
• Delete protection is disabled by default.
• You can enable delete protection when you create the database or you canupdate a database configuration toenable delete protection.

List databases

Use one of the following methods to list your databases:

gcloud firestore databases list

View database details

To view details about a single database, use one of the following methods:

gcloud firestore databases describe --database=DATABASE_ID

Update database configuration

To update the configuration settings of a database, use thegcloud firestore databases updatecommand.

Use this command to change, enable, or disable delete protection.

Update the delete protection setting

To enable delete protection on a database, use thegcloud firestore databases updatecommand with the--delete-protection flag. For example:

gcloud firestore databases update --database=DATABASE_ID --delete-protection

ReplaceDATABASE_ID with a database ID.

To disable delete protection on a database, use thegcloud firestore databases updatecommand with the--no-delete-protection flag. For example:

gcloud firestore databases update --database=DATABASE_ID --no-delete-protection

ReplaceDATABASE_ID with a database ID.

Delete a database

To delete a database, use the console or command-line tool.Deleting a database does not incur charges for delete operations.

If the database has the delete protection setting enabled, you mustfirstdisable delete protection.

gcloud firestore databases delete --database=DATABASE_ID

Clone a database

You can clone an existing database at a selected timestamp into a new database:

• The cloned database is a new database that will be created in the samelocation as the source database.

  To make a clone,Cloud Firestore usespoint-in-time recovery (PITR) data of the source database. The cloned database includes all data and indexes.

• By default, the cloned database will be encrypted in the same way as thesource database, using either Google's default encryption orCMEK encryption. You can specify a differentencryption type or use a different key for CMEK encryption.

• The timestamp has a granularity of one minute and specifies a point of timein the past, in the period defined by thePITR window:

  • If PITR is enabled for your database, you select any minute in the last 7days (or less if PITR was enabled less than 7 days ago).
  • If PITR isn't enabled, you can select any minute in the past hour.
  • You can check the earliest timestamp that you can pickin your database's description.

gcloudfirestoredatabasesclone\--source-database='SOURCE_DATABASE'\--snapshot-time='PITR_TIMESTAMP'\--destination-database='DESTINATION_DATABASE_ID'

gcloudfirestoredatabasesclone\--source-database='projects/example-project/databases/example-source-db'\--snapshot-time='2025-06-01T10:20:00.00Z'\--destination-database='example-dest-db'

gcloudfirestoredatabasesclone\--source-database='projects/example-project/databases/(default)'\--snapshot-time='2025-06-01T10:20:00.00Z'\--destination-database='example-dest-db'\--tags=key1=value1,key2=value2

gcloudfirestoredatabasesclone\--source-database='projects/example-project/databases/example-source-db'\--snapshot-time='2025-06-01T10:20:00.00Z'\--destination-database='example-dest-db'\--encryption-type='customer-managed-encryption'\--kms-key-name='projects/example-project/locations/us-central1/keyRings/example-key-ring/cryptoKeys/example-key'

Configure per-database access permissions

You can useIdentity and Access Management Conditionsto configure access permissions on a per-database level.The following examples use the Google Cloud CLI to assign conditional access forone or more databases. You can alsodefine IAM conditions in the Google Cloud console.

gcloud projects get-iam-policyPROJECT_ID

gcloud projects add-iam-policy-bindingPROJECT_ID \--member='user:EMAIL' \--role='roles/datastore.user' \--condition='expression=resource.name=="projects/PROJECT_ID/databases/DATABASE_ID",title=TITLE,description=DESCRIPTION'

gcloud projects add-iam-policy-bindingPROJECT_ID \--member='user:EMAIL' \--role='roles/datastore.user' \--condition='expression=resource.name!="projects/PROJECT_ID/databases/DATABASE_ID",title=TITLE,description=DESCRIPTION'

gcloud projects remove-iam-policy-bindingPROJECT_ID \--member='user:EMAIL' \--role='roles/datastore.user' --all

You can have a maximum of 100 databases per project.You cancontact support to request anincrease to this limit.

What's next

• Run theQuickstart: Create a database and connect to it.
• Learn aboutBehavior differences.
• Learn aboutCloud Monitoring metrics forCloud Firestore.