Usage and limits

Stay organized with collections Save and categorize content based on your preferences.

100

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

• 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 __.*__

• 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]+__

• Must be valid UTF-8 characters
• Cannot match the regular expression __.*__

• 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).

• Contains only the characters a-z, A-Z, 0-9, and underscore (_)
• Does not start with 0-9

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
      }
    ]
  }
}
      

• 200 when you have not enabled billing for your Google Cloud project.

  If you need more quota, you must enable billing for your Google Cloud project.

• 1000 when you enable billing for your Google Cloud project.

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

• 200 when you have not enabled billing for your Google Cloud project.

  If you need more quota, you must enable billing for your Google Cloud project.

• 1000 when you enable billing for your Google Cloud project.

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.

Maximum number of index entries for each document

40,000

The number of index entries is the sum of the following for a document:

• The number of single-field index entries
• The number of composite index entries

To see how Cloud Firestore turns a document and a set of indexes into index entries, see this index entry count example.

7.5 KiB

To see how Cloud Firestore calculates index entry size, see index entry size.

8 MiB

The total size is the sum of the following for a document:

1500 bytes

Field values over 1500 bytes are truncated. Queries involving truncated field values may return inconsistent results.

• 200 when you have not enabled billing for your Google Cloud project.

  If you need more quota, you must enable billing for your Google Cloud project.

• 1000 when you enable billing for your Google Cloud project.

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.

• 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.

• 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.