Head to head · Open-weight models you run yourself · October 2026 research run
LFM2.5-2.6B vs LFM3-VL-2B
LFM3-VL-2B scores 61 (C) on agent readiness against LFM2.5-2.6B's 50.3 (D), and leads in 2 of 4 scored categories. LFM2.5-2.6B leads on reach and 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
Best for Agents that want a small local helper for tool calls, extraction and RAG on a laptop, phone or CPU, at organisations under the licence's revenue threshold
Ahead on
- Reach, 90 against 85
- Risk, 50 against 40
Watch for
Liquid lists it as deprecated, replaced by LFM3-1.7B; deprecated models stay downloadable but get no further updates
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
- Agent interface, 90 against 75
- Documentation and upkeep, 77 against 57
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.
Documentation and upkeep LFM3-VL-2B +20
LFM2.5-2.6B 57
The model card earns 17, with everything but a knowledge cut-off. Training data earns 5 for a general description without a cut-off. The last change earns 20, a card commit on 3 November 2026 naming LFM3-1.7B as the new version. Responsiveness earns 5, with Liquid replies in 2 of 16 discussions. Version policy earns 5, as Liquid now lists the model as deprecated with a replacement but no date. File health earns 5, since the files agree but a report about the card waits without a reply.
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.
Agent interface LFM3-VL-2B +15
LFM2.5-2.6B 75
The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 25, as Liquid's card and tool-use page say how tools go in and how calls come back, and its vLLM and SGLang pages name the lfm2 parser. Trained tool calling earns 20, with several calls in one Python list and agentic RL inside agent harnesses. Structured output earns nothing, as JSON output isn't documented for the model. Reasoning control earns nothing, since the model always thinks. Context earns 10 for 131,072 tokens trained.
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.
Risk LFM2.5-2.6B +10
LFM2.5-2.6B 50
File safety earns 25, safetensors and GGUF only, and nothing from the repository runs to load it or build prompts. Provenance earns 15, files in the LiquidAI organisation Liquid links to, with a checksum for every file. Safety evaluation and agent guidance earn nothing, since Liquid publishes neither. Licence risk earns 10, losing 5 for the revenue threshold, with no use policy and no change since release. The security programme earns nothing, since no security.txt, disclosure policy or security contact was found.
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.
Reach LFM2.5-2.6B +5
LFM2.5-2.6B 90
Memory earns the full 30, since Liquid's own 4-bit GGUF is 1.59 GB and fits 8 GB with room to spare. Runtimes earn 25, with the lfm2 architecture in released llama.cpp, vLLM, SGLang and Transformers, and in Ollama through the llama.cpp version it pins. Builds earn 15 for Liquid's own GGUF, MLX and ONNX builds at many precisions. Terms earn 10, a custom licence that is free for commercial use under $10M of annual revenue. Download earns 10, with no gate. Hosted earns nothing, as Hugging Face maps no inference provider and Liquid's docs list no hosted API for 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.
Score by category
| Category | Weight this run | LFM2.5-2.6B | LFM3-VL-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 90 | 85 | LFM2.5-2.6B +5 |
| Risk | 20%20 | 50 | 40 | LFM2.5-2.6B +10 |
| Agent interface | 10%10 | 75 | 90 | LFM3-VL-2B +15 |
| Documentation and upkeep | 10%10 | 57 | 77 | LFM3-VL-2B +20 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.3/100 | C 61/100 |
Facts side by side
| Fact | LFM2.5-2.6B | LFM3-VL-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Liquid AI | Liquid AI |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | LFM Open License v1.0 (free commercial use below $10M annual revenue) | LFM Open License v1.0 (free commercial use below $10M annual revenue) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-03 | 2026-11-09 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.5/5 (4) | none |
How the scores have moved
LFM3-VL-2B
No score change since it was listed.
Verdicts
LFM2.5-2.6B
A small, fast model for tool calls, extraction and long-context steps on a laptop or phone, which Liquid now lists as deprecated in favour of LFM3-1.7B. Liquid's own 4-bit build is 1.6 GB and five common runtimes run it. It always thinks, and organisations over $10M of revenue need another licence. There are no safety results or security contact.
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
LFM2.5-2.6B
- Quickest start is
ollama run LiquidAI/lfm2.5-2.6b, 1.7 GB, orllama-cli -hf LiquidAI/LFM2.5-2.6B-GGUF - With vLLM or SGLang pass
--tool-call-parser lfm2; for vLLM add--reasoning-parser qwen3so the thinking comes back separately - Sample at temperature 0.1, top_k 50 and repetition_penalty 1.1, as the card and generation_config.json set
- Put tools in the system prompt as
List of tools: [...]JSON, or pass tools to apply_chat_template; calls come back as a Python list of function calls, and the system prompt can ask for JSON calls instead - Leave max_tokens unset or generous, since a low cap cuts the reasoning off mid-thought
- Earlier thinking is dropped from the prompt unless
preserve_thinkingis true - Liquid's 328M LFM2.5-2.6B-DSpark drafter speeds decoding about 2.6 times in SGLang and on Apple silicon, per Liquid
- Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
LFM3-VL-2B
- Start it with
llama-server -hf LiquidAI/LFM3-VL-2B-GGUF:Q4_K_M --jinjaorollama run lfm3-vl, with llama.cpp b11960 or later - Use temperature 0.1, top_k 50 and repetition penalty 1.1, per the card
- Video is sampled at 2 frames a second up to 768 frames, and each frame costs context. Video input in llama.cpp needs ffmpeg
- Don't plan on vLLM or SGLang until a release carries LFM3-VL
- Validate JSON output yourself
- Liquid doesn't recommend it for coding, multi-turn conversations or complex reasoning
Questions
Which is better for AI agents, LFM2.5-2.6B or LFM3-VL-2B?
LFM3-VL-2B scores 61 (C) on agent readiness against LFM2.5-2.6B's 50.3 (D), and leads in 2 of 4 scored categories. LFM2.5-2.6B leads on reach and risk.
Other comparisons with LFM2.5-2.6B or LFM3-VL-2B
- Agents-A1-4B vs LFM2.5-2.6B
- Agents-A1-4B vs LFM3-VL-2B
- Apertus v1.5 8B vs LFM2.5-2.6B
- Apertus v1.5 8B vs LFM3-VL-2B
- Apodex-1.1-mini vs LFM2.5-2.6B
- Apodex-1.1-mini vs LFM3-VL-2B
- Arete-27B vs LFM2.5-2.6B
- Arete-27B vs LFM3-VL-2B
- BigBang-v1 vs LFM2.5-2.6B
- BigBang-v1 vs LFM3-VL-2B
- Carbon-X vs LFM2.5-2.6B
- Carbon-X vs LFM3-VL-2B
- Cosmos-Reason2-2B vs LFM2.5-2.6B
- Cosmos-Reason2-2B vs LFM3-VL-2B
- Darwin-36B-Opus vs LFM2.5-2.6B
- Darwin-36B-Opus vs LFM3-VL-2B
- DeepSeek-V3.2 vs LFM2.5-2.6B
- DeepSeek-V3.2 vs LFM3-VL-2B
- DeepSeek V4.1 Flash vs LFM2.5-2.6B
- DeepSeek V4.1 Flash vs LFM3-VL-2B
- DeepSeek-V4-Flash-0731 vs LFM2.5-2.6B
- DeepSeek-V4-Flash-0731 vs LFM3-VL-2B
- DiffusionGemma 26B A4B IT vs LFM2.5-2.6B
- DiffusionGemma 26B A4B IT vs LFM3-VL-2B
- Gemma 4 12B IT vs LFM2.5-2.6B
- Gemma 4 12B IT vs LFM3-VL-2B
- Gemma 4 26B A4B IT vs LFM2.5-2.6B
- Gemma 4 26B A4B IT vs LFM3-VL-2B
- Gemma 4 31B IT vs LFM2.5-2.6B
- Gemma 4 31B IT vs LFM3-VL-2B
- Gemma 4 E2B IT vs LFM2.5-2.6B
- Gemma 4 E2B IT vs LFM3-VL-2B
- Gemma 4 E4B IT vs LFM2.5-2.6B
- Gemma 4 E4B IT vs LFM3-VL-2B
- GLM-4.5-Air vs LFM2.5-2.6B
- GLM-4.5-Air vs LFM3-VL-2B
- GLM-4.7-Flash vs LFM2.5-2.6B
- GLM-4.7-Flash vs LFM3-VL-2B
- GLM-5.3-Flash vs LFM2.5-2.6B
- GLM-5.3-Flash vs LFM3-VL-2B
- GLM-5.3 vs LFM2.5-2.6B
- GLM-5.3 vs LFM3-VL-2B
- gpt-oss-120b vs LFM2.5-2.6B
- gpt-oss-120b vs LFM3-VL-2B
- gpt-oss-20b vs LFM2.5-2.6B
- gpt-oss-20b vs LFM3-VL-2B
- Granite 4.2 30B vs LFM2.5-2.6B
- Granite 4.2 30B vs LFM3-VL-2B
- Granite 4.2 3B vs LFM2.5-2.6B
- Granite 4.2 3B vs LFM3-VL-2B
- Granite 4.2 8B vs LFM2.5-2.6B
- Granite 4.2 8B vs LFM3-VL-2B
- Hy-Memory-30B-A3B vs LFM2.5-2.6B
- Hy-Memory-30B-A3B vs LFM3-VL-2B
- Hy3 vs LFM2.5-2.6B
- Hy3 vs LFM3-VL-2B
- Inkling-Small vs LFM2.5-2.6B
- Inkling-Small vs LFM3-VL-2B
- Inkling vs LFM2.5-2.6B
- Inkling vs LFM3-VL-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM2.5-2.6B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-VL-2B
- Kimi K3.1 Pro vs LFM2.5-2.6B
- Kimi K3.1 Pro vs LFM3-VL-2B
- Kimi K3 vs LFM2.5-2.6B
- Kimi K3 vs LFM3-VL-2B
- Kolibri-1 vs LFM2.5-2.6B
- Kolibri-1 vs LFM3-VL-2B
- Kronos vs LFM2.5-2.6B
- Kronos vs LFM3-VL-2B
- Laguna M.1 vs LFM2.5-2.6B
- Laguna M.1 vs LFM3-VL-2B
- Laguna S 2.1 vs LFM2.5-2.6B
- Laguna S 2.1 vs LFM3-VL-2B
- Laguna XS 2.1 vs LFM2.5-2.6B
- Laguna XS 2.1 vs LFM3-VL-2B
- LBS-27B vs LFM2.5-2.6B
- LBS-27B vs LFM3-VL-2B
- LFM2.5-2.6B vs LFM3-1.7B
- LFM2.5-2.6B vs LFM3-Audio-2B
- LFM2.5-2.6B vs LFM3-Omni-2B
- LFM2.5-2.6B vs Ling-3.0-tiny
- LFM2.5-2.6B vs Ling-3.1-flash-1019
- LFM2.5-2.6B vs MiMo-V2.6 Distill Qwen 9B
- LFM2.5-2.6B vs MiniCPM-o 4.5
- LFM2.5-2.6B vs MiniCPM-V 4.7 1B
- LFM2.5-2.6B vs MiniCPM-V 4.7 35B-A3B
- LFM2.5-2.6B vs MiniCPM5-2B
- LFM2.5-2.6B vs MiniMax-M2.5
- LFM2.5-2.6B vs MiniMax-M2.7
- LFM2.5-2.6B vs MiniMax-M3.1-Flash
- LFM2.5-2.6B vs Mistral Large 4
- LFM2.5-2.6B vs Muse Glimmer 30B
- LFM2.5-2.6B vs Nanbeige4.3-33B
- LFM2.5-2.6B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM2.5-2.6B vs Nemotron 3.5 Lightning 30B A3B
- LFM2.5-2.6B vs Nemotron 3 Nano 30B A3B
- LFM2.5-2.6B vs Nemotron 3 Nano 4B
- LFM2.5-2.6B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM2.5-2.6B vs Nemotron 3 Super 120B A12B
- LFM2.5-2.6B vs Nemotron 3 Ultra 550B A55B
- LFM2.5-2.6B vs occamy-1.0
- LFM2.5-2.6B vs Olmo 3 7B Think
- LFM2.5-2.6B vs Ornith-1.5-122B
- LFM2.5-2.6B vs Ornith-1.5-35B-A3B
- LFM2.5-2.6B vs Ornith-1.5-397B
- LFM2.5-2.6B vs Ornith-1.5-9B
- LFM2.5-2.6B vs Qwen-AgentWorld-35B-A3B
- LFM2.5-2.6B vs Qwen3-30B-A3B-Instruct-2507
- LFM2.5-2.6B vs Qwen3-4B-Instruct-2507
- LFM2.5-2.6B vs Qwen3.5-0.8B
- LFM2.5-2.6B vs Qwen3.5-122B-A10B
- LFM2.5-2.6B vs Qwen3.5-2B
- LFM2.5-2.6B vs Qwen3.5-397B-A17B
- LFM2.5-2.6B vs Qwen3.5-4B
- LFM2.5-2.6B vs Qwen3.5-9B
- LFM2.5-2.6B vs Qwen3.6-27B
- LFM2.5-2.6B vs Qwen3.6-35B-A3B
- LFM2.5-2.6B vs Qwen3.8-27B
- LFM2.5-2.6B vs Qwen3.8-Flash-Next
- LFM2.5-2.6B vs Qwen3-Coder-30B-A3B-Instruct
- LFM2.5-2.6B vs Qwen3-Coder-Next
- LFM2.5-2.6B vs Qwen3-Omni-30B-A3B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-2B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-30B-A3B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-32B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-4B-Instruct
- LFM2.5-2.6B vs Qwen3-VL-8B-Instruct
- LFM2.5-2.6B vs Qwopus3.8-27B-Flash-V2
- LFM2.5-2.6B vs Recursive Flint
- LFM2.5-2.6B vs Ripple-65B Preview
- LFM2.5-2.6B vs SmolLM3-3B
- LFM2.5-2.6B vs Spark-X2.6-4B
- LFM2.5-2.6B vs Swift 1.5 Qwen3.8-27B
- LFM2.5-2.6B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM2.5-2.6B vs ThinkingCap (Qwen3.8 27B)
- LFM2.5-2.6B vs Baidu Unlimited-OCR-2
- LFM3-1.7B vs LFM3-VL-2B
- LFM3-Audio-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-VL-2B vs Ling-3.0-tiny
- LFM3-VL-2B vs Ling-3.1-flash-1019
- LFM3-VL-2B vs MiMo-V2.6 Distill Qwen 9B
- LFM3-VL-2B vs MiniCPM-o 4.5
- LFM3-VL-2B vs MiniCPM-V 4.7 1B
- LFM3-VL-2B vs MiniCPM-V 4.7 35B-A3B
- LFM3-VL-2B vs MiniCPM5-2B
- LFM3-VL-2B vs MiniMax-M2.5
- LFM3-VL-2B vs MiniMax-M2.7
- LFM3-VL-2B vs MiniMax-M3.1-Flash
- LFM3-VL-2B vs Mistral Large 4
- LFM3-VL-2B vs Muse Glimmer 30B
- LFM3-VL-2B vs Nanbeige4.3-33B
- LFM3-VL-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM3-VL-2B vs Nemotron 3.5 Lightning 30B A3B
- LFM3-VL-2B vs Nemotron 3 Nano 30B A3B
- LFM3-VL-2B vs Nemotron 3 Nano 4B
- LFM3-VL-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM3-VL-2B vs Nemotron 3 Super 120B A12B
- LFM3-VL-2B vs Nemotron 3 Ultra 550B A55B
- LFM3-VL-2B vs occamy-1.0
- LFM3-VL-2B vs Olmo 3 7B Think
- LFM3-VL-2B vs Ornith-1.5-122B
- LFM3-VL-2B vs Ornith-1.5-35B-A3B
- LFM3-VL-2B vs Ornith-1.5-397B
- LFM3-VL-2B vs Ornith-1.5-9B
- LFM3-VL-2B vs Qwen-AgentWorld-35B-A3B
- LFM3-VL-2B vs Qwen3-30B-A3B-Instruct-2507
- LFM3-VL-2B vs Qwen3-4B-Instruct-2507
- LFM3-VL-2B vs Qwen3.5-0.8B
- LFM3-VL-2B vs Qwen3.5-122B-A10B
- LFM3-VL-2B vs Qwen3.5-2B
- LFM3-VL-2B vs Qwen3.5-397B-A17B
- LFM3-VL-2B vs Qwen3.5-4B
- LFM3-VL-2B vs Qwen3.5-9B
- LFM3-VL-2B vs Qwen3.6-27B
- LFM3-VL-2B vs Qwen3.6-35B-A3B
- LFM3-VL-2B vs Qwen3.8-27B
- LFM3-VL-2B vs Qwen3.8-Flash-Next
- LFM3-VL-2B vs Qwen3-Coder-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-Coder-Next
- LFM3-VL-2B vs Qwen3-Omni-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-VL-2B-Instruct
- LFM3-VL-2B vs Qwen3-VL-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-VL-32B-Instruct
- LFM3-VL-2B vs Qwen3-VL-4B-Instruct
- LFM3-VL-2B vs Qwen3-VL-8B-Instruct
- LFM3-VL-2B vs Qwopus3.8-27B-Flash-V2
- LFM3-VL-2B vs Recursive Flint
- LFM3-VL-2B vs Ripple-65B Preview
- LFM3-VL-2B vs SmolLM3-3B
- LFM3-VL-2B vs Spark-X2.6-4B
- LFM3-VL-2B vs Swift 1.5 Qwen3.8-27B
- LFM3-VL-2B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM3-VL-2B vs ThinkingCap (Qwen3.8 27B)
- LFM3-VL-2B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/lfm2-5-2-6b-vs-lfm3-vl-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lfm2-5-2-6b.json·/api/v1/tools/lfm3-vl-2b.json - From a terminal
anchor compare lfm2-5-2-6b lfm3-vl-2b(the CLI) - Over MCP
compare_tools {"a": "lfm2-5-2-6b", "b": "lfm3-vl-2b"}at/mcp, no key