Claude Pro price, limits and what you get

What Claude Pro costs

Claude Pro costs $20 per month billed monthly, or $17 per month if you pay for a year up front. Those are the figures on Anthropic's pricing page as of August 2026. Prices vary by region, and annual billing is taken as one payment rather than twelve. If you are already paying for ChatGPT and deciding whether to run both, the two subscription ladders set side by side shows where each one wins on price for coding work.

The annual option comes to $204 for the year against $240 paid month by month. You save $36 and you commit for twelve months. Pay monthly for the first cycle or two, watch what you actually use, then switch if the plan fits. If you change your mind later, cancelling or downgrading leaves you the rest of the period you have already paid for.

The price does not include API access. Pro covers Claude on the web, in the desktop and mobile apps, and in Claude Code. Calling the Claude API from your own code is billed separately per token through the Console, against its own balance. Comparing the subscription against API pricing does that arithmetic properly.

What Pro adds over the free plan

The free plan is a real product, not a trial. It gives you chat on web, mobile and desktop, web search, memory across conversations, file creation with code execution, and extended thinking. What the free tier actually allows covers where it stops.

Pro adds five things worth paying for.

• More usage. Anthropic's help centre states that Pro gives at least five times the usage per session compared to the free service.
• Claude Code. The terminal agent starts at Pro, and for most developers it is the whole reason to subscribe.
• More model choice. The pricing page lists additional model options for Pro, so you can match the model to the task instead of taking the default. Picking between Opus, Sonnet and Haiku explains when the cheaper model is the correct one.
• Unlimited projects, and access to Research.
• Priority access when traffic is heavy, plus early access to new features.

The pricing page also lists Claude Cowork, Claude Design and Claude Science under Pro, along with Microsoft 365 integration.

Claude Code on Pro, and the shared limit pool

Claude Code runs in a terminal. You install it, then log in with the same account you use on claude.ai. There is no separate purchase and no API key to paste.

Here is the mechanic that surprises people. Pro's usage limits are shared across Claude and Claude Code. Anthropic states that all activity in both tools counts against the same limits, so a long refactor in the terminal spends the same allowance as a long chat in the browser. There is no second quota waiting behind the first. What Claude Code actually costs to run weighs that against paying per token.

Run /status inside Claude Code to see what is left. Settings > Usage on the web shows the same picture plus your next reset time.

The subscription follows your account, not your machine, so running Claude Code on a VPS inside tmux costs exactly what running it on your laptop costs. One warning goes with that. A detached session keeps working while you are away from the keyboard, which makes it easy to spend a week's allowance in an afternoon without watching it happen. Read how to run Claude Code safely on a VPS before you give an agent a shell on a public box.

How Claude Pro usage limits work

Two limits run at the same time, and you can hit either one.

The session limit resets every five hours. Settings > Usage shows the exact time of your next reset, which is the only reliable way to know where you sit in the window.

The weekly limit sits on top of that and applies across all models. It resets at a fixed time each week that is assigned to your account. That day and time stay the same whatever day you subscribed on and whenever you start using Claude, and you receive the full weekly allowance each cycle.

Anthropic publishes no message count for Pro, and that is not evasion. Usage is measured in tokens, so the number of messages you can send varies with message length, including the length of any files you attach. Fifty short questions and five long code reviews are not the same load, which means any figure printed as a fixed message count would be wrong for most people most of the time. The full mechanics behind Claude's usage limits go deeper than one tier needs.

Usage can also be restricted further at Anthropic's discretion to manage capacity. It is uncommon, and it is in the terms.

What burns through a Pro limit fastest

Every message in a chat resends the whole conversation so far, because the model holds no memory of the previous turn beyond the text you send it. Turn 40 of a long thread therefore costs several times what turn 1 cost. Starting a fresh chat for a new topic is the cheapest habit on this page.

After conversation length, these consume the most.

• Attached files. Size counts, and a large document attached to a chat is re-read on every turn of that chat.
• Tools. Web search, Research and MCP (model context protocol) connectors are token heavy, because everything they fetch comes back into the conversation.
• Extended thinking at a high effort level. Higher effort uses more tokens by design, so lower it for routine work.
• Artifacts, which are written out in full each time they are regenerated.

Two habits claw the usage back. Put reference documents in a project instead of attaching them to every chat, because project documents are cached and only the new or uncached parts count against your limit. And group related questions into one message rather than sending them one at a time, since each round trip carries the whole thread again.

Context window against usage limit

These two get confused constantly, and one sentence each sorts it out. The context window controls how long a single conversation can become. The usage limit controls how much you can use Claude across all conversations. Filling the context window ends one chat. Hitting the usage limit pauses everything until the reset.

On paid plans the standard context window is 200K tokens. Claude Opus 5 and Sonnet 5 support a 1M token window on paid plans. Claude Code carries one catch specific to Pro: Pro users must enable usage credits to get the 1M token context window for Opus models. What one million tokens actually holds puts that number in real terms, and managing context inside Claude Code covers the day to day part.

Usage credits, and paying past the Pro limit

Hitting the limit on Pro leaves you four options: wait for the reset, upgrade to Max, turn on usage credits, or stop for the day.

Usage credits let you keep working past the included allowance. Usage beyond the plan is billed at standard API rates and appears on your bill as a separate line item, apart from the subscription charge. Enable it under Settings > Usage, add a payment method, and set a monthly spending cap. You can prepay by adding funds, up to $2,000 per day, and switch on auto reload if you would rather not think about it. Session limits still reset every five hours as normal.

Set the cap on the first day. A spending cap is the only thing standing between an agent stuck in a retry loop and an invoice you did not plan for. Controlling what an AI agent costs you on a VPS covers the larger version of that problem.

Check your real numbers before you upgrade

Settings > Usage shows your current session and weekly consumption along with your next reset time. /status in Claude Code shows the remaining allocation across both surfaces. Watch both for one ordinary working week before you spend more money.

Two patterns mean different things. Running dry every Thursday is a capacity problem, and a bigger plan is the honest fix. Running dry only inside one heavy session is a habit problem, and shorter chats plus project caching fix it at no cost.

You have outgrown Pro when

Four signals, and none of them is a feeling.

• You hit the weekly limit before the week ends, more than once.
• You are paying real money in usage credits every month. Add that overage to $20 and compare the total against the next plan up.
• One task cannot finish inside one session window, so your work spans resets. Large repositories in Claude Code do this first.
• Somebody else needs to use your account. Sharing one login is where the wrong plan starts costing you more than money.

The first three signals point at Max. The Max plan at $100 against $200 compares the two tiers, which cost $100 and $200 per month as of August 2026 and give five times and twenty times Pro's usage per session. The last signal points at Team, which exists for central billing and admin controls: Claude Team plans for a small business.

If you are not yet sure Pro is the right place to start, the Claude plan chooser walks the whole ladder instead of one rung of it.

FAQ

How much does Claude Pro cost per month?

$20 per month billed monthly, or $17 per month on annual billing, as listed on Anthropic's pricing page in August 2026. Annual works out at $204 for twelve months against $240 paid month by month. Prices vary by region, and the annual plan is charged as a single payment rather than twelve.

Does Claude Pro include Claude Code?

Yes. Claude Code is included from Pro upward, and you log in with the same account you use on claude.ai. The detail that matters is that Claude Code and claude.ai share one usage allowance, so terminal work and browser chats draw down the same limit. Run /status in Claude Code to see what is left before you start a long job.

How many messages do you get on Claude Pro?

Anthropic does not publish a message count, because usage is measured in tokens rather than messages. What you get depends on how long your messages are, including any files you attach, and on whether tools such as web search or Research are running. Anthropic does state that Pro gives at least five times the usage per session of the free plan. Check Settings > Usage for your own consumption rather than trusting any published estimate.

What happens when you hit the Claude Pro limit?

Claude stops accepting new messages until the limit resets. The session limit resets every five hours, and the weekly limit resets at a fixed time assigned to your account. Both times are shown in Settings > Usage. You can wait for the reset, enable usage credits and continue at standard API rates, or upgrade to Max.

Does Claude Pro include API access?

No. Pro covers the Claude apps and Claude Code. API usage is a separate product, set up in the Console and billed per token against its own balance. Paying for Pro gives you no API credit, and API spending does not count against your Pro limits.