Short answer: As of September 15, 2026, Claude subscription usage is best understood as a rolling five-hour session allowance plus a separate weekly allowance on paid plans. Claude on the web, desktop and mobile and Claude Code generally draw from the same subscription usage pool. The amount you can use is not a fixed message count: conversation length, model, effort, files and tools all matter. API usage is a separate, token-billed system with its own rate limits.
The Claude Code weekly-limit promotion that Anthropic described for eligible users was time-bounded through August 31, 2026. This refresh treats that offer as historical and does not assume an extension. The current official account panel remains the authority for your actual allowance, reset times and any account-specific notice. This guide keeps the original search intent—understanding Claude rate limits in 2026—but removes future-tense advice tied to the expired date.
Last checked: September 15, 2026, against Anthropic’s current pricing, help and Claude Code documentation. Prices and entitlements can vary by country, tax, billing channel, plan and account, so use the linked official pages and your Usage screen before making a purchase or billing decision.
What changed after the March 2026 limit complaints?
March reports are useful history, but they are not a current universal rulebook. Earlier explanations of “peak-hour” behavior described faster five-hour consumption during busy periods. Anthropic’s May 6, 2026 higher-limits announcement then said that Claude Code’s five-hour rate limits were doubled for Pro, Max, Team and seat-based Enterprise plans, and that the peak-hour limit reduction was removed for Claude Code Pro and Max accounts.
That announcement also discussed higher Claude Opus API rate limits. Those are API changes, not a change to the included allowance on a Claude subscription. Do not combine a Claude Code subscription entitlement, a Claude web usage bar and an API organization limit into one number.
Anthropic separately described a Claude Code weekly-limit promotion for eligible Pro, Max, Team and legacy seat-based Enterprise users. The official promotion page says the offer provided 50% higher weekly Claude Code usage through August 31, 2026, while leaving the five-hour limit and other Claude surfaces unchanged. Free plans and consumption-based Enterprise seats were excluded. Because the stated end date has passed, do not plan current capacity around that extra allowance without checking your account.
How Claude usage limits work now
1. The five-hour session limit is rolling
Anthropic describes the session allowance as a rolling five-hour usage window. It is a budget over time, not a promise of a particular number of prompts. A short question and a long request with a large attachment, extended thinking or several tool calls can consume different amounts of capacity.
When the session allowance is exhausted, Claude shows a reset time. The practical choices are to wait for the window to reset, change plans, or—if enabled on your paid account—continue with separately billed usage credits. A reset of the five-hour window does not guarantee that a separate weekly allowance is available.
2. Paid plans also have weekly limits
Anthropic’s usage-and-length-limit guidance and plan help pages distinguish the rolling session allowance from a weekly allowance on paid plans. The weekly reset is assigned to the account rather than being a promise that every user resets at the same clock time. Check the next reset shown in Settings > Usage.
Weekly limits can apply across models. Plan labels such as Max 5x and Max 20x describe higher session capacity relative to Pro; they do not turn the service into an unlimited message bucket. Anthropic can also vary allowances by plan, model, feature and demand.
3. Claude surfaces share subscription usage
Anthropic’s current pricing information says activity across Claude on the web, desktop and mobile and Claude Code draws from the same subscription usage pool. A long Code session can therefore affect the capacity available for a chat under the same paid account.
Shared usage does not make every product rule identical. A Code-only promotion remains scoped to Code, an API key can move billing into the API system, and a server-side incident can produce a temporary error that is not the same as exhausting your plan allowance.
4. Usage limits are not context-window limits
A usage limit controls how much work an account can do over time. A length or context limit controls how much information fits into one conversation. Anthropic’s help guidance discusses large context windows for some paid models, but a larger context window does not provide unlimited messages or remove the five-hour and weekly allowances.
Conversation history, large files, web search, Research, connectors, extended thinking and higher effort can change how quickly the usage budget is consumed. That is why old message-count calculators are a poor substitute for your live Usage page.
Claude plan prices and usage capacity
| Plan | Current web price snapshot | What the official pages say | Limit note |
|---|---|---|---|
| Free | $0 | Limited access for occasional work | Availability and usage can be limited by the account and demand. |
| Pro | $20/month monthly; $200 billed upfront annually is an effective $17/month | At least 5x Free usage per five-hour session; Claude Code is included | Rolling five-hour usage plus a separate weekly allowance; API usage is separate. |
| Max 5x | $100/month on the web | 5x more usage per session than Pro, with higher output limits and priority at high traffic | Still subject to session and weekly limits; exact allowance can vary. |
| Max 20x | $200/month on the web | 20x more usage per session than Pro, with higher output limits and priority at high traffic | Still subject to session and weekly limits; it is not unlimited. |
| Team and Enterprise | Check the current plan page and contract | Entitlements depend on the plan, seats and account configuration | Do not infer a team allowance from an individual Pro or Max account. |
The prices above are a checked snapshot, not a lifetime price guarantee. Mobile storefront billing, tax, country and annual versus monthly billing can change the amount you see. The “5x” and “20x” labels describe usage capacity relative to Pro per session; they do not promise five or twenty times as many messages.
For a model-selection question, use DMT’s separate Fable 5 versus Sonnet 5 comparison. For Claude Code connection paths, use the Claude Code channels and authentication guide. Those pages have different owners; this page remains the canonical explanation of subscription capacity.
Claude subscription, Claude Code and the API are different scopes
| Surface | How usage is measured | Where to check |
|---|---|---|
| Claude web, desktop and mobile | Plan session and weekly usage; consumption varies with context, model, effort, files and features. | Claude account > Settings > Usage. |
| Claude Code with a subscription login | Uses the subscription pool. The historical May–August promotion affected its weekly allowance only. | /usage in Claude Code and the account Usage panel. |
| Claude API / Console | Token billing and organization-level request, input-token and output-token limits. | API rate-limit documentation, Console and billing pages. |
| Bedrock, Vertex or another cloud provider | Provider account billing and quota rules. | The connected provider’s console and current quota documentation. |
There is an important Claude Code authentication boundary. Anthropic’s subscription guidance warns that an ANTHROPIC_API_KEY can cause Claude Code to use API billing instead of the subscription login. If you expected included Pro or Max usage but see API charges or API-style 429 errors, check the environment and signed-in account before changing plans.
Claude Code’s error documentation separates subscription session or weekly-limit messages from temporary server throttling and API-key rate-limit errors. For API traffic, reduce concurrency or follow the provider’s retry guidance; a consumer plan reset will not repair an organization quota.
How to check your current Claude limit
- Open Settings > Usage. Review the five-hour bar, weekly bars and the reset times shown for your account.
- Separate the two budgets. A session reset does not necessarily restore a spent weekly allowance.
- Check the surface and login. In Claude Code, run
/usageand confirm the subscription account. Check whether an API key is present. - Read the credit prompt. Paid users can enable usage credits, but those are a separately billed continuation at standard API rates. Set a cap you understand.
- For API traffic, use the Console. Check organization limits, spend controls, model availability and the provider’s response headers rather than the Claude subscription Usage bar.
Anthropic’s usage-credit guidance says paid users can enable credits, set spending preferences and control a monthly cap. Credits do not change the included allowance or its reset schedule. They provide a separately billed way to continue after included usage is exhausted.
Ways to stretch Claude capacity without guessing
Start a fresh conversation for a new task
A long conversation carries more history into later turns. Start a fresh chat when the task changes, or use Claude Code’s available compaction workflow when a concise summary is enough. This reduces unnecessary context without pretending that every prompt consumes the same amount.
Use Projects for stable reference material
Keep documents you reference repeatedly in a focused Project rather than pasting the same material into every turn. Remove unused files and keep project instructions concise. The exact saving depends on the task, retrieval behavior and account, so measure the effect in your Usage panel.
Match the model and effort to the task
Use a lighter model or lower effort for routine work when it is sufficient, and reserve deeper reasoning for tasks that need it. Model choice, conversation history and project context affect consumption. This is a budgeting practice, not a guarantee of a particular message count.
Control tools and attachments
Large files, web search, Research, connectors and extended thinking add context or tool activity. Trim an attachment to the relevant material, disable non-critical tools for a simple task and avoid carrying a full codebase into every prompt when a focused file reference will do.
If you use Claude Code channels or integrations, keep that setup decision separate from the quota decision. DMT’s channels guide covers supported connection paths; this page covers capacity and billing boundaries.
What to do after a Claude Code limit is reached
The old August 31 checklist should not be left in future tense. The official promotion page stated that the 50% Claude Code weekly increase ran through August 31, 2026; this refresh does not carry that temporary benefit into the current plan table. No fresh official source checked for this update provides an extension. If your account shows a different entitlement, follow the account-specific notice and record the date.
- Open the Usage panel and identify whether the five-hour or weekly allowance is the constraint.
- If it is a five-hour limit, defer non-urgent work until the displayed rolling reset.
- If it is a weekly limit, plan against the displayed weekly reset rather than an assumed Monday or Sunday schedule.
- If you enable usage credits, set a monthly spending cap and remember that they are standard-API-rate charges.
- If you see an API 429 or a provider quota error, inspect the API key, organization and concurrency; do not wait for a consumer subscription reset as the only remedy.
Anthropic’s May announcement is still relevant for historical comparisons: Claude Code Pro and Max peak-hour reduction was removed, according to Anthropic. That statement should not be expanded into a universal promise about every Claude surface or every future model. Use the current account display for operational decisions.
A small API check when subscription limits are the wrong tool
For a backend workload, test the API boundary with a deliberately small request. Prerequisites are a Console account with API access, a funded or otherwise enabled billing arrangement, the current model ID from Anthropic’s API documentation and an ANTHROPIC_API_KEY stored in your shell environment. Do not paste the key into a page, script committed to a repository or support ticket.
curl https://api.anthropic.com/v1/messages ^
--header "x-api-key: %ANTHROPIC_API_KEY%" ^
--header "anthropic-version: 2023-06-01" ^
--header "content-type: application/json" ^
--data "{\"model\":\"<current-model-id>\",\"max_tokens\":64,\"messages\":[{\"role\":\"user\",\"content\":\"Reply with one short sentence.\"}]}"Expected outcome: a JSON response containing a short assistant message, token usage and request metadata if the account, model and quota are valid. Failure cases: a 401 usually points to authentication; a model or access error points to the selected model or account; a 429 can indicate organization rate limits or temporary overload; and a billing error means the Console account is not enabled for the request. This example was not executed during this refresh, so its outcome is a documented expectation rather than a test result.
Should you use Pro, Max or the API?
| Workflow | Relevant choice | Decision rule |
|---|---|---|
| Occasional chat, writing or research | Free or Pro | Compare how often you hit the session or weekly allowance with the paid features you need. |
| Daily Claude Code within a bounded workload | Pro or Max 5x | Compare the current Usage panel and price; do not count on the historical August promotion. |
| Heavy daily Claude work across many projects | Max 20x or a controlled API budget | Max provides more subscription capacity; API provides token billing, spend controls and organization-level limits. Neither is unlimited. |
| Production application or repeatable backend workload | Claude API / Console | Use API pricing, rate limits, retries, spend caps and observability. Do not estimate cost from a Pro or Max message allowance. |
There is no current official evidence for a universal “cancel Pro” threshold. Compare your measured session and weekly usage with the work you actually need to complete, then price optional credits or API consumption with a cap.
Frequently asked questions
Is Claude unlimited on Pro or Max?
No. Paid plans have usage limits. Anthropic describes a rolling five-hour session window and a separate weekly allowance. The amount of work varies with context, model, effort, files and tools.
Do Claude limits reset every five hours?
The session-based allowance uses a rolling five-hour window. Paid plans also have a weekly allowance with an account-specific reset schedule. Check Settings > Usage for both.
Does the 50% Claude Code promotion apply to Claude web?
No. The official promotion page stated that the offer applied to Claude Code’s weekly usage only and left Claude web, desktop, mobile and Cowork at their normal limits. It also stated that the five-hour limit was unchanged. The offer was time-bounded through August 31, 2026, so check your account rather than assuming it is still active.
Is peak-hour throttling still active?
Anthropic said on May 6 that it removed the peak-hour limit reduction for Claude Code Pro and Max accounts. March explanations remain historical context. Current public documentation does not publish a universal peak-hour multiplier for Claude web or mobile, so do not present a March timetable as a current rule for every surface.
Does Claude Code share my Claude subscription limit?
Yes, when Claude Code is authenticated through a Pro or Max subscription, Anthropic says Claude and Claude Code activity shares the same usage pool. An API key can move the work into the separately billed Console/API system.
How much are Max 5x and Max 20x?
The current Anthropic Max help page lists Max 5x at $100 per month and Max 20x at $200 per month on the web. Your checkout can differ by region, tax and billing channel. The 5x and 20x labels describe per-session capacity relative to Pro, not a fixed number of messages.
Can usage credits keep me working after I hit a limit?
Paid users can enable usage credits in Settings > Usage. Anthropic says subsequent usage is billed at standard API rates and appears as an additional charge. Set a spending cap and check whether credits are enabled before starting a high-context task.
Are Claude API rate limits the same as Pro or Max limits?
No. The API uses organization-level limits such as requests per minute and input/output tokens per minute, plus spend controls. API requests are billed separately from a consumer subscription. Cloud-provider deployments have their own quotas as well.
Does a 1M-token context window mean I can send unlimited messages?
No. Context-window size is a length limit for one conversation. Usage limits are the amount of work allowed over time. Long context, tools, model choice and effort can affect how quickly the usage budget is consumed.
Bottom line
Claude rate limits in 2026 have two primary subscription layers: a rolling five-hour session allowance and, on paid plans, a weekly allowance. Claude web, desktop, mobile and Claude Code generally share the subscription pool, while API usage is a separate token-billed system. The historical Claude Code promotion provided 50% higher weekly Code usage through August 31, 2026; this refresh does not assume it continues.
The most important correction to older coverage is scope and date. Anthropic said it removed the peak-hour reduction for Claude Code Pro and Max accounts in May, while current public documentation does not publish a universal peak-hour multiplier for every Claude surface. Check Settings > Usage, use /usage in Claude Code, control optional credits and distinguish API 429 errors from subscription exhaustion before changing plans.
For adjacent workflows, see DMT’s Claude browser, Skills and Files guide and Claude model comparison. Those pages answer access and model-selection questions; this page remains the canonical owner for Claude subscription rate limits and capacity planning.
