Head to head · Open-weight models you run yourself · October 2026 research run
Kimi K3 vs LFM3-VL-2B
Kimi K3 scores 62.4 (B) on agent readiness against LFM3-VL-2B's 61 (C), and leads in 1 of 4 scored categories. 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
Kimi K3 B
Best for Teams with a multi-node GPU cluster who want an open 1M-context agent model for long coding and research work
Ahead on
- Risk, 65 against 40
Watch for
1,561 GB of files at its smallest publisher build, far beyond any single machine
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 50
- Agent interface, 90 against 65
- Documentation and upkeep, 77 against 41
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 +36
Kimi K3 41
The model card earns 11, covering intended use, architecture, parameters and context, but not limitations, languages or a knowledge cut-off. Training data earns 5 for a general description with no cut-off. The last change earns 15, an encoding_k3.py update on 20 August, 74 days before 2 November and within 90; the GitHub repository's last commit is 6 August. Responsiveness earns nothing, with no Moonshot reply in the 40 most recent discussions. Version policy earns 5 for a first release. File health earns 5, because a report that the tokeniser goes past the declared vocabulary waits without a reply.
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 +35
Kimi K3 50
Memory earns nothing, because the only build of 4-bit precision or better from Moonshot or a runtime's own library is Moonshot's MXFP4 release of 1,561 GB, about 1,873 GB with the fifth added, far above 256 GB. Ollama and LM Studio list it only as a cloud model. Runtimes earn 15, for model code in released vLLM, SGLang and llama.cpp; Transformers has no kimi_k3 code of its own and loads Moonshot's remote code, so it doesn't count. Builds earn 10 for one publisher precision, the MXFP4 files the model was trained for. Terms earn 10, a custom MIT-based licence that is free for commercial use below a revenue threshold. Download earns 10, with no gate and no account. Hosted earns 5, since Moonshot's API serves it and five inference providers are live for it on Hugging Face.
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.
Risk Kimi K3 +25
Kimi K3 65
File safety earns 15, safetensors only with no pickle files, less 10 because the documented loading path runs Moonshot's Python with trust_remote_code and builds prompts with encoding_k3.py. Provenance earns the full 15, files in the organisation Moonshot links to with a SHA-256 for every shard. Safety evaluation earns 20 for the cyber assessment the UK AI Security Institute and CAISI ran and published, which found its safeguards didn't stop exploit development. Agent guidance earns 5 for the blog's general cautions about proactiveness and passing back thinking. Licence risk earns 10, losing 5 for the model-as-a-service revenue threshold and nothing else. The security programme earns nothing, with no security.txt, disclosure policy, SECURITY.md or public advisories found.
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.
Agent interface LFM3-VL-2B +25
Kimi K3 65
The chat template earns 10, because there is no Jinja template and the prompt format exists only as encoding_k3.py, code you run. The tool-calling format earns 10, since Moonshot documents the tools channel but the parser name comes only from vLLM's and SGLang's own recipes. Trained tool calling earns 20 for indexed parallel calls in one turn. Structured output earns 5, as the card names it among its linked guides without saying how to ask the weights for it, and the how sits in hosted-API docs. Reasoning control earns 10, with per-request effort documented on the card and reasoning returned as reasoning_content. Context earns 10 for 1,048,576 tokens trained in.
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.
Score by category
| Category | Weight this run | Kimi K3 | LFM3-VL-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 50 | 85 | LFM3-VL-2B +35 |
| Risk | 20%20 | 65 | 40 | Kimi K3 +25 |
| Agent interface | 10%10 | 65 | 90 | LFM3-VL-2B +25 |
| Documentation and upkeep | 10%10 | 41 | 77 | LFM3-VL-2B +36 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.4/100 | C 61/100 |
Facts side by side
| Fact | Kimi K3 | LFM3-VL-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Moonshot AI | Liquid AI |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Kimi K3 License (modified MIT) | LFM Open License v1.0 (free commercial use below $10M annual revenue) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-09-02 | 2026-11-09 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.3/5 (4) | none |
Verdicts
Kimi K3
Kimi K3 is a 2.8T multimodal agent model with a 1M-token context, parallel tool calls and per-request effort, for long coding and research sessions. Its 1,561 GB of files need a multi-node GPU cluster, so most agents will call a hosted copy. The main risks are Moonshot's Python running at load and prompt time, 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
Kimi K3
- Start it with SGLang on a node of 8 B300s, sglang serve --trust-remote-code --model-path moonshotai/Kimi-K3 --tp-size 8 --context-length 65536 --mem-fraction-static 0.82 --reasoning-parser kimi_k3 --tool-call-parser kimi_k3 --port 30000
- Use the kimi_k3 tool-call and reasoning parsers in vLLM or SGLang, and validate tool-call arguments against the schema, since vLLM's recipe says K3 sometimes emits a format its parser doesn't expect
- Pass the whole assistant message back every turn, reasoning_content and tool_calls included, or output becomes unstable
- Thinking is always on; set reasoning_effort to low or high when max is too slow
- Sampling per the card is temperature 1.0, with top-p 0.95 for single-step tasks and 1.0 for agentic ones
- Don't hand an ongoing session from another model to K3, and state boundaries in the system prompt, since Moonshot warns it can act on its own when intent is unclear
- Without the hardware, call it through Moonshot's API or an inference provider listed on its Hugging Face page
LFM3-VL-2B
- Start it with
llama-server -hf LiquidAI/LFM3-VL-2B-GGUF:Q4_K_M --jinjaorollama run lfm3-vl, with llama.cpp b11960 or later - Use temperature 0.1, top_k 50 and repetition penalty 1.1, per the card
- Video is sampled at 2 frames a second up to 768 frames, and each frame costs context. Video input in llama.cpp needs ffmpeg
- Don't plan on vLLM or SGLang until a release carries LFM3-VL
- Validate JSON output yourself
- Liquid doesn't recommend it for coding, multi-turn conversations or complex reasoning
Questions
Which is better for AI agents, Kimi K3 or LFM3-VL-2B?
Kimi K3 scores 62.4 (B) on agent readiness against LFM3-VL-2B's 61 (C), and leads in 1 of 4 scored categories. LFM3-VL-2B leads on reach, agent interface and documentation and upkeep.
Other comparisons with Kimi K3 or LFM3-VL-2B
- Agents-A1-4B vs Kimi K3
- Agents-A1-4B vs LFM3-VL-2B
- Apertus v1.5 8B vs Kimi K3
- Apertus v1.5 8B vs LFM3-VL-2B
- Apodex-1.1-mini vs Kimi K3
- Apodex-1.1-mini vs LFM3-VL-2B
- Arete-27B vs Kimi K3
- Arete-27B vs LFM3-VL-2B
- BigBang-v1 vs Kimi K3
- BigBang-v1 vs LFM3-VL-2B
- Carbon-X vs Kimi K3
- Carbon-X vs LFM3-VL-2B
- Cosmos-Reason2-2B vs Kimi K3
- Cosmos-Reason2-2B vs LFM3-VL-2B
- Darwin-36B-Opus vs Kimi K3
- Darwin-36B-Opus vs LFM3-VL-2B
- DeepSeek-V3.2 vs Kimi K3
- DeepSeek-V3.2 vs LFM3-VL-2B
- DeepSeek V4.1 Flash vs Kimi K3
- DeepSeek V4.1 Flash vs LFM3-VL-2B
- DeepSeek-V4-Flash-0731 vs Kimi K3
- DeepSeek-V4-Flash-0731 vs LFM3-VL-2B
- DiffusionGemma 26B A4B IT vs Kimi K3
- DiffusionGemma 26B A4B IT vs LFM3-VL-2B
- Gemma 4 12B IT vs Kimi K3
- Gemma 4 12B IT vs LFM3-VL-2B
- Gemma 4 26B A4B IT vs Kimi K3
- Gemma 4 26B A4B IT vs LFM3-VL-2B
- Gemma 4 31B IT vs Kimi K3
- Gemma 4 31B IT vs LFM3-VL-2B
- Gemma 4 E2B IT vs Kimi K3
- Gemma 4 E2B IT vs LFM3-VL-2B
- Gemma 4 E4B IT vs Kimi K3
- Gemma 4 E4B IT vs LFM3-VL-2B
- GLM-4.5-Air vs Kimi K3
- GLM-4.5-Air vs LFM3-VL-2B
- GLM-4.7-Flash vs Kimi K3
- GLM-4.7-Flash vs LFM3-VL-2B
- GLM-5.3-Flash vs Kimi K3
- GLM-5.3-Flash vs LFM3-VL-2B
- GLM-5.3 vs Kimi K3
- GLM-5.3 vs LFM3-VL-2B
- gpt-oss-120b vs Kimi K3
- gpt-oss-120b vs LFM3-VL-2B
- gpt-oss-20b vs Kimi K3
- gpt-oss-20b vs LFM3-VL-2B
- Granite 4.2 30B vs Kimi K3
- Granite 4.2 30B vs LFM3-VL-2B
- Granite 4.2 3B vs Kimi K3
- Granite 4.2 3B vs LFM3-VL-2B
- Granite 4.2 8B vs Kimi K3
- Granite 4.2 8B vs LFM3-VL-2B
- Hy-Memory-30B-A3B vs Kimi K3
- Hy-Memory-30B-A3B vs LFM3-VL-2B
- Hy3 vs Kimi K3
- Hy3 vs LFM3-VL-2B
- Inkling-Small vs Kimi K3
- Inkling-Small vs LFM3-VL-2B
- Inkling vs Kimi K3
- Inkling vs LFM3-VL-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kimi K3
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-VL-2B
- Kimi K3.1 Pro vs LFM3-VL-2B
- Kimi K3 vs Kimi K3.1 Pro
- Kimi K3 vs Kolibri-1
- Kimi K3 vs Kronos
- Kimi K3 vs Laguna M.1
- Kimi K3 vs Laguna S 2.1
- Kimi K3 vs Laguna XS 2.1
- Kimi K3 vs LBS-27B
- Kimi K3 vs LFM2.5-2.6B
- Kimi K3 vs LFM3-1.7B
- Kimi K3 vs LFM3-Audio-2B
- Kimi K3 vs LFM3-Omni-2B
- Kimi K3 vs Ling-3.0-tiny
- Kimi K3 vs Ling-3.1-flash-1019
- Kimi K3 vs MiMo-V2.6 Distill Qwen 9B
- Kimi K3 vs MiniCPM-o 4.5
- Kimi K3 vs MiniCPM-V 4.7 1B
- Kimi K3 vs MiniCPM-V 4.7 35B-A3B
- Kimi K3 vs MiniCPM5-2B
- Kimi K3 vs MiniMax-M2.5
- Kimi K3 vs MiniMax-M2.7
- Kimi K3 vs MiniMax-M3.1-Flash
- Kimi K3 vs Mistral Large 4
- Kimi K3 vs Muse Glimmer 30B
- Kimi K3 vs Nanbeige4.3-33B
- Kimi K3 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Kimi K3 vs Nemotron 3.5 Lightning 30B A3B
- Kimi K3 vs Nemotron 3 Nano 30B A3B
- Kimi K3 vs Nemotron 3 Nano 4B
- Kimi K3 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Kimi K3 vs Nemotron 3 Super 120B A12B
- Kimi K3 vs Nemotron 3 Ultra 550B A55B
- Kimi K3 vs occamy-1.0
- Kimi K3 vs Olmo 3 7B Think
- Kimi K3 vs Ornith-1.5-122B
- Kimi K3 vs Ornith-1.5-35B-A3B
- Kimi K3 vs Ornith-1.5-397B
- Kimi K3 vs Ornith-1.5-9B
- Kimi K3 vs Qwen-AgentWorld-35B-A3B
- Kimi K3 vs Qwen3-30B-A3B-Instruct-2507
- Kimi K3 vs Qwen3-4B-Instruct-2507
- Kimi K3 vs Qwen3.5-0.8B
- Kimi K3 vs Qwen3.5-122B-A10B
- Kimi K3 vs Qwen3.5-2B
- Kimi K3 vs Qwen3.5-397B-A17B
- Kimi K3 vs Qwen3.5-4B
- Kimi K3 vs Qwen3.5-9B
- Kimi K3 vs Qwen3.6-27B
- Kimi K3 vs Qwen3.6-35B-A3B
- Kimi K3 vs Qwen3.8-27B
- Kimi K3 vs Qwen3.8-Flash-Next
- Kimi K3 vs Qwen3-Coder-30B-A3B-Instruct
- Kimi K3 vs Qwen3-Coder-Next
- Kimi K3 vs Qwen3-Omni-30B-A3B-Instruct
- Kimi K3 vs Qwen3-VL-2B-Instruct
- Kimi K3 vs Qwen3-VL-30B-A3B-Instruct
- Kimi K3 vs Qwen3-VL-32B-Instruct
- Kimi K3 vs Qwen3-VL-4B-Instruct
- Kimi K3 vs Qwen3-VL-8B-Instruct
- Kimi K3 vs Qwopus3.8-27B-Flash-V2
- Kimi K3 vs Recursive Flint
- Kimi K3 vs Ripple-65B Preview
- Kimi K3 vs SmolLM3-3B
- Kimi K3 vs Spark-X2.6-4B
- Kimi K3 vs Swift 1.5 Qwen3.8-27B
- Kimi K3 vs Swift 1.5 Qwen3.8-Flash-Next
- Kimi K3 vs ThinkingCap (Qwen3.8 27B)
- Kimi K3 vs Baidu Unlimited-OCR-2
- Kolibri-1 vs LFM3-VL-2B
- Kronos vs LFM3-VL-2B
- Laguna M.1 vs LFM3-VL-2B
- Laguna S 2.1 vs LFM3-VL-2B
- Laguna XS 2.1 vs LFM3-VL-2B
- LBS-27B vs LFM3-VL-2B
- LFM2.5-2.6B vs LFM3-VL-2B
- LFM3-1.7B vs LFM3-VL-2B
- LFM3-Audio-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-VL-2B vs Ling-3.0-tiny
- LFM3-VL-2B vs Ling-3.1-flash-1019
- LFM3-VL-2B vs MiMo-V2.6 Distill Qwen 9B
- LFM3-VL-2B vs MiniCPM-o 4.5
- LFM3-VL-2B vs MiniCPM-V 4.7 1B
- LFM3-VL-2B vs MiniCPM-V 4.7 35B-A3B
- LFM3-VL-2B vs MiniCPM5-2B
- LFM3-VL-2B vs MiniMax-M2.5
- LFM3-VL-2B vs MiniMax-M2.7
- LFM3-VL-2B vs MiniMax-M3.1-Flash
- LFM3-VL-2B vs Mistral Large 4
- LFM3-VL-2B vs Muse Glimmer 30B
- LFM3-VL-2B vs Nanbeige4.3-33B
- LFM3-VL-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM3-VL-2B vs Nemotron 3.5 Lightning 30B A3B
- LFM3-VL-2B vs Nemotron 3 Nano 30B A3B
- LFM3-VL-2B vs Nemotron 3 Nano 4B
- LFM3-VL-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM3-VL-2B vs Nemotron 3 Super 120B A12B
- LFM3-VL-2B vs Nemotron 3 Ultra 550B A55B
- LFM3-VL-2B vs occamy-1.0
- LFM3-VL-2B vs Olmo 3 7B Think
- LFM3-VL-2B vs Ornith-1.5-122B
- LFM3-VL-2B vs Ornith-1.5-35B-A3B
- LFM3-VL-2B vs Ornith-1.5-397B
- LFM3-VL-2B vs Ornith-1.5-9B
- LFM3-VL-2B vs Qwen-AgentWorld-35B-A3B
- LFM3-VL-2B vs Qwen3-30B-A3B-Instruct-2507
- LFM3-VL-2B vs Qwen3-4B-Instruct-2507
- LFM3-VL-2B vs Qwen3.5-0.8B
- LFM3-VL-2B vs Qwen3.5-122B-A10B
- LFM3-VL-2B vs Qwen3.5-2B
- LFM3-VL-2B vs Qwen3.5-397B-A17B
- LFM3-VL-2B vs Qwen3.5-4B
- LFM3-VL-2B vs Qwen3.5-9B
- LFM3-VL-2B vs Qwen3.6-27B
- LFM3-VL-2B vs Qwen3.6-35B-A3B
- LFM3-VL-2B vs Qwen3.8-27B
- LFM3-VL-2B vs Qwen3.8-Flash-Next
- LFM3-VL-2B vs Qwen3-Coder-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-Coder-Next
- LFM3-VL-2B vs Qwen3-Omni-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-VL-2B-Instruct
- LFM3-VL-2B vs Qwen3-VL-30B-A3B-Instruct
- LFM3-VL-2B vs Qwen3-VL-32B-Instruct
- LFM3-VL-2B vs Qwen3-VL-4B-Instruct
- LFM3-VL-2B vs Qwen3-VL-8B-Instruct
- LFM3-VL-2B vs Qwopus3.8-27B-Flash-V2
- LFM3-VL-2B vs Recursive Flint
- LFM3-VL-2B vs Ripple-65B Preview
- LFM3-VL-2B vs SmolLM3-3B
- LFM3-VL-2B vs Spark-X2.6-4B
- LFM3-VL-2B vs Swift 1.5 Qwen3.8-27B
- LFM3-VL-2B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM3-VL-2B vs ThinkingCap (Qwen3.8 27B)
- LFM3-VL-2B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/kimi-k3-vs-lfm3-vl-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kimi-k3.json·/api/v1/tools/lfm3-vl-2b.json - From a terminal
anchor compare kimi-k3 lfm3-vl-2b(the CLI) - Over MCP
compare_tools {"a": "kimi-k3", "b": "lfm3-vl-2b"}at/mcp, no key