Source-tracked model comparison

Gemini 3.5 Live Translate Preview vs Gemini 2.5 Pro: which costs less for a practical API workload?

Compare verified pricing and model limits for routing within the Gemini 3.5 Live Translate family. The cost example uses a classification and routing workload and does not assume equal model quality.

Direct cost answer: Gemini 2.5 Pro is estimated at $837.50 per month and Gemini 3.5 Live Translate Preview at $147.50 for 700 input tokens, 80 output tokens, and 500,000 monthly requests. Gemini 3.5 Live Translate Preview is $690.00 lower under these assumptions. This does not identify a quality winner.
low priorityobserveSources checked 2026-07-12 / 2026-07-14
Tracked facts

Pricing and model limits

Prices are USD per 1M tokens under each model's verified default profile.

FieldGemini 2.5 ProGemini 3.5 Live Translate Preview
ProviderGoogleGoogle
API model IDgemini-2.5-progemini-3.5-live-translate-preview
Input / 1M$1.25$0.25
Cached input / 1M$0.125$0.025
Output / 1M$10.00$1.50
Context window1,048,576 tokens131,072 tokens
Maximum output65,536 tokens65,536 tokens
Accepted inputtext, image, video, audio, pdftext, image, audio
Example workload

Classification and routing cost scenario

700 input and 80 output tokens per request, 500,000 monthly requests, and 0% cached input.

Google

Gemini 2.5 Pro

$837.50 / month
Input cost
$437.50
Output cost
$400.00
Per 1,000 calls
$1.675
Pricing profile
standard / short context
View model details
Google

Gemini 3.5 Live Translate Preview

$147.50 / month
Input cost
$87.50
Output cost
$60.00
Per 1,000 calls
$0.295
Pricing profile
standard
View model details

Cost result: Gemini 3.5 Live Translate Preview is $690.00 lower per month for these assumptions. This is a price comparison, not a model-quality ranking.

StackLens assessment

Questions to answer before choosing

  • Which model meets the required quality threshold on representative inputs?
  • How do output length, retries, and caching change the measured cost?
  • Which provider and deployment path fit the team's operational requirements?
Workload caveat

What this estimate leaves out

Quality and latency are not assumed equal across models; validate labels on a representative evaluation set.

Latency, reliability, output quality, retries, regional processing, and provider-specific tool charges can change the practical decision.