Mechanics Explained · The 5-Hour Rolling Window

How Claude's 5-Hour Rolling Window Actually Works
When the window starts, and how it stacks with the weekly limit

The 5-hour rolling window doesn't reset at fixed times each day — it starts rolling from the moment you first use quota within it. A dashboard that doesn't match your expectation is usually about this starting point.

#5-hour rolling window#rolling vs fixed#stacks with weekly limit#dashboard mismatch

Four key facts

5 hours

Window length

Counted from the moment you first use quota within this window, rolling for 5 hours — not reset on the hour.

2 layers

The 5-hour window and weekly limit coexist

The 5-hour rolling window governs short bursts of heavy use; the weekly limit governs total usage for the whole week. They're calculated independently, and either one filling up gets you rejected.

Rolling

Not a fixed clock

It doesn't reset at fixed times like midnight, 5am, 10am, etc. — every new bit of usage rolls out a fresh 5-hour window.

The error text

How to tell which layer you hit

If the reset time in the error is hours away, it's almost certainly the 5-hour window; if it's days away, it's the weekly limit.

How the 5-hour window actually works

The 5-hour rolling window starts counting from the moment you actually make a request that uses quota, and rolls forward 5 hours; you can keep using it within that window until the quota fills up, or until the 5 hours pass and the window naturally rolls into the next period. It isn't the kind of mechanism that zeroes out at fixed times each day — which is exactly why many people find 'the time on my dashboard doesn't match what I expected': the starting point is triggered by you, not scheduled by the system on the hour.

Why it often gets confused with the weekly limit

The 5-hour rolling window and the weekly limit are two completely independent layers — one governs short bursts of heavy use, the other governs the whole week's total. In everyday use you rarely hit both at once, but when your account is already close to the weekly limit, a request can get rejected by the weekly layer even if the 5-hour window still has headroom — in that case, watching for 'the 5-hour window just reset' doesn't help; you need to look at the weekly limit's reset time instead.

Timeline

Ongoing

The 5-hour rolling window has existed since Claude subscription plans introduced usage limits, as the main constraint on short bursts of heavy use.

2026-08-18

Anthropic officially announces the +50% weekly quota boost is extended through 2026-08-31 — during this window, both layers have more real headroom than usual.

Ongoing

The mechanism of the 5-hour window and weekly limit being calculated independently hasn't changed; only when the weekly layer's temporary boost expires is changing.

Confirmed vs. common misreading

Confirmed

The 5-hour window rolls from the actual moment of usage and is calculated independently from the weekly limit; the reset time given in error text (hours away vs. days away) is the most direct way to tell which layer you hit.

Common misreading

Many people assume the 5-hour window resets at fixed clock times each day, and suspect their account is broken the moment an observation doesn't match. In reality, the starting point is triggered by your own usage, not scheduled by the system on the hour.

5-hour window vs. weekly limit

5-hour rolling window

Governs short bursts of heavy use; the start point is set by your own usage, and once the window's quota is full you wait for that window to roll past.

Weekly limit

Governs the total for the whole billing cycle, calculated independently of the 5-hour window; even with headroom left in the 5-hour window, hitting the weekly limit still gets you rejected.

How to tell which layer you hit

Check the reset time given in the error text: hours away almost certainly means the 5-hour rolling window; days away means the weekly limit. You can also check your dashboard directly — in most cases it shows current usage and reset time for both layers separately, so don't draw a conclusion from a single number alone.

What to do on QCode

Whichever layer fills up — the 5-hour window or the weekly limit — you can route the current task through one QCode key to GPT, Gemini, GLM and other models as a stopgap, without waiting for either layer to roll over or reset.

FAQ

Does the 5-hour window reset at a fixed time each day?

No. It rolls forward 5 hours from the moment you actually use quota — it isn't a 'fixed times each day' mechanism.

Are the 5-hour window and the weekly limit the same thing?

No. They're calculated independently — the 5-hour window governs short bursts of heavy use, the weekly limit governs the total for the whole week, and either one filling up gets you rejected.

How do I know which layer I'm currently stuck on?

Check the reset time in the error: hours away means the 5-hour window, days away means the weekly limit; you can also check both layers' usage directly on your dashboard.

The 5-hour window is full — how long until it recovers?

Just wait for that window to roll past, usually no more than 5 hours; check your account dashboard for the exact reset time.

Do the two layers affect each other?

They don't offset each other, but they do constrain you jointly — even with headroom left in the 5-hour window, hitting the weekly limit still gets you rejected, and vice versa.

Does the temporary +50% weekly boost affect the 5-hour window?

No. That boost only applies to the weekly limit layer; how the 5-hour window operates hasn't changed.

Sources

How the 5-hour rolling window operates, and how to tell it apart from the independently-calculated weekly limit, come from Anthropic's official documentation and consistent public developer discussion over time. Compiled 2026-08-27.

5-hour window full? Don't just wait around

One QCode key switches to GPT, Gemini, GLM and more as a stopgap — no need to wait for the window to roll over.