Pricing & Plans
Claude Max Plan
The Claude Max plan is Anthropic’s individual subscription for people who work with Claude most of the day and keep hitting Pro’s session walls.
This page is part of the Pricing & Plans hub, which covers the whole topic end to end.
Not affiliated with Anthropic. Claude Token Optimization is an independent site and audit service. Claude® and related product names are trademarks of Anthropic PBC. Plan prices, model rates, and usage limits change; always confirm on Anthropic’s own docs. [VERIFY: 2026-09-17]
Last verified: 2026-09-17 (Anthropic Max Help Center article + claude.com/pricing).
This page covers the two tiers, 5x and 20x, published web prices, who each is for, and when paying more still fails because the prompts are wasteful. For a side-by-side decision table, use Pro vs Max.
Max pricing tiers (web)
Max is billed monthly on the web, with no standard annual Max card like Pro’s yearly option. Mobile store prices may differ. [VERIFY: 2026-09-17]
| Tier | Web list price | Usage framing |
|---|---|---|
| Max 5x | $100 / month | 5× Pro’s per-session usage allowance |
| Max 20x | $200 / month | 20× Pro’s per-session usage allowance |
Marketing cards often say “From $100” because 5x is the entry Max tier. [VERIFY: 2026-09-17]
You also get Pro’s feature set plus Max-specific extras Anthropic lists as higher output limits, early and priority access patterns, and the same unified pool for Claude Code and chat. [VERIFY: 2026-09-17]
How Max limits work (plain language)
Like other Claude plans, Max uses: [VERIFY: 2026-09-17]
- A rolling 5-hour session window for session capacity.
- A weekly limit on top for paid plans.
- A shared pool across Claude on web, desktop, and mobile, and Claude Code.
There is no fixed message count. Long contexts, heavy models, tools, and coding sessions burn the bar faster. Check Settings > Usage for your bars and next reset. [VERIFY: 2026-09-17]
When you hit a limit you can wait for reset, change tier or plan, or turn on usage credits that continue at standard API rates. [VERIFY: 2026-09-17]
Who Max is for
Max 5x tends to fit
- People who already use Pro hard several days a week.
- Mixed workflows: research, drafting, and light Claude Code.
- Users who need fewer mid-afternoon hard stops, not all-day agentic load.
Max 20x tends to fit
- All-day Claude collaboration as a primary work surface.
- Deep coding sessions that share the chat pool.
- Users who repeatedly empty 5x and still have real work left.
Max is usually the wrong tool when
- You need org admin, shared projects, and seat governance: choose Team.
- Your product needs metered backend inference: see API pricing.
- You only bump limits once a month: stay on Pro or clean prompts first.
Max vs Pro (short)
| Pro | Max | |
|---|---|---|
| List price | $20 / month, or $17 / month annual-equivalent ($200 / year) [VERIFY: 2026-09-17] | From $100 / month (5x); $200 / month (20x) [VERIFY: 2026-09-17] |
| Billing | Monthly or annual | Monthly on web [VERIFY: 2026-09-17] |
| Session capacity | Baseline paid individual | 5× or 20× Pro per 5-hour session [VERIFY: 2026-09-17] |
| Priority / early access language | Standard paid | Called out on Max [VERIFY: 2026-09-17] |
| Best for | Everyday paid work | All-day or high-intensity individual work |
Pro still gives “at least 5× Free” style session capacity in Anthropic’s FAQ language; Max multiplies on top of Pro, not Free. [VERIFY: 2026-09-17]
When Max still wastes tokens
Upgrading to Max solves capacity. It does not solve structure.
You can still burn a $100-$200 month on:
- Re-pasting the same SOPs and PDFs every thread.
- Giant system prompts that never move into Projects, files, or cache patterns.
- Retry loops and “continue” chains that regenerate the same answer.
- Defaulting to the heaviest model for triage work.
- Parallel Claude Code and chat sessions that share one pool without prioritization.
If you are about to pay more because the bar keeps hitting zero, pause. Sometimes the right move is Max. Often the cheaper move is deleting dead context and tightening prompts. Start at optimize, then decide whether 5x or 20x is still required.
Token rates for API overflow and credits still follow the API pricing table. Rough-check volume with the cost calculator. Log resets with the usage tracker.
Choosing 5x vs 20x without drama
- Run Pro or Max 5x for two weeks and note how often you hit session versus weekly walls.
- If walls are occasional and recoverable with a break, fix prompts first.
- If walls are daily and block shipping, try 5x.
- Move to 20x only when 5x empties mid-day on work that still needs Claude the same day.
- If you need shared seats, stop stacking personal Max accounts and evaluate Team.
Depth on limit mechanics belongs in the usage limits guide.
What Max does not change
Max raises capacity and priority-style access. It does not:
- Remove weekly or session limits entirely. [VERIFY: 2026-09-17]
- Give you a separate unlimited Claude Code bucket; it is the same shared pool. [VERIFY: 2026-09-17]
- Replace Team admin, project sharing, or Enterprise security controls.
- Fix bloated prompts; it only delays the wall.
If your real problem is org collaboration, read Team pricing. If your real problem is product metering, read API pricing.
Get a written audit of heavy Max threads
Max users often paste the richest, messiest threads. That is exactly when a written pass helps.
Get a written audit of your prompts if you want a token map and change list from your own sample. See the example report, privacy, and about.