Firestore: 8 RESOURCE_EXHAUSTED: Quota exceeded (free-tier daily limit or write rate)
The project hit a Firestore quota, such as the Spark plan's daily read/write limits or rate limits on writes.
8 RESOURCE_EXHAUSTED: Quota exceeded.Firestore quota exceededFirebaseError: Quota exceeded. (resource-exhausted)resource-exhausted Firestore daily limitQuota exceeded: Firestore free tier Meaning
On Spark the daily free quota is 50K reads / 20K writes / 20K deletes; upgrade to Blaze for more. Also reduce reads (cache, listeners instead of polling, limit queries), batch writes, and look for loops or runaway listeners in the usage dashboard.
Common causes
- Spark plan daily quota used up
- Runaway read/write loop
- Too many listeners or full-collection reads
- Write rate too high on a key range
- Billing not enabled
⚡ Quick fix
- Upgrade to Blaze or reduce usage
- Add caching/limits/pagination
- Check Usage in the Firebase console
Detailed fix by platform
Shell
firebase open firestore:usage
How to diagnose
- Plan — Spark?
- Usage — Spiking?
- Loop — Present?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 429 RESOURCE_EXHAUSTED: Quota exceeded for quota metric Google API: 429 RESOURCE_EXHAUSTED — Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute per user'
- BigQuery: Quota exceeded: Your project exceeded quota for free query bytes scanned BigQuery: Quota exceeded: Your project exceeded quota for free query bytes scanned. Consider enabling billing
- connections Realtime Database: 100 simultaneous connections limit on the Spark plan (new connections refused)
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026