// head_to_head
Gemma 2 27B vs MiniMax M3
Published LiveBench scores across all seven categories, live list pricing, context windows, and the measured cost of a point of capability — for both models, side by side.
MiniMax M3 is the cheaper of the two; neither can be ranked on quality here.
Gemma 2 27B does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
minimax
MiniMax M3
- Blended / 1M
- $0.525
- Context
- 1.0M
- Released
- May 31, 2026
- Overall score
- 67.3
Specs and pricing
| Metric | Gemma 2 27B | MiniMax M3 |
|---|---|---|
| LiveBench overall Mean of the seven LiveBench category scores, 0–100. Higher is better. | — | 67.3 |
| Cost per point Measured benchmark spend divided by overall score — dollars per point of capability. | — | $0.0339 |
| Blended price / 1M 3:1 input:output mix, the usual shape of production traffic. | $0.650 | $0.525win |
| Input price / 1M | $0.650 | $0.300win |
| Output price / 1M | $0.650win | $1.20 |
| Cached input / 1M Price of an input token served from the prompt cache, where the provider publishes one. | — | $0.060 |
| Context window | 8K | 1.0Mwin |
| Max output tokens | 2K | 512Kwin |
Benchmarks by category
An overall score averages away the thing you probably care about. These are the seven LiveBench categories scored separately — Gemma 2 27B on top, MiniMax M3 below, both out of 100.
What each one costs to run
Per-token prices are hard to feel. These are monthly list costs for both models across five workload shapes, using each provider's published cached-input rate where there is one.
| Workload | Gemma 2 27B | MiniMax M3 |
|---|---|---|
| Support chatbot 1.2K in / 400 out × 200K requests | $208.00/mo | $150.72/mo |
| RAG assistant 8K in / 600 out × 100K requests | $559.00/mo | $216.00/mo |
| Coding agent 40K in / 4K out × 20K requests | $572.00/mo | $201.60/mo |
| Document extraction 20K in / 1.5K out × 50K requests | $698.75/mo | $378.00/mo |
| Bulk classification 500 in / 20 out × 5M requests | $1,690/mo | $750.00/mo |
Which should you pick?
You need to fit large documents in one call
MiniMax M3
Wider context window — 1.0M against 8K.
Gemma 2 27B vs MiniMax M3 FAQ
Which is better, Gemma 2 27B or MiniMax M3?
MiniMax M3 is the cheaper of the two; neither can be ranked on quality here. Gemma 2 27B does not have a published LiveBench run, so this comparison covers price, context and declared capabilities only. A missing score means "not evaluated", not "worse" — the right way to separate these two is an eval on your own workload.
Is Gemma 2 27B cheaper than MiniMax M3?
MiniMax M3 is cheaper. On a 3:1 input:output blend, Gemma 2 27B lists at $0.650 per million tokens and MiniMax M3 at $0.525 — MiniMax M3 is 24% cheaper. Input and output are priced separately — Gemma 2 27B charges $0.650 in and $0.650 out, MiniMax M3 charges $0.300 and $1.20 — so the model that looks cheaper flips depending on how output-heavy your workload is.
Does Gemma 2 27B or MiniMax M3 have a bigger context window?
MiniMax M3 has the larger context window: 8K for Gemma 2 27B against 1.0M for MiniMax M3. Note that a window you can fill is not a window you should fill — retrieval quality usually degrades well before the limit, and you pay for every token you put in it.
Do Gemma 2 27B and MiniMax M3 support prompt caching?
MiniMax M3 publishes a cached-input rate of $0.060 per million tokens against a full input rate of $0.300. The catalogue lists no separate cached rate for Gemma 2 27B, which means the provider does not price it separately here — not that caching is unavailable.
Related comparisons
How these numbers are produced
- Price — provider list price from OpenRouter, refreshed every 15 minutes. “Blended” is a 3:1 input:output mix.
- Scores — LiveBench release 2026-06-25, using their own category map. Each model shows its strongest published run. A blank means “not evaluated”, never “bad”.
- Cost per point — the measured dollars LiveBench spent on the run, divided by the score it earned.
- “Win” — awarded only past a threshold: one full point on a benchmark score, 10% on a price, 25% on a context window. Anything tighter reports as a tie, because effort settings alone move a LiveBench score by more than that.
Published benchmarks rank models on someone else's tasks. Before committing, see LLM & agent evaluation for building an eval on your own.