← All posts
Claude session limits

Claude Session Limit Explained: The 5-Hour Window, Its Warnings and When It Resets

Updated November 2026 · 7 min read

Quick answer

Claude's session limitis a usage cap on a 5-hour window that starts with your first message. “You've used 90% of your session limit” means about a tenth of that window's allowance is left: enough for a few short messages, not a big task. It resets in full five hours after the session began, and Settings → Usage shows the exact time. When it runs out, Claude says “5-hour limit reached - resets [time]”; Claude Code says “You've hit your session limit · resets [time]”.

ClaudeKit shows how much of your 5-hour session is left and when it resets, and warns you at 90%. Free, no account.

Add to Chrome, free

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 before starting anything expensive. Claude may also word it as “Approaching session limit”. ClaudeKit keeps your usage on screen and shows its own heads-up card at 90% with the exact reset time; ClaudeKit Pro adds a run-out forecast and a notification when Claude is back.

Got a “Reset for free” Button? That's a Limit Reset

Since the Fable 5.2 launch on November 9, 2026, many paid accounts see a Limit resets section in Settings → Usage, and the same Reset for free button on the limit message. A limit reset refills a limit now instead of when it would reset on its own. A Fable reset refills the whole 5-hour window and gives back the weekly usage you spent on Fable, but it doesn't reset your whole week. A full reset refills both the session and the weekly limit.

Max, Ultra and premium Team seats got one to three Fable resets depending on how long they have subscribed, and those expire on March 8, 2027. The types, how many each plan gets and when they expire are in Claude limit resets: how many you get and what each one does.

Every Claude Limit Message, and What It Means

Claude words its limit messages differently depending on whether you are close to a limit, past it, or paying with usage credits. Here is each one:

MessageWhat it meansWhat to do
“Approaching session limit” or “You've used 90% of your session limit”Warning. Most of the current 5-hour window is used; you can still send messages.Finish small follow-ups and save your context before anything long.
“Approaching weekly limit” or “You've used 75% of your weekly limit”Warning for the 7-day cap. The percentage varies.Pace the rest of the week. See Claude weekly limits explained.
“5-hour limit reached - resets [time]”The session limit is used up. New messages are blocked until that time.Wait for the reset, or carry the conversation to another chat or AI.
“You've reached your weekly limit. It resets [day] at [time].”The weekly limit is used up, whatever the session window says.Wait for that day, or check whether a limit reset is offered.
“5-hour limit resets [time] - continuing with usage credits” or “Now using credits. Your plan limit resets [day] at [time]”Not blocked: on a paid plan with usage credits turned on, Claude keeps going and charges your credits.Usage credits are turned on in Settings → Usage, which is also where you turn them off.
“You've hit your session limit · resets [time]” (Claude Code)Claude Code's version of the 5-hour message, from the same shared limit.Run /usage in Claude Code to see your limits and reset times.
“Your message will exceed the length limit for this chat”Not a usage limit: the conversation or attachment is too long for one chat.Start a new chat with a summary. See moving a Claude conversation to a new chat.

The claude.ai wording comes from Anthropic's help article on Claude error messages; the Claude Code line is how Claude Code prints the limit in the terminal.

When Does Claude's Session Limit Reset?

Claude's session limit resets on a rolling schedule, not at one fixed time every day. For Claude Pro, the window commonly refreshes around five hours after the session window began, but the exact reset time shown by Claude is the one to rely on. Here is how to find your Claude limit reset time.

Session usage and weekly usage reset separately. A session reset can let you continue working even when your longer weekly allowance is still partially used.

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.

Does Claude Code Use the Same Session Limit?

Yes. On Pro, Max and Ultra plans, Claude Code is not a separate pool: Anthropic's Claude Code plan article says limits are shared across Claude and Claude Code, including IDE usage. A long Claude Code run can use up the 5-hour window you planned to spend in chat, and the other way round.

In the terminal the limit reads “You've hit your session limit · resets [time]”, and /usage shows where you stand. After a heavy coding session, check Settings → Usage before starting a long chat.

LimitReset periodWho hits it
Session~5 hours (rolling)Daily heavy users
Weekly7 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.

ClaudeKit, a free Claude usage tracker, keeps that number on screen instead: a small circle in the bottom-right of claude.ai, refreshed while the tab is open and shortly after each message (see the one-minute demo). It appears only when Claude returns usage data:

  • Inner ring — how much of your current 5-hour session you've used
  • Outer ring — your weekly usage
  • Hover — each limit with its reset countdown

The values are not sent to ClaudeKit or stored as history. For a walkthrough, see the Claude usage tracker guide, or use Claude's Usage settings directly. If your plan has been offered a limit reset, see how Claude's “Reset for free” works.

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.

A saved checkpoint and reusable prompt can help you resume a task without rebuilding the thread from memory.

Here is what ClaudeKit shows before and after you hit the limit: a heads-up at 90%, the reset time, and a notification when Claude is back.

36 seconds: the 90% heads-up, the limit-reached card and the Claude-is-back notification

Strategies for Working Within Session Limits

Know what you need to resume. Save the goal, decisions, constraints, and next action before starting an intensive task.

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 by Plan: Free, Pro, Max and Ultra

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
  • Claude Ultra ($200/month) — no five-hour session limit on verified accounts; only the weekly limit applies

ClaudeKit works on every plan; its usage circle shows whichever limits Claude reports for your account.

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. Claude warns you as either one gets close, but only on the page in front of you, so it pays to keep both numbers in view.

Understanding the limit is useful. Pairing it with a small checkpoint is a practical way to keep work recoverable when an interruption arrives.

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.

What does “5-hour limit reached” mean in Claude?

Your current five-hour session allowance is used up. The message includes the reset time ("5-hour limit reached - resets [time]"), and you can send messages again after that. If you have turned on usage credits, Claude keeps going on credits instead and says so.

Does Claude Code use the same session limit as claude.ai?

Yes. Anthropic says limits are shared across Claude and Claude Code, including IDE usage, so a long Claude Code run uses the same 5-hour window as your chats. In Claude Code the message reads "You've hit your session limit · resets [time]", and /usage shows your limits.

When does the Claude session limit reset?

Five hours after the session started. The window opens with your first message and resets in full five hours later; Settings → Usage shows the exact reset time. Weekly limits reset separately.

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 5-hour window that starts with your first message, while the weekly limit resets at a fixed day and time assigned to your account. You can hit either one independently.

What is a limit reset in Claude?

A free, one-time refill Anthropic gives eligible paid plans. A five-hour reset refills your session limit, a weekly reset refills your weekly limit, a full reset refills both, and a Fable reset refills the 5-hour window plus the weekly usage spent on Fable. Use it from Settings → Usage → Reset for free.

Can I increase Claude session limit?

No extension can bypass Anthropic limits. Your options are a higher plan, usage credits, or a limit reset if your plan has been offered one (Settings → Usage → Reset for free). You can also make a session last longer with shorter contexts and fresh chats.

Free Chrome Extension

Keep Claude work organized.

See your session and weekly usage on claude.ai, plus prompts, forks, pins, token estimates, and exports. Usage appears only when Claude returns real data.

Add to Chrome — It's Free