Google cuts Gemini 2.5 Pro pricing 40% — our budget long-context verdict flips
- What happened
- Google cut Gemini 2.5 Pro pricing 40% — same model, same 1M context, $0.75/M input.
- Why it matters
- Cost was the only thing keeping it conditional for budget long-context work; that gate just opened.
- What to do
- Re-run the chunking-vs-full-context math if you ruled out long-context passes on price.
Google dropped Gemini 2.5 Pro input pricing from $1.25 to $0.75 per million tokens this week, with output pricing down proportionally. Nothing else changed: same model, same 1M-token context window, same latency.
That's enough to flip our verdict. The capability was never the question — 2.5 Pro has handled our full-corpus document passes well since December. The blocker was cost: at the old price, processing a 50K-page archive was a budget line item; at the new price it's a rounding error next to the engineering time it saves.
If you previously ruled out long-context processing on cost and built chunked retrieval instead, it's worth re-running that math. Chunking still wins above the context ceiling and for high-frequency querying of the same corpus — but the crossover point just moved substantially.
A 40% input-price cut puts full-corpus passes within reach of mid-size budgets; our long-document pipeline cost dropped proportionally with no quality regression.
What to do
- 1 Re-price any long-document workload you previously chunked for cost reasons
- 2 Keep retrieval for corpora above the 1M-token ceiling or with high query frequency
Affected tools & models
Never need to catch up again
The weekly delta — only verdict changes and act-now items. No digest filler.