Updated guide · June 2026
In 2025 Anthropic added a weekly limit on top of Claude's rolling five-hour session limit for paid plans. It is the cap that explains why a short wait sometimes does nothing, and why heavy weeks feel tighter than busy hours. This guide covers what the weekly limit is, why it exists, how it resets, and what to do when you hit it.
Straight answer
Paid plans have a weekly cap on top of the 5-hour limit; check Settings → Usage for your reset. Even with a fresh five-hour window you can still be slowed once your weekly budget runs out. It applies to Pro, Max, Team and seat-based Enterprise, and was added in 2025. Verify in Claude → Settings → Usage; numbers change.
The weekly limit resets on a fixed weekly schedule, separate from the rolling five-hour window. Opus is tracked and reset separately from other models, and Max carries two weekly limits (all-models plus Sonnet-only). Read your exact reset time in Settings → Usage; numbers change.
What it is
For its first years Claude ran on a single short limit. The weekly cap is a newer, longer layer that measures usage across a whole week rather than a few hours, and it changes how heavy users plan their time.
Where the five-hour limit asks how much you did in the last few hours, the weekly limit asks how much you did across the week. It catches sustained, all-week usage that short windows never noticed.
Weekly limits apply to Pro, Max, Team and seat-based Enterprise. The free tier has its own tighter limits instead. If you are on a paid plan, you now have at least two limits stacked.
Settings then Usage shows separate reset information for Opus versus all other models, because Opus is far heavier. Max plans go further with two weekly limits, one across all models and one just for Sonnet.
Claude Code, Claude.ai chat and Cowork all draw from the same usage pool, so agent and coding work counts toward the same weekly budget as your chats.
Why it exists
The weekly limit was not added to punish normal users. It exists because a single short rolling window could not keep very high-volume, around-the-clock use sustainable for everyone sharing the same capacity.
| Problem | What the five-hour limit missed | What the weekly limit does |
|---|---|---|
| Round-the-clock automation | A script could reset its five-hour window again and again, running heavy work all day every day without ever tripping a short cap. | Caps total usage across the week so sustained automated load stays within a fair share. |
| A few users straining capacity | A small number of extreme users could consume a large share of resources, degrading speed and availability for everyone else. | Spreads capacity more evenly so the heaviest users cannot crowd out typical users. |
| Predictable cost and capacity | Open-ended weekly volume made demand hard to plan for, especially as agents like Claude Code grew popular. | Gives Anthropic a clearer ceiling per plan so service stays reliable. |
For most individual users the weekly cap is generous enough to never appear in normal work. It becomes visible mainly for daily Opus users, heavy Claude Code runs and teams pushing a plan hard all week.
Weekly vs 5-hour
The two limits feel completely different in practice, and knowing which one paused you tells you whether to wait a couple of hours or rethink your whole week.
| Aspect | Five-hour session limit | Weekly limit |
|---|---|---|
| Window length | A short rolling window of roughly five hours. | A long window covering the whole week. |
| How it resets | About five hours after your first message in the window. | On a fixed weekly schedule, separate for Opus and other models. |
| What clears it | A short wait usually frees you up again. | Only the weekly reset; waiting hours does nothing. |
| Best response | Pause, take a break, come back shortly. | Switch models, shrink scope, use another tool, or upgrade. |
| Where to check | Settings then Usage, session indicator. | Settings then Usage, weekly indicator with Opus reset. |
If a short break restores access, you hit the five-hour limit. If access stays blocked for the rest of the day no matter how long you wait, you are on the weekly limit and need a different strategy.
When you hit it
Hitting the weekly cap on a Wednesday can feel like a dead end, but you usually have more headroom than it appears. These steps keep you productive until the reset.
Open Settings then Usage. If the session indicator looks fine but the weekly one is exhausted, a wait will not help and you should switch strategy instead.
Opus is tracked separately, so you may be out of weekly Opus budget while still having room on Sonnet or Haiku. Move heavier reasoning to a lighter model.
Smaller, focused tasks cost less. Break a big request into the essential part now and defer the rest until after the weekly reset.
Claude Code and Cowork share the same pool. Holding off on big agent runs preserves the weekly headroom you have left for chat.
Keep a second model ready so a weekly cap never fully stops you. Running Claude alongside other models means one reset schedule does not block your week.
Note your weekly reset time from Settings then Usage and schedule your heaviest Claude work just after it, when you have a full budget again.
Max headroom
If you keep hitting the weekly cap during normal work, the cleanest fix is more headroom. Max multiplies your weekly budget and adds Opus, but it is worth understanding exactly what changes before you pay.
Roughly five times Pro usage at about $100 per month, which lifts both your five-hour and weekly budgets and unlocks Opus in chat. Good for daily heavy users who outgrow Pro.
Roughly twenty times Pro usage at about $200 per month, aimed at people who run Opus and Claude Code intensively every day and need the most headroom available on a seat.
Max carries two weekly limits, an all-models cap and a Sonnet-only cap, so heavy Sonnet work and heavy Opus work are budgeted separately. Confirm current numbers before upgrading.
Before buying, watch your Usage screen for a week to learn your real pattern, then compare it to the multiples. See our Claude Max limits and Claude Pro limits guides for the full comparison.
Alternatives
Because the weekly cap will not clear with a short wait, the cleanest fix is to not depend on one app's schedule. MultipleChat lets you run Claude alongside other models, so a single weekly reset does not block your work.
Run Claude-style answers next to ChatGPT, Gemini and search models in one workspace. When Claude is at its weekly limit, keep working in another model instead of waiting days for the reset.
AlternativeBroad assistant for writing, coding, images and everyday productivity when Claude is unavailable.
AlternativeUseful for Google Workspace and Google-context work.
ResearchResearch-focused answers with web sources when you need citations.
Our guideHow the Pro plan's 5-hour and weekly limits work day to day.
Our guideExactly when the 5-hour and weekly limits reset.
Our guideHow many messages each plan gives and why it varies.
Sources
Limits, prices and resets change. Use these official pages, and your own Settings then Usage screen, before making decisions.
Open Claude and check Settings then Usage for your live session and weekly limits.
Official plan names, current Pro and Max pricing and usage wording.
Anthropic explains Pro usage limits, resets and variables.
Details on what consumes usage and how the weekly limit is counted.
The acceptable use policy that frames how the service may be used.
FAQ
Short, hedged answers for people searching Claude weekly limit, Claude weekly cap, weekly vs 5-hour limit and Opus weekly reset.
The weekly limit is a longer cap that sits on top of the rolling five-hour session limit on paid plans. Even if you have not exhausted a five-hour window, you can still be slowed once you reach your weekly budget. It resets on a fixed weekly schedule, with separate tracking and reset timing for Opus versus other models, shown in Claude under Settings then Usage.
Anthropic introduced weekly limits in 2025 for Pro, Max, Team and seat-based Enterprise plans to keep heavy automated and round-the-clock use sustainable, so that a small number of very high-volume users could not degrade capacity for everyone. The five-hour limit alone did not catch sustained week-long usage.
The five-hour limit is a short rolling window that resets about five hours after your first message, so a short wait usually clears it. The weekly limit is a longer cap that resets on a fixed weekly schedule, so waiting a few hours does not help if you have hit it. The two stack, and Settings then Usage shows both.
Yes. Settings then Usage shows separate reset information for Opus versus all other models, and Max plans carry two weekly limits, one across all models and one specifically for Sonnet. You can be out of weekly Opus budget while still having headroom on lighter models.
Waiting hours will not help because the weekly cap resets on its own schedule, not every five hours. If you still have headroom on lighter models, lean on Sonnet or Haiku, reduce the scope of tasks, work in another tool, or consider Max. The reset time is shown in Settings then Usage.
Weekly limits apply to paid plans including Pro, Max, Team and seat-based Enterprise. The free tier has its own much tighter limits. Max plans raise the weekly headroom substantially and add a second weekly limit specifically for Sonnet. Verify your plan details in Settings then Usage.
Max 5x is roughly five times Pro usage and Max 20x roughly twenty times, which raises both the five-hour and weekly headroom and adds Opus access. Max also has two weekly limits, an all-models cap and a Sonnet-only cap. Confirm current pricing and limits on the official pages before upgrading.
Claude Code, Claude.ai chat and Cowork all draw from the same usage pool, so a few large agent or coding runs earlier in the week can consume your weekly budget even if your chat use looks light. Check Settings then Usage to see how much of the week you have already spent.