01 — LIVE COUNTDOWNSTime until the next reset
Because Claude's subscription resets are personal, an honest countdown needs your anchor point. The session timer below starts as a demo session opened when this page loaded — press the button the moment you send your first message of a session and it becomes your real clock.
Next session reset
Resets —
Demo session anchored to when you opened this page. Your real window opens with your first message of a session — the reset lands exactly 5 hours later, in every time zone at once. Exception: verified Ultra accounts have no session window at all — only the weekly cap below applies to them. Newer Ultra accounts keep this window temporarily, until verified.
Next weekly reset
Resets —
Anthropic assigns each account a fixed weekly reset day and time — it stays the same regardless of when you subscribed or start using Claude. Find yours in Settings → Usage, then set it here. The limit message itself shows it too, e.g. “You've hit your weekly limit · resets Mon 12:00am”.
Next monthly API reset — 00:00 UTC, 1st of the month
Resets — · this is the one Claude reset that is universal: if your organization hits its monthly spend cap, API access pauses until 00:00 UTC on the 1st.
02 — THE CYCLESEvery Claude reset cycle, with times & time zones
Four different mechanisms get called a “reset.” Only one of them has a fixed clock time, and it belongs to the API — not to your subscription.
| Cycle | When it resets, exactly | Time zone behaviour | Who it applies to |
|---|---|---|---|
| 5-hour session window rolling |
Exactly 5 hours after the window opened (your first usage of the session). Example: first message 09:12 → full allowance back at 14:12. | Relative, so time zones are irrelevant — the reset is the same instant worldwide: 14:12 PT = 17:12 ET = 05:12 next day Beijing in the example above (06:12 Beijing while the US is on standard time). | Free, Pro, Max, Team, and unverified (newer) Ultra accounts. One shared pool across claude.ai, Claude Code and Claude Desktop, and across all models. Exception: verified Ultra accounts have no five-hour limit — only the weekly cap applies to them. |
| Weekly limit — all models fixed · account-assigned |
At a fixed day and time assigned to your account, every week, e.g. Monday 00:00 or Monday 18:00 as shown in your Usage panel. It does not move with your usage, your billing date, or when your subscription began — and you receive the full allowance each cycle. | Displayed in your local time in Settings → Usage and in limit messages. There is no published universal weekday — two accounts can reset on different days. | Paid plans: Pro, Max, Ultra (per member on Team — limits are not pooled). |
| Weekly limit — Opus only fixed · account-assigned |
A separate weekly readout for Opus alongside the all-models one. Exhaust Opus and other model families may still work — switching with /model can get you moving again; exhaust the all-models limit and switching does nothing. | Same account-assigned schedule as your other weekly readout; check Settings → Usage for both. | Paid plans that include Opus. |
| API rate limits token bucket · no fixed reset |
No reset moment. Limits are per minute — requests (RPM), input tokens (ITPM), output tokens (OTPM) — and capacity refills continuously via a token bucket. Every API response carries anthropic-ratelimit-*-reset headers (RFC 3339, UTC) and, on a 429, a retry-after in seconds. | Headers are in UTC. Your tier and limits live in the Console at platform.claude.com/usage/limits. | API organizations only. Tiers (Evaluation, Start, Build, Scale, Custom) are assigned automatically from usage history — completely separate from any Pro/Max subscription. |
| API monthly spend cap fixed · 00:00 UTC |
If spend hits the tier cap (Start $500 · Build $1,000 · Scale $200,000 per month), API usage pauses until 00:00 UTC on the 1st of the next month — the countdown above tracks it live. | 00:00 UTC = 08:00 Beijing (same day) · 16:00 PT / 19:00 ET on the last day of the previous month in winter, 17:00 PT / 20:00 ET in summer (DST). | API organizations on Start, Build and Scale tiers. Custom tier: no cap. |
About “monthly limits” on subscriptions: Anthropic's plan pages reserve the right to apply weekly and monthly caps at its discretion, but no monthly cap size or schedule is published for Pro or Max. If a site gives you an exact monthly reset date for a Claude subscription, it invented it. The monthly clock that is published is the API spend cap above.
03 — BY PLANPro vs Max vs Ultra vs API: different tank sizes — and one clock fewer on verified Ultra
Upgrading never makes a reset come sooner. It makes the window bigger. Anthropic publishes multipliers, not message counts — how much you actually get depends on message length, attachments, conversation length, tool use, model choice and effort level.
| Plan | Price (US) | Per 5-hour session | Weekly limit | Reset behaviour |
|---|---|---|---|---|
| Free | $0 | Baseline — at least 5× less than Pro | None published | 5-hour session window only. No Claude Code. |
| Pro | $20/mo · $17/mo billed annually | The baseline paid allowance (≥5× Free) | Yes — all-models, plus a separate Opus readout | 5-hour session + account-assigned weekly reset |
| Max | $100/mo | 5× Pro per session | Yes — same structure, larger allowance | 5-hour session + account-assigned weekly reset, identical clocks to Pro |
| Ultra | $200/mo | No five-hour limit for verified accounts (newer accounts keep a temporary 5-hour window until verified) | Yes — 10× Pro usage per week | Weekly reset only for verified accounts; the session window is gone, the weekly cap is unchanged |
| API (Console) | Pay per token | — no session window — | — no weekly window — | Per-minute RPM / ITPM / OTPM by tier, continuous refill; monthly spend cap resets 00:00 UTC on the 1st |
- One pool, every surface: chat, Claude Code and Desktop draw from the same session and weekly allowances. An afternoon in the terminal can end your browser chat, and vice versa.
- Two weekly bars, not one: an Opus-only weekly limit sits next to the all-models weekly limit. Know which one you hit before you decide to wait or switch models.
- Usage credits don't move the clock: past a limit you can keep going at standard API rates with prepaid credits — but the reset timing is unchanged.
04 — YOUR NUMBERSWhere to check your own usage & reset times
Your account panel is the only authoritative source for your reset times — no public page, including this one, can know them. Three official places to look:
Claude app — Settings → Usage
claude.ai → Settings → UsageShows your current session and time remaining in it, your progress toward the session limit, and both weekly readouts (all-models and Opus-only) with their exact reset day and time. Available on Pro, Max, Team and seat-based Enterprise plans.
Open Settings → Usage on claude.ai ↗Claude Code — /usage
/usageRun it inside Claude Code to see the same plan usage bars and the reset time attached to each window. The limit banner in your terminal names the reset too — e.g. resets 3:45pm for a session limit, resets Mon 12:00am for the weekly one.
API — Claude Console
platform.claude.com/usageUsage charts and rate-limit headroom for your organization, with your tier and per-model limits on the Rate limits page, and billing and spend caps under Settings → Billing.
Open Console rate limits ↗ API rate-limit docs ↗05 — FAQClaude reset questions, answered straight
What does Claude's “5-hour window” actually mean?
It is a rolling session allowance. A session window opens when you start using Claude, and the allowance refreshes five hours later. It is not a set of fixed blocks on the clock (it doesn't align to midnight or the top of the hour), and it doesn't tick down message by message on a sliding scale in a way you can game — think of it as: session starts → 5 hours later, full tank again.
The same window is shared across claude.ai, Claude Code and Claude Desktop, and across all models. Settings → Usage shows how much of the current session you've used and how much time is left in it.
When exactly does my Claude limit reset?
Depends which limit stopped you. Session limit: five hours after that window opened — the blocking message names the time (“5-hour limit reached – resets [time]”). Weekly limit: at the fixed day and time assigned to your account. Both are shown for your account in Settings → Usage, or with /usage in Claude Code. Waiting five hours does nothing for a weekly limit.
Does the Claude limit reset at midnight?
No. The session limit resets five hours after the window opened, at whatever time of day that lands. The weekly limit resets at your account's assigned day and time, which is not necessarily Monday and not necessarily midnight. The only Claude reset actually pinned to a clock is on the API side: a reached monthly spend cap lifts at 00:00 UTC on the 1st.
Does starting a new chat reset my usage?
No. Limits belong to your account, not to a conversation — a new chat draws from the same 5-hour and weekly allowances. A fresh chat still helps going forward: Claude re-reads the entire conversation on every turn, so a shorter conversation costs less per message. In Claude Code, /clear between tasks is the single strongest version of this lever.
Does Claude Code have a separate limit from claude.ai?
Not on a subscription. Usage on claude.ai, Claude Code and Claude Desktop all counts toward the same limits — Anthropic states this directly. The exceptions: API-key usage is metered separately per organization in the Console, and seat-based Enterprise allowances are pooled differently. If you're signed into Claude Code with an API key, there is no hard subscription stop — you're charged for what you use.
Why did I hit the limit after only a few messages?
Because Claude meters usage, not messages — and Anthropic publishes no fixed message count for any plan. The documented factors: message length, attachment size, current conversation length, tool usage (Research, web search, connectors), model choice, effort level, and artifact creation. One long Opus conversation with Research on can cost more than dozens of short Haiku chats. Longer conversations that trigger automatic context management cost extra, too.
Do Max and Ultra reset faster than Pro?
No — there is no faster clock. Max keeps the same clocks as Pro: the same 5-hour session window and an account-assigned weekly reset — it just fits more usage inside each window (5× Pro per session). Verified Ultra removes only the session window; its weekly reset is unchanged, so the weekly clock runs at exactly the same pace as Pro's.
Do Ultra accounts still have a 5-hour limit?
Not if the account is verified. Since October 30, 2026, verified Ultra accounts have no five-hour session limit at all. Newer Ultra accounts keep a temporary five-hour limit until they are verified. Either way, the weekly limit is unchanged — 10× Pro usage per week, resetting at your account's assigned day and time in Settings → Usage.
Can I make my limit reset sooner?
Nothing in Anthropic's documentation shortens a window. Your real options: wait for the reset shown in Settings → Usage; switch model families if only the Opus weekly limit is exhausted; turn on usage credits to keep working at standard API rates (credits explicitly don't affect reset timing); or upgrade for a larger allowance in the next window — upgrading doesn't move a weekly reset day either.
How are API rate limits different from Pro / Max limits?
Completely different system. The API has no 5-hour or weekly windows: it enforces per-minute limits — RPM, input TPM, output TPM — by organization and usage tier, refilled continuously with a token bucket, so there is no fixed reset time to count down to. Check the anthropic-ratelimit-*-reset headers on any response for the exact replenishment instant. The one fixed API clock is the monthly spend cap, which lifts at 00:00 UTC on the 1st.
Where can I see my exact reset time?
On claude.ai: Settings → Usage — current session, time remaining, and weekly reset times including the separate Opus readout. In Claude Code: /usage. For the API: the Console's Usage page (platform.claude.com/usage) and Rate limits page (platform.claude.com/usage/limits). The countdown tools at the top of this page will mirror any of these once you feed them your anchor time.