Back to News & Guides

Claude Code pricing and limits

Claude Code Pricing and Limits: What Pro, Max 5x, Max 20x and Team Include

By ·

The quick answer

The price list tells you what you pay. It does not tell you what you get, because every Claude plan meters usage in session windows rather than in requests, tokens or hours of work.

Build your budget shortlist

Author & editorial method · Suggest a correction with sources

In this guide
  1. What each Claude plan costs
  2. The allowance is a session window, not a request count
  3. Claude Code and Claude draw on one allowance
  4. What happens when you hit the limit
  5. Team seats are individual allowances, not a shared pool
  6. Which tier fits which situation
  7. Check one task before paying for more capacity
  8. Sources

The price list tells you what you pay. It does not tell you what you get, because every Claude plan meters usage in session windows rather than in requests, tokens or hours of work. Before putting $100 a month next to $20, separate the fee from the allowance structure, then check which account your terminal is actually charging.

What each Claude plan costs

Plan Who it is for Billed monthly Billed annually Seat basis
Pro One person using Claude and Claude Code $20 $200 charged up front, listed as $17/month Single subscription
Max 5x One person who keeps reaching the Pro limit $100 Not offered Single subscription
Max 20x One person who keeps reaching the Max 5x limit $200 Not offered Single subscription
Team, standard seat Organization, two members or more $25 per member $20 per member per month, billed yearly Per named member
Team, premium seat Organization, one power user $125 per member $100 per member per month, billed yearly Per named member

Several details in that table decide the real cost:

  • These are US prices and they exclude applicable tax. Anthropic states that pricing, currency and tax handling vary by region, and that some regions show tax in the displayed price while others add it at checkout. Compare the number in your own currency, not this one. What is the Pro plan · What is the Max plan · What is the Team plan
  • Max is a monthly subscription only. There is no annual Max tier.
  • The $200 Pro figure is the amount actually charged once a year. The $17 is the monthly equivalent Anthropic displays, not a separate monthly debit.
  • The annual Team figures are per-member monthly rates. Multiplying them by twelve produces an annual total, but Anthropic does not quote that total as a separate price.
  • Anthropic offers no standing discount on individual Pro or Max plans, and support cannot issue one-off coupons. Team and Enterprise have a separate nonprofit programme.
  • Team requires a minimum of two members and supports up to 150 seats. Organizations can mix seat types, so one person can move to a premium seat without moving everyone.
  • Moving up a Max tier is charged on a prorated basis for the rest of the cycle. Moving from an annual Pro plan to Max credits the remaining annual balance when it exceeds the Max price, but only if the billing address is unchanged. A Google Play upgrade is charged the full new price, and the unused value of the old plan becomes extra days, which shifts the renewal date.
  • Max and Team include monthly API credits. Those credits cannot be spent in Claude Code or in the Claude apps, including as extra usage when you hit a limit. Do not count them as coding headroom. Monthly API credits for Max and Team plans

The allowance is a session window, not a request count

Plan Per-session allowance Weekly limit Applies to
Pro Baseline (1×) One weekly limit across all models The subscriber
Max 5x 5× the Pro per-session allowance All-model weekly limit plus a separate Fable weekly limit The subscriber
Max 20x 20× the Pro per-session allowance All-model weekly limit plus a separate Fable weekly limit The subscriber
Team, standard seat 1.25× the Pro per-session allowance One weekly limit across all models Each named member
Team, premium seat 6.25× the Pro per-session allowance One weekly limit across all models Each named member

Four properties of those windows matter more than the multipliers:

  1. The session limit resets every five hours. It is a five-hour session allowance, not a daily allowance.
  2. The weekly limit resets at a fixed day and time assigned to your account. Your reset day and time stay the same regardless of when you start using Claude or when the subscription begins, and you receive your full weekly allowance each cycle. Anthropic shows the next reset time in Settings > Usage. This is why a "weekly" allowance can run out on a day that has nothing to do with your invoice date.
  3. The multipliers are per-session allowances. 5×, 20×, 1.25× and 6.25× are not request counts, not token budgets, and not a promise of working hours. Anthropic does not publish the underlying numbers, so nobody can convert them into "prompts per day".
  4. Anthropic reserves other limits. The plan pages say it may limit usage in other ways, such as weekly and monthly caps or limits on particular models and features, at its discretion. A plan description is not a complete statement of every limit that can apply.

Message capacity also depends on the work itself. How much you can send in a session varies with message length, the length of attached files, the length of the current conversation, and which model or feature you use. Two people on the same plan can genuinely reach the limit at different times.

Claude Code and Claude draw on one allowance

Claude Code is included with Pro, Max and Team, in the terminal and in supported IDEs, under the same subscription as Claude on the web, desktop and mobile. Usage in VS Code, in Cursor and other VS Code forks, and in JetBrains IDEs such as IntelliJ and PyCharm counts toward the same limits as Claude chat. Use Claude Code with your Pro or Max plan

Surface Counts toward the session and weekly limits Charged as API usage
Claude on web, desktop and mobile Yes No
Claude Code in the terminal Yes when using subscription authentication Only if you accept the API credit option, or if an API key is set
Claude Code in a supported IDE Yes when using subscription authentication Same as the terminal
Claude Console and the Claude API No Yes, at standard API rates

Two mechanisms quietly move you from "my plan" to "my API bill":

  • An ANTHROPIC_API_KEY environment variable takes priority over the subscription. If that variable is set, Claude Code authenticates with the key and bills API usage instead of drawing on the plan allowance. If you signed in through Claude Console pay-as-you-go, run /login inside Claude Code to switch back to the subscription.
  • Accepting the API credit option. When you reach a limit, Claude Code offers to continue on API credits. Claude Code and the Claude Console are two separate systems here: auto-reload is a Console setting, and it only applies once you have chosen API credits. Declining the offer keeps usage inside the plan, and /status shows the remaining allocation. If you never want the prompt, log out with claude logout, then log in with claude login using only your plan credentials, and do not add Console credentials during login.

One more behavior is worth knowing before you blame the plan. If the five-hour limit is reached while a response is still in progress, Claude Code may keep working briefly to finish that step, showing "Usage limit reached · wrapping up". The allowance is small and capped, it counts toward the weekly limit, and it applies only to a response already in progress, never to a new message. On Pro it applies up to once per weekly usage period; on Max it can apply each time you reach a session limit, within the weekly limit. Anthropic is rolling it out gradually, so it may not be on your account yet.

What happens when you hit the limit

Option Pro Max What it costs
Upgrade the tier Pro to Max 5x Max 5x to Max 20x The price difference, prorated for the rest of the cycle
Enable usage credits Yes Yes Prepaid credits, on the same plan
Buy API credits in the Console Yes Yes Standard API rates, billed apart from the plan
Wait for the window or week to reset Yes Yes Nothing

There is a fifth option that most people do not know about. Anthropic gives eligible plans an occasional free limit reset. Using one sets either the five-hour session limit or the weekly limit back to full immediately. You do not have to wait until you have hit a limit to use it, you cannot undo it once used, and an unused one expires at the date and time shown in Settings > Usage. The "Reset for free" button appears in Settings > Usage and on the message you see when you reach a limit. It is not currently available in Claude Code in your terminal or IDE, and not on Claude Mobile, so open Claude in a browser or use Claude Desktop. Your limits are shared across the account, so after you use it the allowance is back to full in Claude Code as well. A reset does not refund usage you have already been billed for and does not change your credit balance, and it disappears if you downgrade or cancel first. What is a limit reset?

Team seats are individual allowances, not a shared pool

The difference between an organization plan and a personal plan is administration, not pooled capacity.

  • Limits are per member. Each member has their own set, one member reaching their limit does not affect anyone else, and the rest of the team keeps working.
  • Limits cannot be transferred or shared between members. Each seat is for one named individual.
  • An organization can enable usage credits for all seat types, so members can continue with Claude, Cowork and Claude Code after reaching the included allowance.
  • Team includes spend caps at organization and individual level, plus central billing, single sign-on, just-in-time provisioning and role-based permissions.
  • Everything in Pro is included: all available models, Claude Code, Cowork, projects, knowledge bases, collaboration features, a 200k context window, and priority access during high-traffic periods.

Which tier fits which situation

If this describes you Start with Why
You use Claude and Claude Code a few times a week and have not hit a limit Pro The session allowance is the baseline everything else multiplies
You keep hitting the five-hour limit on a large repository Max 5x Five times the per-session allowance, same weekly structure
You hit the Max 5x limit regularly Max 20x Twenty times the per-session allowance
You want a second person on one invoice with admin controls Team, standard seat 1.25× Pro per session, per member, two-member minimum
One member of a team needs materially more than the rest Team, premium seat 6.25× Pro per session, and seat types can be mixed
You need a hard ceiling on one person inside an organization Team with individual spend caps Per-user limits are part of Team administration

Check one task before paying for more capacity

Pick a task you actually have to do: a bug with a failing test, a migration, a review of a diff. Write down the files it touches and the check that proves it worked. Run it on the plan you are considering, and record what happened: how many sessions it took, whether a limit interrupted the work, and whether you accepted the result. Then compare the same task on your current plan.

That measurement is worth more than any table, because the tables are what the vendor publishes and the measurement is about your work. If the thing stopping you is a five-hour window that ends mid-task, a larger multiplier helps. If the thing stopping you is that your terminal is billing you as API usage, no upgrade helps, and you should check your environment for an API key first.

For another way to meter coding usage, see GitHub Copilot pricing and AI credits. Use the usage comparison guide or budget planner to compare plans.

Sources

Prices, multipliers and limit behavior above were read from Anthropic's own pages on 2026-10-20. Anthropic's Pro, Max, Team and Claude Code pages all carried an "updated this week" marker on that date. Limits are account-level rules that can change, and this article does not describe what any specific account will be granted.