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

LFM3-VL-2B vs Nemotron 3 Ultra 550B A55B

Nemotron 3 Ultra 550B A55B scores 69.3 (B) on agent readiness against LFM3-VL-2B's 61 (C), and leads in 1 of 4 scored categories. LFM3-VL-2B leads on reach and documentation and upkeep. 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-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
  • Documentation and upkeep, 77 against 70

Watch for

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

Nemotron 3 Ultra 550B A55B B

Best for Agents with a multi-GPU Blackwell or Hopper node, or using a hosted endpoint, that want NVIDIA's strongest open model for long agent runs

Ahead on

  • Risk, 70 against 40

Watch for

The smallest build is 352 GB and needs at least four B200-class GPUs

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

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.

Nemotron 3 Ultra 550B A55B 55

Memory earns 0, because the smallest 4-bit build, NVIDIA's 352 GB NVFP4, needs about 423 GB with the fifth added, above the 256 GB band, and no runtime library has a local build. Runtimes earn 20 from released vLLM, SGLang, llama.cpp and Transformers, with Ollama's cloud-only entry not counted. Builds earn 10 for the single NVFP4 build. Terms earn 10, because OpenMDW-1.1 is permissive with no threshold or use policy but isn't an OSI licence. Download earns 10, with no gate or account. Hosted earns 5, since NVIDIA's own API serves it and two providers host it.

Risk Nemotron 3 Ultra 550B A55B +30

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.

Nemotron 3 Ultra 550B A55B 70

File safety earns 15, safetensors only but with 10 off because the documented commands pass trust-remote-code and the repository ships Python files. Provenance earns 15, files in NVIDIA's linked organisation with a hash for every file. Safety evaluation earns 0, since NVIDIA describes safety training but publishes no results. Agent guidance earns 15, as the technical report documents training the model to ignore instructions injected through tool output, beside the subcard's warnings and safeguards. Licence risk keeps all 15 under OpenMDW-1.1. The security programme earns 10 for the reporting route on the card and NVIDIA's public bulletins.

Documentation and upkeep LFM3-VL-2B +7

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.

Nemotron 3 Ultra 550B A55B 70

The model card earns 20, all seven items with limitations in the linked subcard. Training data earns 20, datasets listed with sources and token counts, cut-offs and filtering, and the corpora published. Last change earns 20, counting NVIDIA's own inference code for the model. The repositories last changed on 24 August, but NVIDIA's TensorRT-LLM, the runtime the card's own serving commands use, changed its Nemotron-H model code on 14 October, 18 days ago. Responsiveness earns 0, with no NVIDIA reply to any of nine questions. Version policy earns 5 as a first release. File health earns 5, since there is no LICENSE file, the BF16 card's SGLang command names a parser SGLang doesn't have, and tool-call reports wait without a reply.

Score by category

CategoryWeight this runLFM3-VL-2BNemotron 3 Ultra 550B A55BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258555LFM3-VL-2B +30
Risk20%204070Nemotron 3 Ultra 550B A55B +30
Agent interface10%109090even
Documentation and upkeep10%107770LFM3-VL-2B +7
Negative events≤1500
TotalC 61/100B 69.3/100

Facts side by side

FactLFM3-VL-2BNemotron 3 Ultra 550B A55B
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)OpenMDW-1.1
Read-only variant documentednono
llms.txtyesno
Last release2026-11-092026-06-04
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.8/5 (4)

How the scores have moved

Verdicts

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.

Nemotron 3 Ultra 550B A55B

NVIDIA's frontier-scale agent cousin with trained parallel tool calls, up to a 1M-token context and training against prompt injection through tool output. It needs at least four Blackwell GPUs for the 352 GB NVFP4 build, so most agents will use NVIDIA's API or a provider. The main risks are serving commands that run repository code and no published safety results.

Before you call either

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

Nemotron 3 Ultra 550B A55B

  1. It doesn't fit the 128 GB reference machine at any precision. Call NVIDIA's API (model nvidia/nemotron-3-ultra-550b-a55b) or a provider instead
  2. With vLLM serve the NVFP4 build with --trust-remote-code --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder on 4 × B200 or more
  3. With SGLang use --reasoning-parser nemotron_3, not the BF16 card's nemotron_v3, which SGLang doesn't register
  4. On SGLang with tools, pass chat_template_kwargs with enable_thinking true and force_nonempty_content true, as the card says, or reasoning and calls won't both parse
  5. Thinking is on by default. Pass enable_thinking: false for short tasks or medium_effort: true to cut reasoning tokens
  6. Use temperature=1.0 and top_p=0.95, as the generation config sets

Questions

Which is better for AI agents, LFM3-VL-2B or Nemotron 3 Ultra 550B A55B?

Nemotron 3 Ultra 550B A55B scores 69.3 (B) on agent readiness against LFM3-VL-2B's 61 (C), and leads in 1 of 4 scored categories. LFM3-VL-2B leads on reach and documentation and upkeep.

Other comparisons with LFM3-VL-2B or Nemotron 3 Ultra 550B A55B

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.