Native mode: Quotas and Limits

This page describes the request quotas and Enterprise edition limits for Cloud Firestore in Native mode.

Free tier usage

Cloud Firestore in Native mode offers a free tier that lets you get started with Cloud Firestore in Native mode at no cost. The free tier amounts are listed in the following table.

Free tier amounts are applied daily and reset at midnight Pacific time.

The free tier applies to only one Cloud Firestore database per project. The first database that is created in a project without a free tier database will get the free tier. If the database with the free tier applied is deleted, the next database created will receive the free tier.

Free tier Quota
Stored data 1 GiB
Read units 50,000 per day
Real-time update units 50,000 per day
Write units 40,000 per day
Outbound data transfer 10 GiB per month

Standard limits

The following tables show the limits that apply to Cloud Firestore in Native mode. These are hard limits unless otherwise noted.

Databases

Limit Details
Maximum number of databases per project

100

You can contact support to request an increase to this limit.

Maximum number of customer-managed encryption keys (CMEK) databases per project

0

By default the quota is 0 because this feature is behind an allowlist. You can request to increase the quota by filling in the CMEK access request form.

Collections, documents, and fields

Limit Details
Constraints on collection IDs
  • Must be valid UTF-8 characters
  • Must be no longer than 1,500 bytes
  • Cannot contain a forward slash (/)
  • Cannot solely consist of a single period (.) or double periods (..)
  • Cannot match the regular expression __.*__
Maximum depth of subcollections 100
Constraints on document IDs
  • Must be valid UTF-8 characters
  • Must be no longer than 1,500 bytes
  • Cannot contain a forward slash (/)
  • Cannot solely consist of a single period (.) or double periods (..)
  • Cannot match the regular expression __.*__
  • If you import Datastore entities into a Firestore database, numeric entity IDs are exposed as __id[0-9]+__
Maximum size for a document name 6 KiB
Maximum size for a document 1 MiB (1,048,576 bytes)
Constraints on field names
  • Must be valid UTF-8 characters
  • Cannot match the regular expression __.*__
Maximum size of a field name 1,500 bytes
Constraints on field paths
  • Must separate field names with a single period (.)
  • May be passed as a dot-delimited (.) string of segments where each segment is either a simple field name or a quoted field name (defined below).
A simple field name is one where all of the following are true:
  • Contains only the characters a-z, A-Z, 0-9, and underscore (_)
  • Does not start with 0-9
A quoted field name starts and ends with the backtick character (`). For example, foo.`x&y` refers to the x&y field nested under the foo field. To construct a field name with the backtick character, escape the backtick character with the backslash character (\). For convenience, you can avoid quoted field names by passing the field path as a FieldPath object (for example, see JavaScript FieldPath).
Maximum size of a field path 1,500 bytes
Maximum size of a field value 1 MiB - 89 bytes (1,048,487 bytes)
Maximum depth of fields in a map or array

20

Map and array fields add one level to the overall depth of an object. For example, the following object has a total depth of three levels: 


{
  nested_map: {         #depth 1
    nested_array: [     #depth 2
      {
        foo: "bar"      #depth 3
      }
    ]
  }
}

Writes and transactions

Limit Details
Maximum API request size 10 MiB
Time limit for a transaction 270 seconds, with a 60-second idle expiration time
Maximum number of field transformations that can be performed on a single document in a Commit operation or in a transaction 500

Indexes

Limit Details
Maximum number of indexes for a database

Maximum number of index entries for each document

40,000
Maximum number of fields in an index 100
Maximum size of an index entry

7.5 KiB
Maximum sum of the sizes of a document's index entries

8 MiB

Time-to-live (TTL)

Limit Details
Maximum number of single-field configurations for a database

One field level configuration can contain multiple configurations for the same field. For example, a single-field indexing exemption and a TTL policy on the same field count as one field configuration towards the limit.

Export/Import

The following limits apply to managed import and export operations:

Limit Details
Maximum total number of both export and import requests for a project allowed per minute 20
Maximum number of concurrent exports and imports 50
Maximum number of collection ID filters for export and import requests 100

Security rules

Limit Details
Maximum number of exists(), get(), and getAfter() calls per request
  • 10 for single-document requests and query requests.

  • 20 for multi-document reads, transactions, and batched writes. The previous limit of 10 also applies to each operation.

    For example, imagine you create a batched write request with 3 write operations and that your security rules use 2 document access calls to validate each write. In this case, each write uses 2 of its 10 access calls and the batched write request uses 6 of its 20 access calls.

Exceeding either limit results in a permission denied error.

Some document access calls may be cached, and cached calls do not count towards the limits.
Maximum nested match statement depth 10
Maximum path length, in path segments, allowed within a set of nested match statements 100
Maximum number of path capture variables allowed within a set of nested match statements 20
Maximum function call depth 20
Maximum number of function arguments 7
Maximum number of let variable bindings per function 10
Maximum number of recursive or cyclical function calls 0 (not permitted)
Maximum number of expressions evaluated per request 1,000
Maximum size of a ruleset Rulesets must obey two size limits:
  • a 256 KB limit on the size of the ruleset text source published from the Firebase console or from the CLI using firebase deploy.
  • a 250 KB limit on the size of the compiled ruleset that results when Firebase processes the source and makes it active on the back-end.