Which Claude Plan You Need: Free, Pro, Max or Team?

Wetin Claude plan you need?

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

The available plans as of October 2026 na: Free, Pro, two Max tiers, Team (with two seat types), and Enterprise. API dey available too, but e no be plan. Na separate pay-per-token account, wey most individual users no need, but most developers eventually need. The question people ask pass get one-line answer: Claude Code dey included for every paid plan, from Pro upward, but e no dey inside free tier. If na only this answer bring you here, the complete answer for Pro, Max, Team and free plan explain the important details, starting with the usage window wey Claude Code share with chat. Everything after that dey help you match your usage pattern with the correct tier.

Prices fit change. I go quote the numbers wey dey claude.com/pricing on the day I write this, and I go include the dates. Treat that page as the source of truth. No use this post or the many third-party posts wey don already become outdated.

Wetin really dey control the tiers

If we remove the marketing talk, na four things dey separate the plans:

• Usage limits. Na this be the real product. Every tier from Pro reach Team dey priced as multiple of Pro allowance. Max na literally "5x" and "20x" Pro usage per session, while Enterprise remove the included allowance completely and measure usage with API rates. Under the hood, these limits na token accounting. Na why heavy Claude Code session go use dem up faster than chat ever go, Claude Code token usage dey mostly come from context wey dem resend, not from wetin you type.
• Claude Code inclusion. Paid plans get am, Free no get am. Pro, Max, and Team (both seat types) cover Claude Code for terminal and supported IDEs, VS Code, Cursor and other forks, JetBrains, with the same shared limit wey chat dey use. Enterprise seats include Claude Code too, but for the current usage-based Enterprise plan, no shared limit dey available to draw down: dem bill Claude Code usage with API rates like every other thing. Which of these surfaces dey available at all depend on your operating system, not your tier, and Linux get the CLI and editor plugins complete, while the desktop app still be beta wey you install from apt. Included no mean free. So if you want the monthly amount for your own usage instead of yes or no, how much Claude Code really cost for each plan go calculate am with a sample month.
• Feature and model access. Free dey limited to Sonnet- and Haiku-class models. Pro and higher plans add Opus and remove the free plan five-project cap. Fable 5 and Fable 5.1 dey on every paid plan, but for Pro and standard Team seats, dem dey run with pay-as-you-go usage credits. Max and premium Team seats fit spend up to half of their weekly limit on dem. Max add higher output limits and priority access when traffic high. Free tier no be useless toy, though. As of October 2026, e include web search, file creation, code execution, and connectors.
• Admin surface. SSO, central billing, and admin controls start from Team. SCIM, audit logs, the Compliance API, custom data retention, and customer-managed encryption keys start from Enterprise. If these acronyms no mean anything to you, you no be Enterprise customer, and no wahala.

Notice wetin mostly no dey for the list: intelligence. The one model line dey between Free and Pro, because Opus and Fable no dey available for free plan at all. Above that step, Pro user and Max user mostly dey talk to the same models. Wetin you dey buy na more usage and more administration features, not smarter Claude.

The casual user: stay for Free until e begin pain, then Pro

If you dey use Claude few times every week for drafting, explaining, and small script once in a while, Free genuinely dey enough, and I go tell you make you remain with am. The limits tight, but dem dey reset, and the features cover most conversational use. Before you upgrade because of one bad afternoon, e good make you know how dem dey count free allowance and when e dey reset, because plenty people wey feel say dem dey permanently capped actually just dey land for the wrong side of one window. This one also cover most students, wey normally write because dem dey expect education rate, and no individual student discount dey as of July 2026, so the choice na the same free tier and the same $20 Pro plan wey everybody else dey get.

Two things suppose push you go Pro. The first one na when you dey hit usage wall for middle of task more than once every week; make dem cut you off while you dey focus on something wey matter to you worth $20 to stop. The second one na if you want Claude Code at all, because Free simply no get am. Whether that second reason worth action depend on calculation wey you fit do within one minute, and with most people hourly rates, the $20 go pay for itself the first time e save you one hour. If none of the two reasons really describe you, deciding from one week of your own usage instead of rule of thumb go settle the matter faster than reading another comparison. As of October 2026, Pro na $20/month when dem bill you monthly, or $17/month with annual billing. The annual discount na real money if you know say you go remain, but I go first do one monthly cycle to confirm say the limits fit you. Trying a tier na low risk for both directions anyway, because going back to cheaper plan or cancelling completely still leave the month wey you don already pay for. If you want the complete list before you commit, wetin Pro add on top of free plan and where its limits fit stop you na the longer version of this paragraph. And if your real question na which $20 subscription to buy instead of whether to buy one at all, Claude and ChatGPT ladders dey align closely enough tier by tier so the answer normally depend on how much coding you dey do.

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 the work wey dem design am for.

The developer: subscription or API?

Na so this fork dey cause the most confusion, because both paths dey run the same models and their pricing structures dey opposite. So whether API cheaper pass subscription depend on how much you dey use am.

Subscription na fixed fee wey get limit. You pay $20 (Pro) or $100/$200 (Max 5x / Max 20x, as of October 2026), and you get usage allowance wey dey reset on rolling basis. Some plans get weekly caps on top. The support docs explain the current windows. Once you reach the limit, work go stop until reset, unless you deliberately opt in to paid usage credits. Anthropic make am clear say per-token billing no go start because usage pass limit unless you give consent. If e stop you in the middle of task, first find out which window you dey wait for because na that one go decide whether you switch to smaller model, reduce context, buy credits, or just go make coffee.

API na meter wey no get limit. You pay per million tokens, for input and output. As of October 2026: Haiku 5.5 cost $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 cost $2 / $10; Opus 5.5 cost $4 / $20; and Fable 5.1, the premium tier, cost $10 / $50. Sonnet 5's $2 / $10 launched as introductory price through August 31, 2026. E don become the standard price now, and the increase to $3 / $15 wey suppose start September 1 was cancelled. Batch processing cut all the prices by half. Prompt-cache reads cost one-tenth of the input price for most models, one-twentieth for Opus 5.5 and Sonnet 5.5, and one-fortieth for Fable 5.1. Fable na the line item wey dey make people worry, so e make sense to know which jobs really justify the price before you send steady traffic go am. If you wan test am free first, API no get free tier, only small signup credit and some parts wey no cost at all. The exception na Max or Team subscription: as of October 2026, those plans include monthly API credits: $100 for Max 5x, $200 for Max 20x, and up to $500 pooled across a Team. You claim the credits by linking a Console organization, and you fit spend dem without adding payment method there. Dem cover API and Agent SDK, but dem no cover Claude Code. Any unused credit expires at the end of each cycle. For Free or Pro, plan to pay from your first real script. Check claude.com/pricing before you set budget; the model lineup and prices don change more than once this year.

The decision rule wey I give customers concern who dey initiate the request:

1. Human wey dey keyboard and work interactively, you, inside Claude Code, throughout the day. Subscription. Interactive coding na exactly the bursty, high-volume, unpredictable usage wey flat pricing dey designed to handle. One day of serious agentic coding fit resend tens of millions of context tokens. At API rates, the invoice fit scary; for Max, na normal Tuesday. Start with Pro. If you dey reach the limit most days, move to Max 5x. If you run parallel sessions or long autonomous tasks, use Max 20x. If you dey between those two, the $100 and $200 tiers differ only for how much usage you get, not for models or features. This one apply whether Claude Code dey run on your laptop or server. Plenty people dey keep Claude Code running on a VPS inside tmux so long sessions go survive dropped SSH connection, and billing still go use the same subscription either way.
2. Program wey dey initiate requests by itself, like cron job, webhook handler, chatbot, or anything server-side. API, no exception. Subscriptions na consumer accounts with consumer terms. Automation belong on API key with per-token billing wey fit scale from small experiments to production traffic. If na this you dey plan, start with your first Claude API app on a VPS, including the account, the key, and the first working script.
3. Both, na the common final arrangement. Use Max plan for your own daily coding and API key for the things you build. Dem be separate accounts with separate billing, and this separation na advantage. Since Max now include $100 or $200 monthly API credits for one linked Console organization, the subscription fit carry small project's API bill too, as long as you remember say those credits never pay for Claude Code itself.

One failure mode dey catch people all the time, so make we state am exactly: 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, even when you dey logged in with Pro or Max subscription. Claude Code go warn you. E go ask which authentication method to use when e find key during setup, and e go show notification after login if both credentials dey active. But prompt wey you approve once for old machine easy to forget, and the charges go enter Console invoice, not your subscription. Before you assume say 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 go show the account wey you authenticate against. Check am once on every new machine. For VPS especially, old key wey somebody export inside dotfile from previous project na the usual culprit.

Team: five people na the threshold

Team dey available for groups from 2 to 150 people, so the five people for that heading na my threshold, no be Anthropic's minimum. As of October 2026, e get two seat types: standard seat wey cost $20/month annual ($25 monthly), with about 1.25x Pro per-session usage, and premium seat wey cost $100/month annual ($125 monthly), with 6.25x. Premium seat na the one for people wey dey use Claude Code constantly, and both seat types include am. You fit mix the seats, and na there the value dey: two developers for premium, three writers for standard, one invoice. The plan still get monthly API credits for anything wey the team build, $20 per standard seat and $100 per premium seat, pooled and capped at $500.

The calculation against individual plans no get anything special, and na intentional: standard seat cost about the same as Pro. Five personal Pro accounts and five standard seats go reach roughly the same monthly amount, so price no be wetin decide this matter. Wetin you really dey buy na the setup around the service: central billing instead of five expense reports, SSO, admin control over who get access, and a default wey no use your data for training — something individual consumer accounts no contractually promise your employer. Five personal accounts no give you any of these, and nobody fit cut off person wey leave the company on their last day. Once person ask, “can we make the company pay for this?”, Team na the answer. The alternative na shared logins and one person's personal card, and both options dey end badly.

But watch whether the seat type fit the user. Developer wey dey reach the standard seat weekly cap every week na premium seat wey get the wrong label; upgrade cheaper pass the afternoons wey work stop. Both seat types get one weekly limit wey apply across all models, on top of the per-session allowance. For premium seat, Fable fit use at most half of that weekly limit before you need usage credits or another model, so heavy users suppose check the Team plan docs before dem assume say the multiplier na the whole matter. Before you buy plenty premium seats, e good make you price the same developers against API keys instead, because the seat-versus-token comparison for Claude Code at Team and Enterprise scale no always match wetin headcount intuition dey suggest. If several people dey reach those weekly caps every week, buying more seats no go solve am, and the question go turn to Enterprise.

Enterprise: when Team no dey enough

Enterprise don change shape, and most third-party pricing posts never update to match am. As of October 2026, e no be “contact sales for one mystery number”: self-serve tier dey with 20-seat minimum wey you fit buy directly, plus sales-assisted tier for bigger contracts. The pricing model dey reverse consumer plans. E get modest per-seat fee, about $20/seat/month, billed annually, and this one cover access only. All usage dey billed separately at API rates. No per-seat usage ceiling at all: your heaviest Claude Code user no go hit any limit, and your bill go follow actual consumption instead of guessing based on seat count. Older Enterprise contracts wey still dey on Standard and Premium seats go keep their seat-based limits until dem move over during renewal. To budget for this model, you need forecast token consumption instead of counting people. So, e make sense to go through wetin the $20 seat actually cover and wetin the meter dey charge on top before you carry any figure go finance.

This reversal show who suppose buy am. If your organization problem na predictability, where you want one fixed line item for each person, Team na your plan. If the problem na capacity, power users dey pass premium-seat limits, or compliance, Enterprise na the only tier wey get any of these: audit logs, SCIM provisioning, the Compliance API, custom data retention, customer-managed encryption keys, US-only inference, and HIPAA-ready configuration. Nobody dey buy Enterprise because of the chat experience; dem dey buy am because security review reject every other option. And if that review dey compare vendors instead of tiers, na only one of the two publish Enterprise seat price at all, so seat minimums, retention terms, and metered agent usage na the things wey really worth putting side by side.

Di whole decision for six lines

• Occasional chat, no coding: Free, until the limits begin annoy you.
• Regular use, or you want Claude Code at all: Pro.
• Claude Code for most of the day, and you dey hit Pro's wall: Max 5x, then 20x.
• Anything programmatic, bots, pipelines, server-side calls: API, no matter which subscription you also get.
• 5+ people, company money, admin needs: Team, wey mix standard and premium seats.
• Compliance requirements or users wey get no usage cap: Enterprise.

And no matter which branch you choose, verify the two numbers wey really matter for claude.com/pricing on the day you buy: the price of your tier and how its usage limit dey work. Both don change for the last twelve months. Both go change again.

FAQ

Pro plan include Claude Code?

Yes. As of October 2026, $20/month Pro plan include Claude Code for terminal and supported IDEs (VS Code and im forks, JetBrains). E dey use the same usage allowance as Claude chat, and no separate Claude Code subscription dey. But if exported ANTHROPIC_API_KEY environment variable dey set, Claude Code go bill your API account instead. Unset am if you want make your subscription cover the usage.

Free tier include Claude Code?

No. As of July 2026, free plan cover Claude for web, desktop, and mobile, including web search, file creation, and code execution, but e no cover Claude Code. To use Claude Code, you need either paid plan (Pro and above) or API key with pay-per-token billing. For regular use, Pro na the cheapest way to start.

I suppose get Claude subscription or use API?

Decide based on who dey initiate the requests. Human wey dey work interactively, especially for Claude Code, suppose use subscription because flat pricing fit absorb the very large token volume wey agentic coding dey use. Program wey dey make requests by itself, like cron jobs, chatbots, and pipelines, suppose use API. For API, per-token billing dey scale with load, and no consumer usage ceiling dey. Most developers eventually get both, and na the expected arrangement be that.

Wetin Claude Max give you pass Pro?

Na volume and plumbing, no be smarter models. Max give you multiples of Pro usage allowance (5x or 20x per session as of October 2026), plus higher output limits and priority access when traffic high. E also give $100 or $200 monthly API credits for your own apps, but the credits no cover Claude Code. The Max tier wey you need depend on how often Pro limit dey stop you: choose 5x if na most days, and 20x if you dey run parallel sessions or long autonomous tasks.

Team or Enterprise: which one my company need?

Decide based on wetin dey break. If you want predictable cost per person, with SSO and one invoice for group of 2 to 150 people, Team na the plan. You fit mix standard and premium seats inside am. If your heaviest users dey hit weekly caps again and again, or security review require SCIM, audit logs, custom data retention, or HIPAA-ready configuration, Enterprise na the tier wey fit handle am. As of October 2026, Enterprise billing too don change: modest per-seat fee cover access, while usage dey bill separately at API rates with no per-seat ceiling.