Platform hub

Gemini API limits

Project-scoped RPM, TPM, daily, batch, file, and model context limits. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Gemini API has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented limits

ConstraintCurrent valueScopeVerified source
rate-limit dimensionsLimits apply per project, not per API key, and daily requests reset at midnight Pacific Time.RPM, TPM, and RPD vary by model and usage tierPer Google Cloud projectGoogleAug 22, 2026
long-context supportThe exact input and output budget must be read from the deployed model specification.Many Gemini models support 1M+ tokensModel specificGoogleAug 22, 2026
batch concurrency and enqueued workBatch token capacity is separate from the fixed concurrent request count.100 concurrent batch requests; enqueued tokens vary by model and tierPer projectGoogleAug 22, 2026
batch/file storageThe file and aggregate storage ceilings are independent of prompt context capacity.2 GB per input file; 20 GB project file storagePer projectGoogleAug 22, 2026

How to apply Gemini API limits safely

The monitored baseline covers rate-limit dimensions, long-context support, batch concurrency and enqueued work, batch/file storage. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active Gemini API console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.

Specific limit pages

These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.

Compare alternatives

Official sources

View Gemini API change history