Which Claude plan you need for 2026?

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 actually 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 above Free cost as a multiple of Pro allowance. Max na literally sold as "5x" and "20x" Pro usage per session. Under the hood, these limits na token accounting. Na why heavy Claude Code session dey use dem up faster than chat ever go. Claude Code token usage mostly dey come from context wey system resend, no be from wetin you type.
• Claude Code inclusion. Paid plans get am; Free no get am. Pro, Max, Team (both seat types), and Enterprise all cover Claude Code for terminal and supported IDEs: VS Code, Cursor and other forks, and JetBrains. E dey use the same shared limit as chat. Which of these surfaces dey available at all depend on your operating system, no be your tier. Linux get the CLI and editor plugins complete, while the desktop app still be beta wey you install from apt. “Included” no mean say e free. So if you want the monthly amount for your own usage instead of simple yes or no, wetin Claude Code actually cost for each plan dey calculate am with one 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 available for every paid plan. But for Pro and standard Team seats, dem dey use 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 crippled 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, Compliance API, custom data retention, and customer-managed encryption keys start from Enterprise. If those acronyms no mean anything to you, you no be the 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. After that step, Pro user and Max user mostly dey talk to the same models. Wetin you dey buy na more usage and administration infrastructure, no be 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.

Developer: subscription or API?

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 your own usage volume.

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

API na meter without limit. You pay per million tokens, for input and output. As of October 2026: Haiku 5.5 na $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 na $2 / $10; Opus 5.5 na $4 / $20; and Fable 5.1, the premium tier, na $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 dem schedule for September 1 cancel. Batch processing cut all 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 price item wey dey make people worry, so e good make you know which jobs really justify the rate before you send steady traffic go am. If you hope say you fit test am free first, API no get free tier. Na only small signup credit and some features wey cost nothing dey available. So plan to pay from your first real script. Check claude.com/pricing before you prepare budget. The model list and prices don change more than once this year.

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

1. Human wey dey use keyboard and work interactively, na you for 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 hit 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 still apply whether Claude Code dey run for your laptop or server. Plenty people keep Claude Code running on a VPS inside tmux so long sessions fit survive dropped SSH connection. Billing still use the same subscription either way.
2. Program wey dey initiate requests by itself, like cron job, webhook handler, chatbot, or anything server-side. Use 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 want do, 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 daily coding and API key for the things you build. Dem na separate accounts with separate billing, and that separation na advantage.

One failure mode dey catch people regularly, and e worth 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. E go silently ignore your Pro or Max subscription. You go discover am when the Console invoice arrive. 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 show which account you authenticate against. Check am once for every new machine. For VPS especially, old key wey dem export inside dotfile from previous project na the usual cause.

The team: five people na the threshold

Dem dey sell Team for groups from 2 to 150, so the five people for that heading na my threshold, no be Anthropic own minimum. As of October 2026, e get two seat types: standard seat na $20/month annual ($25 monthly), with about 1.25x Pro per-session usage, while premium seat na $100/month annual ($125 monthly), with 6.25x. Na premium seat dem design for people wey dey live inside Claude Code, and both seat types include am. You fit mix the seats, and na that be the main point: two developers for premium, three writers for standard, one invoice.

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 go decide this matter. Wetin you dey really buy na the setup: central billing instead of five expense reports, SSO, admin control over who get access, and default wey no use your data for training; individual consumer accounts no promise your employer this contractually. Five personal accounts no give you any of these, and nobody fit cut off person wey comot from 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 person own card, and both options dey end badly.

But make you check whether the seat type fit the person. Developer wey dey reach standard seat weekly cap every week dey really use premium seat but dem give am wrong badge; 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. Heavy users suppose first scan the Team plan docs before dem assume say the multiplier na the whole matter. Before you buy plenty premium seats, e make sense to price those same developers against API keys instead, because the seat-versus-token comparison for Claude Code at Team and Enterprise scale no always land where headcount intuition expect. 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 again

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”: one self-serve tier dey with 20-seat minimum wey you fit buy directly, plus one sales-assisted tier for bigger contracts. Pricing model dey opposite to consumer plans. E get modest per-seat fee (about $20/seat/month, billed annually) wey cover access only, while 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 scale with actual consumption instead of seat-count guessing. To budget for this model, forecast token consumption instead of counting users. So, before you give finance any figure, e good make you check wetin the $20 seat actually cover and wetin the meter dey charge on top.

That inversion show who suppose buy am. If your organization problem na predictability—one fixed line item for each person—Team na your plan. If the problem na capacity, power users wey dey pass premium-seat limits, or compliance—audit logs, SCIM provisioning, Compliance API, custom data retention, customer-managed encryption keys, US-only inference, or HIPAA-ready configuration—Enterprise na the only tier wey get any of dem. 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 comparing side by side.

Di whole decision for six lines

• Chat wey dey happen sometimes, no coding: Free, until the limits begin disturb you.
• Regular use, or you wan use Claude Code at all: Pro.
• You dey use Claude Code most of the day and Pro limit don block you: Max 5x, then 20x.
• Anything wey program dey do, bots, pipelines, server-side calls: API, no matter the subscription wey you still get.
• People wey pass 5, company money, admin needs: Team, wey fit mix standard and premium seats.
• Compliance requirements or power users wey no want usage cap: Enterprise.

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

FAQ

Claude Code dey inside Pro plan?

Yes. As of October 2026, $20/month Pro plan dey include Claude Code for terminal and supported IDEs (VS Code and e forks, JetBrains). Dem dey charge am against the same usage allowance as Claude chat, so no separate Claude Code subscription dey. The catch be say, if you export ANTHROPIC_API_KEY environment variable, Claude Code go charge your API account instead. Unset am if you want make your subscription cover the usage.

Free tier dey 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.

Make I get Claude subscription or use the 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 high 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 later get both, and na so the setup suppose be.

Wetin Claude Max give you pass Pro?

Na more usage and extra capacity, no be smarter models. Max dey give multiples of Pro usage allowance (5x or 20x per session as of October 2026), plus higher output limits and priority access when network traffic high. The Max tier wey you need depend on how often Pro limit dey stop you: choose 5x if na most days, or 20x if you dey run parallel sessions or long autonomous tasks.

Team or Enterprise: which one my company need?

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