Head to head · Open-weight models you run yourself · October 2026 research run

DiffusionGemma 26B A4B IT vs LFM3-VL-2B

LFM3-VL-2B scores 61 (C) on agent readiness against DiffusionGemma 26B A4B IT's 51.3 (D), and leads in 3 of 4 scored categories. DiffusionGemma 26B A4B IT leads on risk. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 4969 open weights comparisons

Which one, for what

DiffusionGemma 26B A4B IT D

Best for Agents with about 64 GB of GPU memory that want fast single-user generation from text and images and can accept lower quality than Gemma 4

Ahead on

  • Risk, 70 against 40

Watch for

No quantised build from Google, so the smallest official build needs the 64 GB band

LFM3-VL-2B C

Best for Agents on a laptop, phone or robot that need to read screens, documents, images and video from a model under 2 GB at 4 bits

Ahead on

  • Reach, 85 against 55
  • Agent interface, 90 against 70
  • Documentation and upkeep, 77 against 60

Watch for

vLLM and SGLang support is unreleased, which the card says itself

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reach LFM3-VL-2B +30

DiffusionGemma 26B A4B IT 55

Memory earns 15 because the only Google build is 51.7 GB of BF16, about 62 GB with the fifth added, which needs the 64 GB band. Runtimes get 15 for Transformers from 5.11.0, SGLang from v0.5.22 and vLLM, whose releases from v0.24.0 (tag commit 28 June 2026) to v0.33.0 register DiffusionGemmaForBlockDiffusion; llama.cpp (b12114, and Ollama through its pin b11963) and LM Studio don't run it. Builds score 0 because Google publishes no quantised build, though others have published FP8, NVFP4, GGUF and 4-bit copies. Apache 2.0 with nothing added gives terms the full 15 and the ungated repository gives download the full 10. Hosted too scores 0, since no inference provider is mapped and the Gemini API doesn't serve it.

LFM3-VL-2B 85

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.20 GB projector file, and 1.30 GB × 1.2 = 1.6 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 15, Released llama.cpp has the lfm3 architecture and the LFM3-VL projector (src/models/lfm3.cpp and tools/mtmd at b12242), Ollama's library has an lfm3-vl entry, and LM Studio's catalogue lists liquid/lfm3-vl-2b. Builds 15, Liquid's GGUF repository holds Q4_0, Q4_K_M, Q8_0, F16 and BF16 files, and Liquid publishes 4-bit and 8-bit MLX builds and an ONNX repository, all in the LiquidAI organisation. Terms 10, the LFM Open License v1.0, a custom licence that lets anyone use it commercially for free below a threshold of $10M annual revenue. Download 10, the Hub API reports gated false for the model and its GGUF, MLX and ONNX repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Liquid's own API lists lfm3-vl-2b among its models, so the publisher hosts it. 30 + 15 + 15 + 10 + 10 + 5 = 85.

Risk DiffusionGemma 26B A4B IT +30

DiffusionGemma 26B A4B IT 70

File safety gets the full 25, safetensors only and loaded by Transformers' own code and a Jinja template. Provenance gets 15 for files in Google's organisation with a hash for every file. Licence risk keeps 15 under plain Apache 2.0. Agent guidance gets 10 for the card's list of harm categories and its advice to add content-safety safeguards. Safety evaluation scores 0 because the card states improvements without figures. The security programme gets 5 for Google's security.txt, with no public advisories for Gemma.

LFM3-VL-2B 40

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, files in the LiquidAI organisation, which Liquid's docs page for the model and its blog post link to (10). Safety evaluation 0, no safety results on the card or in Liquid's blog post for the LFM3 family, neither of which mentions safety testing. Agent guidance 0, Nothing on prompt injection, an instruction hierarchy, what refusals cover or safeguards to add. Licence risk 10, 15 less 5 for the $10M annual revenue threshold on commercial use. Security programme 0, no way to report a flaw found. 15 + 15 + 0 + 0 + 10 + 0 = 40.

Agent interface LFM3-VL-2B +20

DiffusionGemma 26B A4B IT 70

The chat template is in the repository (20) and handles several tool calls in one turn, and the card names function calling as trained (20). The tool-calling format gets 10, since only the template and the shipped response schema say how tools work here and Google's tool-calling guide is for Gemma 4. Structured output scores 0, undocumented and rejected by SGLang. Thinking can be turned on or off per request with the reasoning in its own channel (10), and the context is 256K (10).

LFM3-VL-2B 90

Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, images and video, tools, deferred tools, tool results and the thinking switch. Tool-calling format 25, the card and Liquid's tool-use page document tools passed through tools= in apply_chat_template, calls returned as XML and results sent back as tool messages. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so several calls fit in one turn, and the card says its fine-tuning mix included tool calling and agentic traces. Structured output 5, the card's vLLM and SGLang commands set a structured-output backend and its fine-tuning table has a JSON extraction notebook, but nothing says how to ask this model for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, Liquid's chat-template page documents enable_thinking=False in apply_chat_template for LFM3, with reasoning on by default inside think tags, and the card documents preserve_thinking and reports a no-thinking configuration in its benchmarks. Context 10, 128K tokens of input and output per the card, and max_position_embeddings 128000 for the language model in config.json. 20 + 25 + 20 + 5 + 10 + 10 = 90.

Documentation and upkeep LFM3-VL-2B +17

DiffusionGemma 26B A4B IT 60

The card covers all seven points (20), and the training data is a general description with a January 2025 cut-off (10). The files last changed on 15 July 2026, 112 days before this check (10). Google organisation members answered 10 of the 20 discussions (10). It's a first release (5). File health gets 5 because the diffusers scheduler config disagrees with the card's sampling settings, though the files on the documented path agree.

LFM3-VL-2B 77

Model card 17, Intended use (questions about video, documents, charts and app screens, finding objects, spatial reasoning), a limitation (not recommended for coding, multi-turn conversations or complex reasoning), architecture (language model, 14-layer vision encoder and projector), parameters (1.92B), context (128K) and 16 languages. Training data 5, A general description: the base's 22T tokens of pre-training with the kinds of data added since LFM2, then vision mid-training on image and video data, supervised fine-tuning, vision reinforcement learning and distillation. Last change 20, the last commit, on 9 November 2026, added the OpenVINO checkpoint to the card's inference table, a day before this check. Responsiveness 20, Of the 5 discussions that aren't pull requests (27 to 31 October 2026), 3 have a reply from a LiquidAI member, which is most. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 10, Config, template and card agree on the lfm3_vl architecture, the 128,000-token context and the vision settings in processor_config.json. 17 + 5 + 20 + 20 + 5 + 10 = 77.

Score by category

CategoryWeight this runDiffusionGemma 26B A4B ITLFM3-VL-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255585LFM3-VL-2B +30
Risk20%207040DiffusionGemma 26B A4B IT +30
Agent interface10%107090LFM3-VL-2B +20
Documentation and upkeep10%106077LFM3-VL-2B +17
Negative events≤1500
TotalD 51.3/100C 61/100

Facts side by side

FactDiffusionGemma 26B A4B ITLFM3-VL-2B
KindOpen-weight modelOpen-weight model
VendorGoogle DeepMindLiquid AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0LFM Open License v1.0 (free commercial use below $10M annual revenue)
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-152026-11-09
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

DiffusionGemma 26B A4B IT

A text diffusion model for fast low-concurrency local generation from text, images and video, with optional thinking and Gemma 4's tool format, under Apache 2.0. Google's BF16 files need about 62 GB, and it runs in Transformers, SGLang and vLLM. Google's own figures put it below Gemma 4 26B A4B, and Google labels it experimental.

LFM3-VL-2B

A 1.92B vision model that reads images and video on an 8 GB machine, with a documented tool-call format and thinking. It runs today in llama.cpp, Ollama and LM Studio, while vLLM and SGLang support is still unreleased. Transformers needs repository code, and there are no safety results, security contact or data sources.

Before you call either

DiffusionGemma 26B A4B IT

  1. Serve it with sglang serve --model-path google/diffusiongemma-26B-A4B-it --dllm-algorithm Gemma4Renoise --trust-remote-code on SGLang v0.5.22 or later, then call /v1/chat/completions
  2. In Transformers, install transformers>=5.11.0 and load DiffusionGemmaForBlockDiffusion with dtype="auto"; generation_config.json already holds the recommended sampler
  3. Turn thinking on with enable_thinking=True in apply_chat_template or <|think|> at the start of the system prompt, read the reasoning between <|channel>thought and <channel|>, and drop it from history before the next turn
  4. Don't rely on temperature, top_p, logit_bias or JSON Schema in SGLang, which ignores or rejects them for this model; validate JSON yourself
  5. Streaming arrives one 256-token canvas at a time, not token by token
  6. Put images before text in the prompt, and pick an image token budget of 70 to 1,120 by how much detail the task needs

LFM3-VL-2B

  1. Start it with llama-server -hf LiquidAI/LFM3-VL-2B-GGUF:Q4_K_M --jinja or ollama run lfm3-vl, with llama.cpp b11960 or later
  2. Use temperature 0.1, top_k 50 and repetition penalty 1.1, per the card
  3. Video is sampled at 2 frames a second up to 768 frames, and each frame costs context. Video input in llama.cpp needs ffmpeg
  4. Don't plan on vLLM or SGLang until a release carries LFM3-VL
  5. Validate JSON output yourself
  6. Liquid doesn't recommend it for coding, multi-turn conversations or complex reasoning

Questions

Which is better for AI agents, DiffusionGemma 26B A4B IT or LFM3-VL-2B?

LFM3-VL-2B scores 61 (C) on agent readiness against DiffusionGemma 26B A4B IT's 51.3 (D), and leads in 3 of 4 scored categories. DiffusionGemma 26B A4B IT leads on risk.

Other comparisons with DiffusionGemma 26B A4B IT or LFM3-VL-2B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.