Claude weekly usage limits, explained

Claude meters your usage on two clocks at once: a rolling five-hour session window and a set of weekly caps that reset seven days after your first message of the cycle. Understanding both is the difference between hitting a wall mid-task and pacing yourself comfortably. And here is the part most people miss: the surplus you do not use each week simply resets.

The two clocks: session windows and weekly caps

Claude does not run on a single monthly bucket. It uses a dual-limit system. The first clock is a rolling five-hour session window that starts with your first message and governs short bursts of heavy use. The second clock is a set of weekly caps layered on top, so even light-but-constant use is bounded over seven days.

The weekly clock resets on a rolling basis, roughly seven days after the first message of your current cycle, rather than on a fixed calendar date like the 1st of the month. That means your personal reset day depends on when you started, not on everyone else's.

Why there are effectively two weekly limits

In practice Claude tracks two separate weekly ceilings. One covers your overall usage across all models; the other applies specifically to the fastest, most capable tier (the Sonnet-class models). You can bump into the fast-tier cap while still having room on the general one, which is why usage can feel uneven near the end of a week.

It also matters that Claude Code and Claude chat draw from the same pool. Time spent in the terminal and time spent in a browser conversation both count against the same weekly caps, so a busy coding day and a busy writing day compound.

How Pro and Max plans differ

Your plan sets how high those ceilings sit. Pro gives a solid weekly allotment suited to regular individual use; Max raises the caps substantially for people who live in Claude all day, across both chat and Claude Code.

The exact numbers are intentionally not published as fixed figures here, because Anthropic has changed limits over time and occasionally runs promotions that temporarily lift them. Treat any specific quota you read online as a snapshot; the mechanism is stable even when the numbers move. When in doubt, check your account's usage screen, which reflects your real current caps.

Use it or lose it: weekly limits do not roll over

Here is the key thing to internalize: weekly limits are a ceiling, not a balance. They are use-it-or-lose-it. When your cycle resets, your allotment refills to the same level whether you used all of it, some of it, or none of it. Unused headroom does not accumulate and does not carry into next week.

For most people that means a real, recurring surplus. If you only reach for Claude a few times a week, a meaningful slice of paid capacity quietly evaporates every reset. You are already paying for it; it simply expires.

Put your weekly surplus to good use

That expiring headroom is exactly what Tokens for Good exists to capture. Instead of letting weekly capacity reset unused, you point it at researching and vetting real nonprofits for a public directory at fiercephilanthropy.org. It runs on your existing subscription at no extra cost; there is nothing new to buy.

To be clear, "tokens" here means AI model tokens (your normal Claude usage), not crypto; there is no coin, wallet, or blockchain. The output is verified through a dual-research and deterministic-scoring pipeline, then published. Best of all, you can wire it to run on a schedule with /schedule so it works quietly in the background. Learn what Tokens for Good is or read the docs to set it and forget it.

Frequently asked questions