Gemini 2.5 Pro vs Gemini 3.1 Pro: pricing & cost comparison
On input tokens, Gemini 2.5 Pro is the cheaper of the two — 38% less per million ($1.25 vs $2). On output, Gemini 2.5 Pro is 17% cheaper ($10 vs $12) — and since output is usually the dominant cost driver, that gap matters more than it looks.
Side by side
| Gemini 2.5 Pro | Gemini 3.1 Pro | |
|---|---|---|
| Input / 1M tokens | $1.25 | $2 |
| Output / 1M tokens | $10 | $12 |
| Context window | 1,000,000 | 1,000,000 |
| Token-count accuracy | ±3% | ±3% |
| Cost — 10,000 input + 2,000 output tokens | $0.0325 | $0.044 |
What a real request costs
Take a representative turn — 10,000 input + 2,000 output tokens. Gemini 2.5 Pro comes to $0.0325, Gemini 3.1 Pro to $0.044. Across 100,000 requests that's a $1150 swing in favour of Gemini 2.5 Pro. To run the numbers on your actual prompt, paste it into the calculator and toggle Compare across all models.
Same vendor — an easy switch
Moving between Gemini 2.5 Pro and Gemini 3.1 Pro is a same-vendor move — one SDK, one tokenizer, so no recalibration. That makes this a straight cost/quality call: send the routine bulk of traffic to Gemini 2.5 Pro ($1.25/$10 per 1M) and reserve Gemini 3.1 Pro for the requests that visibly need its extra headroom. On the worked example above that split is worth about 26% per request — small per call, real money once you multiply by volume.
See the full breakdown on the dedicated pages for Gemini 2.5 Pro and Gemini 3.1 Pro.
FAQ
- Is Gemini 2.5 Pro or Gemini 3.1 Pro cheaper?
- For a typical request (10,000 input + 2,000 output tokens), Gemini 2.5 Pro is cheaper — about 26% less, or roughly $1150 saved per 100,000 requests. Gemini 2.5 Pro runs $1.25/$10 per 1M input/output tokens; Gemini 3.1 Pro runs $2/$12.
- Which has the larger context window?
- Both support a 1,000,000-token context window.
- How accurate are these token counts?
- Gemini 2.5 Pro: Approximated with o200k_base; drift typically ~3% on English and code. Gemini 3.1 Pro: Approximated with o200k_base; drift typically ~3% on English and code. The dollar math itself is exact once the token count is known.
Both prices are computed from tokenmath's verified pricing table. Rates sourced from ai.google.dev and ai.google.dev, verified 2026-07-06. Vendor pricing changes often — confirm before you commit.