LFM3-Audio-2B vs Qwen3-VL-2B-Instruct

LFM3-Audio-2B 85

Chat template 20, chat_template.jinja in the repository (9,328 characters), with roles, 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 names turning spoken requests into tool calls as one of its four uses. Structured output 5, the card says the model is designed for structured outputs without saying how to ask for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, the card documents reasoning per request for text replies: the caller prefills the assistant turn with an open think tag to let the model reason, or a closed one for a direct answer, with a use_thinking example. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 5 + 10 + 5 = 85.

Qwen3-VL-2B-Instruct 60

A Jinja chat template in the repository (20). The tool-call format lives only in the template, Hermes-style JSON in tool_call tags, and Alibaba names no parser (10). Trained for function calling with several calls allowed in a turn, per the family's technical report (20). No documented structured output (0). No thinking mode in this edition, so reasoning control scores 0 by the rule. 262,144 tokens of native context (10).

LFM3-Audio-2B 52

Model card 17, Intended use (local agents, tool calling, structured outputs, fine-tuning), limitations (not recommended for agentic coding or complex multi-step reasoning, voice chat in English only), an architecture section, parameters (2B), context (32K) and 19 speech languages and locales. 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 31 October, edited the card. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (27 and 31 October 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. 17 + 5 + 20 + 0 + 5 + 5 = 52.

Qwen3-VL-2B-Instruct 31

The card misses limitations, languages and a cut-off (11). Training data is described only in the technical report, with no cut-off (5). The last change to code that runs it was the qwen-vl-utils fix of 4 January 2026, and the weights and cards haven't changed since November 2025 (5). Qwen answered none of the 13 Hugging Face discussions that aren't pull requests (0), and GitHub issues weren't counted. Earlier versions kept in their own repositories without notes (5). A report waits without a reply and the GGUF card's example names a file the repository doesn't hold (5). 11 + 5 + 5 + 0 + 5 + 5 = 31.

LFM3-Audio-2B 80

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

Qwen3-VL-2B-Instruct 95

Alibaba's own Q4_K_M GGUF with its vision file is 1.56 GB, so with a fifth added it needs about 1.9 GB and fits well within 16 GB (30). Transformers 4.57.0, vLLM, SGLang, llama.cpp and Ollama all run it in released versions, which reaches the 25 cap. Alibaba publishes FP8 and GGUF builds at F16, Q8_0 and Q4_K_M (15). Apache 2.0 with nothing added (15). No gate and no account (10). Only Featherless was found serving it, so it isn't hosted too (0). 30 + 25 + 15 + 15 + 10 + 0 = 95.

LFM3-Audio-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-VL-2B-Instruct 55

Safetensors and GGUF only and no code in the repositories, so the FP8 card's trust_remote_code flag runs nothing (25). Files in the Qwen organisation with a checksum on every file (15). No safety evaluation at all (0). No guidance for agent use, which matters for a model sold as a GUI agent (0). Apache 2.0 carries none of the licence risks (15). No security contact, disclosure policy or public advisories found for Qwen (0), and Alibaba's group-wide security centre wasn't checked.