How to See How Many Tokens Left in Claude (All Methods)

In this article

Claude does not display a live token counter during conversations, but there are three practical ways to check your remaining usage: the /usage slash command in Claude Code, the usage dashboard at claude.ai/settings/usage, and Usagebar for continuous menu bar monitoring. The method that fits you depends on whether you use Claude Code or claude.ai, and how often you need to check.

  • Claude Code users: run /usage in any session for an instant snapshot
  • Claude.ai users: visit Settings → Usage for a usage summary
  • Power users: Usagebar ($9 one-time) shows your 5-hour window, weekly cap, and context usage in the macOS menu bar with alerts at 50%, 75%, and 90%

Why doesn't Claude show a token count?

Claude's consumer plans (Pro, Max) enforce usage limits based on a rolling 5-hour window and a weekly cap, not a static per-message token budget. Because the limit is dynamic and time-based, there is no fixed "tokens remaining" number to display at any given moment. What you actually need to track is how much of your 5-hour and weekly allowance has been consumed, and how much context the current conversation is using.

How do you check usage in Claude Code?

Run /usage at any point in a Claude Code session. It returns your current usage within the active 5-hour window, your weekly consumption, and context tokens used in the current conversation. This is the fastest built-in method if you're already in a coding session. According to Anthropic's support documentation, Claude Code usage on Pro and Max plans draws from the same shared pool as claude.ai usage.

  • Open a Claude Code session
  • Type /usage and press Enter
  • Review the 5-hour window usage, weekly usage, and context size

For more detail on what these numbers mean, see how to check your Claude Code usage limits and how Claude Code's context window works.

How do you check token usage on claude.ai?

Go to claude.ai/settings/usage while logged in. The page shows your message usage and resets on a rolling basis. This view is better suited to understanding aggregate consumption over time rather than real-time remaining capacity. It does not show mid-conversation context size.

If you want to know when your usage resets so you can time your work accordingly, see when Claude Code usage resets and what timezone Claude usage resets in.

What is the best way to monitor Claude tokens continuously?

Usagebar is a $9 one-time macOS menu bar app purpose-built for tracking Claude Code usage. It shows your 5-hour window usage, weekly cap consumption, and current context token count without requiring you to interrupt your session to type a command. Notifications fire at 50%, 75%, and 90% so you can pace your work before hitting a hard limit.

MethodWhereShows context tokens?Real-time alerts?Cost
/usage commandClaude Code sessionYesNoFree
claude.ai/settings/usageBrowserNoNoFree
UsagebarmacOS menu barYesYes (50/75/90%)$9 one-time

What's the difference between context tokens and usage limits?

Claude tracks two separate things. Context tokens are the tokens in your current conversation window. Claude's models support up to 200,000 context tokens per conversation, and as a conversation grows longer it consumes more of that window. Usage limits are separate: they govern how many total interactions you can have within a 5-hour rolling window and a weekly cap. Running into a context limit ends one conversation; running into a usage limit blocks new requests until the window resets.

For strategies to stay within both constraints, see how to reduce Claude Code token usage and what to do when the Claude context window is exceeded.

Key takeaways

  1. Type /usage in Claude Code for a quick snapshot of your 5-hour window, weekly cap, and context size.
  2. Visit claude.ai/settings/usage in a browser to review your historical usage.
  3. Install Usagebar ($9 one-time, macOS) if you want passive monitoring and alerts before you hit limits mid-session.
  4. Claude enforces a rolling 5-hour window and a weekly cap, not a static per-message token budget.
  5. Context tokens (conversation length) and usage limits (rate limits) are separate systems -- both can stop a session.

Sources

Find Out Before You’re Locked Out, Not After

Checking your usage means stopping what you’re doing to go look. Usagebar keeps your 5-hour and weekly limits in the menu bar while you work, and alerts you at 50%, 75%, and 90% — so a lockout never lands mid-task.

Get Usagebar

$9 — one-time, lifetime updates