How Does Claude's 5-Hour Limit Work? (Pro & Max Plans Explained)

In this article

Claude's 5-hour limit is a rolling usage window, not a fixed daily reset. When you hit your message cap, you're locked out for up to 5 hours from the time you sent your first message in that burst, not from when you hit the wall. It applies to both Claude Pro and Claude Max plans, though the thresholds differ significantly.

  • The window is rolling: starts when you begin a heavy usage session
  • Claude Pro is capped at roughly 45 messages per 5-hour window (varies by model and message length)
  • Claude Max 5x raises that to ~225 messages; Max 20x to ~900 messages
  • There is also a separate weekly cap that resets independently

What is Claude's 5-hour limit?

The 5-hour limit is Anthropic's primary rate-limiting mechanism for Claude.ai chat. It caps the number of messages (or token-weighted usage) you can send within any 5-hour rolling period. Once you hit the cap, Claude shows a message like "You've reached your usage limit. You can resume in X hours." The clock started from your first message in that session, not from when you got blocked.

This design means two people on the same plan can hit their limits at completely different clock times. There is no shared global reset at midnight or at the top of the hour.

How does the rolling window work?

A rolling window means the 5-hour timer begins at the timestamp of your first message in a usage session, and new capacity is unlocked continuously as older messages age out. If you sent your first message at 9:00 AM, your window expires at 2:00 PM, regardless of whether you hit the cap at 9:30 AM or 1:55 PM.

This is different from a fixed reset (e.g., "resets at midnight UTC"). The practical implication: if you front-load your usage early in the day, you may be locked out during your most productive hours later. Spreading usage across the window gives you more consistent access.

For more detail on the reset mechanics, see when does Claude Code usage reset and the breakdown of Claude Code weekly limit vs 5-hour lockout.

What are the limits per plan?

Claude Pro gives you the baseline 5-hour window. Claude Max (available at 5x and 20x tiers) multiplies that capacity proportionally. As of mid-2026, Anthropic's support documentation describes the Claude Max plans as providing 5x or 20x the usage of a standard Pro subscription.

PlanPrice/monthApprox. 5-hour capWeekly cap
Claude Pro$20~45 messagesYes (separate)
Claude Max 5x$100~225 messagesYes (separate)
Claude Max 20x$200~900 messagesYes (separate)

Note: Anthropic does not publish exact message counts. These are community-observed estimates. Actual limits vary based on message length, model selected (Opus vs. Sonnet), and conversation context size. Longer prompts consume more of your window faster. See Claude Pro vs Max limits for a deeper comparison.

Is the 5-hour limit the only cap?

No. Claude has two independent limits running simultaneously: the 5-hour rolling window and a separate weekly usage cap. You can exhaust your weekly cap before ever hitting a 5-hour lockout if you use the tool heavily across multiple sessions in a week. Both limits must be respected, and hitting one does not reset or affect the other.

The weekly cap resets on a fixed schedule tied to your billing cycle or account creation date, not to calendar weeks. If you've been blocked and the 5-hour window has passed but you're still locked out, the weekly cap is likely what you've hit. Check what to do when you hit the Claude Code rate limit for next steps.

Does the 5-hour limit apply to Claude Code?

Yes. Claude Code (the CLI agent) draws from the same usage pool as Claude.ai when you authenticate with a Pro or Max plan. Heavy Claude Code sessions, especially those running multi-file edits or long agentic loops, can consume your 5-hour window quickly because each tool call and response round-trip counts toward usage. See does Claude Code usage affect Pro limits for how the two interact.

Anthropic's support page on using Claude Code with Pro or Max confirms that Claude Code usage counts against your plan's limits, not as a separate allocation.

How do you check how much of your 5-hour window is left?

There are three ways to monitor your remaining Claude usage in real time. The built-in options require manual checking; Usagebar automates it.

  • /usage command: In Claude Code, type /usage to get a snapshot of current usage against your limits.
  • claude.ai/settings/usage: Web dashboard showing usage for the current period.
  • Usagebar: A $9 one-time macOS menu bar app that shows your 5-hour window usage, weekly cap, and context window in real time. Sends notifications at 50%, 75%, and 90% so you're never surprised by a lockout mid-session.

For a full walkthrough of all three methods, see how to check your Claude Code usage limits.

Get Usagebar to track your 5-hour window passively, without stopping work to check a dashboard. One-time purchase, no subscription.

How do you avoid hitting the 5-hour limit?

Hitting the 5-hour cap usually comes down to three habits: using long context windows, running long agentic loops without checkpoints, and front-loading all usage into a short burst. Fixing any one of these extends how long your window lasts.

  • Keep context windows short. Summarize and start new conversations rather than carrying huge context across dozens of turns.
  • Use checkpoints in agentic tasks. Break long Claude Code sessions into discrete tasks with pauses between them, rather than one continuous run.
  • Spread usage across the window. If you know you need 4 hours of access, don't burn through 80% of your cap in the first 30 minutes.
  • Monitor in real time. Use the /usage command or Usagebar to catch yourself before you hit the wall, not after.

If you're regularly hitting the 5-hour cap on Pro, upgrading to Max 5x is the most direct fix. If you're hitting it on Max, the usage patterns above will matter more than plan tier.

Key takeaways

  1. The 5-hour window is rolling from first message, not a fixed reset time.
  2. Pro, Max 5x, and Max 20x have proportionally higher caps (roughly 1x, 5x, 20x).
  3. A separate weekly cap exists and operates independently of the 5-hour window.
  4. Claude Code usage counts against the same pool as Claude.ai chat.
  5. Check remaining usage via /usage, the web dashboard, or Usagebar for continuous monitoring.

Sources

Never Get Locked Out Mid-Task Again

Never hit your usage limits unexpectedly. Usagebar lives in your menu bar and shows your 5-hour and weekly limits at a glance.

Get Usagebar

$9 — one-time, lifetime updates