Head to head · Open-weight models you run yourself · October 2026 research run
LFM3-VL-2B vs MiniMax-M3.1-Flash
LFM3-VL-2B scores 61 (C) on agent readiness against MiniMax-M3.1-Flash's 54.3 (C), and leads in every scored category. 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
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 55
- Risk, 40 against 35
- Agent interface, 90 against 70
- Documentation and upkeep, 77 against 41
Watch for
vLLM and SGLang support is unreleased, which the card says itself
Best for Teams with a 4 to 8 GPU server who want an open multimodal agent and coding model with 1M tokens of context and can meet the licence's attribution and notice terms.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
SGLang's cookbook still points to a pull request or a dev image on 4 November 2026, and vLLM's recipe still names a nightly image, though both runtimes' releases carry the model code
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
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.
MiniMax-M3.1-Flash 41
The model card earns 11, missing limitations, languages and a knowledge cut-off. Training data earns nothing, as it isn't described. The last change earns 20, an evaluation-results commit of 30 October 2026 after the release commit of 23 October. Responsiveness earns nothing, with no MiniMax reply in nine discussions opened from 23 to 31 October. Version policy earns 5 for a first release in its own repository. File health earns 5, for the tokenizer's 40,960,000-token model_max_length against the 1M context, the Transformers library tag against the card, and an unanswered vLLM streaming report. 11 + 0 + 20 + 0 + 5 + 5 = 41.
Reach LFM3-VL-2B +30
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.
MiniMax-M3.1-Flash 55
Memory earns nothing. MiniMax's only build is its 250 GB NVFP4 and MXFP8 release, about 300 GB with the fifth added, above 256 GB, and no runtime library has a local build. Runtimes earn 20. llama.cpp from b11861 runs it, Ollama v0.40.14 pins llama.cpp b11963 with the minimax-m3 architecture, vLLM v0.33.0 (tagged 1 November 2026) registers the architecture and meets its recipe's minimum version, and SGLang v0.5.23 (tagged 29 October) registers it with M3.1 processor code and tests, though its cookbook still points to a pull request. Transformers support is in progress per the card and LM Studio has no entry. Builds earn 10 for one publisher precision. Terms earn 10, since commercial use is free with attribution and a notice below $20M of yearly revenue. Download earns 10, with no gate. Hosted earns 5, since MiniMax's API and Novita serve it. 0 + 20 + 10 + 10 + 10 + 5 = 55.
Agent interface LFM3-VL-2B +20
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.
MiniMax-M3.1-Flash 70
The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 10, since only the template shows the format and the parsers come from vLLM's and SGLang's own docs. Trained tool calling earns 20, with several invoke blocks in one call. Structured output earns nothing, as it isn't documented. Reasoning control earns 10, with reasoning_effort per request on the card and the reasoning in mm:think tags. Context earns 10 for 1,048,576 tokens with no position scaling.
Risk LFM3-VL-2B +5
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.
MiniMax-M3.1-Flash 35
File safety earns 15, safetensors only, less 10 because the SGLang route the card links passes trust_remote_code for the repository's configuration and processor code. Provenance earns the full 15, files in the organisation MiniMax links to with a SHA-256 for each shard. Safety evaluation and agent guidance earn nothing; the launch post's security testing measured offensive capability, and the template's root role isn't documented as a trained hierarchy. Licence risk earns 5, after the military-use ban and the $20M threshold. The security programme earns nothing, with no security.txt, disclosure policy or advisories.
Score by category
| Category | Weight this run | LFM3-VL-2B | MiniMax-M3.1-Flash | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 85 | 55 | LFM3-VL-2B +30 |
| Risk | 20%20 | 40 | 35 | LFM3-VL-2B +5 |
| Agent interface | 10%10 | 90 | 70 | LFM3-VL-2B +20 |
| Documentation and upkeep | 10%10 | 77 | 41 | LFM3-VL-2B +36 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 54.3/100 |
Facts side by side
| Fact | LFM3-VL-2B | MiniMax-M3.1-Flash |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Liquid AI | MiniMax |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | LFM Open License v1.0 (free commercial use below $10M annual revenue) | MiniMax Community License (custom; commercial use needs a "Built with MiniMax M3.1-Flash" line and a one-time notice to MiniMax, and MiniMax's written authorisation above $20M yearly revenue) |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-09 | 2026-10-23 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 2.3/5 (4) |
How the scores have moved
LFM3-VL-2B
No score change since it was listed.
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.
MiniMax-M3.1-Flash
A 428B mixture-of-experts model, 23B active, for agent work, coding and computer use, with image and video input, about 1M tokens of context and parallel tool calls. It needs a 4 to 8 GPU server for 250 GB of NVFP4 and MXFP8 weights. vLLM 0.33.0 and SGLang 0.5.23 carry its code. Commercial use needs attribution and notice.
Before you call either
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
MiniMax-M3.1-Flash
- Check the use case first; commercial products must show "Built with MiniMax M3.1-Flash" and notify MiniMax once, or get written authorisation above $20M yearly revenue
- On 8 H100 or H200 GPUs use vLLM 0.33.0 or later, or the recipe's image vllm/vllm-openai:minimax-m31-flash, with --tensor-parallel-size 8 --block-size 128 --kv-cache-dtype fp8 --moe-backend marlin --max-model-len 262144
- Pass --reasoning-parser minimax_m3 --tool-call-parser minimax_m3 --enable-auto-tool-choice in vLLM, or minimax-m3 for both in SGLang with --trust-remote-code
- --block-size 128 is mandatory in vLLM, since MSA's sparse block size is 128
- Set effort per request with chat_template_kwargs reasoning_effort (low, medium, high, xhigh, max); sample at temperature 1.0 and top_p 0.95
- On Blackwell or MI355X, 4 GPUs serve it with the DSpark draft from dspark/; vLLM's Hopper command leaves DSpark off and turns video input off
- For GGUF builds by others, use llama.cpp b11861 or later; earlier builds mis-scale the NVFP4 experts and produce garbage
- Without the hardware, call MiniMax-M3.1-Flash on MiniMax's API (minimax-api), whose thinking defaults to max effort
Questions
Which is better for AI agents, LFM3-VL-2B or MiniMax-M3.1-Flash?
LFM3-VL-2B scores 61 (C) on agent readiness against MiniMax-M3.1-Flash's 54.3 (C), and leads in every scored category.
Other comparisons with LFM3-VL-2B or MiniMax-M3.1-Flash
- Agents-A1-4B vs LFM3-VL-2B
- Agents-A1-4B vs MiniMax-M3.1-Flash
- Apertus v1.5 8B vs LFM3-VL-2B
- Apertus v1.5 8B vs MiniMax-M3.1-Flash
- Apodex-1.1-mini vs LFM3-VL-2B
- Apodex-1.1-mini vs MiniMax-M3.1-Flash
- Arete-27B vs LFM3-VL-2B
- Arete-27B vs MiniMax-M3.1-Flash
- BigBang-v1 vs LFM3-VL-2B
- BigBang-v1 vs MiniMax-M3.1-Flash
- Carbon-X vs LFM3-VL-2B
- Carbon-X vs MiniMax-M3.1-Flash
- Cosmos-Reason2-2B vs LFM3-VL-2B
- Cosmos-Reason2-2B vs MiniMax-M3.1-Flash
- Darwin-36B-Opus vs LFM3-VL-2B
- Darwin-36B-Opus vs MiniMax-M3.1-Flash
- DeepSeek-V3.2 vs LFM3-VL-2B
- DeepSeek-V3.2 vs MiniMax-M3.1-Flash
- DeepSeek V4.1 Flash vs LFM3-VL-2B
- DeepSeek V4.1 Flash vs MiniMax-M3.1-Flash
- DeepSeek-V4-Flash-0731 vs LFM3-VL-2B
- DeepSeek-V4-Flash-0731 vs MiniMax-M3.1-Flash
- DiffusionGemma 26B A4B IT vs LFM3-VL-2B
- DiffusionGemma 26B A4B IT vs MiniMax-M3.1-Flash
- Gemma 4 12B IT vs LFM3-VL-2B
- Gemma 4 12B IT vs MiniMax-M3.1-Flash
- Gemma 4 26B A4B IT vs LFM3-VL-2B
- Gemma 4 26B A4B IT vs MiniMax-M3.1-Flash
- Gemma 4 31B IT vs LFM3-VL-2B
- Gemma 4 31B IT vs MiniMax-M3.1-Flash
- Gemma 4 E2B IT vs LFM3-VL-2B
- Gemma 4 E2B IT vs MiniMax-M3.1-Flash
- Gemma 4 E4B IT vs LFM3-VL-2B
- Gemma 4 E4B IT vs MiniMax-M3.1-Flash
- GLM-4.5-Air vs LFM3-VL-2B
- GLM-4.5-Air vs MiniMax-M3.1-Flash
- GLM-4.7-Flash vs LFM3-VL-2B
- GLM-4.7-Flash vs MiniMax-M3.1-Flash
- GLM-5.3-Flash vs LFM3-VL-2B
- GLM-5.3-Flash vs MiniMax-M3.1-Flash
- GLM-5.3 vs LFM3-VL-2B
- GLM-5.3 vs MiniMax-M3.1-Flash
- gpt-oss-120b vs LFM3-VL-2B
- gpt-oss-120b vs MiniMax-M3.1-Flash
- gpt-oss-20b vs LFM3-VL-2B
- gpt-oss-20b vs MiniMax-M3.1-Flash
- Granite 4.2 30B vs LFM3-VL-2B
- Granite 4.2 30B vs MiniMax-M3.1-Flash
- Granite 4.2 3B vs LFM3-VL-2B
- Granite 4.2 3B vs MiniMax-M3.1-Flash
- Granite 4.2 8B vs LFM3-VL-2B
- Granite 4.2 8B vs MiniMax-M3.1-Flash
- Hy-Memory-30B-A3B vs LFM3-VL-2B
- Hy-Memory-30B-A3B vs MiniMax-M3.1-Flash
- Hy3 vs LFM3-VL-2B
- Hy3 vs MiniMax-M3.1-Flash
- Inkling-Small vs LFM3-VL-2B
- Inkling-Small vs MiniMax-M3.1-Flash
- Inkling vs LFM3-VL-2B
- Inkling vs MiniMax-M3.1-Flash
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-VL-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs MiniMax-M3.1-Flash
- Kimi K3.1 Pro vs LFM3-VL-2B
- Kimi K3.1 Pro vs MiniMax-M3.1-Flash
- Kimi K3 vs LFM3-VL-2B
- Kimi K3 vs MiniMax-M3.1-Flash
- Kolibri-1 vs LFM3-VL-2B
- Kolibri-1 vs MiniMax-M3.1-Flash
- Kronos vs LFM3-VL-2B
- Kronos vs MiniMax-M3.1-Flash
- Laguna M.1 vs LFM3-VL-2B
- Laguna M.1 vs MiniMax-M3.1-Flash
- Laguna S 2.1 vs LFM3-VL-2B
- Laguna S 2.1 vs MiniMax-M3.1-Flash
- Laguna XS 2.1 vs LFM3-VL-2B
- Laguna XS 2.1 vs MiniMax-M3.1-Flash
- LBS-27B vs LFM3-VL-2B
- LBS-27B vs MiniMax-M3.1-Flash
- LFM2.5-2.6B vs LFM3-VL-2B
- LFM2.5-2.6B vs MiniMax-M3.1-Flash
- LFM3-1.7B vs LFM3-VL-2B
- LFM3-1.7B vs MiniMax-M3.1-Flash
- LFM3-Audio-2B vs LFM3-VL-2B
- LFM3-Audio-2B vs MiniMax-M3.1-Flash
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs MiniMax-M3.1-Flash
- 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 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
- Ling-3.0-tiny vs MiniMax-M3.1-Flash
- Ling-3.1-flash-1019 vs MiniMax-M3.1-Flash
- MiMo-V2.6 Distill Qwen 9B vs MiniMax-M3.1-Flash
- MiniCPM-o 4.5 vs MiniMax-M3.1-Flash
- MiniCPM-V 4.7 1B vs MiniMax-M3.1-Flash
- MiniCPM-V 4.7 35B-A3B vs MiniMax-M3.1-Flash
- MiniCPM5-2B vs MiniMax-M3.1-Flash
- MiniMax-M2.5 vs MiniMax-M3.1-Flash
- MiniMax-M2.7 vs MiniMax-M3.1-Flash
- MiniMax-M3.1-Flash vs Mistral Large 4
- MiniMax-M3.1-Flash vs Muse Glimmer 30B
- MiniMax-M3.1-Flash vs Nanbeige4.3-33B
- MiniMax-M3.1-Flash vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- MiniMax-M3.1-Flash vs Nemotron 3.5 Lightning 30B A3B
- MiniMax-M3.1-Flash vs Nemotron 3 Nano 30B A3B
- MiniMax-M3.1-Flash vs Nemotron 3 Nano 4B
- MiniMax-M3.1-Flash vs Nemotron 3 Nano Omni 30B A3B Reasoning
- MiniMax-M3.1-Flash vs Nemotron 3 Super 120B A12B
- MiniMax-M3.1-Flash vs Nemotron 3 Ultra 550B A55B
- MiniMax-M3.1-Flash vs occamy-1.0
- MiniMax-M3.1-Flash vs Olmo 3 7B Think
- MiniMax-M3.1-Flash vs Ornith-1.5-122B
- MiniMax-M3.1-Flash vs Ornith-1.5-35B-A3B
- MiniMax-M3.1-Flash vs Ornith-1.5-397B
- MiniMax-M3.1-Flash vs Ornith-1.5-9B
- MiniMax-M3.1-Flash vs Qwen-AgentWorld-35B-A3B
- MiniMax-M3.1-Flash vs Qwen3-30B-A3B-Instruct-2507
- MiniMax-M3.1-Flash vs Qwen3-4B-Instruct-2507
- MiniMax-M3.1-Flash vs Qwen3.5-0.8B
- MiniMax-M3.1-Flash vs Qwen3.5-122B-A10B
- MiniMax-M3.1-Flash vs Qwen3.5-2B
- MiniMax-M3.1-Flash vs Qwen3.5-397B-A17B
- MiniMax-M3.1-Flash vs Qwen3.5-4B
- MiniMax-M3.1-Flash vs Qwen3.5-9B
- MiniMax-M3.1-Flash vs Qwen3.6-27B
- MiniMax-M3.1-Flash vs Qwen3.6-35B-A3B
- MiniMax-M3.1-Flash vs Qwen3.8-27B
- MiniMax-M3.1-Flash vs Qwen3.8-Flash-Next
- MiniMax-M3.1-Flash vs Qwen3-Coder-30B-A3B-Instruct
- MiniMax-M3.1-Flash vs Qwen3-Coder-Next
- MiniMax-M3.1-Flash vs Qwen3-Omni-30B-A3B-Instruct
- MiniMax-M3.1-Flash vs Qwen3-VL-2B-Instruct
- MiniMax-M3.1-Flash vs Qwen3-VL-30B-A3B-Instruct
- MiniMax-M3.1-Flash vs Qwen3-VL-32B-Instruct
- MiniMax-M3.1-Flash vs Qwen3-VL-4B-Instruct
- MiniMax-M3.1-Flash vs Qwen3-VL-8B-Instruct
- MiniMax-M3.1-Flash vs Qwopus3.8-27B-Flash-V2
- MiniMax-M3.1-Flash vs Recursive Flint
- MiniMax-M3.1-Flash vs Ripple-65B Preview
- MiniMax-M3.1-Flash vs SmolLM3-3B
- MiniMax-M3.1-Flash vs Spark-X2.6-4B
- MiniMax-M3.1-Flash vs Swift 1.5 Qwen3.8-27B
- MiniMax-M3.1-Flash vs Swift 1.5 Qwen3.8-Flash-Next
- MiniMax-M3.1-Flash vs ThinkingCap (Qwen3.8 27B)
- MiniMax-M3.1-Flash vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/lfm3-vl-2b-vs-minimax-m3-1-flash.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lfm3-vl-2b.json·/api/v1/tools/minimax-m3-1-flash.json - From a terminal
anchor compare lfm3-vl-2b minimax-m3-1-flash(the CLI) - Over MCP
compare_tools {"a": "lfm3-vl-2b", "b": "minimax-m3-1-flash"}at/mcp, no key