Claude Ultra Plan Goes Live: Max 20x Renamed, Five-Hour Limit Removed

Anthropic has made a quiet but far-reaching adjustment to its Claude subscription system: the former Max 20x plan has been renamed Ultra, and the five-hour usage limit has been removed for verified accounts. This change was first disclosed by an RSS source and subsequently sparked discussion in user communities. For users who rely heavily on Claude for long-document processing, code generation, or complex reasoning, this is not just a name change—it redefines usage pacing and cost structure.

The signal behind the rename: from "multiplier" to "tier"

Renaming Max 20x to Ultra appears on the surface to be a branding terminology adjustment, but in substance it reflects Anthropic's rethinking of subscription tiers. In the past, naming like "20x" pointed directly to usage multiples, making it easy for users to focus on "how much more than Pro" they were getting; "Ultra" feels more like a standalone tier, emphasizing that it is the top-end option for high-intensity scenarios.

This shift in naming logic is consistent with Anthropic's recent push into developer tools and the enterprise market. As the product line expands from a single chat product to code, agents, and the API ecosystem, describing plans with "multiples" seems too linear, while "Ultra" can carry more imaginative space for scenarios. For ordinary users, the most direct question is: after the rename, have my plan benefits changed?

Removal of the five-hour limit: who benefits, who is unaffected

According to the source information, the removal of the five-hour limit applies only to verified accounts. This means unverified users may still be subject to the original window constraint. Verified accounts usually refer to users who have completed email or identity verification; the specific criteria should be based on what is displayed on the account page.

The practical significance of removing the five-hour limit is that users no longer need to deliberately allocate usage times to avoid window resets. For scenarios requiring continuous multi-turn conversations, long-context reasoning, or batch code generation, this continuity is more important than raw usage allowance. However, this does not mean usage becomes unlimited—weekly quotas still exist; only the measurement method shifts from "short-cycle windows" to "long-cycle totals."

The "10x weekly label" mentioned in the source is worth noting. It indicates that the Ultra plan's weekly usage label is marked as 10x, rather than directly corresponding to the 20x in the old naming. Users need to understand what this label means: it describes the relative level of weekly available usage, not the real-time rate. In other words, the loosening of limits is reflected in the time dimension, not in unlimited expansion of the total volume dimension.

How to confirm your plan status

The source recommends that users check their account page to confirm their current plan. The specific path usually involves the subscription or usage section in account settings, checking whether the Ultra label and weekly usage label are displayed. Because displays may differ across regions and verification statuses, checking the account page directly is the most reliable way, rather than relying on community rumors.

The difference between rate limits and total volume management

In subscription-based AI services, limits are usually implemented in two ways: rate limits and quotas. Rate limits constrain request frequency or token consumption within a time window, such as "at most N messages per 5 hours," with the purpose of preventing burst traffic from overwhelming the backend and ensuring fairness among multiple users. Quotas specify the cumulative available usage within a longer period, such as "X million tokens per week," which is closer to a resource-pack model.

The five-hour window is a typical rate limit: even if users have sufficient total volume, they may be forced to wait for a reset because the window is exhausted. After removing this limit, the constraint shifts to the weekly quota, allowing users to arrange their usage rhythm freely within the weekly total, but they cannot "refresh" quota by waiting for a short window. This shift is friendlier for continuous long tasks, but it also means usage planning needs to be done on a weekly basis.

What "verified account" means

"Verified account" usually refers to an account that has completed additional identity verification, such as binding a phone number, verifying a corporate email, or verifying through a payment method. The purposes of setting verification thresholds on platforms include preventing abuse, meeting compliance requirements, and distinguishing real users from automated bulk registrations.

In terms of subscription benefits, verification status may directly affect available features or restriction rules. The removal of the five-hour limit mentioned in this article applies only to verified accounts, which means unverified users may continue to be subject to window constraints even if they subscribe to the same plan. Because platform verification standards are not public and may be adjusted dynamically, users should not assume they automatically qualify, but should rely on the verification indicator on the account settings page.

Differences between Max and Ultra: how users should choose

Based on the information provided by the source, the core differences between Max and Ultra are concentrated in usage labels and restriction rules. Max retains the original usage rhythm, while Ultra removes the five-hour window limit for verified accounts and carries a 10x weekly usage label. For occasional or moderate-usage users, Max may still be sufficient; for users who run Claude for long periods every day, need to handle large contexts, or frequently call the model, Ultra's continuity advantage is more obvious.

When choosing, consider not only price but also workflow fit. If your usage pattern is "intensive use concentrated over several hours," removing the five-hour limit directly reduces interruption costs; if your usage is "scattered throughout the day," the total weekly quota may be more critical than the window limit. The source did not disclose price adjustment information, so judging cost-effectiveness requires referring to the official subscription page.

The "multiplier" logic in plan naming

Labels such as "20x" and "10x" in subscription products usually indicate usage multiples relative to a baseline plan. The baseline may be the free version or an entry-level subscription, and a higher multiple means a larger available allowance within the period. But this naming has two problems: first, users may easily misunderstand it as a speed or performance multiple; second, when the product line expands, a single multiple cannot reflect functional differences.

Anthropic changed Max 20x to Ultra and labeled it 10x weekly, indicating that the new label describes the relative level of weekly usage, not the real-time rate. Users should understand "10x" as a weekly quota tier, not as "10 times faster than some plan." Before the official specific measurement units are announced, multiplier labels can only be used for rough comparison; actual available usage should still be based on the account usage page.

Potential impact on the Claude ecosystem

This adjustment sends a signal: Anthropic is shifting its subscription system from "rate limiting" toward "total volume management." The five-hour window is a typical rate-control measure; removing it means the platform has greater confidence in backend capacity, and also means it is competing for heavy users under competitive pressure. For the developer community, a more continuous experience may drive the implementation of more long-flow agents and automated workflows.

But it should also be noted that describing the weekly quota label as changing from 20x to 10x may give some users the intuitive impression of "reduced allowance." The source did not explain whether this means an actual change in available usage or merely an adjustment in labeling terminology. Until the official further explanation is available, users should rely on the actual usage displayed on the account page and avoid over-inferring based on name changes.

Overall, the launch of Ultra is a pragmatic product iteration: clearer naming, more flexible limits, but the core quota logic still exists. For heavy Claude users, it is worth spending a few minutes checking their account status to confirm whether they have switched to the new rules.

One-line Summary

Anthropic renamed Max 20x to Ultra, removing the five-hour limit for verified accounts while retaining weekly quotas.

Paragraph Summary

Anthropic quietly adjusted the Claude subscription system: the Max 20x plan was renamed Ultra, and the five-hour usage limit was removed for verified accounts. The rename reflects a shift in subscription tiers from "usage multiples" to a standalone top-tier level, while the removal of the limit means the constraint shifts from short-cycle rate control to long-cycle total volume management—weekly quotas still exist, labeled as 10x weekly. Unverified accounts may still be subject to the original window constraint, and users need to check their account page to confirm their status. The article analyzes the potential impact of this change on heavy users, selection strategies, and the Claude ecosystem, noting that improved continuity benefits long-flow agents and automated workflows, but the change in labeling may create an intuitive impression of reduced allowance, so actual usage should be treated as authoritative.