Codex 5-hour vs weekly usage limits
Codex can have separate 5-hour and weekly usage windows. Read each allowance and reset time from your account; a full banked reset can refresh both.
Start here
Identify which allowance is exhausted and read its displayed reset time.
Two windows, two behaviours
The official material refers to a short window and a weekly window as separate Codex usage windows. They behave differently in the one way that matters for planning your day:
- The 5-hour window is a separate allowance. Read its reset time from your account. The reviewed help article does not define enough accounting detail to calculate it from your last prompt or assume that every request moves the deadline.
- The weekly window is a longer cycle with a date. It is the one whose reset date can change — for example after a full banked reset is applied.
That difference is exactly why a single countdown cannot describe your situation. A countdown answers “when does this one thing happen”. If you have two things, you need two answers.
How they interact
From the documented description of a full banked reset: it refreshes both windows and changes the weekly reset date.
Two practical consequences:
- Refreshing one does not imply the other is fresh. Check both rather than assuming.
- The weekly date is the one that moves after a reset. If you wrote down a weekly date and then applied a reset, your note is stale.
Why a shared public timer misleads here
Public announcements describe events, not your personal short-window allowance. An announcement can refresh your windows, which is genuinely useful. But a public post does not expose your account’s remaining allowance or its displayed reset time.
So the honest model is:
- Read your own state from Settings, the usage dashboard or
/status. - Track your own dates deliberately, especially the weekly one, because it is the one that moves.
- Treat public events as additional information, not as a replacement for your own numbers.
Setting up two timers without confusing yourself
This site’s personal timer supports two named timers for exactly this reason. If you use it:
- Name them. “Short window” and “Weekly” is enough. A label you cannot read at a glance is a label you will misread later.
- Enter the time your account shows, in your own timezone. The tool displays both your local time and UTC, and records the offset you confirmed, so a later timezone mistake is visible rather than silent.
- Do not derive one from the other. Five hours from now is not a weekly reset, and the weekly date is not the end of the short window.
- Re-set them after anything that moves a date. After a full banked reset, replace the saved dates. After a plan or policy change, check whether the displayed times changed before editing your timers.
Quick checks when the two disagree with reality
- Which window was actually exhausted? The usage screen tells you; a countdown does not.
- Did you apply a reset since you set the timer? Then the weekly date changed.
- Are you on a workspace plan? An administrator may control your effective limit and reset period.
- Did you cross a daylight-saving change? Your local time moved; the instant did not. Compare in UTC if you are unsure.
When a limit notice is already blocking requests, follow the usage limit reached guide for the account checks and available next steps.
What this guide deliberately does not do
It does not state how many requests or how much usage any window allows, and it does not infer reset scheduling beyond the two windows named by the source. Those numbers vary by plan and change; inventing them would make every countdown built on them wrong.
FAQ
Are the 5-hour and weekly windows the same allowance?
No. Identify which window is exhausted in your account. A countdown for one window does not tell you the remaining allowance in the other.
Can I calculate my weekly reset by adding five hours?
No. Read each displayed reset time separately. Do not derive the weekly date from a short-window countdown or another account’s schedule.
What should I do with saved timers after a full banked reset?
Read the updated times in your account and replace the saved dates. A full banked reset refreshes both windows and changes the weekly reset date.
Known limits of this guidance
- Evidence level: documentary, from the official help article as read on the review date.
- The source names the 5-hour and weekly windows but does not fully specify the accounting algorithm. This guide does not infer rolling behavior or compute reset times from activity.
- Other allowance types, such as credits or workspace budgets, are separate again and are covered by their own guides.
This guide is part of our Codex usage limits and reset guides.
Useful Codex tools
Sources
Each source lists what it is used to support. Sources are re-read on the review schedule, not continuously.
Using Codex with your ChatGPT plan (OpenAI Help Centre)
That the official material refers to a 5-hour window and a weekly window as distinct Codex usage windows; that applying a full banked reset refreshes both and changes the weekly reset date; and that the usage screen should be checked afterwards for the updated reset time.
Using Codex with your ChatGPT plan - which allowance is exhausted
That more than one allowance can exist on an account and that the documented check is to identify which allowance is exhausted, which is the reason this guide treats the windows as separate clocks.
Related guides
How this page is checked
- Evidence level
- Documentary - supported by official documentation
- Last reviewed
- 2026-09-22
- Content updated
- 2026-10-10
- Full version scope
- Official help guidance reviewed on 2026-09-22. Per-plan allowance amounts and the detailed accounting algorithm are not asserted.
- Symptoms indexed
-
- You set one timer and it disagreed with the app
- You were unblocked on one window but still limited on another
- You are unsure which countdown to trust
Reviewer note
Confirmed the two named windows and full banked reset behavior. Removed unsupported rolling-window inference. FAQ and related links added on 2026-09-28; the full-article review date remains as shown.