AI Tool Profile
DiffusionGemma: Architecture, Benchmarks, Pricing, and Evaluation
DiffusionGemma is an experimental Apache-2.0 open-weights model that generates text by iteratively denoising 256-token canvases in parallel and accepts text, image and video inputs.

Verification & Sources
- Evidence state
- Recheck due
- Source links
- 5
- Freshness
- Needs recheck: checked July 28, 2026
- Last updated
- August 26, 2026
What this evidence state means
- Definition
- The claim was previously checked, but its review window expired or a material change may have invalidated it.
- Required provenance
- The prior evidence and check date are retained, together with the expiry or change signal that triggered recheck.
- Owner
- Kingy freshness queue owner and assigned editorial reviewer
- Freshness rule
- This is already outside its freshness rule. It must not be presented as current until reviewed against current evidence.
- Disputes and corrections
- Use “Suggest a correction” on the record. Kingy editorial reviews the cited evidence, records material corrections, and changes or removes the state when it is not supported.
Key source checks
Suggest a correction
Kingy verdict: DiffusionGemma is a meaningful experiment in text generation architecture, not an automatic replacement for a strong autoregressive model. Its parallel 256-token denoising canvases can turn spare GPU compute into low-latency output, but Google’s own model card shows material quality trade-offs on many reasoning, coding, vision and long-context tests. Benchmark it on the exact hardware and tasks that matter before buying into the headline speed.
What is different
DiffusionGemma is an Apache-2.0 open-weights model from Google DeepMind. The model card describes a 25.2-billion-parameter mixture-of-experts architecture with 3.8 billion active parameters. Instead of committing to one next token at a time, the decoder starts with a block of placeholder tokens and refines the entire canvas over repeated denoising steps. Finished 256-token blocks are committed to the context cache before the next block begins.
That design changes where inference work happens. Google says the model is intended to shift generation away from a memory-bandwidth bottleneck and toward parallel compute. The developer guide reports throughput above 700 tokens per second on an RTX 5090 and above 1,000 on an H100 under specific configurations. Those are provider measurements, not Kingy replications, and the result will vary with quantization, sampler settings, prompt length, batch size, accelerator and serving stack.
Capabilities and evidence
The model accepts interleaved text, image and video inputs and returns text. Google documents up to a 256K-token context, thinking mode, function calling and an OpenAI-compatible local server through vLLM. The official model card also publishes a useful counterweight to the launch narrative: DiffusionGemma trails the related Gemma 4 model on many listed evaluations, including MMLU Pro, AIME, LiveCodeBench, GPQA Diamond, MMMU Pro and long-context retrieval. One HLE result is higher, but no single benchmark settles the product decision.
Safety results, training-data filtering and speed claims on the model card are first-party evidence. Kingy did not download the weights, reproduce the benchmark harness, inspect the training corpus or run red-team tests. Teams should treat the experimental label seriously, especially where a minor serving change, sampler choice or framework integration could move both latency and output quality.
Pricing and deployment
The weights are released under Apache 2.0, so there is no model license fee in the ordinary self-hosted path. That does not make inference free. GPU time, storage, networking, monitoring, safety controls and engineering work remain real costs. Google also points to Model Garden and NVIDIA NIM deployment routes, whose commercial terms depend on the selected provider and infrastructure.
How Kingy would evaluate it
Build a paired test against the autoregressive model already in use. Hold prompts, decoding goals and output limits constant; record time to first useful token, end-to-end latency, tokens per second, GPU memory, energy or instance cost, factual accuracy and human preference. Include short code generation, long-form constrained writing, tool calls, vision inputs and long-context retrieval. Repeat across easy and difficult prompts because adaptive stopping can make throughput task-dependent.
Inspect failure shape, not just averages. Parallel refinement may recover from local mistakes inside a canvas, while a committed block still constrains later generation. Verify streaming behavior, cancellation, batching, monitoring and deterministic replay in the intended serving stack. Keep the existing model as a fallback until quality and operations remain stable under production-like load.
Kingy reviewed the official guide, model documentation, model card, weight page and training recipe. We did not perform hands-on inference or independently validate performance, quality or safety claims.
Primary sources
- Google’s DiffusionGemma developer guide
- DiffusionGemma documentation
- Official model card and benchmark table
- Official Hugging Face weight page
- Google DeepMind training recipes
The Kingy Brief
Follow The Kingy Brief.
One consequential launch, one pricing, limit, or shutdown change, one hands-on test, one exact prompt or Test Pack, and one try / watch / skip verdict.
Free · Choose your subjects · Double opt-in · Unsubscribe anytime
Tool Links
Launch History
DiffusionGemma
Google DeepMind released DiffusionGemma, an experimental Apache-2.0 open-weights 25.2B mixture-of-experts model that generates text by iteratively denoising 256-token canvases in parallel.
- Launch readiness
- 8.3 / 10
- Demo evidence
- Not scored yet
- Creator-story fit
- Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.
- Scale
- 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
- Assigned by
- Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
- Rubric and check date
- Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-28.
- Confidence and missing data
- Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
- Freshness
- Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
- Disputes
- Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
DiffusionGemma is a credible architecture experiment for small-batch GPU generation, but Google’s own benchmark table shows substantial quality trade-offs against Gemma 4 on many…