Claude Ultra Plan: Max Renamed, 5-Hour Limit Removed

Anthropic renamed Claude Max 20x to the Claude Ultra plan and removed the five-hour limit for verified accounts. Prices are unchanged and weekly caps remain.
Anthropic has renamed Claude’s paid tiers. Max 20x is now called Ultra, and verified Ultra accounts no longer run into the five-hour usage limit. Pricing stays the same and existing subscribers do not have to do anything. Below I go through what actually changed, what did not, and how I am adjusting the way I use Claude Code because of it.
What changed in the Claude Ultra plan
The announcement comes down to five lines.
- Max 5x → Max (still $100/month)
- Max 20x → Ultra (still $200/month)
- Verified Ultra accounts: no five-hour limit
- Weekly caps unchanged
- No action required from existing users
So the invoice does not move. The top tier gets a new name, and for verified Ultra accounts the five-hour window goes away. Everything else is as it was.
The removal is rolling out to existing subscribers starting today. Newly created accounts keep the limit temporarily as an anti-abuse measure until verification is complete, and an email arrives when it is lifted. That means someone who signs up for Ultra right now will not necessarily see the limit disappear immediately. If your behavior has not changed yet, the first thing to check is whether your account is still waiting in the rollout or waiting on verification — not whether the feature exists.
Why removing the five-hour limit matters for Claude Code users
The part I am glad about is narrow and specific: the dead time goes away. When I run a long refactor or a long investigation through Claude Code, the work does not fail — it stops. I hit the limit in the middle of something and the rest has to wait until later. The expensive part is not the waiting itself but the context. I want to keep going while the shape of the problem is still in my head. Picking it back up means re-reading what was already checked and reconstructing where I was. For verified Ultra accounts that break is gone.
The people who gain the most from this are the ones who work in long stretches:
- Going back and forth between implementing and verifying for several hours straight
- Blocking out a night or a weekend to do a big chunk of work
- Handing an agent a long sequence of steps and interjecting as results come back
- Clearing a backlog in one sitting before a deadline
If you ask Claude a handful of short questions a day, this changes almost nothing for you. If you cannot remember the last time you hit the limit, it is not a reason to upgrade. What got more valuable here is continuous, long-session use — nothing else.
Weekly caps remain, so this is not unlimited
This is the easiest part to misread. Only the five-hour limit was removed. The weekly cap is still there, unchanged. And because the five-hour checkpoint is gone, consumption can now pile up in a much shorter span — which means you may reach the weekly cap sooner than you used to. That was my first reaction to the announcement: nice, and I am probably going to hit the weekly wall fast.
So the planning unit shifts from five hours to one week. How I think about the allocation:
- Don’t stack every heavy job into the start of the week
- Keep long unattended runs to the number of repetitions you actually need
- Alternate between expensive work and cheap work instead of batching all the expensive work together
- Reserve headroom for anything due late in the week
When the shape of a limit changes, the best way to work under it changes too. Before, the assumption was that you would be interrupted often, so you kept units of work short. Now the assumption is that you will be interrupted rarely but severely. Fewer stops, bigger consequences when one arrives — that calls for a coarser, week-level plan rather than minute-by-minute pacing.
Max or Ultra: how I would decide
The gap is 2x — $100/month for Max against $200/month for Ultra. The announcement states the five-hour removal for verified Ultra; it says nothing about removing it for Max. So the question is what that extra $100 buys you.
Two criteria are enough. First: do you work in long continuous sessions, or in short bursts? Second: is the time you lose to interruptions worth more than $100 a month to you? If you hit the limit several times a week and throw away thirty minutes or an hour each time while you reload context, the difference pays for itself quickly. If you have never noticed the limit, Max is fine. Buying the top tier before your usage justifies it is just a more expensive version of the same workflow.
How a plan rename lands in Japan
For readers outside Japan, it is worth knowing that a renamed subscription tier creates more internal work at a Japanese company than the words “no action required” suggest. Tool subscriptions typically go through an internal approval process and then live on in expense claims, asset ledgers and approved-tool lists. Nobody has to re-subscribe, but somebody does have to go edit every document that says “Max 20x” so it says “Ultra.” The useful thing to say alongside that is that the price did not change, so no budget needs to be re-approved — that is what lets the paperwork pass quickly instead of turning into a new review.
The second issue is wording. Internally, “the limit was removed” gets heard as “it’s unlimited now.” If you do not lead with the fact that the weekly cap still exists, teams will run flat out, hit the cap, and conclude they were misled. What changed is the unit of the limit, not the total amount available.
The third is seat allocation. If a single person is no longer stopped every five hours, one person can go deep for a long time. That tilts the economics away from spreading the top tier thinly across a team and toward concentrating it on whoever actually works in long sessions. The right criterion for who gets Ultra is not how often someone uses Claude but whether they use it continuously for hours at a stretch.
Notes for AI companies announcing changes to a Japanese audience
This release also works as a template for how to communicate a change here.
- Lead with “only the name changed,” “the price is the same,” and “you don’t need to do anything.” Japanese users’ first worry about any change is whether they are now responsible for some step
- Separate what was removed from what remains. Blend them and people read “unlimited”
- Staged rollouts and verification waits generate support tickets, so spell out who qualifies and how they will be notified
- Keep a window where the old and new names appear together, because internal request forms and accounting entries are still running on the old name
A rename is less exciting than a feature launch, but it touches documents and internal explanations, which is exactly the kind of change that produces questions in Japan. Answering them in advance costs one extra paragraph.
How to apply this at your company
Two things. First, confirm which tier you are actually on and when the five-hour removal reaches your accounts, then fix the plan name wherever it appears internally. Second, rebuild your usage habits around a weekly limit instead of a five-hour one: identify who really works in long continuous sessions, concentrate the higher tier on them, and watch weekly consumption to adjust the split. At the same price, changing how you work to match the shape of the limit is what increases how much you actually get out of it.
FAQ
Does the Claude Max to Ultra rename change the price?
No. Max 5x becomes Max at $100/month and Max 20x becomes Ultra at $200/month, so the billing stays the same. Existing subscribers do not need to take any action.
Who gets the five-hour limit removed?
Verified Ultra accounts. It is rolling out to existing subscribers starting today. Newly created accounts keep the limit temporarily as an anti-abuse measure until verification completes, and an email arrives once it is lifted.
Does removing the five-hour limit make Claude unlimited?
No. The weekly caps are unchanged. Without the five-hour checkpoint, usage can concentrate into a shorter span, so you may reach the weekly cap sooner than before.
Based on a post on XOriginal post ↗