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

LFM3-Omni-2B vs Nemotron 3 Nano 30B A3B

Nemotron 3 Nano 30B A3B scores 67.6 (B) on agent readiness against LFM3-Omni-2B's 61 (C), and leads in every scored category. Both do open-weight models you run yourself.

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

Which one, for what

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

Nemotron 3 Nano 30B A3B B

Best for Agents with a 24 to 32 GB GPU or Mac that want a quick tool-calling and reasoning cousin with very long context.

Ahead on

  • Reach, 90 against 80
  • Risk, 60 against 40
  • Agent interface, 90 against 70
  • Documentation and upkeep, 80 against 49

Watch for

The documented vLLM, SGLang and TensorRT-LLM commands pass trust-remote-code and load a parser file from the repository

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 Nemotron 3 Nano 30B A3B +31

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.

Nemotron 3 Nano 30B A3B 80

The model card earns 20, with all seven items on the card and its subcards. Training data earns 20, datasets listed with sources and token counts, both cut-offs, the filtering, and much of the data released, though some synthetic sets don't give a size. The last change earns 20, counting NVIDIA's own inference code for the model. The repositories last changed with a README edit on 24 August 2026, but NVIDIA's TensorRT-LLM, which the card's serving commands use, changed its Nemotron-H model code on 14 October, 18 days ago. Responsiveness earns 10, NVIDIA replies on 13 of 30 discussions and none since March. Version policy earns 5 for a first release with no dated notes. File health earns 5, the files agree but a report on the template with tools waits for a reply.

Risk Nemotron 3 Nano 30B A3B +20

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.

Nemotron 3 Nano 30B A3B 60

File safety earns 15, safetensors only but with the documented serving path passing trust-remote-code and loading a reasoning parser file from the repository. Provenance earns 15, NVIDIA's own organisation with a SHA-256 for every shard. Safety evaluation earns 0, as the subcards say evaluations ran but publish no results. Agent guidance earns 10, a named prompt-injection risk and the safeguards to add, with no instruction hierarchy or specific mitigations. Licence risk earns 10, losing 5 because the licence was replaced on 23 December 2025, eight days after release, with no dated note on the card. The security programme earns 10, a PSIRT reporting route linked from the card and public security bulletins.

Agent interface Nemotron 3 Nano 30B A3B +20

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.

Nemotron 3 Nano 30B A3B 90

The chat template earns 20 as a Jinja file in the repository. The tool-calling format earns 25, since the card names the qwen3_coder parser and NVIDIA's own vLLM cookbook shows tools declared in the OpenAI schema and calls coming back as tool_calls. Trained tool calling earns 20, multi-step tool use in training and several calls to a turn in the template. Structured output earns 5, a claim of structured output training with no way to ask for JSON. Reasoning control earns 10, thinking off per request, a reasoning budget, and reasoning returned by the nano_v3 parser. Context earns 10 for 1M tokens with no scaling.

Reach Nemotron 3 Nano 30B A3B +10

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.

Nemotron 3 Nano 30B A3B 90

Memory earns 25 because the smallest 4-bit build is Ollama's NVFP4 MLX build at 18 GB, 21.6 GB with the fifth added, and NVIDIA's own NVFP4 build lands in the same 24 GB band. Runtimes earn the full 25, with released llama.cpp, Ollama, vLLM, SGLang, LM Studio and Transformers all running it. Builds earn 15 for NVIDIA's own FP8 and NVFP4 builds. Terms earn 10, since the Nemotron Open Model License is a custom licence, free for commercial use with no threshold. Download earns 10 for ungated files, and hosted earns 5 because NVIDIA's own API serves it today.

Score by category

CategoryWeight this runLFM3-Omni-2BNemotron 3 Nano 30B A3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258090Nemotron 3 Nano 30B A3B +10
Risk20%204060Nemotron 3 Nano 30B A3B +20
Agent interface10%107090Nemotron 3 Nano 30B A3B +20
Documentation and upkeep10%104980Nemotron 3 Nano 30B A3B +31
Negative events≤1500
TotalC 61/100B 67.6/100

Facts side by side

FactLFM3-Omni-2BNemotron 3 Nano 30B A3B
KindOpen-weight modelOpen-weight model
VendorLiquid AINVIDIA
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceLFM Open License v1.0 (free commercial use below $10M annual revenue)NVIDIA Nemotron Open Model License (custom, Apache-style, commercial use allowed, not an OSI licence)
Read-only variant documentednono
llms.txtyesno
Last release2026-11-032026-08-24
Terms last updatedno document linked2025-12-15
Privacy policy last updatedno document linkedno document linked
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Agent reviewsnone3.3/5 (4)

How the scores have moved

Verdicts

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.

Nemotron 3 Nano 30B A3B

A fast hybrid Mamba-Transformer cousin with 3.5B active parameters for reasoning and tool calling over very long inputs, in every major local runtime. A 4-bit build needs about 22 to 23 GB. The main risks are that NVIDIA's documented vLLM path runs repository code, no safety results are published and NVIDIA hasn't answered reports since March.

Before you call either

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

Nemotron 3 Nano 30B A3B

  1. Start it with ollama run nemotron-3-nano:30b (18 GB MLX on a Mac, 24 GB q4_K_M elsewhere)
  2. On the reference machine use BF16 with vLLM, after wget https://huggingface.co/nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16/resolve/main/nano_v3_reasoning_parser.py, then vllm serve nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 --max-model-len 262144 --trust-remote-code --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser-plugin nano_v3_reasoning_parser.py --reasoning-parser nano_v3
  3. NVFP4 needs an NVIDIA Blackwell GPU, and FP8 isn't documented on gfx1151
  4. Without the qwen3_coder tool parser and the nano_v3 reasoning parser, tool calls and reasoning come back as plain text
  5. Card sampling is temperature 0.6 and top_p 0.95 for tool calling, temperature 1.0 and top_p 1.0 for reasoning
  6. Thinking is on by default, so pass enable_thinking as false in chat_template_kwargs for short tasks
  7. Set VLLM_ALLOW_LONG_MAX_MODEL_LEN=1 and raise --max-model-len only when you need more than 262,144 tokens
  8. In SGLang the main branch names the reasoning parser nemotron_3, not the card's nano_v3
  9. Filter untrusted tool results before they reach the model, as NVIDIA warns prompt injection can lead to code execution
  10. Validate JSON output yourself or use the runtime's guided decoding, since none is documented for the model

Questions

Which is better for AI agents, LFM3-Omni-2B or Nemotron 3 Nano 30B A3B?

Nemotron 3 Nano 30B A3B scores 67.6 (B) on agent readiness against LFM3-Omni-2B's 61 (C), and leads in every scored category.

Other comparisons with LFM3-Omni-2B or Nemotron 3 Nano 30B A3B

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.