What Causes Claude Rate Limits
Claude enforces rate limits at two levels:
- Per-user usage window — a cap on how much compute you can consume within a rolling 5-hour window (Pro) or similar rolling period (Free)
- Server-side capacity limits — triggered when Claude's infrastructure is under high global load, affecting all users temporarily
The error messages you see differ between these two cases:
| Error | What It Means | |-------|---------------| | "You've reached your usage limit" | You personally exhausted your plan's rolling window | | "Claude is at capacity right now" | Global server load — not your personal limit | | "Too many requests" (API) | API rate limit exceeded — slow down requests | | "Rate limit — try again later" | Rolling window exhausted — wait for oldest requests to cycle out |
How the 5-Hour Rolling Window Works
Claude Pro does not reset at midnight or at a fixed time each day. Instead, it uses a 5-hour rolling window:
- Every message you send enters the window
- 5 hours after each message, it exits the window and the quota it used is freed
- When the window fills up, you're rate limited until old messages expire
Practical example:
- 9:00am — you send 30 long messages; window fills up
- You see "usage limit reached"
- 2:00pm — the 9:00am messages start expiring; quota frees up gradually
- By 2:30pm — enough quota has freed that you can send new messages
This is why the rate limit notification shows a specific time estimate rather than "try again tomorrow."
As of May 6, 2026: Anthropic removed peak-hour throttling for Pro and Max subscribers. You no longer experience slower responses during the 5am–11am PT busy period. The rolling window limit still applies, but you won't be throttled below your normal speed during peak hours.
Claude Rate Limits by Plan
| Plan | Usage Window | Monthly Cost | |------|-------------|--------------| | Free | Small rolling window, no 5-hour structure | $0 | | Claude Pro | 5-hour rolling window (~5x free) | $20 | | Claude Max | 5-hour rolling window (5x Pro) | $100 | | Claude Max | 5-hour rolling window (20x Pro) | $200 | | API (Tier 1) | Tokens per minute + requests per day | Pay per use | | API (Higher Tiers) | Higher TPM/RPD unlocked by spend history | Pay per use |
Free plan limits are not published officially but are significantly lower than Pro. Claude Pro gives priority access; as of May 2026, this also means no peak-hour throttling.
Step-by-Step Fix
1. Check the Reset Time in the Error Message
When Claude shows a rate limit notification, it typically includes an estimated wait time. Note that time and stop sending requests. Every additional attempt wastes quota without getting you closer to a response.
2. Understand What You Can Do Right Now
While waiting, you have a few options:
- Work on tasks that do not require Claude (local tools, other work)
- Use a different AI tool temporarily (ChatGPT, Gemini, Perplexity)
- Plan your next Claude session so you use it more efficiently when quota resets
3. Slow Down Your Request Pace
If you hit limits regularly, batch multiple questions into a single message instead of rapid-fire follow-ups.
Instead of:
Message 1: "Summarize this article" Message 2: "Now translate it to Spanish" Message 3: "Make the Spanish version shorter"
Do this:
"Summarize this article, then translate the summary to Spanish, then shorten the Spanish version to 100 words."
One message = one slot in the rolling window. Combining tasks dramatically extends how long your quota lasts.
4. Keep Conversations Shorter
Long conversation threads consume more quota per message because Claude re-processes the entire history each time. Start fresh conversations for new topics rather than extending one long thread.
Rule of thumb: When you switch topics, start a new conversation. Each new chat starts with zero accumulated context, making each message cheaper.
5. Request Shorter Outputs
When you do not need a full essay, say so:
- "In 2-3 sentences..."
- "Just the code, no explanation"
- "Give me the bullet points only"
Shorter responses consume less of your rolling window.
6. Upgrade Your Plan
If you regularly hit the Pro rate limit, consider Claude Max:
- Claude Max $100/month — 5x the Pro window (effectively 25x free)
- Claude Max $200/month — 20x the Pro window (effectively 100x free)
Upgrade at claude.ai/upgrade.
7. Switch to the Claude API for Heavy Workloads
For automated or high-volume use, the Claude API is more appropriate than the web app:
- Limits are token-based (tokens per minute), not conversation-based
- Higher throughput available at higher API tiers
- Supports exponential backoff and programmatic retry logic
Set up access at console.anthropic.com.
API Rate Limit Errors (429 Too Many Requests)
If you're using the Claude API and seeing HTTP 429 errors:
- Check your tier limits at console.anthropic.com under Usage and Limits
- Implement exponential backoff — start with a 1s delay, double on each retry, cap at 60s
- Reduce tokens per minute — large prompts consume TPM faster than short ones
- Batch requests — combine multiple short requests into one where possible
- Request a tier upgrade — API tiers unlock automatically based on cumulative account spend
Why This Happens: The Technical Reason
Claude is computationally expensive to run. Each response requires significant GPU processing, and the cost scales with the length and complexity of both your input and Claude's output. The 5-hour rolling window exists to prevent a small number of power users from consuming infrastructure that degrades response times for everyone else. The rolling structure (rather than a midnight reset) distributes load more evenly across the day.
Common Mistakes to Avoid
- Retrying immediately after a limit — this wastes remaining quota and can worsen throttling; wait for the reset time shown
- Running many parallel conversations — each browser tab or API call counts against the same rolling window
- Sending very long prompts repeatedly — long inputs consume the rolling window faster; be concise with context
- Confusing server capacity errors with personal limits — "Claude is at capacity" is global and clears on its own; your personal limit requires waiting out the 5-hour window
- Expecting a midnight reset — Claude Pro uses a rolling window, not a daily cycle; you may hit a limit at 3pm and not get a reset until 8pm
- Uploading large files repeatedly — file uploads count toward the rolling window; upload once and reference in subsequent messages
When to Contact Support
If you believe you're being rate limited incorrectly — for example, you've barely used Claude that day and still see a limit message — contact Anthropic support at support.anthropic.com. Include the exact error message text, the timestamp, and your plan type.