When Claude tells you that you’re “rate limited,” it means you’ve hit a built‑in usage cap and the system is temporarily blocking or slowing further requests so the service stays stable and fair for everyone.

What “rate limited” means on Claude

In practice, “rate limited” usually means one of these:

  • You’ve sent too many messages or API calls in a short time (for example, many prompts in a minute).
  • You’ve generated or processed too many tokens (text) in a given time window.
  • On subscriptions or API tiers, you’ve reached a weekly or daily cap for that plan, especially if you’re a heavy user.

Claude then returns an error like “Too many requests” or “Global rate limit exceeded” and may ask you to wait before trying again.

Why Claude has rate limits

Rate limits exist so that:

  • No single user can consume a disproportionate amount of compute resources.
  • Capacity stays available and responsive for other users during busy times.
  • Abuse is reduced (e.g., bots hammering the system, scraping, or DDoS‑like behavior).
  • Costs and infrastructure load remain predictable, especially on lower pricing tiers.

Anthropic also uses usage tiers for API and credits, where higher tiers get more generous limits once you deposit or spend more.

Typical limits you might hit

Exact numbers depend on whether you’re using the website/app or the API, but common patterns include:

  • Requests per minute (RPM): Maximum number of prompts per 60‑second window.
  • Tokens per minute (TPM): Total number of input+output tokens per minute. Long conversations can hit this faster.
  • Daily or weekly caps for subscribers: Especially for features like Claude Code, new weekly limits were added after some users ran it continuously or shared accounts.

On the API, these limits are tied to your organization’s tier and spend caps, which you manage in the console and billing settings.

What you can do if you’re rate limited

If you see a rate‑limit message:

  1. Wait for the window to reset
    • Most short‑term limits reset in seconds or minutes; subscription weekly caps reset on the next period.
  1. Slow down your requests
    • Space out prompts, avoid firing many nearly identical requests at once, and keep drafts local instead of repeatedly hitting the model.
  1. Shorten your prompts and outputs
    • Reduce context length, avoid pasting huge documents repeatedly, and request shorter answers when possible. This lowers your token usage.
  1. Upgrade or adjust your plan (API / paid tiers)
    • On the API side, moving to a higher usage tier via larger deposits/spend increases available limits.
 * For consumer subscriptions, options may include switching to a higher plan or buying extra usage when that’s offered.
  1. Check for unusual usage
    • If you’re not using Claude heavily but still see rate limits, make sure you’re not sharing accounts and that no automated tools are sending hidden requests.

Quick example

Imagine you’re using Claude Code and run it nonstop as an always‑on coding assistant: background tasks, continuous refactors, large codebase summaries. After a while, you hit the weekly usage cap that Anthropic introduced to stop a small number of users from consuming most of the capacity, and Claude starts refusing new runs with a rate‑limit message until your week resets or you adjust your plan.

TL;DR: “Rate limited” on Claude means you’ve used the service faster or more heavily than your current time‑window or tier allows, so you need to slow down, wait for a reset, or increase your available limits.

Information gathered from public forums or data available on the internet and portrayed here.