Head to head · Open-weight models you run yourself · October 2026 research run
LFM3-Omni-2B vs Qwen3.5-2B
LFM3-Omni-2B scores 61 (C) on agent readiness against Qwen3.5-2B's 50.5 (D), and leads in 2 of 4 scored categories. Qwen3.5-2B 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
Best for Voice and camera agents on a laptop or phone that want one small model for hearing, seeing, speaking and calling tools
Ahead on
- Agent interface, 70 against 60
- Documentation and upkeep, 49 against 37
Watch for
Only llama.cpp and Ollama run it in a release
Best for Builders who want a cheap local helper or fine-tuning base for narrow tasks and image reading on a laptop, small GPU or CPU
Ahead on
- Risk, 55 against 40
Watch for
No quantised build from Alibaba, and only one inference provider
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.
Risk Qwen3.5-2B +15
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.
Qwen3.5-2B 55
Safetensors only with no remote code gives file safety its 25, and files in the Qwen organisation the publisher's GitHub links to, each with a hash on the Hub, give provenance 15. The Apache 2.0 licence carries none of the deductions, so licence risk keeps 15. Safety evaluation, agent guidance and a security programme score 0, since the card has no safety results or agent cautions and no reporting route was found. The Qwen3.5 blog and Alibaba's security response centre couldn't be read, so those are scored as absent and left open. 25+15+0+0+15+0 = 55.
Documentation and upkeep LFM3-Omni-2B +12
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.
Qwen3.5-2B 37
The card covers six of the seven items, missing only a cut-off (17), because it states the intended uses and warns about thinking loops. Training data is a general description without a cut-off (5). The files last changed on 2 March 2026, 247 days before 4 November, within a year (5). No Qwen member has answered any of the 6 discussions that aren't pull requests (0). Qwen3-1.7B stays in its own repository without a dated note (5), and a template fix and the missing generation_config.json wait unanswered (5). 17+5+5+0+5+5 = 37.
Agent interface LFM3-Omni-2B +10
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.
Qwen3.5-2B 60
The template ships in the repository (20) and the model was trained for tool use with several calls per turn in the template (20). Tool-calling format gets 10, because the card names the qwen3_coder parser but leaves the format to the template. Reasoning control scores 0, since the card shows how to turn thinking on but not where the reasoning comes back. 262,144 tokens is native (10). Structured output scores 0, as nothing documents JSON output for the model. 20+10+20+0+0+10 = 60.
Score by category
| Category | Weight this run | LFM3-Omni-2B | Qwen3.5-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 80 | 80 | even |
| Risk | 20%20 | 40 | 55 | Qwen3.5-2B +15 |
| Agent interface | 10%10 | 70 | 60 | LFM3-Omni-2B +10 |
| Documentation and upkeep | 10%10 | 49 | 37 | LFM3-Omni-2B +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | D 50.5/100 |
Facts side by side
| Fact | LFM3-Omni-2B | Qwen3.5-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Liquid AI | Alibaba (Qwen team) |
| 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) | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-03 | 2026-03-02 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 3/5 (4) |
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.
Qwen3.5-2B
A small vision-language model for prototypes, fine-tuning and narrow local steps such as tool calls, tagging or reading an image. It runs in about 2 GB at 4 bits in six runtimes under plain Apache 2.0. Keep thinking off, since the card warns it loops. The card has no safety results, and Qwen has answered none of its discussions.
Before you call either
LFM3-Omni-2B
- Start it with
llama-server -hf LiquidAI/LFM3-Omni-2B-GGUF:Q4_K_M --jinjaorollama run lfm3-omni - Greedy decoding for text. For speech use audio_temperature 0.4 and audio_repetition_penalty 1.2, per the card
- The context is 32K, and llama.cpp samples video at 2 frames a second up to 384 frames
- Parse tool calls yourself from the XML it returns
- It doesn't reason, so don't pass enable_thinking
- Validate JSON output yourself
Qwen3.5-2B
- Smallest start is
ollama run qwen3.5:2b-q4_K_M(1.9 GB); plainqwen3.5:2bpulls the 2.7 GB Q8_0 build - Full precision
vllm serve Qwen/Qwen3.5-2B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder - Thinking is off by default; if you turn it on with
"chat_template_kwargs": {"enable_thinking": true}, stream and cut off runaway output, since the card warns of thinking loops, and add--reasoning-parser qwen3in vLLM or SGLang to split the reasoning out - There's no generation_config.json, so pass the card's sampling yourself, for example
temperature=1.0, top_p=1.0, top_k=20, presence_penalty=2.0for text without thinking - Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
- Validate any JSON it returns, since structured output isn't documented
Questions
Which is better for AI agents, LFM3-Omni-2B or Qwen3.5-2B?
LFM3-Omni-2B scores 61 (C) on agent readiness against Qwen3.5-2B's 50.5 (D), and leads in 2 of 4 scored categories. Qwen3.5-2B leads on risk.
Other comparisons with LFM3-Omni-2B or Qwen3.5-2B
- Agents-A1-4B vs LFM3-Omni-2B
- Agents-A1-4B vs Qwen3.5-2B
- Apertus v1.5 8B vs LFM3-Omni-2B
- Apertus v1.5 8B vs Qwen3.5-2B
- Apodex-1.1-mini vs LFM3-Omni-2B
- Apodex-1.1-mini vs Qwen3.5-2B
- Arete-27B vs LFM3-Omni-2B
- Arete-27B vs Qwen3.5-2B
- BigBang-v1 vs LFM3-Omni-2B
- BigBang-v1 vs Qwen3.5-2B
- Carbon-X vs LFM3-Omni-2B
- Carbon-X vs Qwen3.5-2B
- Cosmos-Reason2-2B vs LFM3-Omni-2B
- Cosmos-Reason2-2B vs Qwen3.5-2B
- Darwin-36B-Opus vs LFM3-Omni-2B
- Darwin-36B-Opus vs Qwen3.5-2B
- DeepSeek-V3.2 vs LFM3-Omni-2B
- DeepSeek-V3.2 vs Qwen3.5-2B
- DeepSeek V4.1 Flash vs LFM3-Omni-2B
- DeepSeek V4.1 Flash vs Qwen3.5-2B
- DeepSeek-V4-Flash-0731 vs LFM3-Omni-2B
- DeepSeek-V4-Flash-0731 vs Qwen3.5-2B
- DiffusionGemma 26B A4B IT vs LFM3-Omni-2B
- DiffusionGemma 26B A4B IT vs Qwen3.5-2B
- Gemma 4 12B IT vs LFM3-Omni-2B
- Gemma 4 12B IT vs Qwen3.5-2B
- Gemma 4 26B A4B IT vs LFM3-Omni-2B
- Gemma 4 26B A4B IT vs Qwen3.5-2B
- Gemma 4 31B IT vs LFM3-Omni-2B
- Gemma 4 31B IT vs Qwen3.5-2B
- Gemma 4 E2B IT vs LFM3-Omni-2B
- Gemma 4 E2B IT vs Qwen3.5-2B
- Gemma 4 E4B IT vs LFM3-Omni-2B
- Gemma 4 E4B IT vs Qwen3.5-2B
- GLM-4.5-Air vs LFM3-Omni-2B
- GLM-4.5-Air vs Qwen3.5-2B
- GLM-4.7-Flash vs LFM3-Omni-2B
- GLM-4.7-Flash vs Qwen3.5-2B
- GLM-5.3-Flash vs LFM3-Omni-2B
- GLM-5.3-Flash vs Qwen3.5-2B
- GLM-5.3 vs LFM3-Omni-2B
- GLM-5.3 vs Qwen3.5-2B
- gpt-oss-120b vs LFM3-Omni-2B
- gpt-oss-120b vs Qwen3.5-2B
- gpt-oss-20b vs LFM3-Omni-2B
- gpt-oss-20b vs Qwen3.5-2B
- Granite 4.2 30B vs LFM3-Omni-2B
- Granite 4.2 30B vs Qwen3.5-2B
- Granite 4.2 3B vs LFM3-Omni-2B
- Granite 4.2 3B vs Qwen3.5-2B
- Granite 4.2 8B vs LFM3-Omni-2B
- Granite 4.2 8B vs Qwen3.5-2B
- Hy-Memory-30B-A3B vs LFM3-Omni-2B
- Hy-Memory-30B-A3B vs Qwen3.5-2B
- Hy3 vs LFM3-Omni-2B
- Hy3 vs Qwen3.5-2B
- Inkling-Small vs LFM3-Omni-2B
- Inkling-Small vs Qwen3.5-2B
- Inkling vs LFM3-Omni-2B
- Inkling vs Qwen3.5-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-Omni-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Qwen3.5-2B
- Kimi K3.1 Pro vs LFM3-Omni-2B
- Kimi K3.1 Pro vs Qwen3.5-2B
- Kimi K3 vs LFM3-Omni-2B
- Kimi K3 vs Qwen3.5-2B
- Kolibri-1 vs LFM3-Omni-2B
- Kolibri-1 vs Qwen3.5-2B
- Kronos vs LFM3-Omni-2B
- Kronos vs Qwen3.5-2B
- Laguna M.1 vs LFM3-Omni-2B
- Laguna M.1 vs Qwen3.5-2B
- Laguna S 2.1 vs LFM3-Omni-2B
- Laguna S 2.1 vs Qwen3.5-2B
- Laguna XS 2.1 vs LFM3-Omni-2B
- Laguna XS 2.1 vs Qwen3.5-2B
- LBS-27B vs LFM3-Omni-2B
- LBS-27B vs Qwen3.5-2B
- LFM2.5-2.6B vs LFM3-Omni-2B
- LFM2.5-2.6B vs Qwen3.5-2B
- LFM3-1.7B vs LFM3-Omni-2B
- LFM3-1.7B vs Qwen3.5-2B
- LFM3-Audio-2B vs LFM3-Omni-2B
- LFM3-Audio-2B vs Qwen3.5-2B
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs Ling-3.0-tiny
- LFM3-Omni-2B vs Ling-3.1-flash-1019
- LFM3-Omni-2B vs MiMo-V2.6 Distill Qwen 9B
- LFM3-Omni-2B vs MiniCPM-o 4.5
- LFM3-Omni-2B vs MiniCPM-V 4.7 1B
- LFM3-Omni-2B vs MiniCPM-V 4.7 35B-A3B
- LFM3-Omni-2B vs MiniCPM5-2B
- LFM3-Omni-2B vs MiniMax-M2.5
- LFM3-Omni-2B vs MiniMax-M2.7
- LFM3-Omni-2B vs MiniMax-M3.1-Flash
- LFM3-Omni-2B vs Mistral Large 4
- LFM3-Omni-2B vs Muse Glimmer 30B
- LFM3-Omni-2B vs Nanbeige4.3-33B
- LFM3-Omni-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM3-Omni-2B vs Nemotron 3.5 Lightning 30B A3B
- LFM3-Omni-2B vs Nemotron 3 Nano 30B A3B
- LFM3-Omni-2B vs Nemotron 3 Nano 4B
- LFM3-Omni-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM3-Omni-2B vs Nemotron 3 Super 120B A12B
- LFM3-Omni-2B vs Nemotron 3 Ultra 550B A55B
- LFM3-Omni-2B vs occamy-1.0
- LFM3-Omni-2B vs Olmo 3 7B Think
- LFM3-Omni-2B vs Ornith-1.5-122B
- LFM3-Omni-2B vs Ornith-1.5-35B-A3B
- LFM3-Omni-2B vs Ornith-1.5-397B
- LFM3-Omni-2B vs Ornith-1.5-9B
- LFM3-Omni-2B vs Qwen-AgentWorld-35B-A3B
- LFM3-Omni-2B vs Qwen3-30B-A3B-Instruct-2507
- LFM3-Omni-2B vs Qwen3-4B-Instruct-2507
- LFM3-Omni-2B vs Qwen3.5-0.8B
- LFM3-Omni-2B vs Qwen3.5-122B-A10B
- LFM3-Omni-2B vs Qwen3.5-397B-A17B
- LFM3-Omni-2B vs Qwen3.5-4B
- LFM3-Omni-2B vs Qwen3.5-9B
- LFM3-Omni-2B vs Qwen3.6-27B
- LFM3-Omni-2B vs Qwen3.6-35B-A3B
- LFM3-Omni-2B vs Qwen3.8-27B
- LFM3-Omni-2B vs Qwen3.8-Flash-Next
- LFM3-Omni-2B vs Qwen3-Coder-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-Coder-Next
- LFM3-Omni-2B vs Qwen3-Omni-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-2B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-32B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-4B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-8B-Instruct
- LFM3-Omni-2B vs Qwopus3.8-27B-Flash-V2
- LFM3-Omni-2B vs Recursive Flint
- LFM3-Omni-2B vs Ripple-65B Preview
- LFM3-Omni-2B vs SmolLM3-3B
- LFM3-Omni-2B vs Spark-X2.6-4B
- LFM3-Omni-2B vs Swift 1.5 Qwen3.8-27B
- LFM3-Omni-2B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM3-Omni-2B vs ThinkingCap (Qwen3.8 27B)
- LFM3-Omni-2B vs Baidu Unlimited-OCR-2
- LFM3-VL-2B vs Qwen3.5-2B
- Ling-3.0-tiny vs Qwen3.5-2B
- Ling-3.1-flash-1019 vs Qwen3.5-2B
- MiMo-V2.6 Distill Qwen 9B vs Qwen3.5-2B
- MiniCPM-o 4.5 vs Qwen3.5-2B
- MiniCPM-V 4.7 1B vs Qwen3.5-2B
- MiniCPM-V 4.7 35B-A3B vs Qwen3.5-2B
- MiniCPM5-2B vs Qwen3.5-2B
- MiniMax-M2.5 vs Qwen3.5-2B
- MiniMax-M2.7 vs Qwen3.5-2B
- MiniMax-M3.1-Flash vs Qwen3.5-2B
- Mistral Large 4 vs Qwen3.5-2B
- Muse Glimmer 30B vs Qwen3.5-2B
- Nanbeige4.3-33B vs Qwen3.5-2B
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs Qwen3.5-2B
- Nemotron 3.5 Lightning 30B A3B vs Qwen3.5-2B
- Nemotron 3 Nano 30B A3B vs Qwen3.5-2B
- Nemotron 3 Nano 4B vs Qwen3.5-2B
- Nemotron 3 Nano Omni 30B A3B Reasoning vs Qwen3.5-2B
- Nemotron 3 Super 120B A12B vs Qwen3.5-2B
- Nemotron 3 Ultra 550B A55B vs Qwen3.5-2B
- occamy-1.0 vs Qwen3.5-2B
- Olmo 3 7B Think vs Qwen3.5-2B
- Ornith-1.5-122B vs Qwen3.5-2B
- Ornith-1.5-35B-A3B vs Qwen3.5-2B
- Ornith-1.5-397B vs Qwen3.5-2B
- Ornith-1.5-9B vs Qwen3.5-2B
- Qwen-AgentWorld-35B-A3B vs Qwen3.5-2B
- Qwen3-30B-A3B-Instruct-2507 vs Qwen3.5-2B
- Qwen3-4B-Instruct-2507 vs Qwen3.5-2B
- Qwen3.5-0.8B vs Qwen3.5-2B
- Qwen3.5-122B-A10B vs Qwen3.5-2B
- Qwen3.5-2B vs Qwen3.5-397B-A17B
- Qwen3.5-2B vs Qwen3.5-4B
- Qwen3.5-2B vs Qwen3.5-9B
- Qwen3.5-2B vs Qwen3.6-27B
- Qwen3.5-2B vs Qwen3.6-35B-A3B
- Qwen3.5-2B vs Qwen3.8-27B
- Qwen3.5-2B vs Qwen3.8-Flash-Next
- Qwen3.5-2B vs Qwen3-Coder-30B-A3B-Instruct
- Qwen3.5-2B vs Qwen3-Coder-Next
- Qwen3.5-2B vs Qwen3-Omni-30B-A3B-Instruct
- Qwen3.5-2B vs Qwen3-VL-2B-Instruct
- Qwen3.5-2B vs Qwen3-VL-30B-A3B-Instruct
- Qwen3.5-2B vs Qwen3-VL-32B-Instruct
- Qwen3.5-2B vs Qwen3-VL-4B-Instruct
- Qwen3.5-2B vs Qwen3-VL-8B-Instruct
- Qwen3.5-2B vs Qwopus3.8-27B-Flash-V2
- Qwen3.5-2B vs Recursive Flint
- Qwen3.5-2B vs Ripple-65B Preview
- Qwen3.5-2B vs SmolLM3-3B
- Qwen3.5-2B vs Spark-X2.6-4B
- Qwen3.5-2B vs Swift 1.5 Qwen3.8-27B
- Qwen3.5-2B vs Swift 1.5 Qwen3.8-Flash-Next
- Qwen3.5-2B vs ThinkingCap (Qwen3.8 27B)
- Qwen3.5-2B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/lfm3-omni-2b-vs-qwen3-5-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lfm3-omni-2b.json·/api/v1/tools/qwen3-5-2b.json - From a terminal
anchor compare lfm3-omni-2b qwen3-5-2b(the CLI) - Over MCP
compare_tools {"a": "lfm3-omni-2b", "b": "qwen3-5-2b"}at/mcp, no key