Google Sheets API rate limits, explained

How Google's quotas work

The Google Sheets API enforces per-minute read quotas scoped to your Cloud project and to each user (historically around 300 reads/minute/project and 60/minute/user, though Google tunes these). Go over and requests come back 429 Too Many Requests. The catch: the limit is on API calls, so an app that reads the sheet on every page view spends that budget fast.

Third-party spreadsheet-to-API services add their own, often much lower, free-tier caps on top — and some fail silently when you cross them, serving a blank page instead of an error.

The official numbers, in one place

These are the published per-minute read quotas. They are rate limits that refill every minute, not a monthly allowance you burn down:

Which limit you are actually hitting

The two quotas fail differently, and knowing which one fired tells you what to change. The per-user limit of 60 reads/minute is the one a single service account trips, because every request your backend makes is attributed to that one identity — so it is the ceiling most server-side apps meet first, no matter how large the project quota is.

The per-project limit of 300 reads/minute is what you hit when many users are each authenticated separately, or when several services share one Cloud project. Splitting work across more service accounts raises the per-user ceiling but not the project one, which is why "add another service account" stops helping at a certain scale.

Both surface as the same error, so read the payload rather than the status code alone.

What the error looks like

Google returns 429 with a RESOURCE_EXHAUSTED status. If you are seeing this string in an editor, a CLI, or an agent — including inside tools like Cursor — it is this quota, not a bug in your code:

{
  "error": {
    "code": 429,
    "message": "Quota exceeded for quota metric 'Read requests' and limit
                'Read requests per minute per user' of service
                'sheets.googleapis.com'",
    "status": "RESOURCE_EXHAUSTED"
  }
}

Why apps hit the wall

• Reading the sheet live on every request instead of caching the result.
• Traffic spikes — a launch or a crawler multiplies reads in a single minute.
• A low free-tier cap on a hosted service that you quietly exceed.
• Polling on a timer — a 5-second refresh in ten open browser tabs is 120 reads a minute on its own.
• Retrying on failure without backoff, which turns one 429 into a stampede.
• No visibility: many setups fail blank rather than returning a clear 429.

Fixing it, in order of payoff

Work down this list — the first step usually ends the problem outright:

1. 1 Cache the read. Serve from a cached copy with a TTL instead of calling Google per request. One read per TTL replaces one read per visitor, and that is a change of orders of magnitude, not percentages.
2. 2 Batch your ranges. If you must call Google directly, use spreadsheets.values.batchGet to fetch several ranges in one request rather than one call per range.
3. 3 Back off on 429. Retry with exponential backoff and jitter. Retrying immediately guarantees a second 429.
4. 4 Stop polling on a timer. Refresh on demand, or lengthen the interval until it fits inside 60 reads a minute across every client.
5. 5 Request a quota increase in the Google Cloud console — worth doing, but slow, and it does not help the per-user ceiling.

How caching removes the problem

PasteSheet reads Google once and serves everyone else from an edge cache, so a thousand visitors in a minute is one read from Google, not a thousand. The quota stops being something you manage, because you are no longer near it — the upstream read rate is fixed by your TTL rather than by your traffic.

When you do reach your plan's limit, you get an explicit 429 with rate-limit headers telling you what to slow down to — never a silent blank page. See how the caching layer works, what to do about an already-exceeded quota, how the cached endpoint fits into using Google Sheets as a REST API, or compare quotas across plans.

Frequently asked questions

Sources

• Usage limits — Google Sheets API — Google

Related guides