Which Claude plan do you need in 2026?

Which Claude plan do you need?

Most people asking which Claude plan they need are stuck on the same handful of decisions. Is Claude Code included in the Pro plan, or is that a separate purchase? Should a developer pay monthly or per token? Does a five-person team buy five Pro accounts or a Team plan? I've answered some version of these in support tickets for a year now, usually from customers setting up Claude Code on one of our servers, so this is the decision guide I wish I could just link.

The lineup, as of October 2026: Free, Pro, two Max tiers, Team (with two seat types), and Enterprise, plus the API, which is not a plan at all but a separate pay-per-token account that most individual users never need and most developers eventually do. The single most-asked question has a one-line answer: Claude Code is included in every paid plan, from Pro up, and is not in the free tier. If that one line is the whole reason you're here, the full answer for Pro, Max, Team and the free plan walks the caveats, starting with the usage window Claude Code shares with chat. Everything after that is about matching your usage shape to a tier.

Prices move. I'll quote the numbers that were on claude.com/pricing the day I wrote this, with dates attached. Treat that page as the source of truth, not this post, and not the dozens of third-party posts that are already stale.

What actually gates the tiers

Strip away the marketing and four things separate the plans:

• Usage limits. This is the real product. Every tier from Pro through Team is priced as a multiple of Pro's allowance, Max is literally sold as "5x" and "20x" Pro usage per session, while Enterprise drops the included allowance altogether and meters usage at API rates. Under the hood these limits are token accounting, which is why a heavy Claude Code session burns through them faster than chat ever will, Claude Code's token usage is dominated by re-sent context, not by what you type.
• Claude Code inclusion. Paid plans yes, Free no. Pro, Max, and Team (both seat types) cover Claude Code in the terminal and in supported IDEs, VS Code, Cursor and other forks, JetBrains, against the same shared limit as chat. Enterprise seats include Claude Code too, but on the current usage-based Enterprise plan there is no shared limit to draw down: Claude Code usage is billed at API rates like everything else. Which of those surfaces exist at all depends on your operating system rather than your tier, and Linux gets the CLI and the editor plugins in full while the desktop app is still a beta you install from apt. Included is not the same as free, so if you want the monthly number for your own usage rather than a yes or no, what Claude Code actually costs on each plan works it through with a sample month.
• Feature and model access. Free is limited to Sonnet- and Haiku-class models. Pro and up add Opus and lift the free plan's five-project cap. Fable 5 and Fable 5.1 are on every paid plan, but on Pro and on standard Team seats they run on pay-as-you-go usage credits, while Max and premium Team seats can spend up to half of their weekly limit on them. Max adds higher output limits and priority access at high-traffic times. The free tier is not a crippled toy, though, as of October 2026 it includes web search, file creation, code execution, and connectors.
• Admin surface. SSO, central billing, and admin controls arrive at Team; SCIM, audit logs, the Compliance API, custom data retention, and customer-managed encryption keys arrive at Enterprise. If those acronyms mean nothing to you, you are not the Enterprise customer, and that's fine.

Notice what's mostly not on the list: intelligence. The one model line sits between Free and Pro, since Opus and Fable are not available on the free plan at all. Above that step, a Pro user and a Max user largely talk to the same models. You are buying volume and plumbing, not a smarter Claude.

The casual user: stay Free until it hurts, then Pro

If you use Claude a few times a week, drafting, explaining, the occasional script, Free is genuinely enough, and I'd tell you to stay on it. The limits are tight but they reset, and the feature set covers most conversational use. Before you upgrade on the strength of one bad afternoon, it is worth knowing how the free allowance is counted and when it resets, because plenty of people who feel permanently capped are really just landing on the wrong side of a single window. That covers most students too, who usually write in hoping for an education rate, and there is no individual student discount as of July 2026, so the choice is the same free tier and the same $20 Pro plan as everyone else gets.

Two triggers should push you to Pro. The first is hitting the usage wall mid-task more than once a week; being cut off in the middle of something you're paying attention to is worth $20 to stop. The second is wanting Claude Code at all, since Free simply doesn't have it. Whether that second trigger is worth acting on comes down to arithmetic you can do in a minute, and at most people's hourly rates the $20 pays for itself the first time it saves you an hour. If neither trigger quite describes you, deciding from a week of your own usage rather than a rule of thumb will settle it faster than reading another comparison. As of October 2026 Pro runs $20/month billed monthly or $17/month on annual billing, the annual discount is real money if you know you'll stay, but I'd do one monthly cycle first to confirm the limits fit you. Trying a tier is low risk in both directions anyway, since dropping back to a cheaper plan or cancelling outright still leaves you the month you already paid for. If you want the full inventory before you commit, what Pro adds over the free plan and where its limits stop you is the longer version of this paragraph. And if your real question is which $20 subscription to buy rather than whether to buy one at all, the Claude and ChatGPT ladders line up closely enough tier by tier that the answer usually turns on how much coding you do.

What Pro does not fix: it will not make limits disappear. Pro's allowance is shared across Claude chat and Claude Code, so the day you start using Claude Code seriously is the day Pro starts feeling small. That's not a defect, it's the tier boundary doing its job.

The developer: subscription or API?

This is the fork that generates the most confusion, because both paths run the same models and the pricing shapes are opposites, so whether the API is cheaper than a subscription comes down to your own volume.

A subscription is a flat fee with a ceiling. You pay $20 (Pro) or $100/$200 (Max 5x / Max 20x, as of October 2026) and you get a usage allowance that resets on a rolling basis, with weekly caps layered on top on some plans, the support docs describe the current windows. When you hit the ceiling, work stops until reset, unless you explicitly opt in to paid usage credits. Anthropic is clear that spilling over into per-token billing never happens without your consent. When it does stop you mid-task, working out which window you are actually waiting on is the first move, because that is what decides whether you drop to a smaller model, trim the context, buy credits, or just go and make coffee.

The API is a meter with no ceiling. You pay per million tokens, in and out. As of October 2026: Haiku 5.5 at $0.10 in / $0.50 out for prompts up to 100,000 tokens ($0.50 / $2.50 above that), Sonnet 5.5 and Sonnet 5 both at $2 / $10, Opus 5.5 at $4 / $20, and Fable 5.1, the premium tier, at $10 / $50. Sonnet 5's $2 / $10 launched as an introductory price through August 31, 2026; it is now the standard price, and the increase to $3 / $15 that was scheduled for September 1 was cancelled. Batch processing halves all of it, and prompt-cache reads cost a tenth of the input price on most models, a twentieth on Opus 5.5 and Sonnet 5.5, and a fortieth on Fable 5.1. Fable is the line item that makes people flinch, so it's worth knowing which jobs actually justify its rate before you point steady traffic at it. If you were hoping to test the water for nothing first, there is no free tier on the API, only a small credit at signup and a few parts that cost nothing at all. The exception is a Max or Team subscription: as of October 2026 those plans include monthly API credits, $100 on Max 5x, $200 on Max 20x and up to $500 pooled across a Team, which you claim by linking a Console organization and can spend without adding a payment method there. They cover the API and the Agent SDK but not Claude Code, and unused credit expires at the end of each cycle. On Free or Pro, plan to pay from your first real script. Check claude.com/pricing before budgeting; the model lineup and its prices have already changed more than once this year.

The decision rule I give customers is about who initiates the request:

1. A human at a keyboard, working interactively, you, in Claude Code, all day. Subscription. Interactive coding is exactly the bursty, high-volume, unpredictable usage that flat pricing is designed to absorb. A day of serious agentic coding can pass through tens of millions of tokens of context re-sends; at API rates that's a scary invoice, on Max it's Tuesday. Start on Pro; if you hit the wall most days, Max 5x; if you run parallel sessions or long autonomous tasks, Max 20x, and if you're stuck between those two, the $100 and $200 tiers differ only in how much you get, not in models or features. This holds whether Claude Code runs on your laptop or on a server, plenty of people keep Claude Code running on a VPS inside tmux precisely so long sessions survive a dropped SSH connection, and it bills against the same subscription either way.
2. A program, initiating requests on its own, a cron job, a webhook handler, a chatbot, anything server-side. API, no exceptions. Subscriptions are consumer accounts with consumer terms; automation belongs on an API key with per-token billing that scales from pocket-change experiments to production traffic. If that's where you're headed, start with your first Claude API app on a VPS, the account, the key, and the first working script.
3. Both, the common end state. A Max plan for your own daily coding and an API key for the things you build. They're separate accounts with separate billing, and that separation is a feature. Since Max now comes with $100 or $200 a month in API credits for one linked Console organization, the subscription can carry a small project's API bill too, as long as you remember those credits never pay for Claude Code itself.

One failure mode catches people constantly, and it's worth stating exactly: if ANTHROPIC_API_KEY is set in your environment, Claude Code authenticates with that key and bills your API account at per-token rates, even while you're logged in with your Pro or Max subscription. Claude Code does warn you: it asks which authentication method to use when it finds a key during setup, and it shows a notification after login if both credentials are active. But a prompt you approved once on an old machine is easy to forget, and the charges land on the Console invoice, not on your subscription. Before assuming Claude Code is using your subscription:

echo "${ANTHROPIC_API_KEY:+key is set - Claude Code will bill the API}"
unset ANTHROPIC_API_KEY   # and remove it from ~/.bashrc or ~/.profile

Inside Claude Code, /status shows which account you're authenticated against. Check it once on every new machine; on a VPS especially, an old key exported in a dotfile from a previous project is the classic culprit.

The team: five people is the threshold

Team is sold for groups of 2 to 150, so the five in that heading is my threshold rather than Anthropic's floor. As of October 2026 it comes in two seat types: a standard seat at $20/month annual ($25 monthly) with about 1.25x Pro's per-session usage, and a premium seat at $100/month annual ($125 monthly) with 6.25x, the premium seat is the one meant for people living in Claude Code, and both seat types include it. Seats can be mixed, which is the point: two developers on premium, three writers on standard, one invoice. The plan also carries monthly API credits for whatever the team builds, $20 per standard seat and $100 per premium seat, pooled and capped at $500.

The arithmetic against individual plans is unremarkable on purpose: a standard seat costs about what Pro costs. Five personal Pro accounts and five standard seats land at roughly the same monthly number, so price is not what decides this one. What you're actually buying is the plumbing: central billing instead of five expense reports, SSO, admin controls over who has access, and a no-training-on-your-data default that individual consumer accounts don't contractually promise your employer. Five personal accounts give you none of that, and nobody can cut off a leaver's access on their last day. The moment someone asks "can we get the company to pay for this?", Team is the answer. The alternative is shared logins and someone's personal card, and both end badly.

Watch the seat-type fit, though. A developer who maxes out a standard seat's weekly cap every week is a premium seat wearing the wrong badge; the upgrade is cheaper than the stalled afternoons. Both seat types carry a single weekly limit that applies across all models, on top of the per-session allowance, and on a premium seat Fable can use at most half of that weekly limit before you need usage credits or another model, so heavy users should skim the Team plan docs before assuming the multiplier is the whole story. Before you buy a row of premium seats, it is worth pricing the same developers against API keys instead, because the seat-versus-token comparison for Claude Code at Team and Enterprise scale does not always land where headcount intuition says it will. If several people hit those weekly caps every week, buying more seats will not fix it, and the question turns into Enterprise.

The enterprise: when Team stops being enough

Enterprise changed shape and most of the third-party pricing posts haven't caught up. As of October 2026 it is not "contact sales for a mystery number": there's a self-serve tier with a 20-seat minimum you can buy directly, and a sales-assisted tier for larger contracts. The pricing model inverts the consumer plans, a modest per-seat fee (about $20/seat/month, billed annually) that covers access only, with all usage billed separately at API rates. No per-seat usage ceilings at all: your heaviest Claude Code user never hits a wall, and your bill scales with actual consumption instead of seat-count guesswork. Older Enterprise contracts still on Standard and Premium seats keep their seat-based limits until they move over at renewal. Budgeting for that shape means forecasting token consumption rather than counting heads, so it's worth walking through what the $20 seat actually covers and what the meter charges on top before you take a number to finance.

That inversion is the tell for who should buy it. If your organization's problem is predictability, a fixed line item per person, Team is your plan. If the problem is capacity, power users blowing through premium-seat limits, or compliance, audit logs, SCIM provisioning, the Compliance API, custom data retention, customer-managed encryption keys, US-only inference, a HIPAA-ready configuration, Enterprise is the only tier that has any of it. Nobody buys Enterprise for the chat experience; they buy it because security review said no to everything else. And if that review is comparing vendors rather than tiers, only one of the two publishes an Enterprise seat price at all, which leaves seat minimums, retention terms and metered agent usage as the things actually worth lining up side by side.

The whole decision in six lines

• Occasional chat, no coding: Free, until the limits annoy you.
• Regular use, or you want Claude Code at all: Pro.
• Claude Code most of the day, hitting Pro's wall: Max 5x, then 20x.
• Anything programmatic, bots, pipelines, server-side calls: API, regardless of what subscription you also hold.
• 5+ people, company money, admin needs: Team, mixing standard and premium seats.
• Compliance requirements or uncapped power users: Enterprise.

And whichever branch you land on, verify the two numbers that actually matter on claude.com/pricing the day you buy: the price of your tier and the shape of its usage limit. Both have changed in the last twelve months. Both will change again.

FAQ

Is Claude Code included in the Pro plan?

Yes. As of October 2026, the $20/month Pro plan includes Claude Code in the terminal and in supported IDEs (VS Code and its forks, JetBrains), billed against the same usage allowance as Claude chat, there is no separate Claude Code subscription. The caveat: an exported ANTHROPIC_API_KEY environment variable makes Claude Code bill your API account instead, so unset it if you want your subscription to cover the usage.

Does the free tier include Claude Code?

No. As of July 2026 the free plan covers Claude on web, desktop, and mobile, including web search, file creation, and code execution, but not Claude Code. To use Claude Code you need either a paid plan (Pro and up) or an API key with pay-per-token billing; the cheapest way in for regular use is Pro.

Should I get a Claude subscription or use the API?

Decide by who initiates the requests. A human working interactively, especially in Claude Code, belongs on a subscription, because flat pricing absorbs the huge token volumes of agentic coding. A program making requests on its own (cron jobs, chatbots, pipelines) belongs on the API, where per-token billing scales with load and there's no consumer usage ceiling. Most developers eventually hold both, and that's the intended shape.

What does Claude Max get you over Pro?

Volume and plumbing, not smarter models. Max buys multiples of Pro's usage allowance (5x or 20x per session as of October 2026), plus higher output limits and priority access during peak traffic, and $100 or $200 a month in API credits for your own apps, which do not cover Claude Code. Which Max tier you want depends on how often Pro's wall stops you: 5x if that is most days, 20x if you run parallel sessions or long autonomous tasks.

Team or Enterprise: which one does my company need?

Decide by what is breaking. If you want a predictable line item per person, with SSO and one invoice for a group of 2 to 150, Team is the plan, and you can mix standard and premium seats inside it. If your heaviest users keep hitting the weekly caps, or if security review asks for SCIM, audit logs, custom data retention or a HIPAA-ready configuration, Enterprise is the tier that carries them. Enterprise also bills differently as of October 2026: a modest per-seat fee covers access, and usage is billed separately at API rates with no per-seat ceiling.