The weekly reset time for your Claude allowance is printed in the error message itself, in the form resets Mon 12:00am. That is your answer, and it is account-specific — which means no article can give you a universal reset hour, including this one.
What this page can do is three things the reset-time tables do not: show you where to read your own value, explain which of the two commonly-repeated figures is actually documented, and give you a conversion table so you can turn the printed UTC-based value into your local clock without guessing.
Read the value off your own account first
Before anything else, get your real number. There are three places:
| Where | What you get | Note |
|---|---|---|
| The error message | resets Mon 12:00am — the exact next reset | Authoritative. Server-issued |
| Settings → Usage on claude.ai | Weekly usage bar plus the next reset | The only view that counts all your activity |
/usage inside Claude Code | Session and weekly bars with reset times | Approximate; read from that machine's local history |
If you have the value from either of the first two, stop reading tables. You already have better information than any published schedule.
The two figures people quote, and which one is documented
Search for this and you will find two claims presented with equal confidence:
Claim one: the weekly cap resets at a fixed day and time assigned to your account. This matches how Anthropic describes it in its error reference — the message names a specific day and time, and that value is yours. Under this reading, the reset is fixed per account, which is why two users can see different printed times.
Claim two: everyone resets at 00:00 UTC on Monday. This is widely repeated, and it is consistent with what a great many users see. It is also not something Anthropic publishes as a guarantee. It reads like an account-assigned anchor that happens to land there for most people, generalised into a rule.
The distinction matters because of what follows from each. If the reset is assigned to your account, then a schedule you read elsewhere cannot be relied on and the printed value is the only truth. If it is globally anchored to UTC, then a conversion table is genuinely useful for planning ahead.
Practically, you can satisfy both readings at once: plan around your printed value, and use the table below only to sanity-check that the value you were given lands where you expect it to.
If your value is the midnight-UTC anchor, here is where that lands
Anthropic uses UTC as the reference timezone for quota periods, so the printed value is best read as a UTC instant and converted. On a Monday 00:00 UTC anchor:
| Your timezone | Local reset time | Day |
|---|---|---|
| UTC | 00:00 | Monday |
| US Eastern (UTC−4, summer) | 20:00 | Sunday |
| US Pacific (UTC−7, summer) | 17:00 | Sunday |
| UK (UTC+1, summer) | 01:00 | Monday |
| Central Europe (UTC+2, summer) | 02:00 | Monday |
| India (UTC+5:30) | 05:30 | Monday |
| China (UTC+8) | 08:00 | Monday |
| Japan (UTC+9) | 09:00 | Monday |
Two things to notice. First, for anyone in the Americas the weekly reset lands on Sunday evening, not Monday — so "it resets Monday" is off by a day in exactly the timezone where most of the confusion gets reported. Second, the offsets above are summer values; add an hour in winter for the northern-hemisphere zones other than the fixed-offset Asian ones.
Why the session limit behaves completely differently
The weekly cap is a fixed anchor. The session window is not, and conflating them is the root of most bad advice on this topic.
The session window rolls from your own activity. There is no hour you can wait for; there is only a countdown that starts when you start using it. That is why the session error shows a time like 3:45pm — a value derived from when you began working — while the weekly error shows a day of the week.
So "wait for the reset" means two different things depending on which error you got. For the session window it means a few hours at most. For the weekly cap it can mean most of a week.
What you cannot do
- Move it. There is no way to reset the weekly window early, on either plan tier.
- Upgrade your way out of it. Moving to a higher tier raises the ceiling for future windows; it does not refill the one you have spent.
- Wait out the session window instead. The two budgets are independent. A session reset restores zero weekly allowance.
- Game it by waiting for a specific hour. Because the session window follows your activity rather than the clock, there is no hour at which waiting becomes productive.
What you can do is change the inputs: switch model when the error names one, reduce how much the same work costs in the first place, buy capacity if your plan offers it, or be told early when the vendor lifts caps so you are not idly waiting.
How to plan a week around a fixed anchor
Once you know your anchor, the useful move is to place work relative to it rather than relative to Monday morning.
If your anchor is Sunday evening in the Americas, the working week effectively starts then: your freshest capacity is Sunday night through Monday, and by Thursday you are living on leftovers. Teams that schedule their heaviest refactors for Wednesday are scheduling them into the thinnest part of their own budget.
An anchor you have verified yourself is worth more than any table, because it is the one input that does not change when someone publishes a new article.
FAQ
Is the weekly reset the same for Pro and Max? The mechanics are the same shape — a rolling session window plus a weekly anchor. What differs is the size of the allowance, which Anthropic does not publish. So the timing question has the same answer on both tiers; the "how much do I get back" question does not.
My printed reset time changed. Is that a bug? If you moved or changed your account's region settings, a shift is expected. Otherwise, treat a change as worth noting rather than assuming — the printed value is the primary source, and it is the one to trust.
Should I use a third-party countdown app instead? Those tools are convenient, and the ones that read your own account are genuinely more accurate than any published schedule. Two cautions: any tool that shows a countdown for a limit it cannot query is estimating, and tools that ask for your credentials are asking you to take a security decision, not a convenience one.
Sources
- Claude Code error reference — Anthropic. The error strings, including the weekly form and its printed reset day.
- Models, usage, and limits in Claude Code — Anthropic. How usage is metered and what is shared.
- Claude plans and pricing — Anthropic. Tier structure.
For which error means what, and the fixes that actually work, see Claude Code has three limits. For why no service can predict a vendor reset for you, see Three kinds of reset.