Claude usage limits cap how much you can use Claude in two windows: a five-hour session limit and a weekly limit. Both scale with your plan, both are shared across Claude on the web, desktop, mobile and Claude Code, and both are consumed by the amount of text Claude processes, measured in tokens, not by a fixed number of messages. Long conversations and large files therefore use far more of each limit than short questions.
Below: the limits for each plan, how the two windows interact, why Claude Code drains them faster, how tokens are counted, where to check usage and how to stretch each limit. All figures come from Anthropic’s official documentation as of November 2026.
Claude usage limits by plan (as of November 2026)
Anthropic does not publish subscription limits in tokens or messages; it publishes multipliers against the Pro plan. The table summarizes the official Pro, Max, Ultra and Team plan pages and Anthropic’s Fable model policy.
Every paid plan can enable usage credits to keep working past a limit at standard API rates, billed separately. Anthropic may also adjust limits to manage capacity and keep access fair, so treat the multipliers as current, not permanent.
Claude API rate limits are a different system
Claude rate limits on the API are not session or weekly allowances. They cap requests per minute (RPM), input tokens per minute (ITPM) and output tokens per minute (OTPM) per model, refill continuously, and sit under a monthly spend cap per usage tier: $500 on Start, $1,000 on Build and $200,000 on Scale. Only uncached input counts toward ITPM by default, so prompt caching raises throughput. Exceeding a limit returns HTTP 429.
How the 5-hour window and weekly cap actually work
The Claude 5-hour limit
The five-hour limit is a session allowance that starts with your first message and resets after a full five hours. It is often called a rolling 5-hour window, but it neither slides minute by minute nor resets at midnight: start at 9:10 and the allowance returns at 14:10, no matter how much you used. Verified Ultra accounts have no five-hour limit.
The Claude weekly limit
The weekly limit caps total usage across all models and resets at a fixed day and time assigned to your account, regardless of when you subscribed. On Max, Ultra and Team Premium seats, up to 50% of that weekly limit can go to Fable models, which consume it faster than other Claude models.
The two caps stack: a developer can have session headroom on Thursday and still be blocked by the weekly cap. Because every surface shares one pool, an afternoon of document analysis in claude.ai also cuts what is left for coding.
Claude Code usage limits: why coding sessions drain faster
Claude Code usage limits are the same limits as the rest of your plan: on Pro, Max, Ultra, Team and seat-based Enterprise, Claude Code draws from the same five-hour and weekly allowances as claude.ai, Claude Desktop and Cowork. What differs is consumption. Every turn re-sends the conversation so far, the project context (CLAUDE.md plus every file Claude has read) and the new prompt, and every tool call adds another request carrying its results. According to Anthropic’s Claude Code guide, the conversation history is the fastest-growing part.
Three behaviors around Claude Code limits catch people out:
• Sign-in decides metering. With a subscription, Claude Code uses plan limits; with an API key, there is no plan cap and every token is billed. If an ANTHROPIC_API_KEY environment variable is set, Claude Code uses it instead of your subscription, and charges move to API billing.
• Switching models rarely rescues you. Session and weekly limits apply across all models; only a model-specific cap, such as an Opus or Fable limit, can be worked around with /model.
• Parallel work multiplies usage. Subagents, workflows and scheduled loops send their own requests, and Anthropic estimates agent teams use about seven times the tokens of a standard session when teammates run in plan mode.
When a session limit hits mid-response, Claude Code may finish the step in progress under a small, capped wrap-up allowance: up to once per week on Pro and at each session limit on Max.
How Claude counts tokens
Claude meters usage in tokens, not messages, which is why Anthropic publishes no fixed Claude message limits. For scale, Anthropic estimates an average 10 kB web page at about 2,500 tokens and a 500 kB research PDF at about 125,000. Claude 4.7 and later models use a tokenizer that produces roughly 30% more tokens for the same text than earlier models, per Anthropic’s pricing page.
Each request counts four token types. Input covers everything sent: instructions, tool definitions, history, attachments and tool results. Output covers the response, including extended thinking. Cache writes store input for reuse at 1.25× the base input price for five minutes or 2× for one hour. Cache reads serve stored input at 0.1× on most models, 0.05× on Opus 5.5 and Sonnet 5.5, and 0.025× on Fable 5.1 and 5.2.
Prompt caching matches the start of each request exactly, so changing the model, effort level or loaded tools mid-session forces the full history to be processed again. On claude.ai, reused Project content is cached and does not count against your limits. Together these mechanics produce four drains:


