How the projection works
Your limit fills over a window: five hours for the session, a week for the weekly limit. From the percentage used and the time left, the calculator knows how much of the window has gone by and how fast you have been going. At the same pace, it gives the time you would reach 100 %, or, if that comes after the reset, the level you would reach at the reset.
Example: 45 % of the session used with 3 hours left means 45 points in 2 hours, 22.5 points an hour. The remaining 55 points go in about 2 h 27 min: 100 % some 33 minutes before the reset. It is the same projection as the pace marker of the UsageMeter extension.
The average or your recent pace
The average since the window opened smooths everything out, a quiet morning and a busy afternoon alike. Add an earlier reading of the same window and the calculator uses the pace between your two readings instead, like the extension’s forecast, which follows your last 45 minutes (12 hours for the week).
Where to read your numbers
In Claude, Settings › Usage shows the percentage of your current session and of your week, the time remaining in the session, and when your weekly limit resets. Claude Code shows the same limits in /usage, and its status line can read them too.
The session window opens with your first message once the previous one is over, and closes about five hours later; the weekly limit resets at a fixed time assigned to your account.
What this calculator cannot know
It projects a pace; it doesn’t see your account. Your pace changes with what you do: a long conversation, a big file or Claude Code working in the background speed it up. Anthropic doesn’t publish its limits in tokens, and can change them. The extension reads the limits Claude shows you and redoes this projection as you go.
Questions
How accurate is the projection?
As accurate as your pace is steady. It assumes you keep going at the same rate: a burst or a break moves the answer. Add an earlier reading to follow your recent pace, and check again later.
What is the difference between the average and the recent pace?
The average spreads your usage over everything since the window opened. The recent pace only looks at the time between your two readings, so a busy last half hour shows at once. The UsageMeter extension uses the recent pace for its forecast.
Does it work for the weekly limit?
Yes: choose the weekly limit and enter the day and time of your weekly reset (Settings › Usage shows them), or the time left. The window is then a week long.
What happens when I reach 100 %?
Claude stops you until the limit resets. On Pro and Max, usage credits can keep you working, billed at standard API rates; Claude Code can also wait in the open session and continue automatically at the reset.
Can I enter tokens instead of a percentage?
No: Anthropic publishes its limits as percentages, not in tokens, so a token count can’t be turned into a share of your limit. Use the percentage Settings › Usage shows.
Related pages
- How to check your Claude usageGuide: Settings › Usage, the apps and Claude Code.
- Claude usage limit reached: what to doGuide: what the message means and what you can do.
- Claude limit reset time calculatorThe time your 5-hour limit comes back, in your time zone, with a countdown.
- Claude peak hours in your time zoneThe last published window on your clock, and what it still changes.
- Claude plan pickerPro, Max 5x or Max 20x, from the limits you hit.
- When Claude’s limits resetThe 5-hour session, the weekly reset and the free limit reset, explained.
Sources
- Anthropic help center: usage limit best practices
- Anthropic help center: what is the Pro plan? (weekly limits)
- Claude Code docs: status line (rate limit fields)
- Anthropic help center: usage credits for paid plans
Checked against Anthropic’s pages on September 24, 2026. Anthropic can change these rules at any time.
UsageMeter is an independent tool, not affiliated with Anthropic. Claude and Claude Code are Anthropic’s products.