Claude Usage Credits: Extra Usage, 5-Hour & Weekly Limits

Billing and limit rules checked against Anthropic’s Help Center · October 19, 2026

What changed: added a balance-mismatch checklist and clarified when self-run API/SDK work differs from interactive Claude Code. The original publication date, bundle example and account-specific reset guidance are retained. This is a source-based guide, not a hands-on billing test.

Claude usage credits are optional pay-as-you-go capacity for paid Pro, Max 5x, and Max 20x plans after included usage limits are reached. They are not the same as the plan’s five-hour session allowance, the separate weekly limit, or Anthropic API Console credits. Usage credits are billed at standard API rates, and the exact amount depends on the model, tokens, files, conversation context, and features used.

The short answer

Pro, Max 5x, and Max 20x subscribers can enable usage credits to continue eligible work after included plan usage is reached.
Your included plan usage is used first. Credits do not make the subscription unlimited or move the normal reset earlier.
Claude’s session-based limit resets every five hours; paid plans can also have a weekly limit with an account-specific reset time.
Usage credits are configured in Settings → Usage. A mobile-billed subscription may still need the web app to enable and purchase credits.
Anthropic API Console credits are a separate organization/API billing balance. If you have credits but are still blocked, use the balance-mismatch checklist before paying again.
Before paying, check whether your account has a free limit-reset offer. It is a different mechanism from buying credits.

Claude limits are several different meters

A “Claude limit” message does not identify one universal counter. Anthropic’s current guidance separates usage limits—which control how much you can use Claude over a period—from length limits, which control how much a single conversation can hold. Paid plan capacity can also include session, weekly, model, feature, or other fair-access controls.

Meter or balance	What it means	What to do
Included plan usage	The capacity bundled with Pro, Max 5x, or Max 20x. It varies with model, effort, files, conversation length, and demand.	Check Settings → Usage and plan the heaviest work inside the included window.
Five-hour session limit	A session-based usage meter with five-hour resets; reaching 100% does not establish a new five-hour countdown.	Use the reset shown on your account, not five hours added to the time you were blocked.
Weekly plan limit	A separate allowance across models with a fixed, account-assigned reset day and time.	Read the next reset in Settings → Usage; do not infer it from subscription start time.
Model-specific weekly limit	An additional meter for a named model. Current usage-credit documentation identifies a separate Fable weekly limit on Max.	Check the named meter as well as the all-model meter; available capacity in one is not extra capacity in the other.
Length/context limit	The maximum usable context for one conversation. It is different from how much you may use Claude over time.	Shorten context, use focused Projects, or start a new conversation when appropriate.
Usage credits	Prepaid overflow that can continue eligible work after included plan limits, billed at standard API rates.	Enable only with a monthly cap and after confirming the account and feature.
Anthropic API Console credits	Developer/API organization billing for programmatic requests, with its own keys, limits, and usage page.	Manage it in the API Console, not in the consumer Claude Usage screen.

Included API credit is not app overflow

Eligible Max and Team plans now offer claimable monthly API credits in a linked Console organization. They do not increase plan limits or fund app extra usage. Treat that benefit separately from the paid usage-credit balance described here. See the official distinction and our Max credit and total-cost examples.

Why do I have credits but Claude is still blocked?

A positive balance is not proof that it can pay for the request in front of you. Match the balance, product and exhausted meter first. A second purchase can leave you with two funded balances and the original problem.

What you see	What it does not prove	Check next
Monthly API credits in Console; Claude chat or interactive Code is limited.	The API grant cannot fund app or interactive Code overflow.	Check the separate Usage screen, not another API top-up.
App usage-credit balance remains; the monthly spending cap is reached.	Prepaid funds do not override the spending cap.	Review paid consumption and the cap; do not raise it automatically.
The session has reset; a weekly meter is still exhausted.	A session refill does not refill the weekly allowance.	Read the exhausted weekly meter’s own reset time.
Code is spending API funds when you expected subscription usage.	A paid plan does not establish the running client’s billing mode.	Check authentication and organization privately; follow the Code billing checklist.

These are different failure paths, not one universal fix. The usage-credit rules, API-grant exclusions and Code billing guidance explain the boundaries.

Self-run SDK work is not the same as interactive Code

For the monthly API grant, how a run is launched and authenticated matters. Self-run Agent SDK or claude -p work can use the grant with an API key from the linked Console organization. With plan sign-in, it uses plan limits instead. Runs launched by the Code GitHub Action, an IDE extension or the desktop app count as Code usage and are excluded, even with -p. Do not generalize this to “every API-key Code session is covered.”

Claimed monthly API credit also expires at the billing-cycle boundary without rolling over. That is not the same rule as purchased app usage-credit expiry. Check the balance’s label and expiry, rather than treating every item called “credits” as one wallet.

A two-minute record before spending again

Identify the request: app or client, selected model, sign-in method and Console organization if applicable. Do not copy an API-key value.
Identify the stop: exact error, affected meter and displayed reset time with time zone. “I have Max” is not enough to diagnose it.
Identify the money: balance type, expiry, current paid consumption, monthly cap and auto-reload status on that same billing surface.
Choose deliberately: wait, redeem an offered reset, restructure the task or authorize a bounded paid continuation. Compare the matching ledger afterwards; do not run repeated retries as a billing test.

If those details still disagree, give official support the redacted record and the time of the failed request. Remove keys, payment details and private prompts from screenshots. This evidence is more useful than buying another bundle to see whether it works.

What happens when included usage is exhausted?

With usage credits enabled, a funded balance and room under your monthly spend limit, the next request after an included limit is exhausted can automatically use paid credits. An approaching-limit warning may briefly remain until that request succeeds and the label becomes “Now using credits.” Do not assume another confirmation will appear before each paid request. This applies to the session or weekly limit, including Max’s Fable weekly meter. Anthropic documents this transition.

Read the dashboard as two ledgers: an included meter at 100% describes plan capacity; a falling usage-credit balance describes paid continuation. A successful reply is therefore not proof that the included meter refilled. Conversely, an old warning alone is not proof that the paid request failed. Check the reply, the current billing label and paid consumption together.

This does not create a fixed conversion such as “one credit equals ten messages.” Anthropic says message capacity varies with the length of files, the current conversation, the selected model, effort, and the feature being used. A long Claude Code task or Research session can therefore consume more capacity than a short text exchange.

Extra usage, session reset, and weekly limit: the practical difference

Extra usage is the paid continuation path. The five-hour session limit is a recurring plan-capacity window. The weekly limit is a broader account-assigned allowance that can constrain usage across models. Credits can let eligible work continue after included limits, but they do not change the reset schedule or guarantee that every model and feature is eligible.

If the Usage page shows that the session reset is near, waiting may be cheaper than adding funds. If the account also shows a weekly cap, waiting for a five-hour session reset may not restore the full weekly allowance. Read both meters and the next reset before deciding.

For the immediate “five-hour limit reached” flow, see our Claude five-hour limit and reset guide. For a plan-tier decision, compare Claude Pro, Max 5x, and Max 20x.

Check for a free limit reset before buying credits

Anthropic occasionally grants resets to eligible accounts; this is not an on-demand benefit promised to every subscriber. In Claude web or Desktop, inspect Settings → Usage → Resets for Reset for free. Read which limit it restores and any offer expiry before confirming. It can restore the specified session or weekly allowance immediately, but does not change the usual weekly schedule, refund earlier paid usage, or add credit balance. Redemption cannot be undone. Mobile and Claude Code users need web or Desktop to redeem it. See the official reset rules.

The practical order is: identify the exhausted meter, inspect any reset offer, check the scheduled reset, then decide whether paid continuation is worth it. Do not repeatedly retry a long task while assuming that a funded account is still blocked for free.

How to enable Claude usage credits

Sign in to Claude on the web with the account that owns your paid plan.
Open Settings → Usage and find the Usage credits section.
Choose Enable, add a payment method if required, and review the spending controls.
Use Adjust limit to choose a monthly spending limit. Anthropic also offers an unlimited option, but a finite cap is safer while you learn your usage.
Use Add funds to purchase a prepaid balance. If available, configure auto-reload only after checking its threshold and cap.

Keep three controls separate: your monthly usage spending limit, the balance you prepay, and any auto-reload purchases. A discounted-bundle purchase cap is a fourth rule, not your personal budget. Confirm the actual cash amount in checkout and inspect the balance after a representative task before committing more money.

What if the subscription was purchased through Apple or Google Play?

Anthropic says usage credits for a mobile-billed paid plan must be enabled and purchased through Claude’s web app, not set up inside the mobile app. This creates two separate routes to keep straight:

Apple App Store or Google Play may handle the recurring Pro/Max subscription.
Claude’s web billing flow handles the usage-credit balance.

Use the same Claude account and verify the Usage screen before buying. If the paid plan itself is missing, use our Claude subscription-not-showing checklist rather than purchasing a second subscription.

How much do Claude usage credits cost?

Usage credits use standard Anthropic API pricing rates. The final cost depends on the selected model, input and output tokens, cached or repeated context, files, tools, Research, and Claude Code activity. There is no reliable universal “dollars per message” figure.

The current bundle documentation lists optional discounted prepaid balances for Pro, Max and Team:

Credit value	Cash paid	Discount
$50	$45	10%
$250	$200	20%
$1,000	$700	30%

For individual Pro/Max accounts, the documented cap is $2,000 of discounted bundle value per month—not per day. Team Owners and Primary Owners have a $3,000 monthly cap. These are discounted-purchase limits, not an unlimited-use allowance; beyond them, the documentation specifies standard-rate usage. Verify Buy usage and the live terms before purchasing.

For a workflow that needs developer keys, token accounting, or an application budget, use the HiseHub AI API Cost Calculator and the API Console. A usage-credit purchase in Claude’s consumer interface should not be treated as an API organization balance.

A discounted bundle is not the same as a lower bill today

Hypothetical bookkeeping example—not a measured Claude session: you buy $50 of credit value for $45, then a task consumes $20 of that value. The three numbers to record are:

Cash paid now: $45. This is the amount committed to the bundle, excluding any separate subscription or checkout adjustments.
Credit value consumed: $20. The unused credit value is $30, not a $30 cash refund.
Allocated cost of the consumed portion: $18. For your own worksheet, $20 × ($45 ÷ $50) assigns the same 10% discount to the consumed value. The remaining $27 of purchase cost is tied to unused credit; this allocation is not a claim about how Anthropic formats its bill.

The bundle can be a good discount if you will use the balance, but “10% off” does not mean you paid only $18 today. Compare the actual purchase amount with your cash budget, and judge future use from recent work rather than buying the biggest discount automatically. Most usage credits do not expire under current guidance, but jurisdiction-specific expiry still matters; use the date shown on your balance, not the monthly bundle-cap reset, to judge that risk.

For a repeatable decision, record the task, model and billing surface, opening credit balance, closing balance, cash purchases and auto-reloads, plus whether the plan meter reset during the task. This separates expensive work from a payment event. A useful month-end comparison is subscription cash + additional payments alongside credit consumed and credit remaining; adding the remaining credit to the amount spent would count the same purchase twice.

Claude Code, Projects, files, and Research

Anthropic says usage credits can apply to Claude conversations and Claude Code terminal usage. Combined activity across those surfaces can matter when you are trying to explain why a seemingly light chat week still reaches a limit. Project files and documents also contribute tokens when used as context; Research can process multiple searches and therefore consume more.

Keep Project knowledge focused instead of attaching the same large files to every turn.
Start a new conversation when old context is no longer needed.
Use a more efficient model for routine work when the task does not require the most expensive model.
Reduce effort, extended thinking, tools, or connectors for simple tasks when those controls are available.
For Claude Code, check whether the workflow is using the subscription surface or an API key/Console organization.

If Claude Code is charging an API balance instead of the subscription path, follow our Claude Code billing-context guide. The exact control depends on the account and current product UI.

When should you wait, buy credits, upgrade, or use the API?

Your situation	Reasonable first choice	Why
Your account displays a free reset for the exhausted meter.	Review the offer and use it if the immediate refill is valuable.	This restores the specified included allowance; buying credits does not.
The five-hour reset is close and the work is not urgent.	Wait and retry at the displayed reset.	It uses included capacity rather than paid overflow.
An occasional deadline needs more work after the limit.	Enable a small credit balance with a monthly cap.	Usage credits are designed for paid continuation, not a permanent tier change.
You hit session or weekly limits most weeks.	Compare Max 5x/20x against actual monthly overflow.	A recurring tier may be easier to budget than repeated standard-rate usage.
You need code integration, keys, logs, or an application budget.	Evaluate the Anthropic API separately.	API Console billing, token rates, and organization limits are a different product boundary.
The problem is one huge conversation or file.	Reduce context or restructure the Project.	A length/context limit is not necessarily solved by buying usage credits.

Use the AI Model Access Map for plan/model availability and the AI Subscription Price Comparison for regional subscription context. Neither replaces the live Usage page for your account.

Safety and billing checks before adding funds

Confirm the account email and whether you are in the personal Claude app or an API organization.
Read the feature, model, and price details on the current Usage or checkout screen.
Set a finite monthly limit and review the auto-reload threshold.
Check the payment method and remember that a mobile subscription and web usage credits can have different billing owners.
After a session, review included usage and paid consumption separately in the dashboard.

Anthropic says usage credits can be disabled in Settings → Usage. Once disabled, only the plan’s included usage remains available. Usage-credit expiry can also vary by jurisdiction; the current help article notes that most credits do not expire, while certain Japanese purchases have a six-month rule beginning September 10, 2026. Follow the expiry shown in your Usage page rather than relying on a general assumption.

Frequently asked questions

Do Claude usage credits replace Pro or Max?

No. They are an additional pay-as-you-go balance for eligible paid-plan usage after included limits.

Do credits change the five-hour reset?

No. Anthropic says the included session limit still resets every five hours. Credits provide continuation; they do not move the timer.

Is the weekly limit the same as the session limit?

No. A session-based five-hour meter and an account-assigned weekly allowance are separate concepts. Both can affect availability.

Can mobile subscribers purchase usage credits in the app?

Anthropic’s current guidance says setup and purchase must be completed on the Claude web app, even if the subscription was bought through Apple or Google Play.

Are Claude usage credits the same as API Console credits?

No. They have separate balances and billing contexts, even if you use the same sign-in email. A linked Max API grant is not app overflow. Check which balance can cover the request before adding funds.

Why did a long chat consume more than expected?

Message capacity depends on context length, files, model, effort, and features. Start a focused conversation and inspect the Usage dashboard instead of converting messages into a fixed credit estimate.

Official sources

Billing and limit rules reviewed October 19, 2026. Bundle amounts are a dated documentation snapshot, not a checkout guarantee. Examples are arithmetic illustrations, not hands-on usage measurements. HiseHub is independent and is not affiliated with Anthropic. Plan access, token rates, expiry and billing behavior can change; your Usage and checkout screens and Anthropic’s current documentation control.