Less guesswork. Better AI spending.
Claude Usage Limits 2026: Session, Weekly Reset & Billing
Find your five-hour session and weekly limits, record the exhausted allowance and distinguish subscription usage, paid extras and eligible Max API credit.
Last reviewed:
Where to read your remaining allowance
For supported paid plans, open Settings > Usage. The official guide describes a five-hour session bar and weekly limits with reset information. The account display is the source for your allowance; this website cannot read it for you or calculate a universal reset timer.
Open the account you actually use, note the plan and take a private record of the displayed allowance and timezone. If you use Claude Code as well as chat, check its active credential before deciding that the same subscription allowance is paying for the request.
Session reset and weekly reset are different
The official Max guide says the session window resets every five hours, while the weekly reset occurs at a fixed time assigned to the account. One reset does not mean every allowance is full. Read the precise bar or message that blocked the task.
Illustrative schedule only: if your account displays a session reset at 18:00 and a weekly reset on Monday at 09:00, waiting until 18:00 cannot be assumed to restore an exhausted weekly allowance. The example times are not your account times. Plan the next task from the displayed constraint, with room for review.
A small log makes the bottleneck visible
Record date and timezone, plan, selected model, task, input or attachments, exhausted bar, displayed reset, accepted result and extra spend. A sample entry is “10 October, local time; document review; session bar exhausted; reset shown 18:00; draft incomplete; no extra spend.” This is a blank-record example, not measured site data.
Compare similar tasks instead of adding all requests together. A long document, repeated retry or multi-step tool task may not cost the same capacity as a short question. Track whether the intended work was accepted after review, rather than treating a quick generated response as the finished result.
Included usage, paid extras and API credit
A subscription allowance, optional usage credits and a Console API balance are distinct. Before using an additional paid path, check the active credential, organization, spending controls and billing record. Do not assume that a chat reset replenishes API credits.
Eligible Max monthly API credits require a claim into a Console organization; Pro is not eligible for that benefit. Follow the official credit page for claiming and expiry. Keep a budget row for subscription payment and another for API or optional usage charges.
Troubleshoot before upgrading
If the account display and a tool disagree, first confirm account identity, connection method and the exhausted allowance. Preserve a non-sensitive error and the displayed time for support. Do not delete credentials or repeatedly retry a billable task simply because a timer in another screenshot has expired.
Reduce avoidable reruns by agreeing on the task and acceptance criteria before starting. If the log shows a repeated capacity bottleneck, compare the relevant higher tier; if most work needs correction, a capacity upgrade alone will not solve the quality issue.