Claude Ultra replaces Max 20x: verified accounts, weekly limits and what changes

1. The rename and usage-window change are confirmed

The official Claude announcement, Ultra help, Max help and pricing page support the change. Existing Max 20x subscriptions move automatically to Ultra. Web monthly prices remain $100 for Max and $200 for Ultra, excluding applicable taxes; mobile pricing can differ. A rename does not require buying the subscription again.

This is a change to plan names and how usage can be scheduled. It does not announce a new flagship model, faster inference, guaranteed task completion or unrestricted concurrency.

2. Compare the plans using the same time window

This table covers individual subscriptions. Team and Enterprise follow separate rules; the rename does not establish the same limits for their seats.

These are the official rules checked October 31. Max and Ultra retain a separate Fable restriction, described as up to half the weekly allowance. Consumption depends on model, context, attachments and features, so these multipliers do not define a fixed message count for everyone.

The old 20x session label and the current 10x weekly figure have different denominators. They cannot establish a weekly increase or reduction by themselves; the announcement says the weekly allowance is unchanged.

3. Understand what verified means here

Ultra's help page describes automatic verification using factors such as account and payment history. Temporary limits are removed automatically after verification. It explicitly separates checkout phone verification, which does not remove this cap. Reviewed documentation does not establish Persona or document verification as a guaranteed route to this status.

Check Settings → Usage. For Ultra, the absence of the Current session bar indicates this verification has completed. If the bar remains, plan around the actual state shown rather than assuming the new plan name proves the cap is gone.

We have not inspected any individual account. Anthropic does not publish a guaranteed verification time or temporary-cap size in these documents. An upgrade should not be described as immediate guaranteed removal.

4. How Chinese and overseas reporting frame it

A headline saying the five-hour limit is removed needs to identify eligible accounts and the continuing weekly budget. The following comparison uses three reports read in full to show how these conditions appear in their headlines and bodies.

October 30 overseas and October 31 Asian dates can reflect time zones. Our editorial view is that the headline should preserve both the eligible audience and the continuing budget constraints. Unlimited use or a doubled total allowance would require additional evidence.

5. Engineering analysis: flexibility within a budget

A simple budgeting model helps: a task must fit both the remaining session allowance and the remaining weekly allowance. Removing the first constraint can help a concentrated task proceed when weekly capacity remains. This is an explanatory model, not a claim about Anthropic's internal scheduler.

For repository work, long reports or iterative research, the potential value is less waiting and fewer handovers. If the weekly limit usually binds first, the benefit may be modest. Concentrating work into one day can also exhaust the week sooner.

Track task acceptance, elapsed time, interruption causes and weekly consumption. Measure waiting avoided separately from completed deliverables. We have not benchmarked performance or verified an account-level capacity gain.

6. Keep competitor comparisons within their product scope

OpenAI's Work and Codex pricing guide also distinguishes a five-hour window from weekly restrictions: Pro currently has no five-hour limit, while weekly limits may apply. That statement has a defined product scope and does not establish unlimited use across every ChatGPT chat feature.

Google's Gemini Apps help describes compute-based personal-account usage refreshed on five-hour windows with a weekly ceiling. Check the account's Usage Limits. This is separate from Gemini API or Vertex AI quotas. Cross-provider multipliers have no shared denominator; compare a fixed task, model and billing surface.

7. Account for API credits separately

The monthly API credit rules describe $100 on Max and $200 on Ultra, with eligibility, claiming, organization-linking and expiry conditions. They do not increase subscription usage or directly pay for overage usage credits in Claude apps. Self-run claude -p or Agent SDK usage with a linked Console organization key has specific coverage rules. Interactive Claude Code and runs started through an IDE, desktop app or GitHub Action remain excluded; adding -p alone does not establish eligibility.

Keep subscription usage, paid overages and API consumption in separate budget lines. A renamed plan, removal of a session cap and activation of API credits are separate states. One becoming active does not prove the others are ready on a particular account.

8. A practical decision for heavy users

• Existing Max 20x subscriber: check the new name and Usage state. The rename is automatic; assess whether weekly capacity fits your work pattern.
• Existing Max subscriber: identify whether the session or weekly constraint usually interrupts you before valuing Ultra's incremental cost.
• New subscriber: assess workload, monthly cost and eligibility. Subscribing to Ultra is not a guarantee of immediate temporary-cap removal.
• Reading older guides: interpret Max 5x/20x labels and session multipliers using their original review dates. Current help and account Usage govern today's rules.

The clear direction is more flexible scheduling of weekly work for eligible heavy users. Your own task records should establish whether it improves delivery.