Platform hub

Gemini limits

Gemini Apps context, file upload, media duration, and compute-based usage limits. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Gemini 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
consumer context windowGoogle describes this as the content Gemini Apps can consider together.32K free; 128K AI Plus; 1M AI Pro and UltraPersonal Google AI plansGoogleAug 22, 2026
compute-based usagePrompt complexity, model, feature, thinking level, and chat length affect consumption.Refreshes every 5 hours until a weekly limit is reachedPersonal accountsGoogleAug 22, 2026
file uploadFolders and repositories count their contained files and have separate caps.10 files per prompt; 100 MB each, or 2 GB per videoSupported Gemini Apps accountsGoogleAug 22, 2026
code folder or repository uploadOne code folder or GitHub repository can be added to a chat within these ceilings.Up to 5,000 files and 100 MBGemini AppsGoogleAug 22, 2026

How to apply Gemini limits safely

The monitored baseline covers consumer context window, compute-based usage, file upload, code folder or repository upload. 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 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.

Official sources

View Gemini change history