Claude Usage: Check What You've Used and When It Resets
Claude usage is the share of your current Anthropic allowance that you have consumed. Claude can apply a 5-hour usage window, weekly limits, and model-specific limits depending on your plan. In the Claude app, Settings › Usage shows your current meters and reset times. In Claude Code, /usage is the fastest way to inspect current usage status.
Check yours now
Two places show your live meters. Pick the surface you are working in.
Click your profile icon in the lower-left corner and open Settings › Usage to view your live 5-hour and weekly progress bars with exact reset countdowns.
Full app walkthrough →Run /usage in any active terminal session as the quickest way to check your current plan usage and limit status in Claude Code.
Which Claude limit is closest to its limit?
Enter the percentages shown in Settings › Usage to see which meter has consumed the highest share of its allowance. Nothing is uploaded or connected to your account.
Applies only to Opus; shares your weekly reset schedule.
Enter the percentages shown in your Claude Settings › Usage above.
The interpreter compares your entered meters, highlights which one is closest to its limit, and outlines the relevant next step.
What do the Claude usage meters mean?
Official Anthropic subscriptions enforce limits across distinct, concurrent meters.
| Meter | What it constrains | How reset works |
|---|---|---|
| 5-hour usageSession window5-hour reset rules → | Short-term prompt frequency and concurrency across Claude and Claude Code. | Rolling countdown; resets exactly 5 hours after your first prompt in that session. |
| Weekly usageAccount ceilingWeekly limits → | Cumulative all-models quota across a 7-day period. Shared across web and CLI. | Fixed schedule; resets on a specific day and hour assigned to your account. |
| Opus weeklyModel-specificOpus allocation details → | Dedicated high-compute sub-cap restricting Opus usage separately from general quota. | Refills on the same assigned weekly account schedule as your all-models cap. |
Short-term prompt frequency and concurrency across Claude and Claude Code.
Rolling countdown; resets exactly 5 hours after your first prompt in that session.
5-hour reset rules →Cumulative all-models quota across a 7-day period. Shared across web and CLI.
Fixed schedule; resets on a specific day and hour assigned to your account.
Weekly limits →Dedicated high-compute sub-cap restricting Opus usage separately from general quota.
Refills on the same assigned weekly account schedule as your all-models cap.
Opus allocation details →Why does Claude usage sometimes drain so quickly?
Anthropic dynamically meters usage based on documented factors affecting prompt and completion size.
Conversation Length
Longer current conversations can consume usage faster because conversation length is one of the factors Anthropic uses when determining usage.
File Attachments
Larger attached files can increase usage. While project files and repeated content may benefit from prompt caching, larger documents and images require more processing capacity.
Tool & Feature Usage
Tool-heavy work—including features such as Research, web search, and Claude Code tool commands—can affect usage rates compared to standard chat.
Model Choice & Effort Level
Different models and configured effort levels can consume available usage differently. Higher-capability models such as Opus draw more from available allowances.
What should I do now?
Direct routing based on your current observed usage state.
Step-by-step walkthroughs for Settings › Usage on web/mobile and /usage in Claude Code.
Understand rolling window anchoring and calculate when your session allowance comes back.
Review assigned 7-day account schedules and compare weekly allowances across plan tiers.
Learn how extra Usage Credits enable pay-as-you-go continuation at API token rates.
Set up persistent terminal statuslines or open-source local session telemetry.
Developing in the terminal with Claude Code?
An open-source companion tool reuses the Claude Code login already on your machine and reads your account's limits directly from Anthropic. Session and weekly windows in your terminal, menu bar, or a localhost dashboard. No API key, no account, no stored history.
Frequently asked questions about Claude usage
Common questions on monitoring limits, reset timing, and quota mechanics.
Where do I see my Claude usage right now?
In Claude web and desktop apps, click your profile avatar in the lower-left corner and navigate to Settings › Usage. You will see progress bars for your active 5-hour session window and weekly all-models cap with exact reset countdowns. In Claude Code, run the command /usage directly in your terminal session as the quickest way to check your current plan usage and limit status.
Which Claude usage limit is closest to its limit?
Whichever meter shows the highest percentage is the one closest to its limit among your active allowances. A high 5-hour percentage means you have consumed more of your short-term session window, while a high weekly percentage reflects cumulative 7-day consumption across all models. On paid plans, Opus also carries an independent weekly sub-cap. Your reset times determine when each allowance refreshes.
When does Claude usage reset?
The 5-hour session window resets exactly five hours after you send your first message in that session, regardless of the clock hour. In contrast, the weekly cap resets on a fixed schedule assigned specifically to your account (e.g., every Wednesday at 4:00 PM UTC), which remains constant week after week.
Can I continue working if I reach my Claude usage limit?
Yes, if you are on a paid plan (Pro, Max, or Team), you can turn on Usage Credits in Settings › Usage. When enabled, hitting your included limit automatically transitions prompts to prepaid API credits billed at standard Anthropic per-token rates, allowing uninterrupted work.