Claude Fable 5 token limits, pricing, and context fit
A plain-English guide to planning prompts for Anthropic's newest flagship family.
Updated Jul 31, 2026 · Reviewed by PromptCostLab
Token and pricing information changes frequently. Use this guide for planning and verify model-specific limits and prices with the provider before production billing.
What counts toward a Claude request?
A Claude request is more than the sentence typed into a chat box. The complete input can include system instructions, conversation history, retrieved documents, tool definitions, image or file content, and formatting added by an SDK. The response also needs room inside the model’s request limits. Treating all of this as one shared budget is the safest way to plan a production workflow.
PromptCostLab gives you a fast local estimate for plain text. That is useful for comparing prompt versions and spotting context pressure without uploading sensitive text. For exact billing or requests containing tools and files, verify the final payload with the provider’s official counting method.
How to calculate a realistic token budget
Start with the stable instructions, add the average amount of retrieved context, include the recent conversation turns your application normally sends, and reserve a deliberate output allowance. Do not plan against the absolute published context limit. Leaving headroom makes retries, citations, tool results, and longer-than-average user messages less likely to break the request.
- Measure the full production prompt, not a shortened demo.
- Reserve output tokens before evaluating context fit.
- Test average and worst-case retrieval sizes.
- Record the model and pricing date used for the estimate.
Context fit and cost are different decisions
A prompt can fit comfortably and still be expensive at scale. Conversely, a very large context window does not mean every request should fill it. Calculate input and output cost separately, then multiply by expected daily request volume. This exposes whether the expensive part is repeated context, generated output, or the number of calls.
For RAG systems, the most effective optimization is often retrieval quality. Sending fewer, more relevant passages can improve answer quality while reducing token use. Long context is a safety net, not a substitute for selecting good evidence.
When local estimates are enough
Use a local estimate while drafting prompts, comparing versions, sizing documents, or selecting a likely model. Use provider-backed counting before setting hard production limits, showing a customer an exact bill, or sending structured requests with tools, images, and attachments. The label matters: a useful estimate should be transparent about what it includes.
- Drafting and prompt cleanup: local estimate.
- Model comparison and capacity planning: local estimate plus headroom.
- Billing reconciliation: official provider usage.
- Tool or multimodal payloads: provider-backed counting.
A practical Claude workflow
Paste the exact reusable prompt into the PromptCostLab Claude calculator, set a realistic output allowance, and note the context percentage. Next, repeat the calculation with the retrieved content your system usually adds. If the result is close to your operational ceiling, reduce repeated instructions, summarize old conversation turns, or retrieve fewer passages before changing models.
Prices, token behavior, and model limits change. These primary provider docs are the right place to verify the details before shipping.