Firestore Quota Exceeded (resource-exhausted)

How to fix it

Try these in order — the most common fix is first.

1. 1. Find what burned the quota

   Copy steps
   1. Firebase console > Usage tab, or Google Cloud console > Firestore > Usage
   2. Look for spikes in reads
   Did this fix it? Yes No

2. 2. Cut reads

   Copy steps
   1. Use limit() and pagination
   2. Detach listeners when screens close
   3. Cache results and avoid reading whole collections
   Did this fix it? Yes No

3. 3. Upgrade to Blaze with protection

   Copy steps
   1. Upgrade, then set a budget alert (notification only)
   2. Use a spend cap for Functions or App Hosting if relevant
   Did this fix it? Yes No

4. 4. Wait for reset

   1. Daily quotas reset around midnight Pacific time
   Did this fix it? Yes No

Symptoms

Quota exceeded or resource-exhausted errors, reads or writes failing until the next day.

Why it happens

• Daily Firestore read/write quota hit on Spark
• Listeners re-reading large collections
• Loops or retries inflating reads
• Spark monthly egress or Hosting transfer limit reached

This guide also covers

• firestore quota exceeded
• firebase resource exhausted
• firebase spark plan limit

Other Firebase errors

• Firestore Missing or Insufficient Permissions (permission-denied)
• Firebase auth/invalid-api-key Error
• Firebase auth/network-request-failed Error
• Firebase auth/too-many-requests Error
• Firebase auth/operation-not-allowed Error
• Firebase Unexpected Bill on Blaze Plan
• Firebase Cloud Messaging Notifications Not Received
• Firebase Deploy Failed (Functions and Hosting)