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

DeepSeek-V4-Flash-0731 vs LFM3-VL-2B

DeepSeek-V4-Flash-0731 and LFM3-VL-2B score within a point of each other on agent readiness, 61.9 (C) and 61 (C). LFM3-VL-2B leads on reach, agent interface and documentation and upkeep. 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

DeepSeek-V4-Flash-0731 C

Best for Agents or teams with a multi-GPU server, or a provider account, who want DeepSeek's V4 agent model under MIT with a 1M context

Ahead on

  • Risk, 50 against 40

Watch for

The smallest 4-bit build is 156.4 GB, so it needs about 188 GB and doesn't fit a 128 GB machine

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 70
  • Agent interface, 90 against 75
  • Documentation and upkeep, 77 against 38

Watch for

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

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

DeepSeek-V4-Flash-0731 38

Model card 8, the card and the DSpark card it names give architecture, parameters and context, with intended use, limitations, languages and cut-off missing. Training data 5, a general description in the report with no cut-off. Last change 10, a card edit on 1 August 2026, 93 days before 2 November, so past 90 and within 180; deepseek-recipe 0.2.0 (20 October) stays read as a library-wide release, not a change to this model's files. Responsiveness 0, DeepSeek answered none of the 61 discussions, the newest opened on 17 October. Version policy 10, the preview and DSpark copies keep their own repositories and the dated 0731 release says what it supersedes. File health 5, the files agree with each other, but reports of tool-call errors and looping and a pull request for a missing chat template wait without a reply from DeepSeek.

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.

Reach LFM3-VL-2B +15

DeepSeek-V4-Flash-0731 70

Memory 5, because the smallest build of 4-bit or better from a runtime's own library is LM Studio's MXFP4 GGUF at 156.4 GB, which with a fifth added needs 187.7 GB, more than our 107.4 GB machine and within 256 GB. DeepSeek's own release, 166.9 GB, sits in the same band. Runtimes 25, the cap, from vLLM v0.32.0, SGLang v0.5.22, llama.cpp release b11771, Transformers 5.20.0 and LM Studio's library, with Ollama not counted since its library entry is retired with no models pushed. Builds 10, DeepSeek ships one build, the FP8 and FP4 release itself. Terms 15, MIT with nothing added. Download 10, not gated. Hosted 5, DeepSeek's API moved to V4.1 Flash, but five inference providers on Hugging Face serve this repository live (Together's mapping has gone since 21 October).

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.

Agent interface LFM3-VL-2B +15

DeepSeek-V4-Flash-0731 75

Chat template 10, there is no Jinja template and the format is given as Python to run. Tool-calling format 10, DeepSeek documents how tools are declared and returned and ships its own parser, but only vLLM's recipe names a runtime parser, so the 25 line isn't met. Trained tool calling 20, several invoke elements in one call block. Structured output 15, DeepSeek's deepseek-recipe library documents JSON Schema response formats for V4 prompts. Reasoning control 10, chat mode with no thinking and three effort levels in thinking mode, with reasoning returned as reasoning_content. Context 10, 1M tokens trained.

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.

Risk DeepSeek-V4-Flash-0731 +10

DeepSeek-V4-Flash-0731 50

File safety 15, safetensors only, less 10 because prompts are built by running DeepSeek's encoding_dsv4.py from the repository and the card's serving commands pass --trust-remote-code. Provenance 15, the deepseek-ai organisation and a SHA-256 on every shard. Safety evaluation 0, none published. Agent guidance 0, the encoding README's notes about the parser and the reserved developer role are usage notes, read alike for all three DeepSeek listings. Licence risk 15, MIT with no deductions. Security programme 5, for the security@deepseek.com reporting address in DeepSeek's site footer, read as for DeepSeek-V3.2, with no security.txt and no public advisories.

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.

Score by category

CategoryWeight this runDeepSeek-V4-Flash-0731LFM3-VL-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257085LFM3-VL-2B +15
Risk20%205040DeepSeek-V4-Flash-0731 +10
Agent interface10%107590LFM3-VL-2B +15
Documentation and upkeep10%103877LFM3-VL-2B +39
Negative events≤1500
TotalC 61.9/100C 61/100

Facts side by side

FactDeepSeek-V4-Flash-0731LFM3-VL-2B
KindOpen-weight modelOpen-weight model
VendorDeepSeekLiquid AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITLFM Open License v1.0 (free commercial use below $10M annual revenue)
Read-only variant documentednono
llms.txtnoyes
Last release2026-07-312026-11-09
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

DeepSeek-V4-Flash-0731

A long-context agent cousin under MIT with documented tool calls, three reasoning effort levels and support in every major runtime but Ollama. It needs about 190 to 200 GB of memory, though five inference providers serve it. The main risks are prompts built from DeepSeek's Python, no published safety results and no answers in its repository.

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.

Before you call either

DeepSeek-V4-Flash-0731

  1. vllm serve deepseek-ai/DeepSeek-V4-Flash-0731 --trust-remote-code --kv-cache-dtype fp8 --block-size 256 --data-parallel-size 4 --enable-expert-parallel --moe-backend deep_gemm_mega_moe --attention-config '{"use_fp4_indexer_cache": true}' --speculative-config '{"method":"dspark","num_speculative_tokens":7,"draft_sample_method":"greedy"}' --tokenizer-mode deepseek_v4 --tool-call-parser deepseek_v4 --enable-auto-tool-choice --reasoning-parser deepseek_v4 (the card's 4x GB300 example plus the parser flags from vLLM's recipe)
  2. Build prompts with encoding_dsv4.py, deepseek-recipe's V4 encoder or vLLM's --tokenizer-mode deepseek_v4, since the repository has no Jinja template
  3. Tool calls come back in a DSML tool_calls block with invoke elements, string parameters carry string="true" and JSON values string="false"
  4. Set temperature 1.0 and top_p 0.95 for agent work, and allow up to 384K output tokens at reasoning effort high or max
  5. Without the hardware, call it through a Hugging Face inference provider (DeepInfra, Novita, Baseten, Scaleway, Featherless), not DeepSeek's API, where deepseek-v4-flash now means V4.1 Flash
  6. LM Studio's library build is a 156.4 GB MXFP4 GGUF and LM Studio states 156 GB minimum system memory

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

Questions

Which is better for AI agents, DeepSeek-V4-Flash-0731 or LFM3-VL-2B?

DeepSeek-V4-Flash-0731 and LFM3-VL-2B score within a point of each other on agent readiness, 61.9 (C) and 61 (C). LFM3-VL-2B leads on reach, agent interface and documentation and upkeep.

Other comparisons with DeepSeek-V4-Flash-0731 or LFM3-VL-2B

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.