Gemini 3.6 Flash vs Gemini 3.5 Flash: cost compared

Last verified

Gemini 3.5 Flash is 0% cheaper on input and -20% cheaper on output than Gemini 3.6 Flash. Whether that makes it the right choice depends entirely on whether it does your task well enough — this page gives you the cost side of that trade, precisely.

Rates side by side

$ per million tokensGemini 3.6 FlashGemini 3.5 Flash
Input$1.50$1.50
Output$7.50$9.00
Cached input$0.15$0.15
Output : input ratio5.0×6.0×

What the difference is worth

Monthly cost for the same workload on each, without caching:

WorkloadGemini 3.6 FlashGemini 3.5 FlashDifference
Support chatbot
1,000 conversations/month · 2,000 in + 500 out each
$6.75$7.50$-0.7500 saved
RAG search
10,000 queries/month · 8,000 in + 400 out each
$150$156$-6.0000 saved
Bulk extraction
10,000 documents · 3,000 in + 300 out each
$67.50$72.00$-4.5000 saved
Coding agent
100 runs/month · 400,000 in + 20,000 out each
$75.00$78.00$-3.0000 saved

Which to use

Gemini 3.5 Flash if the task is well-specified and mechanical — extraction, classification, formatting, routine transformation. The saving is real and compounds with volume.

Gemini 3.6 Flash if the task involves genuine reasoning, long-horizon planning, or work where a wrong answer is expensive to catch. Paying 1.0× more on input is trivial compared to the cost of shipping a bad result.

Both are Google models, so switching is usually a one-line change and the tokenizer is the same — which makes this a genuinely easy experiment to run. Test on your own workload before deciding.

Don't skip caching

Cached input costs $0.15 on Gemini 3.6 Flash and $0.15 on Gemini 3.5 Flash. If your prompts share a stable prefix, caching on the more expensive model can beat switching to the cheaper one outright — worth checking before you migrate anything.

Sources

Google rates verified 2026-08-05 (source). Google rates verified 2026-08-05 (source).