Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Gemini has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 4 scoped observations for Gemini. The baseline covers consumer context window, compute-based usage, file upload, code folder or repository upload. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| consumer context windowGoogle describes this as the content Gemini Apps can consider together. | 32K free; 128K AI Plus; 1M AI Pro and Ultra | Personal Google AI plans | GoogleAug 22, 2026 |
| compute-based usagePrompt complexity, model, feature, thinking level, and chat length affect consumption. | Refreshes every 5 hours until a weekly limit is reached | Personal accounts | GoogleAug 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 video | Supported Gemini Apps accounts | GoogleAug 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 MB | Gemini Apps | GoogleAug 22, 2026 |
Tracked constraints and impact
Gemini Apps context, file upload, media duration, and compute-based usage limits. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
Gemini Apps Context Window by Plan
Gemini Apps Context Window by Plan, verified against Gemini's official documentation with scope, implementation impact, caveats, and a direct check.
Gemini Apps Usage Limits & Reset Time
Gemini Apps Usage Limits & Reset Time, verified against Gemini's official documentation with scope, implementation impact, caveats, and a direct check.
Gemini Apps File Upload Limits
Gemini Apps File Upload Limits, verified against Gemini's official documentation with scope, implementation impact, caveats, and a direct check.
Gemini Code Folder & Repository Limits
Gemini Code Folder & Repository Limits, verified against Gemini's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Gemini baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Five-hour and weekly limits, plan multipliers, context windows
File count, byte size, media duration, and repository constraints