Which Claude plan I suppose buy for 2026?

Which Claude plan do you need?

Most people wey dey ask which Claude plan dem need dey stuck for same few decisions. Claude Code dey inside Pro plan, or na separate purchase? Developer suppose pay monthly or per token? Five-person team suppose buy five Pro accounts or one Team plan? I don answer many versions of these questions for support tickets for one year now, mostly from customers wey dey set up Claude Code for our servers, so na this decision guide I wish I fit just link.

The lineup, as of July 2026: Free, Pro, two Max tiers, Team (with two seat types), and Enterprise — plus the API, wey no be plan at all but na separate pay-per-token account wey most individual users no need, but most developers go eventually need am. The single most-asked question get one-line answer: Claude Code dey inside every paid plan, from Pro up, and e no dey inside free tier. Everything after that na about how your usage shape fit your tier.

Prices dey move. I go quote the numbers wey dey claude.com/pricing the day I write this, with dates attached. Treat that page as the source of truth, no be this post, and no be those dozens of third-party posts wey don old already.

What actually gates the tiers

If you strip away the marketing, four things dey separate the plans:

• Usage limits. Na this one be the real product. Every tier wey dey above Free get price wey be multiple of Pro allowance — Max na literally "5x" and "20x" Pro usage per session. Under the hood, these limits na token accounting, na why heavy Claude Code session dey burn through dem faster than chat ever will — Claude Code's token usage na re-sent context dey dominate am, no be what you type.
• Claude Code inclusion. Paid plans yes, Free no. Pro, Max, Team (both seat types), and Enterprise all cover Claude Code for terminal and for supported IDEs — VS Code, Cursor and other forks, JetBrains — against the same shared limit as chat.
• Feature and model access. Pro and up get full model picker and unlimited projects; Max add higher output limits and priority access to new models when traffic plenty. The free tier no be crippled toy, though — as of July 2026 e include web search, file creation, code execution, connectors, and extended thinking.
• Admin surface. SSO, central billing, and admin controls dey come with Team; SCIM, audit logs, the Compliance API, custom data retention, and customer-managed encryption keys dey come with Enterprise. If those acronyms no mean anything to you, you no be Enterprise customer, and that one fine.

Notice wetin no dey on the list: intelligence. A Free user and a Max user dey talk to the same models largely. You dey buy volume and plumbing, no be smarter Claude.

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

If you dey use Claude few times a week — drafting, explaining, the occasional script — Free enough, and I go tell you say make you stay on am. The limits tight but dem dey reset, and the feature set cover most conversational use.

Two things suppose push you go Pro. The first one na hitting the usage wall mid-task more than once a week; to dey cut you off for middle of something wey you dey pay attention to worth $20 to stop. The second one na if you want Claude Code at all, since Free simply no get am. As of July 2026 Pro dey $20/month for monthly billing or $17/month for annual billing — the annual discount na real money if you know say you go stay, but I go do one monthly cycle first to confirm the limits fit you.

Wetin Pro no fit fix: e no go make limits disappear. Pro allowance dey shared between Claude chat and Claude Code, so the day you start to use Claude Code seriously na the day Pro go start to feel small. That one no be defect, na the tier boundary dey do its job.

The developer: subscription or API?

Na this fork dey generate most confusion, because both paths dey run the same models and the pricing shapes dey opposite, so whether the API is cheaper than a subscription depend on your own volume.

A subscription na flat fee with a ceiling. You pay $20 (Pro) or $100/$200 (Max 5x / Max 20x, as of July 2026) and you get usage allowance wey dey reset on a rolling basis, with weekly caps layered on top for some plans — the support docs explain the current windows. When you hit the ceiling, work stop until reset, unless you explicitly opt in to paid usage credits. Anthropic clear say spilling over into per-token billing no dey happen without your consent.

The API na meter wey no get ceiling. You pay per million tokens, in and out. As of July 2026: Haiku 4.5 at $1 in / $5 out, Sonnet 5 at an introductory $2 / $10 through August 31, 2026 (then $3 / $15), Opus 4.8 at $5 / $25, and Fable 5 — the premium tier — at $10 / $50. Batch processing dey halve all of am, and prompt-cache reads cost roughly one-tenth of the input price. Check claude.com/pricing before you budget; the Sonnet intro price alone go don change by the time many of una read this.

The decision rule wey I dey give customers na about who dey start the request:

1. A human for keyboard, working interactively — you, inside Claude Code, all day. Subscription. Interactive coding na exactly the bursty, high-volume, unpredictable usage wey flat pricing design for absorb. One day of serious agentic coding fit pass tens of millions of tokens of context re-sends; for API rates, that one na scary invoice, for Max, na Tuesday. Start on Pro; if you hit the wall most days, Max 5x; if you run parallel sessions or long autonomous tasks, Max 20x. This one hold whether Claude Code dey run for your laptop or for server — plenty people dey keep Claude Code running on a VPS inside tmux precisely so long sessions go survive if SSH connection drop, and e dey bill against the same subscription either way.
2. A program, starting requests on its own — a cron job, a webhook handler, a chatbot, anything server-side. API, no exceptions. Subscriptions na consumer accounts with consumer terms; automation belong for API key with per-token billing wey dey scale from pocket-change experiments to production traffic. If na there you dey go, 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 wey you build. Dem be separate accounts with separate billing, and that separation na feature.

One failure mode dey catch people constantly, and e worth to state am clearly: if ANTHROPIC_API_KEY dey set for your environment, Claude Code go authenticate with that key and bill your API account at per-token rates — your Pro or Max subscription go dey ignored silently. You go find out when the Console invoice arrive. Before you assume Claude Code dey use 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 show which account you dey authenticate against. Check am once for every new machine; for VPS especially, an old key wey dem export for dotfile from previous project na the classic culprit.

The team: five people is the threshold

Team dey exist for groups of 5 to 150 and, as of July 2026, e come with two seat types: a standard seat at $20/month annual ($25 monthly) with about 1.25x Pro per-session usage, and a premium seat at $100/month annual ($125 monthly) with 6.25x — the premium seat na the one for people wey dey live inside Claude Code, and both seat types include am. You fit mix seats, na the point: two developers on premium, three writers on standard, one invoice.

The math against individual plans no get anything special by design: a standard seat cost about wetin Pro cost. Five personal Pro accounts and five standard seats land at roughly the same monthly number, so price no be wetin dey decide this one. Wetin you dey actually buy na the plumbing: central billing instead of five expense reports, SSO, admin controls over who get access, and a no-training-on-your-data default wey individual consumer accounts no promise your employer for contract. Five personal accounts no dey give you any of that, and nobody fit cut off a person wey leave dem access for their last day. The moment person ask "can we get the company to pay for this?", Team na the answer. The alternative na shared logins and someone personal card, and both dey end bad.

Watch the seat-type fit, though. A developer wey dey max out a standard seat weekly cap every week na premium seat wey wear wrong badge; the upgrade cheaper than the stalled afternoons. Premium seats carry two weekly limits — one across all models and one for Sonnet-class models specifically — so heavy users suppose skim the Team plan docs before dem assume say the multiplier na the whole story. If several people dey hit those weekly caps every week, buying more seats no go fix am, and the question go turn to Enterprise.

The enterprise: when Team stops being enough

Enterprise change shape and most of the third-party pricing posts never catch up. As of July 2026 e no be "contact sales for a mystery number": e get a self-serve tier with a 20-seat minimum wey you fit buy directly, and a sales-assisted tier for larger contracts. The pricing model invert the consumer plans — a modest per-seat fee (about $20/seat/month, billed annually) wey cover access only, with all usage billed separately at API rates. No per-seat usage ceilings at all: your heaviest Claude Code user no go ever hit a wall, and your bill go scale with actual consumption instead of seat-count guesswork.

That inversion na the sign for who suppose buy am. If your organization problem na predictability — a fixed line item per person — Team na your plan. If the problem na capacity — power users wey dey blow 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 na the only tier wey get any of am. Nobody dey buy Enterprise for the chat experience; dem dey buy am because security review say "no" to everything else.

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 wey actually matter for claude.com/pricing the day you buy: the price of your tier and the shape of its usage limit. Both don change for the last twelve months. Both go change again.

FAQ

Is Claude Code included in the Pro plan?

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

Does the free tier include Claude Code?

No. As of July 2026 the free plan cover Claude for web, desktop, and mobile — including web search, file creation, and code execution — but no 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 for regular use na Pro.

Should I get a Claude subscription or use the API?

Decide by who dey start the requests. A human working interactively — especially for Claude Code — belong for a subscription, because flat pricing absorb the huge token volumes of agentic coding. A program making requests on its own (cron jobs, chatbots, pipelines) belong for the API, where per-token billing scale with load and e no get consumer usage ceiling. Most developers eventually hold both, and na that one be the intended shape.

What does Claude Max get you over Pro?

Volume and plumbing, no be smarter models. Max buy multiples of Pro usage allowance (5x or 20x per session as of July 2026), plus higher output limits and priority access during peak traffic. Which Max tier you want depend on how often Pro's wall stop you: 5x if na most days, 20x if you run parallel sessions or long autonomous tasks.

Team or Enterprise: which one does my company need?

Decide by wetin dey break. If you want a predictable line item per person, with SSO and one invoice for a group of 5 to 150, Team na the plan, and you fit mix standard and premium seats inside am. If your heaviest users dey keep hitting the weekly caps, or if security review ask for SCIM, audit logs, custom data retention or a HIPAA-ready configuration, Enterprise na the tier wey carry dem. Enterprise also bill differently as of July 2026: a modest per-seat fee cover access, and usage dey billed separately at API rates with no per-seat ceiling.