Claude's 5-hour session and weekly limits, explained
What the Claude 5-hour session limit and weekly limits really mean, when they reset, and what to do when you hit 'usage limit reached'.
Anthropic caps Claude usage on two timescales, and understanding both is the difference between planning your week and getting blocked mid-task. Here's how each one works.
The 5-hour session limit
Your usage is measured in rolling 5-hour sessions. The clock starts on your first message and resets roughly five hours later — so there's no single daily reset time; it moves with you. Heavy Claude Code runs (large files, long agentic loops) burn this bucket fastest.
The weekly limits
On top of the session cap there are weekly limits on a 7-day rolling window: one for all models combined, and on Max plans a separate, tighter cap for Opus. You can be fine on your session but still blocked because the weekly bucket is spent.
What 'usage limit reached' actually means
That message means one of the buckets above is empty. The fix is simply to wait for the relevant reset — but knowing *which* limit you hit (and when it comes back) saves hours of guessing.
The most common surprise is hitting the weekly Opus cap while the all-models weekly still has room — switch to Sonnet and you can often keep working.
Stop getting surprised
How Much Claude shows both limits with live reset countdowns and warns you at ~90% so you can slow down or switch models before you're blocked.
Frequently asked questions
- What's the difference between the session and weekly limit?
- The 5-hour session limit is short-term and resets a few hours after your first message; the weekly limits reset on a 7-day rolling window and include a separate Opus cap on Max plans.
- How do I know which limit I hit?
- Claude only says 'limit reached'. A dashboard that shows each bucket separately (session, weekly all-models, weekly Opus) tells you which one, and when it resets.