Quick answer
Firebase documents document size as 1 MiB. Index entries and field-value indexing have separate size constraints.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| document sizeIndex entries and field-value indexing have separate size constraints. | 1 MiB | Cloud Firestore | FirebaseAug 22, 2026 |
Why does this limit matter?
Embedding large arrays or blobs can exhaust both document and index budgets.
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?
- Estimate encoded document size and index entry expansion before writes.
- 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
- Use Cloud Storage for large binary objects rather than treating a Firestore document as a file.
- 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