Quick answer
Firebase documents index configuration and entries as 200 composite indexes without billing; 1,000 with billing; 40,000 entries/document. Single-field configurations and entry byte sizes impose additional ceilings.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| index configuration and entriesSingle-field configurations and entry byte sizes impose additional ceilings. | 200 composite indexes without billing; 1,000 with billing; 40,000 entries/document | Cloud Firestore | FirebaseAug 22, 2026 |
Why does this limit matter?
Array and map fields can multiply index entries far faster than document count suggests.
This value is scoped to Cloud Firestore; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Use index-entry estimation for representative documents and remove unused composite indexes.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Support can increase some configured index counts, but per-document entry limits remain design constraints.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related