How this calculation works
Measure a comparable block of work, keep the model, effort and speed fixed, and enter its meter changes. Exact profile matching prevents one model’s sample from silently being reused for another. The slowest and fastest observed rates form a scenario range, not a statistical confidence interval.
Observed rate = used percentage-point increase / active minutes; quota time = remaining points / rate; stop before the earliest relevant resetA worked example
Fictional request example: enter an allowance of one hundred, twenty already used and a pace of half a request per minute. Eighty requests remain and require 160 active minutes. These numbers demonstrate the arithmetic only; they are not a ChatGPT plan entitlement.
Good to know
Unofficial independent estimator, not affiliated with or endorsed by ChatGPT. Usage can vary with plan, model, reasoning, context, caching, tools, attachments, parallel tasks, server load, promotions and policy changes. Results are conditional projections, not guaranteed maximum hours, requests or access. Account meters and provider notices take priority. Sources checked 9 November 2026.
Reference: OpenAI — ChatGPT models and limits (opens in a new tab) ↗
What ChatGPT officially says
ChatGPT Chat has model-specific allowances and fallbacks. Its Pro-model limits are distinct from Work and Codex. A paid Pro subscription does not make every Pro-model request unlimited. Use the reset and allowance shown for the selected Chat model.
Use the quota category and reset time shown in your own account. The model names and effort labels help organize measurements; they do not grant access to a model or assert that every listed setting exists on every plan.
The Codex usage limit calculator covers a separate account or billing model. Compare its own documented scope rather than carrying a quota percentage or hosted rate across providers.
Read more: OpenAI — ChatGPT models and limits (opens in a new tab) ↗
What community reports can and cannot tell us
Participants distinguish manual browser conversations from coding-agent usage and disagree about how much Pro access they expected. This supports checking the actual product and model, not importing a Codex session percentage into Chat. The discussion is not evidence for a fixed number of free Pro hours.
This linked discussion was checked on 9 November 2026. It is a selected self-reported example, not a representative survey. Different accounts, promotions, workloads and observation windows cannot be combined into a reliable universal hourly rate.
Read more: Community discussion — Pro limits in Chat (opens in a new tab) ↗
Measure a profile without confusing its clocks
Record used percentage before and after a short comparable task without crossing a reset. If your meter shows remaining capacity, subtract the later remaining value from the earlier one. A weekly meter from seventeen to twenty percent used represents three percentage points, not twenty.
Measure active work consistently. If another device or agent is using the shared pool, pause it or include its work in the measured scope. Repeating a measurement with the same model, effort and speed gives a useful observed range; one sample gives only one observed pace.
How to reduce ChatGPT usage
Start a task with its intended result, output length and necessary source material. Ask for a brief answer when a short answer is sufficient, rather than generating an essay and then asking for a summary.
Use a lighter available thinking setting for routine work and compare the result before increasing effort. A new unrelated topic can use a fresh chat, with a short handoff of facts you still need.
Keep image generation, research and file analysis separate in your usage notes. A text-chat observation should not be used to predict a media quota or a separate tool allowance.
Read the SVG forecast and plan the next block
The usage lines show a constant-pace projection up to the entered next reset. Each activity tile represents an equal block of that active-time interval, not a calendar day or imported account history. Blocks, grouped and cumulative views reorganize the same scenario; equal intensity reflects its constant-rate assumption.
A cautious pre-reset estimate uses the fastest matching sample and whichever tracked pool runs out first. The slower-sample endpoint is an optimistic scenario, not an upper bound guaranteed by the provider. If the next task is longer, has more files or changes effort, take a new sample.
Independent estimate disclaimer
Unofficial independent estimator, not affiliated with or endorsed by ChatGPT. Usage can vary with plan, model, reasoning, context, caching, tools, attachments, parallel tasks, server load, promotions and policy changes. Results are conditional projections, not guaranteed maximum hours, requests or access. Account meters and provider notices take priority. Sources checked 9 November 2026.
The calculation runs on your device and does not connect to your AI account. Demo observations and request caps are fictional. A zero or rounded meter change cannot establish unlimited usage; a reset or decrease during measurement requires a fresh sample.
A few questions, answered
Does selecting Ultra apply a fixed quota multiplier?
No. Only settings your provider actually offers should be measured. Model and effort selections label samples, not invented provider multipliers.
Why can a five-hour limit end after two hours?
The window governs when allowance resets. It is not a guarantee of five active hours. A workload can consume its allowance before the window ends, while weekly or other feature limits can bind independently.