Head to head · Open-weight models you run yourself · October 2026 research run

LFM3-VL-2B vs Qwen3.5-0.8B

LFM3-VL-2B scores 61 (C) on agent readiness against Qwen3.5-0.8B's 46.7 (D), and leads in 3 of 4 scored categories. Qwen3.5-0.8B 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

LFM3-VL-2B C

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

  • Reach, 85 against 80
  • Agent interface, 90 against 60
  • Documentation and upkeep, 77 against 37

Watch for

vLLM and SGLang support is unreleased, which the card says itself

Qwen3.5-0.8B D

Best for Builders who want a near-free local helper or fine-tuning base for narrow tasks on a phone-class device, laptop or CPU

Ahead on

  • Risk, 55 against 40

Watch for

No quantised build from Alibaba and no inference provider found

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 +40

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.

Qwen3.5-0.8B 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, 248 days before this check, within a year (5). No Qwen member has answered any of the 15 discussions that aren't pull requests (0). Qwen3-0.6B 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-VL-2B +30

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.

Qwen3.5-0.8B 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.

Risk Qwen3.5-0.8B +15

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.

Qwen3.5-0.8B 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.

Reach LFM3-VL-2B +5

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.

Qwen3.5-0.8B 80

Memory earns the full 30, since LM Studio's Q4_K_M build with its projector is 0.73 GB (0.88 GB with the fifth added) and Ollama's Q8_0 build was 1.0 GB, both far within 16 GB. Alibaba publishes no quantised 0.8B, so builds scores 0. Runtimes reach the 25 cap on llama.cpp, Ollama (through its pinned llama.cpp), vLLM, SGLang, LM Studio and Transformers. Apache 2.0 with nothing added gives terms 15 and the ungated repository download 10. Hosted too scores 0, as the Hub maps no inference provider to this size. 30+25+0+15+10+0 = 80.

Score by category

CategoryWeight this runLFM3-VL-2BQwen3.5-0.8BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258580LFM3-VL-2B +5
Risk20%204055Qwen3.5-0.8B +15
Agent interface10%109060LFM3-VL-2B +30
Documentation and upkeep10%107737LFM3-VL-2B +40
Negative events≤1500
TotalC 61/100D 46.7/100

Facts side by side

FactLFM3-VL-2BQwen3.5-0.8B
KindOpen-weight modelOpen-weight model
VendorLiquid AIAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceLFM Open License v1.0 (free commercial use below $10M annual revenue)Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-11-092026-03-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.8/5 (4)

Verdicts

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.

Qwen3.5-0.8B

A tiny vision-language model for prototypes, fine-tuning and narrow local steps such as routing, tagging or reading an image. It runs in about 1 GB at 4 or 8 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-VL-2B

  1. Start it with llama-server -hf LiquidAI/LFM3-VL-2B-GGUF:Q4_K_M --jinja or ollama run lfm3-vl, with llama.cpp b11960 or later
  2. Use temperature 0.1, top_k 50 and repetition penalty 1.1, per the card
  3. Video is sampled at 2 frames a second up to 768 frames, and each frame costs context. Video input in llama.cpp needs ffmpeg
  4. Don't plan on vLLM or SGLang until a release carries LFM3-VL
  5. Validate JSON output yourself
  6. Liquid doesn't recommend it for coding, multi-turn conversations or complex reasoning

Qwen3.5-0.8B

  1. Smallest start is ollama run qwen3.5:0.8b, or qwen3.5:0.8b-q8_0 at 1.0 GB
  2. Full precision vllm serve Qwen/Qwen3.5-0.8B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. 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 qwen3 in vLLM or SGLang to split the reasoning out
  4. 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.0 for text without thinking
  5. Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
  6. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, LFM3-VL-2B or Qwen3.5-0.8B?

LFM3-VL-2B scores 61 (C) on agent readiness against Qwen3.5-0.8B's 46.7 (D), and leads in 3 of 4 scored categories. Qwen3.5-0.8B leads on risk.

Other comparisons with LFM3-VL-2B or Qwen3.5-0.8B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.