Verified against Anthropic Help Center · July 31, 2026
Claude weekly usage limits are separate from the five-hour session limit. A paid account can therefore have capacity left in its current five-hour window but still be blocked by a weekly cap—or reach the five-hour limit while weekly capacity remains. Pro generally has one weekly limit across all models, while Max and certain premium organization seats can show an additional model-specific weekly limit.
The short answer
- Five-hour limit: a shorter usage window that resets five hours after the applicable session begins or limit is reached.
- Weekly limit: a longer allowance that resets at a fixed day and time assigned to the account.
- Pro: Anthropic currently describes one weekly limit that applies across all models.
- Max: Anthropic currently describes an all-model weekly limit plus another weekly limit for Sonnet models.
- Shared usage: work in Claude on the web, Claude Desktop, and Claude Code can draw from the same subscription limits.
- No universal message number: conversation length, files, tools, model, effort, and task complexity change how fast capacity is consumed.
Claude’s limits are layered, not interchangeable
| Limit | What it controls | Reset behavior | Where to check it |
|---|---|---|---|
| Five-hour session | Short-term use across conversations and supported Claude surfaces | Every five hours under the account’s current session schedule | Settings → Usage and the warning message |
| Weekly all-model limit | Total included use across the models covered by the plan | Fixed weekly day and time assigned to the account | Settings → Usage |
| Model-specific weekly limit | Use of the model family named on the account’s meter | Fixed weekly schedule shown on the meter | Settings → Usage |
| Conversation length | How much material one chat can hold | Does not reset like a usage allowance | The conversation warning or context indicator |
| Usage credits | Pay-as-you-go use after included capacity | Does not change the included limit’s reset time | Settings → Usage |
The first three are usage limits. Conversation length is a context limit, not another weekly allowance. Starting a new chat can solve a length problem, but it does not restore the account’s five-hour or weekly capacity.
How the five-hour session limit works
Anthropic describes paid Claude plans as having a session-based allowance that resets every five hours. The allowance is not a promise of a fixed number of messages. A short question in a fresh chat consumes less than a long request that includes files, Research, web search, extended thinking, or a large conversation history.
When the account approaches the session limit, Claude can show an “Approaching 5-hour limit” warning. If the included session allowance is exhausted, the blocking message normally includes the reset time. Our separate guide explains what to do when the Claude five-hour limit is reached; this article focuses on the longer weekly layer.
How the weekly reset works
The weekly limit does not necessarily reset seven days after your first message, at midnight, or when your subscription renews. Anthropic says each account receives a fixed weekly reset day and time. That schedule stays the same regardless of when the user begins working during the week.
To find the authoritative time for your account:
- Open Claude on the web or desktop app.
- Open Settings.
- Select Usage.
- Look under Plan usage limits.
- Read the reset date and time shown beside each weekly meter.
Use the displayed time rather than converting a schedule from another user’s screenshot. Account time zones, plan types, model access, and staged product changes can make two Usage pages look different.
Pro, Max, and Team do not show identical weekly limits
| Plan or seat | Five-hour capacity | Current weekly structure described by Anthropic |
|---|---|---|
| Pro | At least 5× the free service per session during peak hours | One weekly limit across all models |
| Max 5x | 5× Pro capacity per session | An all-model weekly limit and a Sonnet-only weekly limit |
| Max 20x | 20× Pro capacity per session | An all-model weekly limit and a Sonnet-only weekly limit |
| Team Standard seat | 1.25× Pro capacity per session | One weekly limit across all models |
| Team Premium seat | 6.25× Pro capacity per session | An all-model weekly limit and a Sonnet-only weekly limit |
These multipliers describe relative session capacity, not a guaranteed number of prompts. Team limits are per member, so one member reaching a cap does not consume another member’s allowance.
Model names and meter labels can change as Anthropic releases or reassigns models. The live meter in Settings → Usage is the final authority for the account. For subscription prices and intended use cases, see our Claude Pro vs Max comparison.
What “all models” and a model-specific cap mean
An all-model weekly limit is the outer budget: eligible work with any covered model contributes to it. A model-specific limit is an additional ceiling for the named family; it is not bonus capacity added on top of the all-model pool.
Consider a simplified example. If a Max account uses Sonnet heavily, that activity can increase both the Sonnet-specific meter and the all-model meter. Reaching the model-specific ceiling may prevent more work with that model even when some all-model capacity remains. Whether the account can switch models depends on the current model access and the message Claude displays.
Do not add the two percentages together or assume that 50% on each means the account has used 100% of one combined balance. They represent overlapping constraints.
Does Claude Code use the same weekly allowance?
Yes—when Claude Code is authenticated through a Pro or Max subscription, Anthropic says Claude and Claude Code share the plan’s usage limits. Long coding sessions, repository scans, tool calls, and large conversation histories can therefore affect what remains in the Claude app.
This is different from Claude Code authenticated with an API key. API use is metered and billed to the Console or cloud provider rather than deducted from the consumer subscription. If coding work unexpectedly creates API charges, follow our guide to checking whether Claude Code is using API billing instead of the subscription.
Why the weekly percentage can rise faster than expected
- Long conversations: Claude processes relevant history again with later turns.
- Large files or project knowledge: more context requires more processing.
- Research and web search: multi-step tool work can consume more capacity than a short response.
- Extended thinking and high effort: deeper computation can use more of the allowance.
- Model choice: different models and model-specific caps affect consumption.
- Claude Code: coding work shares limits when signed in with the subscription.
- Several devices: the limit belongs to the account, not one browser or computer.
Counting visible prompts is therefore unreliable. Compare the Usage page before and after a controlled task if you need to identify which workflow is expensive.
What happens when a weekly limit is reached?
The account may be unable to continue included usage for the affected models until the weekly reset. The exact options depend on the plan and which meter was exhausted:
- Wait for the reset time shown in Settings → Usage.
- Switch to another available model if only a model-specific cap was reached and the app offers that option.
- Enable usage credits to continue at pay-as-you-go rates.
- Move from Pro to Max, or from Max 5x to Max 20x, if limits are reached consistently.
A subscription upgrade is usually a better structural answer for recurring heavy work. Usage credits are more flexible for occasional overflow but create charges separate from the subscription.
Usage credits do not refill the weekly meter
Usage credits let eligible paid subscribers continue after included capacity is exhausted. They do not increase the percentage shown on an included meter or move its reset time. Once credit use begins, additional work is charged at Anthropic’s standard pay-as-you-go rates.
Credits are enabled on the web, even for a subscription originally purchased in a mobile app. Set a conservative monthly spending limit before adding funds. Read our full explanation of Claude usage credits, costs, and spending controls before turning them on.
How to make Claude capacity last longer
- Start a fresh chat for a new task. Do not carry an unrelated long history into every request.
- Plan before sending. Combine requirements into one precise prompt rather than repeatedly correcting incomplete instructions.
- Use Projects for reusable sources. Anthropic says project knowledge can benefit from caching when reused.
- Choose the efficient model for routine work. Reserve more capable or model-limited options for tasks that need them.
- Reduce unnecessary tools and effort. Disable Research, web search, connectors, or extended thinking when they add no value.
- Monitor both time horizons. A low five-hour percentage does not mean the weekly meter is healthy.
Common misunderstandings
“My five-hour limit reset, so weekly use should reset too.”
No. The five-hour and weekly schedules are independent. A session reset restores short-window capacity but does not restart the account’s assigned weekly cycle.
“Starting a new conversation restores my usage.”
A fresh conversation can reduce future context processing and solve a length-limit problem. It does not erase capacity already consumed from the five-hour or weekly allowance.
“Max 20x means twenty times as many messages every week.”
Anthropic describes 20x as relative session capacity compared with Pro. Actual message volume still changes with model, files, tools, thinking, and conversation length, and weekly limits remain.
“The Claude API is included in Pro or Max.”
No. Consumer subscription usage and API billing are separate. Usage credits can continue Claude app work at pay-as-you-go rates, but that does not turn the subscription into prepaid API credit.
Practical decision guide
| What you see | Likely issue | Best next step |
|---|---|---|
| “5-hour limit reached” with a time | Short session allowance exhausted | Wait for that time or use enabled credits |
| A weekly meter at 100% | Weekly allowance exhausted | Wait for its fixed reset, use credits, or upgrade |
| One model-specific meter is full | Named model family reached its extra ceiling | Use an available alternative model if offered |
| “Length limit” in one conversation | Chat context is full | Start a new chat, compact, or move reusable material to a Project |
| Unexpected Console or cloud charges | Claude Code may be using an API key | Check authentication and the billed workspace |
Official sources
- Anthropic: What is the Pro plan?
- Anthropic: What is the Max plan?
- Anthropic: What is the Team plan?
- Anthropic: How usage and length limits work
- Anthropic: Usage limit best practices
- Anthropic: Manage usage credits for paid plans
Source details were verified on July 31, 2026. HiseHub is independent and is not affiliated with Anthropic. Plan rules, model-specific meters, prices, and capacity can change; check the Usage page in your account.