Alpha
Contact
Use · Gemma 4

Is it good enough?

Ownership levelSubstantialnone·limited·partial·substantial·fullAnalytical input C ยท 68.8/100

This page is a projection of the one entry record, the Reliability factor that Use covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor
  • AssessUse & modify + Transparency
  • ImplementData control + Reliability
  • UseReliability
  • SupportTransparency

Capabilities & modalities

Gemma 4 is a multimodal family that reads text and images (all sizes), video as frames, and audio (E2B, E4B and 12B only) and writes text (ev-card-31b). It has a configurable thinking mode, coding ability, native function calling and a native system role.

Audio is limited to 30 seconds and video to 60 seconds at one frame per second. Image detail is set with a visual token budget of 70, 140, 280, 560 or 1120: use low budgets for classification and video, high budgets for OCR and small text.

The sizes differ a lot. On the publisher's table the 31B scores 84.3 percent on GPQA Diamond and 2150 on Codeforces Elo, the E4B 58.6 percent and 940, and the E2B 43.4 percent and 633. The 26B A4B activates 3.8B parameters per token and is the fast choice, the 31B is the quality choice, and the 12B Unified takes audio without a separate encoder. Independent capability evidence is mixed (see Assess, evaluation item).

Context window & long-context behaviour

E2B and E4B support 128K tokens; the 12B, 26B A4B and 31B support 256K (ev-card-31b). The models interleave sliding-window attention (512 tokens for the small models, 1024 for the others) with global layers.

Long-context retrieval is publisher-reported and falls with size: on 8-needle 128K retrieval the 31B scores 66.4 percent, the 26B A4B 44.1, the 12B 43.4, the E4B 25.4 and the E2B 19.1. Do not assume a small model can use its full window; chunk and retrieve, and test your own documents. Memory for the KV cache grows with context (ev-docs-overview).

Prompt format & chat template

Gemma 4 uses standard system, user and assistant roles. Use the template (apply_chat_template) instead of hand-rolling role markers (ev-card-31b). The card sets these rules:

  • Switch thinking on by putting the <|think|> token at the start of the system prompt; remove it to switch thinking off. Thinking output is delimited as <|channel>thought ... <channel|> before the answer.
  • With thinking off, every size except E2B and E4B still emits an empty thought block.
  • Do not put earlier turns' thinking content back into history, except on tool-call turns.
  • Put image content before the text and audio content after the text.
  • Use temperature 1.0, top_p 0.95 and top_k 64.
  • Instruction-tuned models end a turn with <turn|>; base models end with <eos> (ev-tech-report).

The template in the repositories has had several fixes (tool-call loops, turn closure, null handling, reasoning preservation), so pin the revision under test (ev-hf-scan).

Language coverage

The card says Gemma 4 is pre-trained on more than 140 languages and supports 35 plus out of the box (ev-card-31b). The publisher reports MMMLU of 88.4 percent for the 31B, 86.3 for the 26B A4B, 83.4 for the 12B, 76.6 for the E4B and 67.4 for the E2B.

These are aggregate figures, and no per-language safety evaluation has been identified. Run your own for each target language, and expect the small models to be weakest.

Function / tool calling

Native function calling is documented in the model card as structured tool use for agentic workflows, and the chat template renders tool declarations and tool results (ev-card-31b). Ollama lists the tools capability for gemma4 (ev-ollama).

The publisher reports a Tau2 average over three of 76.9 percent for the 31B, 68.2 for the 26B A4B, 69.0 for the 12B, 42.2 for the E4B and 24.5 for the E2B. Keep thinking content on tool-call turns, and test tool-result rendering for images, since a repository discussion dated 18 November 2026 reports a template problem there (ev-hf-scan).

Structured / JSON-constrained output

The launch blog claims native structured JSON output (ev-blog), but the model card documents function calling and no JSON-schema mode (ev-card-31b), so coverage is partial. For guaranteed schemas, use constrained decoding at the serving layer (for example grammars in vLLM or llama.cpp) and validate outputs.

How this scores

The ownership factor this domain covers, drawn from the one entry record.

3

ReliabilityIs it reliable and good enough for the job?

Moderate

Operational readiness is good (score 4), but the safety evidence is publisher-only and qualitative (score 3) and no guard model has been identified, so the deployer supplies the safety layer (ev-tech-report, ev-docs-overview).

How this scores (AOI sub-dimensions)
Operational4/5how practical it is to run, serve and maintain in productionStandard safetensors on Transformers, with Google documenting official quantised routes for llama.cpp, vLLM and SGLang, drafter checkpoints for speculative decoding, a memory table per precision and 128K to 256K context.
Safety3/5whether misuse risks are evaluated and guardrails are providedInstruction-tuned checkpoints with a publisher safety evaluation and stated policies (child safety, dangerous content, sexually explicit content, hate speech, harassment), documented risks and mitigations, and a Responsible Generative AI Toolkit pointer.
What this means for adoptionUse of these weights is owned outright: plain Apache-2.0, no gate, no use policy and no remote shut-off, which the older Gemma Terms of Use did have. What the weights are is not owned: the training data is closed, Google states that user data from its products went into training, and safety evidence is publisher-only. Adopt the instruction-tuned checkpoints behind your own guardrails and check the licence per checkpoint, because Gemma 1 to 3n and the Gemma 3 derivatives you may already run remain under the old terms.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Licenceread2026-11-19
The Gemma 4 licence page (linked as license_link by every Gemma 4 model card) is the Apache License 2.0.
Documentationread2026-11-19
The Hugging Face API (anonymous) shows the google organisation as verified.
Model cardread2026-11-19
The Gemma 4 model card (README of google/gemma-4-31B-it, same text in the other cards, plus the gemma.ai model card page) lists five sizes: E2B, E4B, 12B Unified, 26B A4B and 31B.
Documentationread2026-11-19
The Gemma 4 overview page gives a memory table per precision for each size and routes official QAT checkpoints: q4_0 GGUF for llama.cpp and LM Studio, w4a16 compressed-tensors for vLLM and SGLang, mobile builds, unquantised QAT weights and matching -assistant drafters.
Technical_reportread2026-11-19
The Gemma 4 Technical Report (arXiv 2607.02770 v2, 24 Jul 2026) states that the models are released under Apache 2.0.
Documentationread2026-11-19
Google's EU AI Act Article 53(1)(d) Public Summary of Training Content for the Gemma 4 family is v1, last updated 31 July 2026, from provider Google Ireland Limited.
Terms of serviceread2026-11-19
The Gemma Terms of Use (last modified April 1, 2026) apply only to the models in their Appendix (Gemma 1, 1.1, 2, 3, 3n and siblings; Gemma 4 is not listed) and state 'For Gemma 4 terms, see the Gemma 4 license'.
Terms of serviceread2026-11-19
The Gemma Prohibited Use Policy (last modified February 21, 2024) lists restricted uses for 'Gemma or Model Derivatives' and is bound into a contract only through section 3.2 of the Gemma Terms of Use.
Vendor announcementread2026-11-19
The launch blog (2 April 2026) says Gemma 4 is 'released under a commercially permissive Apache 2.0 license'.
Third-party analysisread2026-11-19
Hugging Face platform data for google/gemma-4-31B-it shows scansDone true with no files with issues, safetensors BF16 parameters 31,273,088,876, an LFS sha256 for each weight shard and no signature files.
Third-party analysisread2026-11-19
The Decoder (2 April 2026) reports Gemma 4 shipping under Apache 2.0 'for the first time' and says earlier Gemma versions used a more restrictive Google proprietary licence.
Third-party analysisread2026-11-19
The Artificial Analysis page for Gemma 4 31B (Reasoning) gives an Intelligence Index v5.0.1 score of 4 and 'Intelligence #14 / 15', and describes the model as at the lower end among comparable open-weights models (median 10).
Third-party analysisread2026-11-19
The European Commission page on the General-Purpose AI Code of Practice (last update 7 October 2026) lists Google among the signatories; it does not say which chapters.
Third-party analysisread2026-11-19
Ollama library page for gemma4: tags e2b, e4b, 12b, 26b and 31b; capability tags vision, tools, thinking and audio; 29.5M downloads; run command 'ollama run gemma4'.
Documentationread2026-11-19
google-deepmind/gemma README and LICENSE: a JAX library to use and fine-tune Gemma with Gemma 4 checkpoint paths; code under Apache-2.0; the library is not the pre-training pipeline; issues go to the repository's GitHub tracker.
Securityread2026-11-19
Google's organisation-wide GitHub SECURITY.md says to report vulnerabilities at g.co/vulnz and that the Google Security Team processes a report within a day and responds within a week.
Third-party analysisunverified2026-11-19
The ADAPT Centre AI Accountability Lab evaluation of the Gemma 4 public training summary is referenced by a secondary blog.