How Claude Code Plans and Usage Limits Work — the 5-Hour and Weekly Limits

Claude's usage limits (shared between claude.ai and Claude Code) are a two-layer system — a "5-hour session limit" and a "weekly limit" — and without knowing the mechanics, reset timing looks baffling. Here is the official help material, organized.

The plan lineup

Plan	Approx. monthly price	Claude Code	Usage
Free	Free	No	Small
Pro	$20 (discounted yearly)	Yes	5x+ Free per session
Max 5x	$100	Yes	5x Pro
Max 20x	$200	Yes	20x Pro
Team / Enterprise	Per-seat pricing	Plan-dependent	With admin features

• Claude Code requires Pro or above. Usage is shared between claude.ai chat and Claude Code (they eat the same allowance)
• Limits are based on processing volume, not message count. The longer the conversation and the bigger the context, the more each message consumes
• Limits and prices change; for authoritative numbers see the official help

There are two layers of limits

Two independent limits, and exhausting either one stops you on the spot.

	5-hour session limit	Weekly limit
Period	A 5-hour window	7 days
Anchor	The moment you send the first message while no window is open	A fixed weekday/time assigned to your account
What the reset restores	The session allowance only	The weekly allowance only
Where to check	/usage (Claude Code) / Settings → Usage (claude.ai)	Same

The weekly limit is a single allowance shared across all models. Max plans get one extra allowance dedicated to the top models (shown as a separate gauge in /usage).

How the 5-hour session limit works

• The session window opens when you send the first message and closes exactly 5 hours later. Send at 9:47 and the window is 9:47–14:47
• While a window is open, resuming at any time does not move its anchor. Break at 11:00, return at 13:00 — the reset is still 14:47
• The first message after a window closes anchors the next window
• Hence both intuitions people have — "5 hours from when I started" and "resets at a fixed time" — can feel right. Precisely: 5 hours from the start of the currently open window

Points people misread:

• Taking a break does not speed up the reset (the window closes by clock time, not usage)
• If you exhaust it mid-window, you can only wait for the window to close (remaining time shows in /usage)
• Conversations survive across windows; only the limit counter is affected

How the weekly limit works

• The reset happens once a week at a fixed weekday and time assigned to your account. From the official help:

Weekly limits reset at a fixed time each week that is assigned to your account. Your reset day and time stay the same regardless of when you start using Claude or when your subscription begins.

• The assignment is not necessarily a calendar week (Monday 00:00 etc.) and has nothing to do with your subscription date or first use. Some accounts are assigned a mid-week day
• Your own assignment shows as the next-reset time on the weekly gauge in /usage

In practice: resets sometimes come earlier than the assigned day

The official story is "once a week, fixed" — but early resets have been widely reported through 2026. My own account is assigned Monday yet reset on a Thursday, and digging around turned up plenty of matching reports.

• Anthropic has, more than once, ad-hoc reset limits for all users as compensation for incidents and bugs (the runaway-subagent consumption issue, a weekly-limit display bug, etc.) — including one on July 10, 2026
• A measurement report that monitored the weekly gauge's API value for ~11 days found resets on roughly a 72-hour (3-day) cycle. Its comment thread is full of off-schedule reports too: "scheduled Sunday, reset Friday," "double reset Thursday and Sunday"

In short, "the weekly allowance coming back earlier than the assigned day" genuinely happens. The discrepancy runs in your favor (never the losing direction of not restoring on schedule), so just enjoy it. Treat it as a place where official spec and operational reality don't currently match.

What happens when the two limits overlap

This is the most confusing part. The key: the two counters are fully independent and never reset each other.

• Weekly reset lands mid-way through a 5-hour window: only the weekly allowance refills. The open session window continues as-is, and whatever session allowance you already spent does not come back
• A session window resetting does not restore the weekly allowance: the classic late-week pattern is "5 hours passed, my session should be back, but I still can't use it" — that is the weekly allowance being empty
• You can stall with weekly allowance to spare: that is the session limit biting. Wait out the 5 hours and you are back
• So whenever a reset feels inexplicable, the first move is /usage to determine which limit you are even looking at

This also explains the gut-level confusion. Session resets happen several times a day while the weekly reset is once a week, so most "something refilled" moments are the session side — and most "it reset but I still can't use it" moments are the weekly side.

Checklist when reset timing looks wrong

1. Check /usage for the next reset time of both the session and weekly limits (mixing up the two is the most common issue)
2. Weekly refilled earlier than scheduled → as covered above, ad-hoc resets make this real. It is in your favor; don't worry about it
3. Not refilled on the scheduled day, or suddenly blocked → check /usage for whether you hit the other limit
4. UI timestamps get rounded, so ignore minute-level discrepancies

Options when you hit a limit

• Wait for the reset: check the next reset time in /usage
• Buy extra usage: paid plans can purchase pay-as-you-go credits after hitting limits (official help)
• Reduce consumption: next section

Tips for spending less

• Keeping context small matters most. Long conversations cost more per message — /clear at natural breakpoints, /compact when it swells
• Build the habit of checking /context to see how much you are carrying
• Light tasks on lighter models (/model); thinking depth can also be lowered with /effort
• Don't re-paste the same material repeatedly (push it into Projects, CLAUDE.md, or skills so caching can work)

Summary

• Limits are two independent layers: "5-hour session" and "weekly." Either running dry stops you
• The session window is anchored by the first message of the currently open window. Breaks don't move it
• The weekly reset is an account-specific fixed weekday/time — not necessarily a calendar week
• The two never reset each other, so when things look strange, start by splitting the question with /usage