When do Claude limits reset?
Claude has two reset clocks. The five-hour session window resets five hours after the message that opened it, so it rolls with you through the day. The weekly caps reset at a fixed time each week that is assigned to your account, which is why there is no single published reset hour anyone can quote you. Both are shown on your own usage screen in your local timezone, and that screen is the only reliable answer.
The short answer
If you went looking for the reset time and could not find one, that is not a documentation gap. There genuinely is not a universal reset hour to find.
- Five-hour session window: resets roughly five hours after your first message of that window, on the top of an hour. Rolling, personal, and at a different time every day depending on when you start.
- Weekly caps: reset at a fixed time each week assigned to your account. Stable week to week for you, but not the same hour for everyone.
- Where the real number lives: Settings > Usage on web and desktop, or
/usagein Claude Code. Both display the next reset in your local timezone.
Everything below is the detail behind those three lines.
Weekly limits reset at a time assigned to your account
Weekly caps do not reset at a global hour like Sunday midnight UTC. Each account is assigned its own fixed weekly reset time, and it stays put week after week. So your reset really is predictable, it is just predictable for you, and copying somebody else's reset time from a forum thread will give you an answer that is wrong by hours or days.
Remember that there are two weekly ceilings: one that applies across all models and a separate one for Opus. Both appear on the usage screen with their own progress bars. You can be pinned against the Opus cap while the general one still has room, in which case switching models gets you working again immediately rather than waiting for any reset at all. Full mechanics: Claude weekly usage limits, explained, plus what the approaching weekly limit warning means.
The five-hour window is the rolling clock
The session window is the one that moves. It opens with your first message, not with a login, and it runs about five hours from there. Anthropic's usage documentation adds one detail worth knowing: reset times land on the top of an hour, counted from the hour in which you sent that first message, so a window opened at 8:55am can end at 1:00pm rather than 1:55pm. Do not count minutes; read the time off your usage screen.
Two details matter when you are waiting on one. The reset is counted from when the window opened, not from when you hit the limit, so running out at 10:30am in a window that opened at 9:00am puts you back at 2:00pm rather than 3:30pm. And the next window does not begin until you send your next message, so windows drift instead of tiling the day neatly. Full detail: the Claude 5-hour session limit.
What timezone does Claude use?
This is the half of the question nobody answers, so here it is directly: read your own usage screen and it is already in your local time. Settings > Usage in the web and desktop apps, and /usage in Claude Code, both render reset times in the timezone your device is set to. There is nothing to convert and no UTC offset to work out.
Which makes the practical answer to "what timezone does Claude use for limits" this: your own, for display, and the underlying weekly schedule is anchored to your account rather than to a public clock. That is exactly why forum answers conflict with each other. Somebody in Sydney and somebody in Denver, each honestly reporting what their own screen says, will give two different reset hours and both will be right about their own account. Do not trust a reset time you did not read on your own usage screen. Walkthrough: how to check your Claude usage.
Planning around your personal reset
Once you have read your actual weekly reset time, it stops being a mystery and becomes a scheduling asset:
- Front-load the week after your reset. The heaviest agentic work is safest in the first days of your cycle, while both weekly ceilings are full.
- Treat the day before your reset as a light day. If you are going to run low, that is when, and a long unattended run is the worst thing to start there.
- Open session windows deliberately. A trivial question at 8:55am opens the same window your 9:30am heavy work has to share. Batching keeps windows whole.
- Count every surface. claude.ai, Claude Desktop, and Claude Code all draw on the same pool, so a heavy terminal day and a heavy browser day compound against the same caps.
- Ignore the time of day. Anthropic removed the peak-hours reduction for Claude Code in May 2026, so as of August 2026 there is no busy-time penalty to plan around. See the best time to use Claude.
What the reset takes away from you
Here is the other thing knowing your reset time tells you: exactly when your unused capacity disappears. Both clocks are ceilings, not balances. At the reset your allowance refills to the same level whether you used all of it, some of it, or none of it, and nothing accumulates.
Tokens for Good is built to catch that recurring surplus before the reset takes it. Your Claude Code claims a queued nonprofit, researches its real-world impact against a fixed methodology with citations, and submits a structured report. Every organization is researched twice by independent contributors, then validated, consolidated, scored deterministically, and human-reviewed before it reaches the public directory. It runs on the subscription you already pay for with no separate API cost, and because it can run on a schedule you can aim it squarely at the quiet part of your cycle. "Tokens" means AI model tokens, not crypto: no coin, no wallet, no blockchain. See how the research works or the docs.
Frequently asked questions
Why did my Claude weekly limit reset after one day instead of seven?
What time do Claude weekly limits reset?
What time zone does Claude use for usage limits?
What time does Claude Max reset?
Does Claude Code show reset times in my local timezone?
What times does Claude reset?
Every reset erases what you did not use
Session windows and weekly caps refill to the same ceiling regardless of how much you touched. Tokens for Good turns that expiring headroom into verified nonprofit research on the plan you already pay for.
See how Tokens for Good works