Prompt Caching Calculator
See how much prompt caching actually saves. Pick your model, then enter your prefix size and request rate to get a monthly figure and the traffic where caching starts to pay.
Cache reads cost 10% of input. Caches prefixes of 512+ tokens. List price checked 30 Sep 2026 (source).
Writes cost 1.25x input. Each hit resets the 5-minute timer.
System prompt, tools, fixed docs. Must be identical every call.
The user's message. Never cached.
About 1,440 a day, one every 1 minutes on average.
Saving by traffic, for this prompt and cache
Caching pays above about 2.9 requests an hour.
requests per hour · the solid bar is your traffic
Assumes requests arrive at random through the hour and that each hit resets the cache timer, which is how Anthropic and OpenAI caches behave. Output tokens are not affected by caching and are left out.
What moves the saving
Three things decide whether caching pays off. The calculator captures all three; here is what each one does.
Read discount
Cached input tokens bill at 2% to 10% of the standard price. The bigger and more repeated your prefix, the more each hit saves.
Write premium
Some providers charge 1.25x or 2x to write a cache. Sparse traffic lets the cache expire between calls, so you pay that premium again and again.
Prefix stability
A cache hit needs a byte-identical prefix. One timestamp in the wrong place drops your hit rate to zero and you pay to re-cache every call.
Caching is one of three levers for cutting your model bill. Read the full guide to prompt caching and the broader playbook on LLM cost optimization.
Prompt caching calculator FAQ
How much does prompt caching save?+
Cache reads cost 2% to 10% of the standard input price on current models, so the repeated span of a prompt costs 90% to 98% less once it is cached. What you actually save depends on how often a request finds the cache warm. The calculator works that out from your request rate and the cache lifetime, then charges the read price on hits and the write price on misses to give a monthly figure for your own numbers.
What is the break-even for prompt caching?+
Providers that charge a write premium (Anthropic 1.25x on the 5-minute cache and 2x on the 1-hour one, GPT-5.6 1.25x) only save money once enough requests find the cache warm. With a 1.25x write and a 0.1x read, break-even is a 22% hit rate, which a 5-minute cache reaches at about 3 requests an hour. The 1-hour cache needs a 53% hit rate but gets there at under 1 request an hour. Providers with no write fee (DeepSeek, Gemini implicit caching) save from the first hit.
What counts as the cacheable prefix?+
The stable content at the start of every request: your system prompt, tool and function definitions, few-shot examples, and any fixed reference documents. It has to be identical byte-for-byte across requests to hit the cache. The variable part, the user message, always sits at the end and is never cached, which is why it does not affect the saving.
Is a higher cache hit rate always better?+
Yes, for cost. Every hit is billed at the read discount instead of full price, and on Anthropic and OpenAI each hit also resets the cache timer for free, which is why busy traffic keeps a cache warm almost indefinitely. The usual reason hit rates are low is a dynamic element (a timestamp, session ID or rotating instruction) buried in the prefix, which changes the hash and forces a fresh write every request. Move anything variable to the end of the prompt.
Which providers does this calculator cover?+
Every model in the site price list: Claude (Fable, Opus, Sonnet, Haiku, with 5-minute and 1-hour caches), GPT-5.6 (Sol, Terra, Luna, 30-minute cache), Gemini (implicit caching, and explicit caching with its storage fee) and DeepSeek, each with its own read price, write fee and minimum cacheable prompt, checked against the providers in September 2026. Pick "Custom" to enter the terms from your own contract.
Cut your AI bill without cutting quality
The calculator shows the prize. We build the caching, routing and cost instrumentation that captures it. Book a free cost review.
Book a Free 30-Minute Call
We map one workflow that eats your team’s week and show you what an engineer and a few AI agents could take off it. No slide deck, no sales pitch. Just a working session.
Don’t want a call? Email [email protected]
Book a free call- One workflow mapped with you, live
- A clear first step for your team
- Reply within one working day
We worked with Seif on the React Native app for our vehicle-appraisal platform. What stood out most was how much ownership he takes: he thinks a feature through, raises edge cases before they turn into bugs, and delivers something that actually works. And then there is one more thing why I wanted to work with Seif after our very first call: Exceptional clear and consistent communication. It is a pleasure to work with him and his team!
Michael EmaschowFounder, RepairCheckFree Strategy Call
30 minutes · Google Meet · Free
No packages, no sales pitch. You leave with a clear first step.
- 30 min
- Google Meet
- Calendly
- No commitment
- The plan is yours to keep
- Built for teams at Tabeebi, RepairCheck and MasterPilot
