How Much Is the Claude Weekly Limit? Pro vs Max Hours Explained

The Claude weekly limit depends on your plan: Claude Pro ($20/mo) gets roughly 40-80 hours of Sonnet 4.5 usage in Claude Code per week, while Max 5x ($100/mo) gets about 140-280 hours plus 15-35 hours of Opus, and Max 20x ($200/mo) gets 240-480 Sonnet hours plus 24-40 Opus hours. The exact number varies by account because Anthropic measures it in model-compute terms, not a flat token count. For developers who burn through limits fast, pairing any plan with Usagebar ($9 one-time) gives a real-time menu bar view of how close you are to both the 5-hour session cap and the weekly cap.

How much is the Claude weekly limit?

The Claude weekly limit is a usage ceiling layered on top of the 5-hour session limit, introduced so a small number of heavy users don't consume disproportionate compute. For Claude Pro, the typical allowance is 40-80 hours of Sonnet 4.5 Claude Code usage per 7-day window. Max 5x and Max 20x scale up from there, with separate (smaller) weekly allowances for Opus since it costs more compute per request (Claude Code usage limits, Anthropic Support).

What are the exact caps by plan?

Anthropic publishes these as hour-ranges rather than fixed numbers because actual usage depends on prompt size, codebase size, and how much context Claude reads per turn. The table below reflects the official ranges Anthropic documents for Claude Code weekly usage.

Plan	Price	Sonnet 4.5 hours/week	Opus hours/week
Claude Pro	$20/mo	~40-80	Not included
Claude Max 5x	$100/mo	~140-280	~15-35
Claude Max 20x	$200/mo	~240-480	~24-40

These ranges are current as of October 2026; Anthropic can adjust them, so check the official usage limits article for the live numbers tied to your account.

When does the weekly limit reset?

The weekly limit resets exactly 7 days after your first Claude Code session in that cycle, not on a fixed calendar day like Monday. This is separate from the 5-hour rolling session window, which resets independently and more frequently. For a full breakdown of how the two clocks interact, see Claude weekly limit reset time and Claude Code weekly limit vs 5-hour lockout.

How do I check my current usage?

Run /usage inside Claude Code to see your remaining 5-hour and weekly allowance directly in the terminal. You can also check claude.ai/settings/usage in a browser, or install Usagebar for a persistent menu bar display that updates without you having to type a command.

• /usage command: fastest, but you have to remember to run it (Claude Code slash commands docs)
• claude.ai/settings/usage: good for a historical view, requires switching to a browser
• Usagebar: always-visible, tracks 5-hour window + weekly cap + context usage simultaneously, with alerts at 50/75/90% so you're never blindsided mid-task

More detail on each method is in how do I check my Claude Code usage limits.

What happens when I hit the weekly cap?

Hitting the weekly cap blocks new Claude Code requests until the 7-day window resets; you'll see a rate-limit message instead of a response. It does not downgrade your plan or charge extra by default. If this happens mid-sprint, see Claude Code rate limit exceeded and what to do while you wait for the reset.

How can I avoid hitting the weekly limit?

Avoid hitting the weekly limit by monitoring usage proactively instead of reacting after a block. Three practical habits:

1. Check remaining hours before starting a large refactor, not after Claude stops responding.
2. Use Sonnet for routine edits and reserve Opus for complex architectural work, since Opus consumes its own smaller weekly pool.
3. Set up alerts (Usagebar does this at 50/75/90%) so you can wrap up a task before the cutoff instead of losing context mid-session.

Key takeaways

• Claude Pro: ~40-80 Sonnet hours/week, no separate Opus allowance.
• Max 5x: ~140-280 Sonnet hours/week + 15-35 Opus hours/week.
• Max 20x: ~240-480 Sonnet hours/week + 24-40 Opus hours/week.
• The weekly reset is a rolling 7-day window from your first session, separate from the 5-hour limit.
• Usagebar ($9 one-time) tracks both limits plus context usage in your macOS menu bar.

Track your limit before you hit it

If you're on Max and still getting blocked mid-week, the fix usually isn't the plan, it's visibility. Get Usagebar for a one-time $9 and see your 5-hour window, weekly cap, and context usage in real time, with alerts at 50/75/90% so you can plan around the reset instead of discovering it mid-task.

Sources

• Claude Code usage limits, Anthropic Support
• Claude Code slash commands docs