Free client-side tool

Claude Context Budget Estimator

Paste your instruction and memory files to estimate token cost, startup load behavior, and the point where memory should move into path-scoped rules or on-demand topic files.

Key facts

CLAUDE.md files loaded at launch consume context alongside the conversation.

Auto memory loads the first 200 lines or 25KB of MEMORY.md at session start.

Imported CLAUDE.md files help organization, but they still load into context at launch.

Context estimate

Use the tool

All calculations and files are generated in this page. Nothing is uploaded.

How to use it

  1. Step 1

    Paste one or more memory files into the estimator.

  2. Step 2

    Choose whether each file is CLAUDE.md, auto-memory MEMORY.md, a rule, or an on-demand topic file.

  3. Step 3

    Review estimated tokens, line count, byte size, and startup load status.

  4. Step 4

    Trim always-loaded context until only durable, high-signal guidance remains.

FAQ

Is the token count exact?

No. It is an estimate for planning. Tokenization varies by model and content, so treat the result as a budget signal rather than an exact bill.

What context window size should I choose?

Choose the context budget that matches your plan and model when you know it. If you are unsure, use the default as a rough planning baseline.

Why does MEMORY.md show a startup cap?

Claude Code docs say auto memory loads only the first 200 lines or 25KB of MEMORY.md at session start, with topic files read on demand.

Primary Sources

Related reading

Back to all tools