Anthropic does not publish exact token counts for any Claude subscription tier. This makes direct comparison between Team Premium seats and individual Max plans unnecessarily difficult, and most online guidance either conflates the two or invents precision that does not exist. What Anthropic does publish are usage multipliers relative to the Pro plan, and those multipliers, combined with the different limit structures each plan uses, are what actually determine which option suits a given workload.
The multipliers tell a surprising story
All Claude paid plans express their usage allowances as multiples of the Pro plan’s per-session capacity. The comparison looks like this:
| Plan | Usage per session (vs Pro) | Price per month |
|---|---|---|
| Pro | 1x | $20 |
| Team Standard seat | 1.25x | $25 ($20 annually) |
| Team Premium seat | 6.25x | $125 ($100 annually) |
| Max 5x | 5x | $100 |
| Max 20x | 20x | $200 |
The counterintuitive finding is that a single Team Premium seat provides more per-session headroom than Max 5x: 6.25x versus 5x. Max 20x comfortably exceeds both at 20x. Most people comparing these plans assume the individual Max tiers are strictly superior on raw capacity, but session for session, Team Premium actually edges ahead of the cheaper Max tier.
How the limits work differently
The multipliers only tell half the story. The two plan families structure their limits in fundamentally different ways, and for sustained use, this matters more than the per-session numbers.
Max plans operate on rolling five-hour windows. Once a window expires, your allocation resets. A power user can burn through multiple windows in a single day, and in principle there is no weekly ceiling beyond the cumulative effect of those rolling resets. Max 5x and Max 20x share their allocation across the Claude web interface and Claude Code, but there is no separate model-specific cap.
Team Premium seats layer weekly limits on top of the session allowance. Premium seat holders face two distinct weekly caps: one across all models and a separate one for Sonnet models specifically. Both reset seven days after the session starts. The practical consequence is that even though any individual five-hour session might be generous, sustained heavy usage across a full working week can hit a ceiling sooner than the per-session multiplier implies.
This structural difference is the real decision point. Bursty, intensive sessions favour Team Premium’s higher per-session allowance. Sustained all-day usage over a working week, the pattern typical of developers running Claude Code through extended coding sessions, tends to favour Max 20x.
What the token numbers might actually be
Anthropic deliberately withholds absolute token counts, but third-party estimates (drawn from user testing rather than official documentation) suggest Pro users receive roughly 44,000 tokens per five-hour window. If those estimates hold, the multipliers imply approximate per-session allocations of 55,000 tokens for Team Standard, 275,000 for Team Premium, 220,000 for Max 5x, and 880,000 for Max 20x.
These figures are unconfirmed. Anthropic’s own documentation states that usage varies based on conversation length, complexity, features used, and model selection. The company also recently adjusted how session limits deplete during peak hours (5am to 11am Pacific on weekdays), with limits burning faster during high-demand periods whilst weekly totals remain unchanged. Treat any specific token estimate as directional rather than guaranteed.
Pricing and the minimum seat requirement
On paper, a Team Premium seat and Max 5x cost the same: $100 per month when billed annually. The structural difference is the seat floor. Team plans require a minimum of five seats; Max plans have no minimum headcount, so a single user can subscribe at $100 or $200 per month.
The crucial detail, and the one most comparisons get wrong, is that those five seats do not all have to be Premium. Team plans let you mix seat types freely, with no minimum number of Premium seats and no required ratio. An organisation with a single heavy user can pair one Premium seat with four Standard seats. On annual billing that is $100 + 4 × $20 = $180 per month; on monthly billing, $125 + 4 × $25 = $225. That, not the $500 that five full Premium seats would cost, is the real floor for putting one person on a Premium seat.
For one heavy user in complete isolation, Max is still leaner: $100 for Max 5x or $200 for Max 20x, with no surplus seats to carry. But the gap is far narrower than the bare five-seat minimum suggests, and the maths shifts the moment more than one person touches Claude at all. At $180 per month, the floor buys a 6.25x Premium seat, four 1.25x Standard seats, and the entire administrative layer Max cannot offer: admin controls, SSO, domain capture, centralised billing, enterprise search, and workplace tool connectors for Slack, Microsoft 365, and Google Workspace, plus a default no-training-on-your-data policy. For a genuine solo developer, Max 20x at $200 per month is still the cleaner choice. For a small team where one person hits limits and the rest use Claude anyway, the five-seat floor is closer to value than to penalty.
Team plans also allow administrators to enable extra usage, which lets team members continue working after hitting their included limits by paying overage at API rates. Max plans simply cut you off when the window allocation is exhausted, though the five-hour rolling reset means the wait is never longer than the remainder of that window.
Context windows differ between chat and Claude Code
In the standard chat interface, every paid Claude plan provides a 200,000-token context window. Enterprise plans offer an expanded 500,000-token window on supported models.
Claude Code is different. Since March 2026, Max, Team (both Standard and Premium seats), and Enterprise users on Opus 4.6 automatically get a 1 million token context window in Claude Code with no additional configuration and no long-context pricing surcharge. A 900,000-token session costs the same per-token rate as a 9,000-token one. For plans where extended context is included in the subscription, it remains covered by that subscription. Pro users can access the 1M window through the extra usage mechanism, but it is not included by default.
This is a meaningful differentiator for developers working with large codebases. At 200,000 tokens, context management and compaction were constant friction points during long coding sessions. At 1 million tokens, an entire medium-sized repository can fit in a single session without chunking or losing intermediate reasoning.
Which plan to choose
The decision reduces to three questions.
First, do you need organisational controls? If SSO, centralised billing, admin permissions, enterprise search, or a contractual no-training guarantee matter, the Team plan is the only option below Enterprise. Budget for five seats minimum.
Second, what does your usage pattern look like? If you work in concentrated bursts with gaps between sessions, Team Premium’s 6.25x per-session allowance and the ability to purchase overage make it well suited. If you use Claude steadily throughout the day, the weekly caps on Team Premium may bind before the rolling five-hour resets on Max 20x would.
Third, how many people need heavy usage? If one or two individuals are the bottleneck and nobody else needs Claude, Max at $100 to $200 per month per person is the simplest route, with no surplus seats to administer. But if those people sit within a team that would use Claude regardless, the five-seat Team floor is not the obstacle it appears: one Premium seat alongside four Standard seats starts at $180 per month on annual billing, undercutting Max 20x while bringing the administrative features with it. If three or more team members regularly hit limits, adding Premium seats within a broader Team plan makes financial sense outright.
The opacity of Anthropic’s usage limits is a deliberate product decision, not an oversight. It gives the company flexibility to adjust allocations without changing published commitments, as demonstrated by the recent peak-hour throttling. For buyers, this means the only reliable way to know whether a plan fits your workload is to try it, which is an unsatisfying answer but an honest one.