Model comparison · accepted catalogue facts 2026-11-22

Gemma 2 27B vs Gemma 4 31B

Gemma 4 31B has an equal-or-higher measured score and an equal-or-lower estimated price. No known model-capability loss from Gemma 2 27B; endpoint and task checks still apply. The reported score intervals do not overlap; this is not a task-specific success guarantee.

Both models belong to the Google Gemma family. Inclusion does not recommend either model. This is a direct pair comparison; global frontier membership is not its verdict.

Gemma 2 27B

LMArena general · Elo · higher is better

Scale starts at 1040 Elo

1231.4

Balanced effective USD / 1M tokens · lower is better

$0.650/M

Gemma 4 31B

LMArena general · Elo · higher is better

Scale starts at 1040 Elo

1442.5

Balanced effective USD / 1M tokens · lower is better

$0.205/M

In-Depth Analysis

Gemma 2 27B vs Gemma 4 31B: Measured Technical Breakdown

Comprehensive comparison across measured human-preference evaluation, effective production token costs, architectural limits, and migration trade-offs.

Measured Capability (LMArena)
Gemma 4 31B leads by 211.1 Elo

Gemma 2 27B: 1231.4 ±3.38 · Gemma 4 31B: 1442.5 ±7.41 Statistically significant preference separation

Cost Comparison Across Canonical Production Workloads

Rates represent effective cost per 1M tokens under standard token blends. Cached prompt reads are factored according to workload context reuse.

Workload & RatioGemma 2 27BGemma 4 31BCost DifferenceAdvantage
Balanced 3 tokens in per 1 out$0.650 /1M tokens$0.205 /1M tokens$0.445 (68% diff)Gemma 4 31B costs less
Summarise Huge input, tiny output$0.650 /1M tokens$0.153 /1M tokens$0.497 (76% diff)Gemma 4 31B costs less
Chat Long cached system prompt$0.650 /1M tokens$0.244 /1M tokens$0.406 (62% diff)Gemma 4 31B costs less
Code gen Output dominates$0.650 /1M tokens$0.296 /1M tokens$0.354 (54% diff)Gemma 4 31B costs less
Agentic Context replayed each turn$0.650 /1M tokens$0.179 /1M tokens$0.471 (72% diff)Gemma 4 31B costs less

Architectural & Operational Specifications

SpecificationGemma 2 27BGemma 4 31BOperational Note
Context window8,192 tokens262,144 tokensGemma 4 31B has a 32.0× larger context window
Max output generation2,048 tokens16,384 tokensGemma 4 31B allows longer single-turn completions
Base input price$0.650 / 1M tokens$0.140 / 1M tokensGemma 4 31B input rate is cheaper
Base output price$0.650 / 1M tokens$0.400 / 1M tokensGemma 4 31B output rate is cheaper
Cached input priceNot listed / standard rate$0.140 / 1M tokens—
Reasoning & thinking tokensStandard generationSupported; standard rates—
Input modalitiestextimage, text, video—
Tool calling / function useNot listedSupportedGemma 4 31B declares function calling / tool support
Open weights & licenceProprietary (API-only)Open weights (apache-2.0)Gemma 4 31B allows independent hosting or local deployment
Provider & reseller marketGoogle · 1 provider offersGoogle · 18 provider offers (7.5× spread)—

When to Choose Gemma 2 27B

  • Direct integration with Google tooling and API features.
Risks when moving from Gemma 4 31B → Gemma 2 27B:
  • Context window: 262,144 → 8,192 tokens.
  • Output limit: 16,384 → 2,048 tokens.
  • Tool use is not supported by the candidate.
  • Reasoning is not supported by the candidate.
  • image input is not supported by the candidate.
  • video input is not supported by the candidate.

When to Choose Gemma 4 31B

  • Higher measured general capability (1442.5 Elo on human evaluation).
  • Larger context window (262,144 tokens) for long-document or repo-level context.
  • Higher maximum completion limit (16,384 tokens).
  • Open weights availability allows private self-hosting and on-premise execution.
  • Broader multimodal input support: image, text, video.
  • Direct integration with Google tooling and API features.

Compare · model decision

Choose two or three models

Inspect the differences, estimate your workload and keep the evidence. All standard catalogue models are available, including unrated ones.

Catalogue facts
2026-11-22

2 / 3 selected · 0 requirements
Open public comparison link
Public workload and requirements

These settings are included in the share link. The fixed-request scenario and private evaluation data below are excluded.

A ↔ B

Gemma 4 31B has an equal-or-higher measured score and an equal-or-lower estimated price. No known model-capability loss from Gemma 2 27B; endpoint and task checks still apply. The reported score intervals do not overlap; this is not a task-specific success guarantee.

Estimated blend: 75% input, 25% output; 0% cached input. Base context tier. Prompt length selects the billing tier. An unlisted cache-read rate uses that tier’s full input rate in this blend; missing required input or output rates prevent an estimate. The fixed-request estimate below validates actual context and output limits and requires a published cache-read rate when cache hits are assumed.

What changes between these models

Quality first, then estimated price. LMArena scores are human-preference measurements, not a benchmark of your application. A missing score is unrated.

  • Gemma 2 27B · Meets the stated model requirements
  • Gemma 4 31B · Meets the stated model requirements
Material differences and unknown evidence. Deltas compare each model with model A. Unknown facts remain visible.
Measured factA Gemma 2 27BB Gemma 4 31B
LMArena general score (Elo)1,231.41,442.5Δ vs A: +211.1 Elo
Score interval half-width (± Elo)3.387.41Δ vs A: +4.03 Elo
LMArena document score (Elo)Unknown1,434.3
Estimated effective USD / 1M tokens$0.65$0.205Δ vs A: -0.445 USD/M
Base input USD / 1M tokens$0.65$0.14Δ vs A: -0.51 USD/M
Base output USD / 1M tokens$0.65$0.4Δ vs A: -0.25 USD/M
Base cached-input USD / 1M tokensUnknown$0.14
Context window (tokens)8,192262,144Δ vs A: +253,952 tokens
Output limit (tokens)2,04816,384Δ vs A: +14,336 tokens
Input modalitiestextimage, text, video
Tool useNot supportedSupportedΔ vs A: +1
ReasoningNot supportedSupportedΔ vs A: +1
Open weightsUnknownSupported
Recorded licenceUnknownapache-2.0
Distinct sellers in the catalogue115Δ vs A: +14
Serving precision differs across offersNot supportedSupportedΔ vs A: +1
Recorded retirement dateUnknownUnknown
3 shared measured facts
Shared measured facts. Deltas compare each model with model A. Unknown facts remain visible.
Measured factA Gemma 2 27BB Gemma 4 31B
Benchmark reasoning effortdefaultdefault
Model providerGoogleGoogle
Retirement evidenceNone announced; not a guaranteeNone announced; not a guarantee

Provider counts and precision flags describe catalogue offers. They do not establish the precision, availability, region, tool behaviour or limits of your chosen endpoint. Open each model’s provider table before switching.

Complete price ladders and billing conditions

Gemma 2 27B

Rates below are USD per 1M tokens. A threshold selects that whole input/output rate pair.

Input-token thresholdInputOutputCached input
Base, up to and including first threshold$0.65$0.65Unknown

Gemma 4 31B

Rates below are USD per 1M tokens. A threshold selects that whole input/output rate pair.

Input-token thresholdInputOutputCached input
Base, up to and including first threshold$0.14$0.4$0.14
Migration preflight · compare each candidate with model A

Keeping Gemma 2 27B is a valid decision. No pairwise comparison certifies a drop-in replacement.

Gemma 2 27B → Gemma 4 31B

No known model-capability loss

  • Provider endpoint, serving precision, availability and task success need your own verification. Catalogue model capabilities do not certify an endpoint.
Check alternatives to Gemma 2 27B

Estimate a fixed request shape

Private to this tab unless you save locally or explicitly export private details. These are estimates, not observed invoices. Cross-model token counts and task success are assumptions.

0.1 extra attempts means 10 extra full attempts per 100 requests. Cache writes, tool charges, taxes and unlisted charges are excluded.

  • Gemma 2 27BEstimated total: $1.625 1,000 full attempts · base rates
  • Gemma 4 31BEstimated total: $0.48 1,000 full attempts · base rates
Prompt and output sensitivity · sampled scenarios

Every point recalculates the entire request shape. Tier-boundary samples include one token below, at and above each threshold. Ordering between samples is not guaranteed. Lowest known cost excludes unknown estimates and is not a replacement recommendation.

Vary input; hold output, requests, cache and retries fixed.
Input tokensGemma 2 27BGemma 4 31BCoverage
2,000$1.625$0.48Lowest knownAll computed
4,096$2.9874$0.77344Lowest knownAll computed
32,768ineligibleInput plus output exceeds the published context window.$4.78752Lowest knownIncomplete
131,072ineligibleInput plus output exceeds the published context window.$18.55008Lowest knownIncomplete
Vary output; hold input, requests, cache and retries fixed.
Output tokensGemma 2 27BGemma 4 31B
128$1.3832$0.3312
2,048$2.6312$1.0992
8,192ineligibleInput plus output exceeds the published context window.$3.5568

Bring your observed evaluation results

JSON is parsed locally. Prompts, filenames, individual responses and extra fields are not retained. Import only aggregate measurements for selected models. Task/version labels do not establish that two evaluations used the same dataset.

Expected format
[{"model":"provider/exact-model-id","task":"support-answer","version":"rubric-1","attempts":100,"successes":84,"costUsd":2.4,"latencyMs":950}]

Use the exact catalogue ID. Replace the example values with observed measurements. Omit costUsd or latencyMs when they are unknown. No public score is inferred from these observations.

Keep the decision and its evidence

A portable record retains selected facts, complete tier ladders, public requirements and the publication manifest. It also embeds the full permitted public catalogue to verify the input artifact checksum. Files are larger for this reason (up to 2 MB); local storage is limited to 12 records. Team review is local to this browser; there is no hosted collaboration.

Saving is opt-in and includes private review fields. Shared comparison links never include them. Version 1 Check references remain separate and are not overwritten or guessed into this format.

Saved local decisions · 0

No version 2 decision records are stored in this browser.

Questions this page answers

Is Gemma 2 27B a better-and-cheaper replacement for Gemma 4 31B?

Gemma 4 31B has an equal-or-higher measured score and an equal-or-lower estimated price. No known model-capability loss from Gemma 2 27B; endpoint and task checks still apply. The reported score intervals do not overlap; this is not a task-specific success guarantee.

Which model is higher rated: Gemma 2 27B or Gemma 4 31B?

Gemma 4 31B scores higher on LMArena general (1442.5 ±7.4) compared to Gemma 2 27B (1231.4 ±3.4), a margin of 211.1 Elo points. The measured confidence intervals do not overlap, demonstrating a statistically significant preference lead on human evaluations.

Which model is more cost-effective: Gemma 2 27B or Gemma 4 31B?

On a standard balanced workload (3 prompt tokens per 1 generated token), Gemma 4 31B costs $0.205 per 1M tokens versus $0.650 for Gemma 2 27B. Gemma 2 27B is approximately 3.2× the price of Gemma 4 31B. Base input rates are $0.650 for Gemma 2 27B and $0.140 for Gemma 4 31B; base output rates are $0.650 for Gemma 2 27B and $0.400 for Gemma 4 31B.

How do their context windows and generation limits compare?

Gemma 2 27B provides a 8,192-token context window with a maximum output limit of 2,048 tokens. Gemma 4 31B provides a 262,144-token context window with a maximum output of 16,384 tokens. Gemma 4 31B offers a 32.0× larger context capacity, making it suitable for larger repositories and multi-document workflows.

What capabilities are lost when switching between Gemma 2 27B and Gemma 4 31B?

Switching from Gemma 2 27B to Gemma 4 31B causes no detected architectural capability loss. Conversely, moving from Gemma 4 31B to Gemma 2 27B involves: Context window: 262,144 → 8,192 tokens; Output limit: 16,384 → 2,048 tokens; Tool use is not supported by the candidate; Reasoning is not supported by the candidate; image input is not supported by the candidate; video input is not supported by the candidate. Run test suites on your specific prompt templates and tool declarations before cutting over production traffic.

Can Gemma 2 27B or Gemma 4 31B be self-hosted or deployed privately?

Gemma 4 31B provides open weights, enabling self-hosting on private GPU infrastructure, local quantization, and private data pipelines. Managed inference is also offered across third-party API providers (1 for Gemma 2 27B, 18 for Gemma 4 31B).

What is included in this comparison?

Accepted model capabilities, context and output limits, complete price-tier ladders, independent LMArena measurements and missing evidence. Provider endpoint precision and application success still need verification.

Can I compare a different workload or keep a decision record?

Yes. Change the public workload, prompt length and requirements in the comparison workspace. Fixed-request scenarios, aggregate evaluations and review notes stay local unless explicitly exported.

Evidence & Ask