LFM3-VL-2B vs Swift 1.5 Qwen3.8-Flash-Next

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.

Swift 1.5 Qwen3.8-Flash-Next 40

Model card 5 of 20, intended use and context only. Training data 5, a general description with no cut-off. Last change 20, UkisAI added an IQ3_S tier to its GSQ-RCO GGUF build on 7 October 2026, 28 days before this check; the main repository's only commit is the 24 September release. Responsiveness 0, UkisAI answered none of 3 discussions. Version policy 5, a first release, renamed without a note. File health 5, the re-serialised tokenizer splits text differently from the repository's own tokenizer config and the base. 5 + 5 + 20 + 0 + 5 + 5 = 40.

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.

Swift 1.5 Qwen3.8-Flash-Next 60

Chat template 20, the base's Jinja file. Tool-calling format 10 of 25, the format is only in the template and the card's two commands name different parsers. Trained tool calling 20, several calls a turn and agentic post-training. Structured output 0, not documented. Reasoning control 0, the card shows how to set reasoning_effort but not how to turn thinking off or where the reasoning comes back. Context 10, 262,144 tokens native.

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.

Swift 1.5 Qwen3.8-Flash-Next 65

Memory 5 of 30, the smallest 4-bit build is UkisAI's IQ4_XS GGUF at 98.6 GB with the vision projector, 118.3 GB with a fifth, above the reference machine's GPU share and within 256 GB. Runtimes 25, the architecture is Qwen3.8-Flash-Next's (qwen4_exp), which released llama.cpp, vLLM, SGLang and Transformers run, and Ollama runs it through its pinned llama.cpp (b11963 in v0.40.14), this run's reading for Ollama. Builds 15, GGUF, INT4 and NVFP4 builds from UkisAI. Terms 10, two custom licences that allow commercial use within limits. Download 10, not gated. Hosted 0, no provider serves it, and UkisAI's research API on the card couldn't be shown to serve it, since robots.txt disallows calling it. 5 + 25 + 15 + 10 + 10 + 0 = 65.

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.

Swift 1.5 Qwen3.8-Flash-Next 45

File safety 25, safetensors only and no code in the repository, though the card's vLLM command passes trust-remote-code. Provenance 15, the files are in the account UkisAI's site links to, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 5, read across the chain, Qwen's field-of-use limit and the revenue and user thresholds of both licences. Security programme 0, no way to report a flaw was found.