What Is Claude's 5-Hour Limit? (And How to Track It)
In this article
- How does the 5-hour limit work?
- How do Pro and Max limits compare?
- What's the difference between the 5-hour limit and the weekly cap?
- When does the 5-hour window reset?
- How do you check how much of the 5-hour window is left?
- Why does Claude Code use a 5-hour window instead of a daily limit?
- How do you avoid hitting the 5-hour limit mid-task?
- Can you reset the 5-hour limit early?
- Key takeaways
- Sources
Claude Code enforces a rolling 5-hour usage window on Pro and Max plans. When you exhaust your token allowance within that window, you're locked out from sending new requests until the window expires and resets. This affects all Claude Code users on paid plans, and the limit is separate from the weekly cap. There's no fixed clock time it resets at; the window is calculated from your first message, not midnight.
- The 5-hour window is rolling, not fixed to a daily schedule
- Pro plan has a significantly lower cap than Max 5x or Max 20x
- A separate weekly cap also applies and resets independently
How does the 5-hour limit work?
Claude Code tracks your token consumption across a rolling 5-hour window. The moment you send your first message in a session, the clock starts. If you consume your full allowance before 5 hours have passed, Claude Code stops accepting new messages and tells you to wait. The lock lifts automatically once that original 5-hour window closes, freeing up the capacity consumed at the start.
This means two things matter: how much you use, and when you use it. Heavy usage early in the window can leave you blocked for several hours, even if you didn't hit the weekly cap. As of August 2026, Anthropic's support documentation confirms this rolling-window architecture is by design, intended to manage backend load rather than enforce a hard daily budget.
How do Pro and Max limits compare?
The 5-hour cap differs significantly across plans. Max 5x gives roughly 5x more usage within each window compared to Pro, and Max 20x gives roughly 20x more. Pro users doing heavy refactoring or large context work can exhaust the window in under an hour. Max 20x users rarely hit the 5-hour cap but may still encounter the weekly cap first.
| Plan | 5-Hour Window Cap | Weekly Cap | Price |
|---|---|---|---|
| Claude Pro | Baseline | Yes | $20/mo |
| Claude Max 5x | ~5x Pro | Yes | $100/mo |
| Claude Max 20x | ~20x Pro | Yes | $200/mo |
For a deeper breakdown of how these plans compare for daily coding work, see Claude Pro vs Max limits.
What's the difference between the 5-hour limit and the weekly cap?
These are two independent constraints. The 5-hour limit is a short-term rate limiter: it resets every 5 hours and prevents burst overuse. The weekly cap is a harder ceiling on total usage within a 7-day period. You can hit either one independently. A Pro user doing a 4-hour coding sprint may hit the 5-hour limit without touching the weekly cap, while a consistent daily user might exhaust the weekly cap by Thursday.
See Claude Code weekly limit vs 5-hour lockout for a full comparison of how each constraint triggers and resets.
When does the 5-hour window reset?
The window resets exactly 5 hours after the first message that consumed capacity in that window. There is no fixed reset time tied to midnight, your time zone, or Anthropic's servers. If you sent your first message at 2:15 PM and burned through your cap, the window re-opens at 7:15 PM. The /usage command inside Claude Code shows a countdown to your next reset.
For more detail on timing behavior, see when does Claude Code usage reset and how long until Claude Code resets.
How do you check how much of the 5-hour window is left?
There are three ways to monitor your remaining capacity. First, run /usage inside a Claude Code session; it returns a summary of current consumption and time until reset. Second, visit claude.ai/settings/usage in your browser to see account-level usage. Third, Usagebar ($9 one-time) sits in your macOS menu bar and shows your 5-hour window consumption, weekly cap, and context usage in real time, with notifications at 50%, 75%, and 90% thresholds so you're never surprised by a lockout mid-session.
Learn more about all available methods in how do I check my Claude Code usage limits and how to check the Claude Code reset timer.
Why does Claude Code use a 5-hour window instead of a daily limit?
A rolling window prevents sustained overload on Anthropic's infrastructure while giving users flexibility. A fixed daily limit would still allow bursting at the start of each day, creating demand spikes. The rolling design smooths demand by spreading consumption over time. It also means a power user hitting the cap at noon isn't blocked until midnight; they only wait until 5 hours after they started.
How do you avoid hitting the 5-hour limit mid-task?
The most effective approach is keeping context windows tight. Large file reads, verbose back-and-forth, and repetitive re-explanations all consume tokens unnecessarily. Some practical strategies:
- Use precise, targeted prompts instead of open-ended requests
- Avoid feeding entire files when only a function is relevant
- Break long sessions into shorter focused tasks with fresh contexts
- Monitor remaining capacity proactively with
/usageor Usagebar before starting a large refactor - Schedule heavy work early in your 5-hour window so you have context on remaining capacity
For token-saving techniques, see how to reduce Claude Code token usage.
Can you reset the 5-hour limit early?
No. Anthropic does not offer a way to manually reset the 5-hour window. Once you've consumed your cap, you wait for the rolling window to expire. Upgrading your plan (for example, from Pro to Max 5x) increases the size of the cap but does not grant an early reset. Canceling and restarting a subscription does not bypass it either. The only option is to wait or to switch to a paid API key with usage-based billing, which has no rolling window cap.
See can you reset Claude usage limit early for the full breakdown.
Key takeaways
- Claude Code's 5-hour limit is a rolling window, not a fixed daily reset
- The window starts from your first message and expires 5 hours later
- Pro, Max 5x, and Max 20x each have different capacity thresholds for the same window
- A separate weekly cap exists independently and resets on a 7-day cycle
- Check remaining capacity with
/usage, claude.ai/settings/usage, or Usagebar - There is no early reset; you wait for the window to expire or switch to API billing
Sources
Never Get Locked Out Mid-Task Again
Never hit your usage limits unexpectedly. Usagebar lives in your menu bar and shows your 5-hour and weekly limits at a glance.
Get Usagebar$9 — one-time, lifetime updates