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

Qwen3-VL-2B-Instruct vs Step 3.7 Flash

Qwen3-VL-2B-Instruct scores 61 (C) on agent readiness against Step 3.7 Flash's 59.8 (C), and leads in 2 of 4 scored categories. Step 3.7 Flash leads on 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 6359 open weights comparisons

Which one, for what

Qwen3-VL-2B-Instruct C

Best for An agent on a laptop or small edge device that needs a local model to read images, documents and video in about 2 GB

Ahead on

  • Reach, 95 against 70
  • Risk, 55 against 45

Watch for

No safety evaluation, agent-use guidance or security contact

Step 3.7 Flash C

Best for Teams with a GPU server or a provider account that want an open, long-context agent model with vision

Ahead on

  • Agent interface, 85 against 60
  • Documentation and upkeep, 39 against 31

Watch for

About 131 GB to run at 4 bits with images, over a 128 GB machine's share

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.

Reach Qwen3-VL-2B-Instruct +25

Qwen3-VL-2B-Instruct 95

Alibaba's own Q4_K_M GGUF with its vision file is 1.56 GB, so with a fifth added it needs about 1.9 GB and fits well within 16 GB (30). Transformers 4.57.0, vLLM, SGLang, llama.cpp and Ollama all run it in released versions, which reaches the 25 cap. Alibaba publishes FP8 and GGUF builds at F16, Q8_0 and Q4_K_M (15). Apache 2.0 with nothing added (15). No gate and no account (10). Only Featherless was found serving it, so it isn't hosted too (0). 30 + 25 + 15 + 15 + 10 + 0 = 95.

Step 3.7 Flash 70

Memory 5, the smallest build at 4 bits is StepFun's IQ4_XS GGUF, 104.99 GB with the 3.97 GB projector, and 108.96 GB × 1.2 = 130.8 GB, over what the reference machine can give a model and within 256 GB. The IQ3 and Q3 builds are below 4 bits and aren't read. Runtimes 20, Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 have the step3p7 model, and llama.cpp b12242 has the architecture, with StepFun's own GGUF. Four at 5 each, and the card documents all four. Builds 15, StepFun publishes GGUF at five quantised precisions, an FP8 build and an NVFP4 build. Terms 15, Apache 2.0 in the card's metadata and its licence section, an OSI licence with nothing added. Download 10, the Hub API reports gated false for all four repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, StepFun's own API serves it, per the card and our StepFun API listing, and Featherless and DeepInfra are live for it on Hugging Face. 5 + 20 + 15 + 15 + 10 + 5 = 70.

Agent interface Step 3.7 Flash +25

Qwen3-VL-2B-Instruct 60

A Jinja chat template in the repository (20). The tool-call format lives only in the template, Hermes-style JSON in tool_call tags, and Alibaba names no parser (10). Trained for function calling with several calls allowed in a turn, per the family's technical report (20). No documented structured output (0). No thinking mode in this edition, so reasoning control scores 0 by the rule. 262,144 tokens of native context (10).

Step 3.7 Flash 85

Chat template 20, chat_template.jinja in the repository (5,723 characters). Tool-calling format 25, the card names the parser to use in two runtimes, step3p5 in vLLM (with auto tool choice) and in SGLang, and both ship Step parsers in a release. Trained tool calling 20, the card presents tool orchestration as a main use, with multi-turn results, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output for the weights. Reasoning control 10, the template has a reasoning_effort setting and keeps reasoning_content, and the card names the step3p5 reasoning parser for vLLM and SGLang, which returns the reasoning apart from the answer. Context 10, 256K tokens per the card, and 262,144 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Risk Qwen3-VL-2B-Instruct +10

Qwen3-VL-2B-Instruct 55

Safetensors and GGUF only and no code in the repositories, so the FP8 card's trust_remote_code flag runs nothing (25). Files in the Qwen organisation with a checksum on every file (15). No safety evaluation at all (0). No guidance for agent use, which matters for a model sold as a GUI agent (0). Apache 2.0 carries none of the licence risks (15). No security contact, disclosure policy or public advisories found for Qwen (0), and Alibaba's group-wide security centre wasn't checked.

Step 3.7 Flash 45

File safety 15, safetensors and GGUF only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the stepfun-ai organisation, which the card's StepFun platform and model page belong to (10). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations section and gives no guidance on prompt injection, instruction priority, refusals or safeguards. Licence risk 15, Apache 2.0 has no use policy, threshold or change clause. Security programme 0, no way to report a flaw on the card, and our StepFun API listing found no security.txt, bug bounty or disclosure policy. 15 + 15 + 0 + 0 + 15 + 0 = 45.

Documentation and upkeep Step 3.7 Flash +8

Qwen3-VL-2B-Instruct 31

The card misses limitations, languages and a cut-off (11). Training data is described only in the technical report, with no cut-off (5). The last change to code that runs it was the qwen-vl-utils fix of 4 January 2026, and the weights and cards haven't changed since November 2025 (5). Qwen answered none of the 13 Hugging Face discussions that aren't pull requests (0), and GitHub issues weren't counted. Earlier versions kept in their own repositories without notes (5). A report waits without a reply and the GGUF card's example names a file the repository doesn't hold (5). 11 + 5 + 5 + 0 + 5 + 5 = 31.

Step 3.7 Flash 39

Model card 14, Intended use, the architecture, the parameters, the context and the language (in the metadata) are on the card. Training data 0, Nothing on the card about the training data. Last change 10, the last commit, on 3 June 2026, fixed the modelling code, 160 days before this check and within 180. Responsiveness 0, none of the 11 most recent discussions that aren't pull requests (29 May to 24 June 2026) has a reply from a stepfun-ai member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, Step-3.5-Flash stays in its own repositories and 3.7 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the context, and June commits fixed the modelling code. 14 + 0 + 10 + 0 + 5 + 10 = 39.

Score by category

CategoryWeight this runQwen3-VL-2B-InstructStep 3.7 FlashEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259570Qwen3-VL-2B-Instruct +25
Risk20%205545Qwen3-VL-2B-Instruct +10
Agent interface10%106085Step 3.7 Flash +25
Documentation and upkeep10%103139Step 3.7 Flash +8
Negative events≤1500
TotalC 61/100C 59.8/100

Facts side by side

FactQwen3-VL-2B-InstructStep 3.7 Flash
KindOpen-weight modelOpen-weight model
VendorAlibaba (Qwen team)StepFun
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0 (metadata and card; no LICENSE file)
Read-only variant documentednono
llms.txtnono
Last release2025-11-012026-06-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.8/5 (4)none

Verdicts

Qwen3-VL-2B-Instruct

The smallest Qwen3-VL cousin, for reading screenshots, documents, charts and video on a laptop or edge box, running in about 2 GB from Alibaba's Q4_K_M GGUF in every major runtime under plain Apache 2.0. Qwen hasn't answered repository questions or published safety work, so keep a human or a check in the loop before it drives a GUI.

Step 3.7 Flash

A capable open agent model with a clean licence, every kind of build and four released runtimes. Two things hold it back: it's a little too big for a 128 GB machine at 4 bits, whatever the card says, and StepFun has gone quiet on the repository since June. No safety results, limitations or data description.

Before you call either

Qwen3-VL-2B-Instruct

  1. Start it with llama-server -hf Qwen/Qwen3-VL-2B-Instruct-GGUF:Q4_K_M --jinja -c 32768, or ollama run qwen3-vl:2b-instruct
  2. In Ollama the plain qwen3-vl:2b tag is the Thinking edition, so name 2b-instruct
  3. With the GGUF, load the mmproj vision file too, or images won't be read
  4. Parse tool calls as JSON inside <tool_call> tags, or use SGLang's --tool-call-parser qwen
  5. Use the card's sampling, temperature=0.7, top_p=0.8, top_k=20, presence_penalty=1.5 for vision and temperature=1.0, top_p=1.0, top_k=40, presence_penalty=2.0 for text
  6. Validate JSON output yourself, since structured output isn't documented
  7. vLLM needs 0.11.0 or later and Transformers 4.57.0 or later

Step 3.7 Flash

  1. On a 128 GB machine the 4-bit GGUF won't fit with a working context. Use StepFun's API or a provider, or a server
  2. On vLLM or SGLang pass --tool-call-parser step3p5 --reasoning-parser step3p5
  3. The card's commands pass trust-remote-code. Released Transformers 5.22.2 has the model built in if you'd rather not run the repository's code
  4. For llama.cpp load the mmproj file from StepFun's GGUF repository for image input
  5. StepFun's API has two hosts. Use the one where your key was issued, api.stepfun.ai or api.stepfun.com
  6. The same model is on our StepFun API listing, with prices and terms

Questions

Which is better for AI agents, Qwen3-VL-2B-Instruct or Step 3.7 Flash?

Qwen3-VL-2B-Instruct scores 61 (C) on agent readiness against Step 3.7 Flash's 59.8 (C), and leads in 2 of 4 scored categories. Step 3.7 Flash leads on agent interface and documentation and upkeep.

Other comparisons with Qwen3-VL-2B-Instruct or Step 3.7 Flash

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.