LFM3-Audio-2B vs Qwen3.6-27B

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.6-27B 31

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, languages and a knowledge cut-off aren't. Training data 5, only a general family description without a cut-off, in the GitHub README. Last change 5, the files last changed on 24 April 2026, 191 days before this check, and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. Responsiveness 0, Qwen answered none of the 40 most recent questions and reports, recounted on 1 November. Version policy 5, earlier and later 27B models stay in their own repositories without dated notes. File health 5, the files agree with the card but template and tool-calling reports wait without a reply.

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.6-27B 55

File safety 25, safetensors only and nothing from the repository runs to load it or build prompts. Provenance 15, the files are in the Qwen organisation that Qwen's GitHub links to, and every file has a hash on the Hub. Safety evaluation 0, none published on the card or README. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 15, plain Apache 2.0 that hasn't changed. Security programme 0, no security.txt, SECURITY.md or reporting route was found, and Alibaba's group security centre couldn't be checked, so it's scored as absent.

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.6-27B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10 of 25, the card names the qwen3_coder parser but the declaration and call format live only in the template. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, not documented. Reasoning control 10, thinking turns off per request and comes back in think tags split out by the qwen3 parser. Context 10, 262,144 tokens native.

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.6-27B 90

Memory 25 of 30, Ollama's text-only 4-bit build is 17 GB and the vision build 18 GB, about 20 to 22 GB with a fifth added, which fits 24 GB. Runtimes 25, released versions of llama.cpp, Ollama, vLLM, SGLang, LM Studio and Transformers all run the qwen3_5 architecture. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 15, Apache 2.0 with nothing added. Download 10, neither repository is gated. Hosted 5, three inference providers are live on Hugging Face and Alibaba's Model Studio serves it per the card.