Renamed, Not Repriced — and the 5-Hour Limit Is Gone: What Claude Max Becoming Ultra Actually Changes

The short version: new names, same prices, and a real change to Ultra's rhythm

On 30 October 2026, Anthropic announced through its official Claude account that Max 5x would become Max and Max 20x would become Ultra. Prices did not move: Max is still $100 a month and Ultra is still $200 a month, and existing subscribers need to do nothing — the new names apply automatically. Read only that far, and this looks like a pure branding tidy-up. Read one line further, and there is a substantive change: verified Ultra accounts are no longer subject to the five-hour usage limit, leaving only the weekly limit. So the rename itself is not worth paying for. What is worth paying for is the same old question: how much you actually use in a week, and whether your real bottleneck is a session being cut short or a weekly total running out.

The judgement up front: for people who spend long stretches of the day in Claude — coding, researching, writing at length — Ultra is genuinely loosened up. For people who only occasionally bump into the five-hour window and never come close to the weekly total, the rename changes nothing, and there is no reason to upgrade for a new name. One misunderstanding matters more than the new names: the old "20x" never meant twenty times Pro's weekly usage. Ultra's weekly allowance is now stated plainly as 10x Pro. Getting that straight matters more than memorising the new labels.

What changed: two side-by-side comparisons

First, the names and prices. Max 5x is now Max at $100 a month; Max 20x is now Ultra at $200 a month. Anthropic said explicitly that prices are unchanged and that subscribers have nothing to do. If you see Ultra on a bill or in settings, do not assume you were moved to a different plan — it is simply the new name for Max 20x.

Second, the allowances. Max offers 5x Pro usage every five hours and every week, plus $100 a month in platform API credits. Ultra offers 10x Pro usage every week, $200 a month in API credits, and no five-hour limit for verified accounts. The pricing page table puts it bluntly: on the five-hour row, Max is 5x and Ultra is "No 5-hour limit" for verified accounts; on the weekly row, Max is 5x and Ultra is 10x. Both plans include Fable, but Fable has its own separate weekly limit, up to about half of the weekly allowance, and it is not mixed into the main allowance.

One detail is easy to miss: removing the five-hour limit does not mean unlimited use. The weekly limit remains, the weekly total across models remains, and Fable's separate weekly limit remains. The help centre also reserves room for further limits to manage capacity and fair access — weekly, monthly, model-level or feature-level — and does not guarantee uninterrupted service. In other words, Ultra fixes the problem of being cut off mid-session, not the problem of wanting unlimited use.

What did not change: price, weekly limits, and effort for existing subscribers

The most creditable part of this rename is what it left alone. First, price: $100 and $200 are exactly the same before and after, with no quiet price rise and no push of existing subscribers onto a more expensive tier. Second, Anthropic says weekly limits are unchanged. Ultra's weekly allowance is now stated as 10x Pro, and that is the number to use after the rename — stop applying the old 20x to the week. Third, existing subscribers do nothing. The announcement's own words were that subscribers have nothing to do, and the help centre confirms that existing Max 20x subscribers move to Ultra automatically with no price change. The best kind of rename is one that changes the label without forcing you to reselect a plan, re-enter payment details, or worry that you woke up on a higher tier.

Pro is untouched too. It remains $20 a month on monthly billing, or $17 a month on an annual subscription, with both a five-hour and a weekly limit still in place. This rename only touched the top two tiers; it did not rearrange the entry-level or mid-tier picture. If you are on Pro, the Max and Ultra rename is not something you missed — your plan was never in scope.

There is a simple test for whether a rename is a disguised price rise: check whether price, total allowance, and limit conditions all moved together. Here, price did not move, the weekly limit is said to be unchanged, and the only condition that moved — Ultra's five-hour limit — moved in the looser direction. That is hard to call a disguised price rise. A fairer description is an honest renaming with one constraint loosened along the way.

What "20x" actually meant: the most misleading part of the old name

Many people saw Max 20x and assumed it meant twenty times Pro's weekly usage, and then asked why Ultra is only 10x — did it shrink? The confusion is understandable, because the old name invited it. The key is to separate two windows: the five-hour window and the weekly window. The 20x in the old name described the five-hour window, not the weekly total. Ultra's new description is: no five-hour window for verified accounts, and a weekly window of 10x Pro. The two numbers measure different things, so comparing 20 with 10 and concluding that the plan shrank by half is a category error.

Put plainly: the old rule was like a large bucket every five hours plus a weekly reservoir. The new Ultra rule removes the five-hour bucket, so you draw directly from the weekly reservoir. Removing the bucket lets you draw continuously for longer, but it does not make the reservoir bigger. If you used to empty the bucket while the reservoir still had plenty left, you will feel a real improvement. If you used to drain the reservoir first, removing the bucket helps you not at all — you will still stop before the week is over.

This distinction decides whether Ultra is worth $200 a month. The test is not how many hours a day you use Claude, but which wall you hit. If you hit the five-hour wall often and the weekly wall rarely, Ultra treats the right problem. If you rarely hit either wall, or if the weekly total is your real constraint, Max or even Pro may be enough. Before upgrading, look at your own usage curve in settings — it is far more reliable than any number in a plan name.

What is a "verified account"? No form, automatic judgement

Ultra's removal of the five-hour limit comes with a qualifier — verified accounts only — and this is the easiest part to misunderstand, so it deserves its own section. First, verification is automatic; there is no form to fill in. The help centre says Anthropic verifies Ultra accounts automatically using factors such as account and payment history, to help prevent fraud and abuse. You cannot speed it up by submitting documents, and there is no verification desk to appeal to. Second, newer or not-yet-verified accounts keep a temporary five-hour limit until verification completes, and it is removed automatically, with an email notification when it happens. Third, verifying a phone number at checkout is a separate step, and the help centre says explicitly that it does not remove this limit. Do not conflate the two.

How do you check your own status? The official method is refreshingly concrete: open Settings > Usage. If you do not see a "Current session" bar, your account is verified and has no five-hour limit. If you can still see it, the temporary limit is still in place. This is more reliable than any third-party tutorial, because it comes straight from the help centre and does not require guessing at a hidden backend state. If you just subscribed to Ultra and see a temporary limit, do not rush to complain — that is the expected behaviour under the rules. Wait for verification and the email.

One fairness issue is worth flagging: the verification criteria are not public. Anthropic mentions only "account and payment history" and similar factors, with no published weights or timeline. Two people subscribing to Ultra on the same day may therefore get the five-hour limit removed at different times. For most individual users that is a minor annoyance; for a team purchase or a deadline-driven project, it is a real uncertainty. Do not assume that subscribing today guarantees an unlimited-session state today — leave buffer in any schedule that depends on it.

Who genuinely benefits, and who only feels like they do

The clearest beneficiaries are long-session, heavy, continuous users. Three patterns stand out: long Claude Code sessions on a large refactor or debugging job, where a five-hour cut breaks momentum; long research or long-form writing that needs many rounds of follow-up and revision; and people who keep Claude open all day as a pairing partner. For them, the five-hour wall is not an occasional inconvenience but a daily ceiling. Removing it changes the work rhythm from "chopped into segments" to "ending when the task naturally ends", and that is a real experience change.

Two other groups benefit much less. One is people who exhaust the weekly total first: if you burn through the week in two days, the five-hour wall is irrelevant, and what you need is a larger weekly allowance or pay-as-you-go API credits, not a longer single session. The other is light users: if you use Claude for an hour or two a day, never fill a five-hour window, and never approach the weekly total, Ultra is simply extra money. A third group needs a specific warning: people thinking of sharing a personal Ultra account across a team. The pricing page and help centre describe individual consumer plans; teams should use Team or Enterprise plans. Stretching a personal Ultra across a team fits neither the product's positioning nor its fair-use expectations.

Existing Max 20x subscribers who barely noticed the five-hour wall deserve a separate note. After the rename you become Ultra automatically, and the removal of the five-hour limit is a free bonus — nothing to do. But do not therefore conclude that you somehow gained double: your weekly allowance is 10x Pro, not 20x. Keeping expectations level will save you a disappointing surprise when you next look at the usage page.

Three checks before upgrading

First, identify which wall you hit. Open Settings > Usage and look at the last few weeks: do you regularly fill the five-hour window while the week still has plenty left, or do you run out of the week first? The first pattern suits Ultra; the second is not solved by Ultra alone. Second, confirm your account status. If you are already on Ultra, check for the Current session bar; if you have not subscribed yet, accept that a new account may start with a temporary limit. Third, do the arithmetic: Max is $100 a month, Ultra is $200. The price difference buys the removal of the five-hour limit, a weekly allowance moving from 5x to 10x Pro, and API credits moving from $100 to $200. If you only want to solve mid-session interruptions and your weekly allowance is already sufficient, ask whether there is a cheaper fix — splitting a long task into stages, or moving part of the work to pay-as-you-go API usage.

Subscription channel matters too. The pricing page quotes web subscription prices; prices and rules through an app store can differ, as can cancellation and refund routes. Before upgrading, confirm whether you subscribe on the web or in an app, so you are not hunting for the right settings page when you later want to downgrade or cancel. It sounds trivial, but a wrong entry point wastes real time at exactly the moment you want to leave.

A final word on Anthropic's move. It got two things right: dropping the misleading "20x" for the clearer Ultra name, and removing the five-hour wall that most frustrated heavy users — starting with most existing subscribers. It also left two things undone: verification criteria remain opaque, with no clear timeline for new users; and the small print about capacity limits and no guarantee of uninterrupted service still stands, so Ultra is still not unlimited. Overall, this is a small, heavy-user-friendly improvement, not a revolution. But for someone interrupted by the five-hour wall every day, a small improvement is the whole daily difference. A rename without a price rise is good news — but whether $200 a month is worth it still depends entirely on which wall you hit.