Claude Session Limit Explained: 5-Hour Reset and 90% Warning
May 2026 · 7 min read
Quick answer
Claude's session limit is a rolling usage cap that commonly resets around every 5 hours. The 90% warning means your current session is nearly exhausted, so start smaller tasks, wait for reset, or track usage in real time before sending a heavy prompt.
Claude.ai limits how much you can use it — not just per month, but within a rolling 5-hour window called a session. Understanding how this works is essential for anyone who uses Claude seriously for work.
What Is Claude's Session Limit?
A session limit is a usage cap that resets on a rolling basis — roughly every 5 hours for Claude Pro subscribers. Within each session, you have a finite amount of Claude compute available. When you exhaust it, Claude shows a pause screen telling you when the limit resets.
The session limit is separate from Claude's context window (how much text Claude can hold in one conversation). You can have a short conversation that consumes a lot of your session allowance, and a long conversation that consumes relatively little — it depends on the computational cost of each task, not just length.
What Does “You've Used 90% of Your Session Limit” Mean?
Claude shows this warning when your current rolling session is close to exhausted. You may still be able to send a few short messages, but a long document, coding request, or extended thinking task can push you into the limit screen immediately.
Treat the 90% warning as a decision point: finish small follow-ups, save the important context, or wait for the reset timer before starting anything expensive. A live usage tracker helps because you can see the warning before Claude interrupts the conversation.
Session Limit vs. Weekly Limit
Claude Pro has two distinct limits that work independently:
Session limit resets approximately every 5 hours. The most common limit for active daily users. Intensive tasks — long documents, complex code, extended thinking mode — consume it faster than simple queries.
Weekly limit is a rolling 7-day cap. Harder to hit for most users, but relevant for anyone running multiple long sessions each day or using Claude for automation-heavy work.
Both limits are independent. You can have 50% session usage remaining while your weekly is nearly exhausted — or vice versa. This is one reason it's worth tracking both numbers simultaneously.
| Limit | Reset period | Who hits it |
|---|---|---|
| Session | ~5 hours (rolling) | Daily heavy users |
| Weekly | 7 days (rolling) | Power users, automation users |
Why Does Anthropic Implement Session Limits?
Running Claude is computationally expensive. Session limits serve a few purposes:
Distributing compute fairly. Without limits, a small number of extremely heavy users could consume disproportionate server capacity, degrading performance for everyone. Session limits smooth usage across the subscriber base.
Making flat-rate pricing sustainable. Claude Pro is priced at a fixed monthly fee. Unlimited usage at that price point would be economically unviable. Limits are what make the subscription model work.
Encouraging efficient usage. Knowing you have a session budget incentivizes structured thinking about tasks rather than running dozens of nearly-identical prompts.
What Counts Toward Your Session Limit?
Not all Claude interactions consume equal amounts of your allowance:
Higher consumption: pasting long documents, conversations with extensive history (every turn re-processes all prior messages), extended thinking mode, complex multi-step tasks.
Lower consumption: short questions and answers, fresh conversations with no history, simple formatting or transformation tasks.
This is why you can sometimes have 15 short exchanges without issue, then hit your limit mid-way through one intensive code review session.
How to Check Your Session Usage
Claude.ai exposes session usage under Settings → Usage. The data is real — Claude reads it from its /usageAPI endpoint. The problem is that navigating to Settings means leaving your active conversation, and you'd need to check manually each time.
A more practical approach: ClaudeKit, a free Chrome extension, adds a persistent usage badge to every Claude.ai page. It shows:
- Session % — how much of your current 5-hour session you've used
- Weekly % — your 7-day cumulative usage
- Reset countdown — exactly when your session limit refreshes
ClaudeKit reads from the same API Claude's own Settings page uses. No scraping, no intercepting conversations — just surfacing data that was already there. For a full walkthrough, see: How to Track Your Claude.ai Usage Limit in Real Time.
What Happens When You Hit the Session Limit
When you exhaust your session limit mid-conversation, Claude displays a message with your reset time. Your conversation history is preserved — Claude doesn't lose context or delete anything. You simply can't send new messages until the timer expires.
The best strategy is to avoid being surprised by this. Knowing you're at 85% of your session limit before starting a heavy task is the difference between planning and frustration.
Strategies for Working Within Session Limits
Know your budget before heavy tasks. With a live badge showing your session %, you can decide whether to start an intensive task now or wait for a fresh session.
Use fresh conversations for unrelated topics. Each conversation loads its entire history as context for every new message. A 50-message conversation costs more per turn than a fresh one. For a new topic, start a new chat.
Fork before experimenting. Running the same prompt with minor variations is expensive. Use conversation forking to explore alternatives from a single context point without duplicating cost.
Save your best prompts. If you spend 5 messages tuning a prompt, save the final version. Next session, you start with what works rather than re-exploring from scratch. See our prompt library guide.
Session Limits on Free vs. Pro vs. Max
Anthropic doesn't publish exact token counts for session limits — the caps are defined in compute terms, not raw tokens. What we know from users:
- Free plan — significantly lower session limits; hits quickly during intensive use
- Claude Pro ($20/month) — standard session limits; most users don't hit weekly limits under normal use, but session limits are reachable during intensive work days
- Claude Max ($100/month) — higher limits across the board; designed for heavy professional use
ClaudeKit works with all three plans and auto-detects which plan you're on.
The Bottom Line
Claude's session limit is a rolling ~5-hour usage cap, separate from your weekly limit. Both affect your ability to use Claude, and neither one warns you proactively before you hit it.
Understanding what the limit is gets you halfway there. Tracking it in real time — so you can plan around it instead of hitting it unexpectedly — is what actually changes how you work.
FAQ
What does Claude session limit mean?
Claude session limit means you have used a capped amount of Claude compute within a rolling work window. For Claude Pro, users commonly see this as an approximately 5-hour session window.
What does “you've used 90% of your session limit” mean in Claude?
It means your current Claude session is almost exhausted. You can usually keep sending messages briefly, but a larger task may push you into the cutoff screen before the reset time.
When does the Claude session limit reset?
Claude session usage resets on a rolling schedule, commonly around every 5 hours for Claude Pro users. The exact reset time can vary by plan and current usage.
What counts toward a Claude session limit?
Long documents, long conversation histories, complex analysis, coding tasks, and extended thinking usually consume more of the session limit than short questions in a fresh chat.
Is Claude session limit the same as weekly usage limit?
No. The session limit is a shorter rolling window, while weekly usage is a longer rolling cap. You can hit either one independently.
Can I increase Claude session limit?
You cannot bypass Anthropic limits with an extension. You can make a session last longer by tracking usage, starting heavy tasks after reset, using shorter contexts, and forking before experiments.
Free Chrome Extension
See your session and weekly usage in real time.
ClaudeKit adds a live badge to every Claude.ai page showing both limits and your reset countdown. Free, no account required.
Add to Chrome — It's Free