Five-hour and weekly usage limits detailed for paid Claude plans
Detected October 9, 2026, 05:15 UTC · How usage and length limits work
Previously, the documentation referenced an unspecified usage limit timeframe. It now formally defines that paid accounts are subject to two distinct caps: a five-hour session reset and a weekly limit.
This documentation outlines the operational caps governing how individuals communicate with Claude across web chats and developer tooling. Previously, the article described usage boundaries generically as a single periodic reset interval without providing specific operational timeframes. The text now establishes that subscribers on paid tiers are subject to two discrete restrictions: a recurring five-hour session window and an overarching allowance that refreshes once every seven days. In practice, this distinction means paying customers must manage consumption across both immediate working periods and broader weekly spans. Users encountering either ceiling can pause until the cycle refreshes, move to a higher tier, or allow pre-funded balances to automatically sustain continued prompts without halting work. Length restrictions per interaction remain managed by starting fresh threads or utilizing organizational workspaces. While the text clarifies these two temporal boundaries, it does not disclose the exact numerical message allowances or token volumes assigned within each window, nor does it state whether differing subscription levels share identical weekly quotas.
We compare this page once a day and record every difference. The text above is written by Claude Network from that comparison; none of it is copied from the source.
Source: How usage and length limits work