Skip to main content

​
Quotas & Limits

To ensure the stability and fairness in a multi-tenant environment, Chroma Cloud enforces input and query quotas across all user-facing operations. These limits are designed to strike a balance between performance, reliability, and ease of use for the majority of workloads.
Most quotas can be increased upon request. If your application requires higher limits, please contact us.
QuotaValue
Maximum embedding dimensions4,096
Maximum document bytes16,384
Maximum URI bytes256
Maximum ID size bytes128
Maximum database name size bytes128
Maximum collection name size bytes128
Maximum record metadata value size bytes4,096
Maximum collection metadata value size bytes256
Maximum metadata key size bytes36
Maximum number of record metadata keys32
Maximum number of collection metadata keys32
Maximum number of where predicates8
Maximum size of full text search or regex search256
Maximum number of results returned300
Maximum number of concurrent reads per collection10
Maximum number of concurrent writes per collection10
Maximum number of collections1,000,000
Maximum number of records per collection5,000,000
Maximum fork edges from root4,096
Maximum number of records per write300
These limits apply per request or per collection as appropriate. For example, concurrent read/write limits are tracked independently per collection, and full-text query limits apply to the length of the input string, not the number of documents searched. For details about the fork edges limit and quota error handling when forking, see Collection Forking. If you expect to approach these limits, we recommend reaching out early so we can ensure your account is configured accordingly.