Quick answer
Firebase documents maximum api request as 10 MiB. Transactions and commits also have time and transformation constraints.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum API requestTransactions and commits also have time and transformation constraints. | 10 MiB | Cloud Firestore | FirebaseAug 22, 2026 |
Why does this limit matter?
A batch with many small documents can exceed request size before reaching operation-count expectations.
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?
- Measure serialized request bytes and split batches with idempotent retry handling.
- 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
- Security rules evaluation and index updates add separate 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