LLMCostLab

Prices → Gemini 2.5 Pro

Gemini 2.5 Pro API pricing

Gemini 2.5 Pro from Google is priced at $1.250 per 1M input tokens and $10.00 per 1M output tokens, with a 1M-token context window. Output costs 8.0x what input costs, which is the number that decides whether this model is expensive for you.

Verified 2026-08-19
advertisement
Input /1M
$1.250
Output /1M
$10.00
Blended /1M (3:1)
$3.438
Pricing shown for prompts up to 200k tokens; above that it is $2.50 in / $15.00 out.

What Gemini 2.5 Pro costs on real workloads

Monthly cost at each workload's default volume, shown with and without prompt caching. The right-hand column is what caching is worth on this specific model.

WorkloadCalls/moNo cacheWith cacheSaved
Customer support chatbot50,000$287.50$287.500%
RAG document Q&A20,000$320.00$320.000%
Coding agent4,000$245.00$245.000%
Bulk summarization100,000$1,900$1,9000%
Structured data extraction500,000$3,438$3,4380%
Long-form content generation10,000$425.00$425.000%
Email triage agent200,000$925.00$925.000%
Translation pipeline150,000$2,681$2,6810%

On caching

This model has no separately published cached-input rate on the provider's rate card, so every input token is priced at $1.250 per 1M regardless of repetition. On repetitive workloads that is a real disadvantage against models that discount cache reads by 90%.

advertisement

Closest alternatives by price

The six models nearest Gemini 2.5 Pro on blended rate — the realistic swap candidates.

ModelIn /1MOut /1MBlendedvs Gemini 2.5 Pro
Gemini 3.5 Flash$1.500$9.000$3.375-2%
Claude Sonnet 5$2.000$10.00$4.000+16%
Gemini 3.1 Pro$2.000$12.00$4.500+31%
GPT-5.6 Terra$1.000$6.000$2.250-35%
GPT-5.3 Codex$1.750$14.00$4.812+40%
Claude Haiku 4.5$1.000$5.000$2.000-42%

Price it against your own volume

Cost calculator

Enter your own numbers, or start from a workload preset. Costs are monthly and update as you type.

Cheapest model
Cheapest → priciest spread
ModelIn /1MOut /1MMonthlyvs best

Cutting this bill in practice

If a cheaper model on the table above would work for your task, the blocker is usually integration effort rather than the price difference.

Switch models without rewriting your integration

The savings on this page are only real if you can actually move traffic to the cheaper model. Aggregators and gateways sit in front of multiple providers so that switch is a configuration change.