If you've been working with Claude and suddenly hit a message that says you've reached your usage limit, you're not alone. When it happens over and over in a single day, it's frustrating enough to make you want to give up on the tool entirely — and lately, more people online have been venting about exactly this. This article breaks down, based on official documentation, what Claude's usage limits actually measure, why they seem to be hitting harder than usual right now, and what you can actually do about it today.
What this article gets you
By the end of this article, you'll understand how Claude's usage limits are structured, how to check what you have left right now, habits that help you avoid hitting the cap, and exactly what to do when you do hit it. It takes about 5-7 minutes to read.
What you need before starting
- A Claude account — Free, Pro, Max, or Team all work. The size of your limit and whether you can buy usage credits depends on your plan.
- (Optional) Claude Code installed — if you code in the terminal, there's a dedicated command for checking usage from inside it.
Quick term glossary
- Usage limit — a cap on the total amount of messages/work you can send Claude over a given period. Once you cross it, you have to wait for a reset or take another action.
- Length limit / context window — a different concept from the usage limit: the cap on how much information a single conversation can hold at once. Starting a new conversation fixes this immediately.
- Session limit — a short-cycle limit that rolls on roughly a 5-hour basis.
- Weekly limit — a limit that resets every 7 days, at a fixed time set per account.
- Usage credits — a way to pay for extra usage once you've used up your base limit.
- Caching — reusing previously processed conversation content instead of recomputing it. Once the cache goes cold after some time, your next message reprocesses everything from scratch.
Why does the limit seem to be hitting harder than usual lately?
If limits have felt tighter recently, it may line up with a temporary promotion ending. According to official support documentation, from May 13 through September 13, 2026, the Claude Code weekly limit ran 50% higher than usual for Pro, Max, Team, and legacy seat-based Enterprise plans, and after that promotion period ends, weekly limits return to their standard level.
However, according to Anthropic's official X account, alongside the promotion ending, the company also announced it would permanently raise the standard weekly limit itself by 25% starting September 14, 2026. In the same announcement, it disclosed that compared to right now (while the promotion is active), this works out to roughly a 17% reduction in weekly limits. In other words, it's neither a full reversion to the old baseline nor a continuation of the current boosted level — it lands somewhere in between. This change concerns the weekly limit only; it has nothing to do with the 5-hour session limit.
Caution: the promotion's end date and the permanent increase's start date have both shifted more than once before, so it's safest to double-check the exact date and numbers against the usage display in your own account.
Separately from the promotion, personal usage habits often make the limit fill up faster than expected. Official documentation points to a few common causes:
- Sessions left open for a long time — Claude Code resends the entire conversation with every request, so even a short question in a session that's been open all day gets billed for the whole conversation's worth of history.
- Resuming after the cache goes cold — on subscription plans, the conversation cache stays warm for about an hour. Come back after a longer break and your next message reprocesses the full context from scratch, using up far more of your limit than expected.
- Automation and scheduled tasks — scheduled tasks and messages delivered from other sessions resend your full context each time they fire, even while you're not looking at the screen.
- Heavy use of Opus — for the same task, Opus costs several times more per turn than Sonnet, so it eats through your limit faster.
Checking how much of your limit is left right now
Checking the actual screen is the most reliable way to know where you stand. On claude.ai, go to Settings > Usage to see progress bars for what's left. In Claude Code, run /usage at any time — if you're connected with an API key, the Session block at the top shows token usage and an estimated cost, and if you're a Pro or Max subscriber, the same screen shows your plan usage bars and activity stats instead.
Habits that help you avoid hitting the limit
Official support and Claude Code documentation recommend a handful of habits for stretching your usage further.
- Plan your message before sending it — thinking through what you actually need cuts down on back-and-forth messages.
- Be specific in a single message — instead of a vague ask, spell out the conditions and context up front. "Improve this codebase" triggers broad scanning, while "add input validation to the login function in auth.ts" lets Claude work efficiently with minimal exploration.
- Batch related requests together — combining what would otherwise be several separate messages into one reduces your total message count.
- Use Projects to take advantage of caching — documents uploaded to a project are cached, so referencing the same content again only counts the newly processed portion against your limit.
- Clear the conversation between unrelated tasks — in Claude Code, clearing when you switch tasks means you're not recomputing the entire prior conversation every time.
- Match the model to the job — for anything short of complex architectural decisions, a cheaper model is often plenty.
If you've already hit the limit: your options
Officially, there are three broad options once you hit a limit — wait, upgrade your plan, or use usage credits.
| Option | What it means | Best for |
|---|---|---|
| Wait | Wait until the limit resets. Recent versions of Claude Code can also wait for the reset automatically and resume your interrupted task on their own. | Non-urgent work, or when the reset is coming up soon |
| Upgrade your plan | Moving from Free to Pro, or Pro to Max, raises your base limit itself. | When you're hitting the limit repeatedly |
| Use usage credits | Keep your current plan and pay for extra usage as needed. In Claude Code, this only works when signed in with your account — it isn't available with API key authentication. | A one-off period of unusually heavy use |
Common sticking points and fixes
- "I used way less than yesterday but I'm already at the limit" — claude.ai, Claude Code, and the desktop app all draw from the same shared usage pool. If you've been switching between apps, your combined usage may have filled up faster than you expected.
- "I got a limit message and starting a new conversation didn't fix it" — that's a sign it's a length limit (context limit), not a usage limit. A usage limit persists no matter how many new conversations you start; it only clears once it resets or you take one of the options above.
- "Switching models doesn't help" — if you've hit the session or weekly limit, switching models won't help, since both apply across all models equally. But if the message names a specific model limit (like Opus), switching to a different model does let you keep working.
Next steps
For a fuller comparison of usage limits across plans, see the Claude usage limits guide. For more on the September transition in Claude Code's weekly limit, see the weekly limits update.
Frequently asked questions
Q. How do I find the exact time my limit resets?
Both the session limit and weekly limit show their reset time on your account screen. On claude.ai, check Settings > Usage; in Claude Code, run /usage.
Q. Do conversations on claude.ai and coding sessions in Claude Code share the same limit?
Yes — according to official guidance, claude.ai, Claude Code, and the desktop app all draw from one shared usage pool. Heavy use in one reduces what's left in the others.
Q. Will limits get better or worse in mid-September?
The standard limit itself permanently goes up by 25%, but that's lower than the temporary 50% increase currently in effect, so it will likely feel like a reduction. That said, the schedule and figures have shifted more than once already, so it's worth double-checking against your account's usage display.
Q. Does the Free plan get this promotion or the permanent increase?
According to official guidance, this change applies to Pro, Max, Team, and legacy seat-based Enterprise plans. Free plans and usage-based Enterprise plans follow different terms.