Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean ChatGPT has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 6 scoped observations for ChatGPT. The baseline covers General per-file hard limit, Text and document token cap, CSV or spreadsheet practical cap, Image limit, Rolling upload allowance, Free plan upload allowance. 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 |
|---|---|---|---|
| General per-file hard limitApplies to files uploaded to a GPT or ChatGPT conversation; more restrictive type-specific limits can apply first. | 512 MB | Platform documented | OpenAIAug 22, 2026 |
| Text and document token capDoes not apply to spreadsheets; the byte-size limit still applies. | 2,000,000 tokens per file | Platform documented | OpenAIAug 22, 2026 |
| CSV or spreadsheet practical capApproximate because the supported size depends on row size. | Approximately 50 MB | Platform documented | OpenAIAug 22, 2026 |
| Image limitType-specific image limit. | 20 MB per image | Platform documented | OpenAIAug 22, 2026 |
| Rolling upload allowanceOpenAI says it may lower this limit during peak hours; Free users have a separate daily cap. | Up to 80 files every 3 hours | Platform documented | OpenAIAug 22, 2026 |
| Free plan upload allowanceA plan-specific allowance, separate from storage and per-file constraints. | 3 file uploads per day | Free | OpenAIAug 22, 2026 |
Tracked constraints and impact
File upload, storage, token, and plan-dependent product allowances. 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.
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 ChatGPT baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
File size restrictions and usage caps