Claude usage tracker, plan by plan

What a tracker can know, and what it cannot

A tracker can only show what Claude reports for your account. On paid plans that is a lot: Settings > Usage has the five-hour session and the time left in it, the weekly limit and its reset, a Fable ceiling when your plan has one, and your usage credits. What nobody can show you is a token allowance, because Anthropic does not publish one: limits are percentages of a budget that depends on your plan.

Three kinds of tools exist:

• Trackers that read claude.ai's own figures, like UsageMeter: the same percentages and reset times as Settings > Usage, kept on screen.
• Trackers that estimate usage by counting the tokens of your messages, files and history. They also work where Claude reports nothing, but their percentages are estimates.
• Claude Code tools that read the local history of one computer: tokens and API-price costs rather than your plan's limits. Anthropic's own /usage breakdown works the same way and "usage from other devices or claude.ai is not included".

On a Free account, Anthropic documents no usage bars: Settings > Usage progress bars are described for Pro, Max, Team and seat-based Enterprise plans. Some trackers read the figures Claude sends with each reply instead; since version 1.6.0 (24 September 2026) UsageMeter does too, so a Free account gets its gauges.

What UsageMeter shows

UsageMeter is the extension we build, independent and not affiliated with Anthropic. For free, it shows:

• a gauge for every limit claude.ai reports for your account: the five-hour session, the weekly limit shared by all models and products, and any separate weekly limit of a model (Fable) or product;
• the countdown to each reset, and your pace: on track, or when you would be blocked at your current pace ("blocked around 9:40 PM");
• under each reply on claude.ai, what it took from your session, and today's budget: what is left of your week, spread until the reset;
• all of it on the page (in the composer, or a ring under it; hover for every limit) and on the toolbar icon;
• the tokens of the current session, and how your week split between chats, Claude Code and Cowork;
• your usage credits: this month's spend against your monthly cap, and whether auto-reload is on;
• Claude Code on Windows, with UsageMeter Link: the tokens of each PC added up, and kept after Claude Code's 30-day local cleanup;
• up to three Claude accounts.

UsageMeter Pro adds alerts before the wall (at your threshold, when your pace would block you soon, at 100% and when a limit is back, never twice across your devices), charts (the current window projected to its reset, the last 24 hours, the last 7 days), 90 days of history and up to ten accounts. Prices are on the pricing page.

Sample data

The weekly limit is shared by every Claude product, so the useful question is often where the week went. claude.ai reports that split, and UsageMeter draws it:

Where the week went: one weekly limit, shared by every product

Example: the week at 58% of the limit, day 4 of 7. The white marker is where a steady pace would be.

Example

• Claude Code53%31 pts
• Chats33%19 pts
• Cowork14%8 pts

At this pacethe limit would be reached around day 6.9 of 7.

Weekly usage by product in this example

Product	Share of the usage	Points of the limit
Claude Code	53%	31
Chats	33%	19
Cowork	14%	8

What UsageMeter reads, and what it never touches

UsageMeter reads usage percentages, reset times and token counts. It never reads, stores or sends your conversations. Your percentages, reset times and settings sync so the web dashboard, the Windows app and your other devices agree, attached to a random device ID until you create an account.

How it compares

Other good trackers exist, and some do things UsageMeter does not: the most installed one counts the tokens of each conversation and works on free accounts, two show Anthropic's peak hours, some notify you at thresholds you choose on the free tier. We compared seven of them, with what each does better, in Claude usage trackers compared.