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

Granite 4.2 30B vs LFM3-Omni-2B

Granite 4.2 30B and LFM3-Omni-2B score within a point of each other on agent readiness, 61 (C) and 61 (C). 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

Granite 4.2 30B C

Best for Agents that want a documented, signed, Apache 2.0 reasoning model with tool calling on a 24 GB card

Ahead on

  • Reach, 90 against 80
  • Risk, 55 against 40
  • Agent interface, 85 against 70
  • Documentation and upkeep, 87 against 49

Watch for

No safety results published for it

LFM3-Omni-2B C

Best for Voice and camera agents on a laptop or phone that want one small model for hearing, seeing, speaking and calling tools

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Only llama.cpp and Ollama run it in a release

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.

Documentation and upkeep Granite 4.2 30B +38

Granite 4.2 30B 87

Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (30B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 30B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 15, the last commit to the repository was on 4 September 2026, 67 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (28 August to 3 November 2026), 3 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 30B stays in its own repository and 4.2 came out in new ones. File health 10, Config, template and card agree on the architecture, the 131,072-token context and the thinking switch. 17 + 20 + 15 + 20 + 5 + 10 = 87.

LFM3-Omni-2B 49

Model card 14, Intended use (one on-device model in place of separate speech recognition, vision, language and speech models), architecture, parameters (2.17B), context (32K) and the text and speech languages. Training data 5, the card has no training section. Last change 20, the last commit, on 3 November 2026, changed the card's navigation icons, seven days before this check, and the one before it, on 28 October, documented video frame rate and frame limits. Responsiveness 0, none of the 12 discussions that aren't pull requests (27 October to 9 November 2026) has a reply from a LiquidAI member. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 5, the card gives a 32K context while config.json gives the language model 128,000 positions and Liquid's API lists 128,000 for the hosted model, so the card and the files don't agree on context. 14 + 5 + 20 + 0 + 5 + 5 = 49.

Risk Granite 4.2 30B +15

Granite 4.2 30B 55

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the ibm-granite organisation, which IBM's Granite docs and the GitHub README link to (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, and the card's licence link resolves. Security programme 5, www.ibm.com/.well-known/security.txt names IBM PSIRT, read for the 3B listing on 4 November 2026 (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.

LFM3-Omni-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 Granite 4.2 30B +15

Granite 4.2 30B 85

Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort. Tool-calling format 25, the card has tool-calling sections for vLLM and SGLang, declares tools with OpenAI's function schema and names the parser to use, qwen3_coder, which both runtimes ship in the released versions read. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so it renders several calls in one turn, and the card names tool calling and agentic workflows as what it's best for. Structured output 0, the card doesn't document JSON or JSON Schema output or how to ask for it. Reasoning control 10, the card documents thinking on by default, non-thinking and low-effort modes per request through the template (enable_thinking and low_effort), with the reasoning returned apart from the answer. Context 10, 131,072 tokens natively per the card and config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

LFM3-Omni-2B 70

Chat template 20, chat_template.jinja in the repository (13,513 characters), with roles, images, video and audio, tools, deferred tools and tool results. 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 documents tool calling from spoken or written requests. Structured output 0, the card doesn't mention JSON or structured output for this model. Reasoning control 0, the card says this is a non-reasoning model and that enable_thinking=True is not supported, so there is no thinking to turn off or budget. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 0 + 0 + 5 = 70.

Reach Granite 4.2 30B +10

Granite 4.2 30B 90

Memory 25, IBM's own 4-bit MLX build granite-4.2-30b-q4-mlx is 16.47 GB, and 16.47 GB × 1.2 = 19.8 GB, which fits 24 GB but not 16 GB. Its Q4_0 GGUF is 16.58 GB and Ollama's library build granite4.2:30b 18 GB, the same band. Runtimes 25, Released versions run the granite architecture in llama.cpp (granite, b12242), vLLM (GraniteForCausalLM in the v0.33.0 registry), SGLang (granite.py at v0.5.23), Transformers (v5.22.2) and Ollama (its own granite4.2 library entry, 30b tag). Builds 15, IBM publishes FP8, MXFP4 and NVFP4 safetensors builds, a GGUF repository with Q4_0 to Q8_0 and BF16 files, and 4-bit, 8-bit and BF16 MLX builds, so quantised builds at two precisions or more. Terms 15, Apache 2.0, an OSI-approved licence, with no use policy or other terms added on the card. Download 10, the Hub API reports gated false for the BF16, FP8, MXFP4, NVFP4, GGUF and MLX repositories, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps one inference provider (DeepInfra, live), short of the two the line needs. 25 + 25 + 15 + 15 + 10 + 0 = 90.

LFM3-Omni-2B 80

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.29 GB projector file, and 1.39 GB × 1.2 = 1.7 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 10, Released llama.cpp has the lfm3 architecture with the LFM3 vision and audio projectors and speech output (src/models/lfm3.cpp and tools/mtmd at b12242, with a realtime client example), and Ollama's library has an lfm3-omni entry. 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-omni-2b among its models, so the publisher hosts it. 30 + 10 + 15 + 10 + 10 + 5 = 80.

Score by category

CategoryWeight this runGranite 4.2 30BLFM3-Omni-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259080Granite 4.2 30B +10
Risk20%205540Granite 4.2 30B +15
Agent interface10%108570Granite 4.2 30B +15
Documentation and upkeep10%108749Granite 4.2 30B +38
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactGranite 4.2 30BLFM3-Omni-2B
KindOpen-weight modelOpen-weight model
VendorIBMLiquid 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.txtnoyes
Last release2026-09-042026-11-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked

Verdicts

Granite 4.2 30B

IBM's largest reasoning cousin, with the same strengths as the 3B. It runs in every runtime we count from IBM's own builds on a 24 GB card, is signed, plain Apache 2.0, and comes with a disclosure of its training data. No safety results are published and structured output isn't documented.

LFM3-Omni-2B

One 2.17B model that sees, listens and talks on an 8 GB machine and turns spoken requests into tool calls. Only llama.cpp and Ollama run it in a release. The context is 32K, it doesn't reason, Liquid hasn't answered a question on the repository, and there are no safety results or data sources.

Before you call either

Granite 4.2 30B

  1. Start it with ollama run granite4.2:30b, or llama-server -hf ibm-granite/granite-4.2-30b-GGUF:Q4_K_M --jinja
  2. With vLLM 0.32.0 or later leave out --reasoning-parser-plugin, since the parser is built in, and use --tool-call-parser qwen3_coder
  3. Thinking is on by default. Pass enable_thinking false to turn it off or low_effort true for short reasoning
  4. The context is 131,072 tokens. The card's 512K extension isn't documented
  5. Validate JSON output yourself, since structured output isn't documented
  6. IBM recommends Granite Guardian beside it to flag risky inputs and outputs

LFM3-Omni-2B

  1. Start it with llama-server -hf LiquidAI/LFM3-Omni-2B-GGUF:Q4_K_M --jinja or ollama run lfm3-omni
  2. Greedy decoding for text. For speech use audio_temperature 0.4 and audio_repetition_penalty 1.2, per the card
  3. The context is 32K, and llama.cpp samples video at 2 frames a second up to 384 frames
  4. Parse tool calls yourself from the XML it returns
  5. It doesn't reason, so don't pass enable_thinking
  6. Validate JSON output yourself

Questions

Which is better for AI agents, Granite 4.2 30B or LFM3-Omni-2B?

Granite 4.2 30B and LFM3-Omni-2B score within a point of each other on agent readiness, 61 (C) and 61 (C).

Other comparisons with Granite 4.2 30B or LFM3-Omni-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.