See exactly where a single prompt's cost comes from — system prompt, user prompt, and output — then project daily, monthly, and annual spend.
Enter your details and click Calculate to see results
The prompt cost estimator breaks a single AI prompt into the three pieces that actually drive its price — a fixed system prompt, a variable user prompt, and the model's generated output — instead of lumping everything into one blended input/output number. That itemized view instantly shows whether a bloated system prompt, an oversized user input, or a chatty model response is the real reason a feature costs more than expected, so you can fix the actual problem instead of guessing.
Paste a system prompt and a user prompt into two separate fields, set an expected output length and a model, and this prompt cost estimator computes four numbers: system prompt cost, user prompt cost, combined input cost, and output cost — then rolls the total cost per prompt into daily, monthly, and annual projections based on how many prompts you run per day. A doughnut chart shows the cost share of each of the three components at a glance, and a bar chart shows the daily/monthly/annual rollup.
Backend engineers deciding whether a verbose system prompt is worth its recurring cost, prompt engineers comparing two candidate prompt structures before shipping one, product managers estimating the per-seat cost of an AI feature, and finance or ops teams building an AI cost-of-goods-sold line item all benefit from seeing prompt cost broken into its components rather than as a single blended figure.
A single blended input/output cost number hides which part of your prompt is actually expensive. If output cost dominates, trimming response length is your highest-leverage lever; if system prompt cost dominates, enabling prompt caching or shortening fixed instructions helps far more than editing the user-facing prompt. This prompt cost estimator's itemized breakdown turns that guesswork into an actual measurement you can act on.
How this prompt cost estimator turns two prompt fields and an output length into an itemized dollar breakdown
Input Price and Output Price are the selected model's published dollars-per-million-token rates, shown directly in the model dropdown. Because the system prompt and user prompt are both billed at the same Input Price, the only reason their cost lines differ is token count — which is exactly what makes the itemized breakdown useful for spotting a bloated system prompt.
Fixed instructions, persona, and formatting rules, billed at input price on every single request. Because it repeats identically each call, it's the best candidate for prompt caching discounts where the provider offers them.
The variable part of the request — the actual question, document, or task — also billed at input price, but its length changes call to call, so its total cost scales with real usage patterns rather than being fixed.
The model's generated response, billed at the usually much higher output token price. Because this rate is 3-5x the input rate on most providers, output length is frequently the single biggest lever for reducing per-prompt cost.
From pasting your two prompts to reading the itemized cost breakdown
Paste your fixed instructions, persona, and formatting rules into the System Prompt field — this text is billed at the model's input price on every single call.
Paste a representative user request into the User Prompt field — this variable text is also billed at input price, but its length changes call to call.
Enter how many tokens the model typically generates in its response, since output tokens are billed at the model's usually higher output price.
Select from 14 models across OpenAI, Anthropic, Google, DeepSeek, and Mistral — each option shows its input/output price per million tokens in the dropdown.
Enter your expected daily prompt volume so the calculator can roll a single prompt's cost into daily, monthly, and annual projections.
See the itemized system/user/output cost breakdown, the cost-share doughnut chart, and the daily/monthly/annual bar chart.
Using the calculator's own default scenario — Claude Sonnet 4.6, a 197-character system prompt, a 148-character user prompt, 400 output tokens, 1,000 prompts/day
Suppose you're budgeting a customer-support reply feature on Claude Sonnet 4.6 ($3.00 / $15.00 per 1M input/output tokens), with a 197-character system prompt, a 148-character user prompt, an average of 400 output tokens per response, and 1,000 prompts per day.
Explanation: Even though the system prompt (50 tokens) and user prompt (37 tokens) are similar in size, output cost still makes up roughly 96% of the total per-prompt cost ($0.006 of $0.006261), because Claude Sonnet 4.6's output price is 5× its input price. The system and user prompt lines each round to "<$0.01" individually, but multiplied across 1,000 prompts/day they still contribute a combined $7.83 of the $187.83 monthly total — small relative to output cost, but not zero once caching or a system prompt rewrite is on the table.
What the system prompt's share of your total cost per prompt generally implies
| System Prompt Share of Total Cost | What It Generally Means | Recommended Next Step |
|---|---|---|
| Under 5% | System prompt is lean; cost is driven by user input and output | Focus optimization effort on output length or user prompt size instead |
| 5% – 15% | Normal range for most well-tuned production prompts | No urgent action; re-check as the system prompt grows over time |
| 15% – 30% | System prompt is a meaningful cost driver | Consider prompt caching or trimming redundant instructions |
| 30% – 50% | System prompt cost rivals or exceeds user input cost | Prompt caching likely saves a double-digit percentage of total spend |
| Over 50% | System prompt costs more than everything else combined | Audit for redundant or verbose instructions; caching is a high priority |
If output cost dominates your breakdown: that's typical, since output tokens are usually priced 3-5x higher than input tokens. The highest-leverage fix is usually capping or reducing response length — through a stricter system prompt instruction, a max-tokens setting, or a more structured output format — rather than trimming the prompt itself.
If system prompt cost is a large share: that's your signal to investigate prompt caching (which can cut the cached portion's cost by roughly 90% on supporting providers) or to simply shorten instructions, few-shot examples, or tool schemas that may have grown bloated over time.
These are cost estimates based on approximate token counts, not exact billing figures. Always reconcile projections against your provider's usage dashboard once the feature is live.
This calculator provides planning estimates only. Actual charges depend on your provider's live pricing, exact tokenizer, prompt caching status, and any negotiated or promotional rates on your account. Always verify against your provider's billing dashboard before finalizing a budget.
Where an itemized system/user/output breakdown genuinely helps
See at a glance whether the system prompt, user prompt, or output is the largest line item before optimizing.
Trim verbose instructions, rules, or formatting guidance once the system prompt's dollar cost is visible, not just its word count.
Run two candidate system or user prompt drafts through the same model and volume to compare their cost impact directly.
Check whether the system prompt cost share is large enough to justify the engineering effort of implementing provider-side caching.
Measure the exact cost impact of adding few-shot examples to a system prompt before deciding they're worth the quality gain.
Estimate cost when retrieved context is inserted into the system or user prompt ahead of the user's actual question.
Turn a per-prompt cost and expected usage into a per-seat or per-customer cost-of-goods-sold figure for pricing decisions.
Re-check an older, organically-grown system prompt to find redundant rules that no longer earn their token cost.
Hold your system and user prompt fixed and swap only the model to see how the cost-per-component mix shifts.
Use the output cost line to justify a max-tokens cap or a more structured, shorter response format.
See how much JSON tool and function schemas embedded in the system prompt add to cost on every single call.
Use the live breakdown and chart in a workshop or course to make prompt engineering cost tradeoffs concrete for students.
What this prompt cost estimator does well, and where it can't replace live billing data
Typical system/user/output cost share for common prompt structures, and the best lever for each
| Prompt Profile | System Share | User Share | Output Share | Best Cost Lever |
|---|---|---|---|---|
| System-prompt-heavy (long instructions, short Q&A) | ~40–60% | ~5–15% | ~30–50% | Prompt caching |
| User-prompt-heavy (RAG with long retrieved context) | ~5–10% | ~60–80% | ~15–30% | Trim retrieved context / chunk size |
| Output-heavy (long-form generation, code generation) | ~2–10% | ~5–15% | ~80–90% | Cap output length / structured output |
| Balanced chat assistant (short system, short turns) | ~10–20% | ~10–20% | ~60–75% | Output length control |
Summary: This prompt cost estimator gives you an instant, free, itemized breakdown of exactly where a single prompt's cost comes from — system prompt, user prompt, and output — so you can optimize the actual driver instead of guessing. Pair it with the LLM API Cost Calculator to pick the right model, and the Fine-tuning Cost Estimator if a fine-tuned smaller model could replace a costly system-prompt-heavy setup.
Common questions about prompt cost breakdowns
Official documentation to complement this calculator — always verify live rates before finalizing a budget
Explore other AI & tech tools