SSD Nodes Learn Hosting plans →
Guides Matt ConnorBy Matt Connor · Updated 2026-11-04

Is there an unlimited Claude plan?

Individual Claude plans have weekly caps. Verified Ultra accounts have no session limit. Enterprise meters usage, with a surcharge for US only inference.

Is there an unlimited Claude plan?

Individual subscriptions have included usage caps. As of October 31, 2026, usage-based Enterprise plans have no plan or seat-level usage limits. Free, Pro and Max have a session allowance that resets every five hours; verified Ultra accounts have no five-hour limit, while unverified Ultra accounts have a temporary limit. All four individual plans have weekly limits. Ultra, formerly Max 20x, is the highest cap an individual can buy, and it is still a cap. Existing Max 20x subscribers move to Ultra automatically with no price change. The current usage-based Enterprise plan works differently. It has no plan or seat-level usage limits and no included usage: the seat fee pays for access only, and every token is billed separately at standard API rates unless US-only inference pricing applies. With US-only inference enabled, usage of Opus 4.6, Sonnet 4.6 and later models costs 10% more, at 1.1 times standard API rates; seat fees do not change. Opus 4.5, Sonnet 4.5, Haiku 4.5 and earlier models stay at standard rates, and existing contractual pricing terms continue to apply. Usage is metered rather than capped at a fixed amount, and admins can set spend limits for the organization and for each member. It is sold to organizations, and the pricing page lists it at 20 USD per seat a month, billed annually, with a 20-seat minimum; what the Enterprise plan costs goes through the bill. The API is another metered option an individual can buy. It charges per token, and it has its own rate tiers, three of which carry a monthly spend cap.

That is the whole answer. Below are the ways around individual plan limits, ordered from cheapest to most expensive, followed by account-sharing and automation shortcuts covered by Anthropic's terms.

What the limit message means

When you use up the session window in the Claude app you see 5-hour limit reached - resets [time], with the real reset time filled in. Shortly before that you see Approaching session limit. Anthropic's help center documents both strings. The same window applies in Claude Code, because Claude and Claude Code draw from one shared allowance. Claude Code also has a small, capped wrap-up allowance to finish an in-progress step after reaching a session limit; it counts toward the weekly limit and is rolling out gradually. On Pro and Max a weekly limit sits on top of the session limit. It applies across all models, and it does not move when the five-hour window resets, so a heavy week can leave you locked out even though the session clock says you are free. Ultra also has a weekly limit across all models, even when its five-hour limit has been removed. On Max and Ultra, Fable models can use at most half of that weekly limit. Past that point Fable needs usage credits, while other models keep running on what is left of the week. On Pro, Fable is outside the plan's limits altogether and runs only on usage credits.

Anthropic does not publish a fixed number of messages per window, so any figure you see quoted is someone's estimate. Usage is measured in tokens, so one long conversation with large attachments empties a window faster than many short questions. Model choice matters too: Anthropic's own Claude Code documentation says Sonnet handles most coding tasks well and costs less than Opus, and suggests Haiku for simple subagent work. If one afternoon in Claude Code emptied a window that normally lasts all day, how Claude Code spends tokens explains the context growth that did it.

What each plan costs and how much usage it includes

These are Anthropic's list prices in USD as of October 2026. The usage column compares each paid individual plan's weekly allowance with Pro's.

ChartClaude individual plans and weekly usage, October 2026
The data behind this chart
[
  {
    "plan": "Pro",
    "monthly_price_usd": 20,
    "weekly_usage_vs_pro": 1
  },
  {
    "plan": "Max",
    "monthly_price_usd": 100,
    "weekly_usage_vs_pro": 5
  },
  {
    "plan": "Ultra",
    "monthly_price_usd": 200,
    "weekly_usage_vs_pro": 10
  }
]

Pro is 20 USD a month billed monthly, or 17 USD a month on an annual plan. Max is 100 USD for 5 times Pro's session and weekly allowances, and Ultra is 200 USD for 10 times Pro's weekly allowance. Max and Ultra are separate plans, both billed monthly only; these are web prices, and mobile pricing may vary. Free is not in the chart because it has no price and no published multiple of its own. Anthropic's help center describes it as having a session limit that resets every five hours, a message allowance that varies with demand, and other limits it may impose. The pricing page also lists a weekly limit for Free. On the pricing page, the Pro plan card promises more usage than Free, with no multiple, while Max and Ultra are compared with Pro. The usage limits answer in the same page's FAQ still says Pro gives at least five times more usage per 5-hour session than Free. Every row in that chart has a weekly limit; Pro and Max also have session limits, while verified Ultra accounts do not. The price buys a taller ceiling, never the absence of one.

Option 1: wait for the window to reset

This costs nothing. The message tells you when the session window opens again, and it is always within five hours of when the window started. The weekly limit resets once a week on its usual day and time, and the weekly limit message tells you when. Anthropic's help pages give you two free ways forward at a limit and two paid ones. The first free way is waiting. The second is an occasional limit reset on eligible plans. When Anthropic gives your account one, a Reset for free button appears under Settings, then Usage, and on the limit message. A standard reset sets either your session limit or your weekly limit back to full, depending on the reset offered. Some resets restore both: Anthropic says admission to the Claude Duet research preview, open to Pro, Max and Ultra users in the US, comes with one full limit reset of both your five-hour session and weekly limits, available until November 30, 2026. Resets are handed out occasionally and expire if unused, so you cannot plan around them. The button is not available in the mobile app or in Claude Code in the terminal or IDE. The paid ways are a bigger plan and usage credits. Getting a limit reset on request is not on the list, which is why you cannot reset Claude usage limits by asking. A new conversation does not help either, since the window is per account rather than per chat. In Claude Code, /rate-limit-options can wait for the reset and continue the interrupted task automatically.

What you can do while waiting is stop the next window from draining as fast. In Claude Code, /model switches to a cheaper model for routine edits. Start a fresh conversation for a new task, because every turn re-sends the whole context. Do not re-attach a large file in each message. When the 90 percent warning appears, finish the current task rather than starting a new one.

Option 2: turn on usage credits, or buy a bundle

Usage credits let a paid subscription keep working past its included limits on pay-as-you-go billing, but they are not an unlimited plan. They are prepaid: you add funds on the Usage settings page, and work on credits continues only until you reach your monthly spend limit or, with auto-reload off, until the balance runs out. They are available on Pro, Max and Ultra, and they are billed at standard API rates, the same per-token prices the API charges. Turn them on under Settings, then Usage, click Enable, add a payment method, and set a monthly spending cap. The cap can be a fixed amount, or you can choose Set to unlimited, which removes the spending cap but not the need to prepay. Auto-reload can top the balance up whenever it drops below a threshold you choose. Once credits are on, the limit message changes to 5-hour limit resets [time] - continuing with usage credits and the conversation keeps going. Credits apply to both Claude conversations and Claude Code. On Pro, Fable models are not included in the plan's usage limits, so every Fable message on Pro is billed to credits from the start, with no limit to use up first. For everything else, credits start once you have used up a limit: any five-hour session limit, the weekly limit, or on Max and Ultra the Fable share of the weekly limit. In most cases the credits do not expire. In certain jurisdictions, Japan among them, credits bought from September 10, 2026 expire six months after purchase. The detail of how a credit is metered lives in what usage credits are and how they are billed.

A usage bundle is the prepaid, discounted form of the same thing. You buy a fixed amount in advance, and Anthropic applies it once you have gone past your plan's limits and are running on usage credits. Bundles are available on Pro, Max, Ultra and Team, and an individual subscriber can buy up to 2,000 USD of them in a month.

ChartUsage bundle prices, October 2026
The data behind this chart
[
  {
    "label": "50 USD bundle",
    "face_value_usd": 50,
    "price_usd": 45,
    "saving_pct": 10
  },
  {
    "label": "250 USD bundle",
    "face_value_usd": 250,
    "price_usd": 200,
    "saving_pct": 20
  },
  {
    "label": "1,000 USD bundle",
    "face_value_usd": "1,000",
    "price_usd": 700,
    "saving_pct": 30
  }
]

The smallest bundle costs 45 USD for 50 USD of usage, a 10 percent saving. The largest costs 700 USD for 1,000 USD of usage, a 30 percent saving. One bundle balance is a single pool across the Claude web app, the desktop and mobile apps, Claude Code, Cowork and third-party products. If you already know you will spend the money, a bundle is strictly cheaper than pay-as-you-go credits.

The honest caveat is that credits are not unlimited in price. A Claude Code session on Opus with a large repository can spend real money in an hour, so set the monthly cap before you enable them, and read the API price table below to understand what a token costs.

Option 3: move from Pro to Max, then Ultra

If you hit the session limit most days, compare the price of a bigger plan with your actual overflow spending on credits. An upgrade from Pro to Max takes effect immediately. Anthropic charges a full month of Max, less a prorated credit for the unused time on your Pro plan, and your billing cycle restarts that day, so you do not have to wait for a renewal date. Moving up from Max to Ultra is billed differently: Anthropic charges the higher plan on a prorated basis for the remainder of your current billing cycle. Subscriptions bought through Google Play are the exception: you pay the full price of the new plan, and the unused value of your old plan is converted into extra days on the new one, so your renewal date lands a few days later than a full month. Max gives five times Pro's session and weekly allowances, while Ultra gives ten times Pro's weekly allowance and removes the five-hour limit for verified accounts. The upgrade raises the weekly ceiling; it does not remove it. Whether the second hundred dollars is worth it depends on the shape of your week, and Max versus Ultra works through the cases where the cheaper plan is enough.

A rough rule: compare your monthly overflow bill with the price difference between plans; how often you hit a limit alone does not tell you which is cheaper. If Max still runs out before lunch, Ultra plus credits is the most usage any individual plan will give you, and that is the true top of the consumer ladder. If you maintain an open source project, check whether you qualify for six free months of Ultra for open source maintainers before paying for that top rung yourself, and know what you will be billed when the six months end.

Option 4: point Claude Code at API billing

The API is a path that is metered rather than capped by a subscription allowance. You open a Console account, buy prepaid API credits, create a key, and pay per token. Claude Code uses that key instead of your subscription once it sees the ANTHROPIC_API_KEY environment variable. In an interactive session it asks once whether to use the key and remembers your answer. With -p it uses the key without asking.

export ANTHROPIC_API_KEY=sk-ant-...
claude

Inside the session, /usage (or its alias /cost) shows the estimated spend for an API-key session. To go back to the subscription, run unset ANTHROPIC_API_KEY, remove the export from your shell profile, and check /status to confirm which login is active. Running /logout and /login is not enough on its own, because Claude Code ranks an API key that is still set above your subscription login. Anthropic's help page warns about this in the other direction: if the variable is set on your machine, Claude Code bills the API even when you thought you were on your plan, and the charge lands on your Console bill rather than counting as plan usage. Keep the variable unset unless you mean to use it. Claude Code's own menu at a plan limit, /rate-limit-options, offers a different set of choices: wait and continue when the limit resets, add usage credits, or upgrade your plan.

Max and Ultra subscribers should know what the new monthly API credits cover and what they do not. Max includes 100 USD and Ultra 200 USD of API credits a month. You claim them by linking a Console organization under Settings, then Billing. They pay for the API, the Agent SDK and Managed Agents, and for claude -p when you run it with an API key from the linked Console organization. Anthropic says they do not cover interactive Claude Code in the terminal, IDE, desktop or web, or usage credits in Claude and Claude Code, so they are not a way to keep a Claude Code session running past a plan limit. Unused credits expire at the end of each billing cycle, and the monthly API credits on Max, Ultra and Team covers the claim in detail.

These are the per-token prices as of October 2026 for the current models. A million tokens is roughly 750,000 English words, and a typical Claude Code turn moves tens of thousands of input tokens because the whole context is re-sent.

ChartClaude API prices per million tokens, October 2026
The data behind this chart
[
  {
    "label": "Haiku 5.5",
    "input_usd_per_mtok": 0.1,
    "output_usd_per_mtok": 0.5
  },
  {
    "label": "Sonnet 5.5",
    "input_usd_per_mtok": 2,
    "output_usd_per_mtok": 10
  },
  {
    "label": "Opus 5.5",
    "input_usd_per_mtok": 4,
    "output_usd_per_mtok": 20
  },
  {
    "label": "Fable 5.1",
    "input_usd_per_mtok": 10,
    "output_usd_per_mtok": 50
  }
]

Sonnet 5.5 costs 2 USD per million input tokens and 10 USD per million output tokens. Opus 5.5 is 4 and 20. The Haiku 5.5 price in the chart applies to prompts up to 100,000 tokens. Longer prompts cost 0.50 USD in and 2.50 USD out per million, and a long Claude Code session can reach that size. If you plan to hand routine work to Haiku, what Haiku 5.5 costs on three real jobs puts both price tiers side by side with Haiku 4.5. Cached input is billed at a tenth of the base input price on Haiku, a twentieth on Sonnet 5.5 and Opus 5.5, and a fortieth on Fable 5.1, which is why a long Claude Code session costs less per turn than the raw numbers suggest. Picking the model is the biggest lever you have, and which model to use for which job is the short version of that decision.

Metered does not mean uncapped. The API enforces rate limits per model, measured in requests per minute and in input and output tokens per minute. Exceed one and the response is HTTP 429 with error type rate_limit_error and a retry-after header telling you how many seconds to wait. The limits refill continuously, so there is no five-hour wall, but a script that fires requests in a burst still gets 429s. On top of that, the Start, Build and Scale tiers each carry a monthly spend cap. When you reach it, requests return the same 429 but with error_code set to enforced_spend_limit_reached and no retry-after header, and usage pauses until 00:00 UTC on the first of next month unless you request a higher limit. New organizations may start in an Evaluation tier with lower limits that rise as the account builds history.

Monthly spend caps by API tier
ChartAPI monthly spend cap per usage tier, October 2026
The data behind this chart
[
  {
    "label": "Start",
    "monthly_spend_cap_usd": 500
  },
  {
    "label": "Build",
    "monthly_spend_cap_usd": "1,000"
  },
  {
    "label": "Scale",
    "monthly_spend_cap_usd": "200,000"
  }
]

The Start tier is capped at 500 USD a month, Build at 1,000 USD, and Scale at 200,000 USD. Only the Custom tier, arranged with a sales contact, has no monthly cap. So even the API has a ceiling until you negotiate one away. It is a ceiling in dollars per month rather than in messages per five hours.

Whether the API works out cheaper than a plan depends on how you use it. A steady daily user of Sonnet on Pro is getting a bargain against the token price, while an occasional heavy user pays for a lot of idle days. API billing versus a subscription runs the numbers for both patterns. If you are building something that runs unattended, putting a spend cap and a kill switch on an AI agent matters more than the plan choice, because an agent in a loop is the fastest way to reach any limit on this page.

Option 5: run an open model on your own server

The only truly unlimited option is one where no one meters you. That means a model you run yourself. You cannot do that with Claude; Claude is not available to self-host on any plan, and the weights are not distributed. You can do it with an open-weights model, and the trade is capability for control: a mid-sized open model on a VPS is well below Opus on hard reasoning, and good enough for a lot of routine drafting and summarising.

On a Ubuntu 24.04 VPS with 16 GB of RAM, Ollama gets you a running model in a few minutes.

curl -fsSL https://ollama.com/install.sh | sh
ollama run qwen3:8b

The first command installs Ollama and registers it as a systemd service. The second downloads an 8-billion-parameter model, about 5 GB, and drops you into a chat. There is no window and no weekly limit. The only bill is the VPS invoice. Running an open model instead of a Claude plan covers which models are worth the RAM and how to wire one into the tools that expect an OpenAI-style endpoint.

What does not work, and breaks the terms

Two shortcuts come up in every forum thread about limits.

Sharing one Max login. Anthropic's consumer terms prohibit sharing your login, API key or account credentials, or making your account available to anyone else. A shared Ultra login for a small team breaks that clause outright, and it does not even help much, because the whole team drains one weekly cap together. The product built for that case is the Team plan, where each seat has its own allowance and a Premium seat carries five times the usage of a Standard one; Claude Team plans for a small business explains the seat maths. If each person would otherwise buy their own Max, a Premium seat on annual billing costs the same 100 USD a month, so Team Premium versus Max comes down to billing intervals, seat control and the terms covering your data.

Rotating between several personal accounts. Each account is a separate subscription with its own limits, so this is paying twice to reach the same ceiling twice, with your projects and memory split across logins. The terms also forbid accessing the consumer app through scripts or bots unless Anthropic explicitly permits it, so automating the hopping without that permission breaks the terms. A site selling "unlimited Claude" does not guarantee access to Claude: Anthropic has documented fraudulent resellers that routed customers to a different model and stole their account credentials.

Which option fits which reader

Someone who hits a limit once in a while should wait, and use the cheaper model in the meantime. Someone on Pro who hits it most days should move to Max. Someone on Max or Ultra who hits it in bursts should turn on usage credits with a monthly cap, or buy a bundle if the spend is predictable. Someone who wants an itemised bill, or who runs Claude Code unattended, should put it on an API key with a spend limit. Someone who needs no meter at all should run an open model on their own server and accept that it is not Claude.

FAQ

Is Claude Ultra unlimited?

No. As of October 2026, Ultra is 200 USD a month for 10 times the Pro plan's weekly allowance. Verified Ultra accounts have no five-hour limit; unverified accounts have a temporary limit. It has a weekly limit that applies across all models, and Fable models can use at most half of that weekly limit. It is the highest cap an individual can buy, and adding usage credits on top of it is the most usage a single consumer account can get.

Does the Claude API have usage limits too?

Yes, but they are different in kind. The API bills per token instead of capping messages per window. It enforces per-model rate limits in requests and tokens per minute, returned as HTTP 429 with a retry-after header, and the Start, Build and Scale tiers each carry a monthly spend cap that pauses requests until the first of the next month. Only the Custom tier, arranged with sales, has no monthly cap.

Can I buy more usage on the Free plan?

No. Usage credits and usage bundles are available on Pro, Max, Ultra and Team plans only. On Free, you can wait for your session or weekly limit to reset, use a free limit reset if Anthropic has offered your account one, or upgrade to Pro. The Pro plan card on Anthropic's pricing page promises only more usage than Free, but the FAQ on the same page says Pro gives at least five times more usage per 5-hour session than Free.

After a limit, is it cheaper to buy usage credits or upgrade to Max?

It depends on how much overflow you use and which models you use. Credits are billed at standard API rates, so compare your actual monthly overflow spending with the jump from Pro at 20 USD to Max at 100 USD, which buys five times the session and weekly allowances. An upgrade takes effect immediately and credits the unused part of your Pro month, or turns it into extra days if you subscribed through Google Play, so you can switch mid-cycle and test that for one week.

Was this article useful?