Head to head · Open-weight models you run yourself · October 2026 research run
Granite 4.2 30B vs Qwen3.5-2B
Granite 4.2 30B scores 61 (C) on agent readiness against Qwen3.5-2B's 50.5 (D), and leads in 3 of 4 scored categories. 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 that want a documented, signed, Apache 2.0 reasoning model with tool calling on a 24 GB card
Ahead on
- Reach, 90 against 80
- Agent interface, 85 against 60
- Documentation and upkeep, 87 against 37
Watch for
No safety results published for it
Best for Builders who want a cheap local helper or fine-tuning base for narrow tasks and image reading on a laptop, small GPU or CPU
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No quantised build from Alibaba, and only one inference provider
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 Granite 4.2 30B +50
Granite 4.2 30B 87
Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (30B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 30B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 15, the last commit to the repository was on 4 September 2026, 67 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (28 August to 3 November 2026), 3 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 30B stays in its own repository and 4.2 came out in new ones. File health 10, Config, template and card agree on the architecture, the 131,072-token context and the thinking switch. 17 + 20 + 15 + 20 + 5 + 10 = 87.
Qwen3.5-2B 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, 247 days before 4 November, within a year (5). No Qwen member has answered any of the 6 discussions that aren't pull requests (0). Qwen3-1.7B 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 Granite 4.2 30B +25
Granite 4.2 30B 85
Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort. Tool-calling format 25, the card has tool-calling sections for vLLM and SGLang, declares tools with OpenAI's function schema and names the parser to use, qwen3_coder, which both runtimes ship in the released versions read. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so it renders several calls in one turn, and the card names tool calling and agentic workflows as what it's best for. Structured output 0, the card doesn't document JSON or JSON Schema output or how to ask for it. Reasoning control 10, the card documents thinking on by default, non-thinking and low-effort modes per request through the template (enable_thinking and low_effort), with the reasoning returned apart from the answer. Context 10, 131,072 tokens natively per the card and config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.
Qwen3.5-2B 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.
Reach Granite 4.2 30B +10
Granite 4.2 30B 90
Memory 25, IBM's own 4-bit MLX build granite-4.2-30b-q4-mlx is 16.47 GB, and 16.47 GB × 1.2 = 19.8 GB, which fits 24 GB but not 16 GB. Its Q4_0 GGUF is 16.58 GB and Ollama's library build granite4.2:30b 18 GB, the same band. Runtimes 25, Released versions run the granite architecture in llama.cpp (granite, b12242), vLLM (GraniteForCausalLM in the v0.33.0 registry), SGLang (granite.py at v0.5.23), Transformers (v5.22.2) and Ollama (its own granite4.2 library entry, 30b tag). Builds 15, IBM publishes FP8, MXFP4 and NVFP4 safetensors builds, a GGUF repository with Q4_0 to Q8_0 and BF16 files, and 4-bit, 8-bit and BF16 MLX builds, so quantised builds at two precisions or more. Terms 15, Apache 2.0, an OSI-approved licence, with no use policy or other terms added on the card. Download 10, the Hub API reports gated false for the BF16, FP8, MXFP4, NVFP4, GGUF and MLX repositories, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps one inference provider (DeepInfra, live), short of the two the line needs. 25 + 25 + 15 + 15 + 10 + 0 = 90.
Qwen3.5-2B 80
Memory earns the full 30, since LM Studio's Q4_K_M GGUF with its vision projector is 1.94 GB, about 2.3 GB with the fifth added (Ollama's Q4_K_M build was 1.9 GB on 21 October). Alibaba publishes no quantised 2B, so builds scores 0. Runtimes reach the 25 cap, with llama.cpp b11963 and Ollama through the build it pins re-read today. Apache 2.0 with nothing added gives terms 15 and the ungated download 10. Hosted too scores 0, as only Featherless AI is in the Hub's provider mapping and the line needs two. 30+25+0+15+10+0 = 80.
Score by category
| Category | Weight this run | Granite 4.2 30B | Qwen3.5-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 90 | 80 | Granite 4.2 30B +10 |
| Risk | 20%20 | 55 | 55 | even |
| Agent interface | 10%10 | 85 | 60 | Granite 4.2 30B +25 |
| Documentation and upkeep | 10%10 | 87 | 37 | Granite 4.2 30B +50 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | D 50.5/100 |
Facts side by side
| Fact | Granite 4.2 30B | Qwen3.5-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | IBM | Alibaba (Qwen team) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-09-04 | 2026-03-02 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 3/5 (4) |
Verdicts
Granite 4.2 30B
IBM's largest reasoning cousin, with the same strengths as the 3B. It runs in every runtime we count from IBM's own builds on a 24 GB card, is signed, plain Apache 2.0, and comes with a disclosure of its training data. No safety results are published and structured output isn't documented.
Qwen3.5-2B
A small vision-language model for prototypes, fine-tuning and narrow local steps such as tool calls, tagging or reading an image. It runs in about 2 GB at 4 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
Granite 4.2 30B
- Start it with
ollama run granite4.2:30b, orllama-server -hf ibm-granite/granite-4.2-30b-GGUF:Q4_K_M --jinja - With vLLM 0.32.0 or later leave out
--reasoning-parser-plugin, since the parser is built in, and use--tool-call-parser qwen3_coder - Thinking is on by default. Pass
enable_thinkingfalse to turn it off orlow_efforttrue for short reasoning - The context is 131,072 tokens. The card's 512K extension isn't documented
- Validate JSON output yourself, since structured output isn't documented
- IBM recommends Granite Guardian beside it to flag risky inputs and outputs
Qwen3.5-2B
- Smallest start is
ollama run qwen3.5:2b-q4_K_M(1.9 GB); plainqwen3.5:2bpulls the 2.7 GB Q8_0 build - Full precision
vllm serve Qwen/Qwen3.5-2B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder - 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 qwen3in vLLM or SGLang to split the reasoning out - 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.0for text without thinking - Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
- Validate any JSON it returns, since structured output isn't documented
Questions
Which is better for AI agents, Granite 4.2 30B or Qwen3.5-2B?
Granite 4.2 30B scores 61 (C) on agent readiness against Qwen3.5-2B's 50.5 (D), and leads in 3 of 4 scored categories.
Other comparisons with Granite 4.2 30B or Qwen3.5-2B
- Agents-A1-4B vs Granite 4.2 30B
- Agents-A1-4B vs Qwen3.5-2B
- Apertus v1.5 8B vs Granite 4.2 30B
- Apertus v1.5 8B vs Qwen3.5-2B
- Apodex-1.1-mini vs Granite 4.2 30B
- Apodex-1.1-mini vs Qwen3.5-2B
- Arete-27B vs Granite 4.2 30B
- Arete-27B vs Qwen3.5-2B
- BigBang-v1 vs Granite 4.2 30B
- BigBang-v1 vs Qwen3.5-2B
- Carbon-X vs Granite 4.2 30B
- Carbon-X vs Qwen3.5-2B
- Cosmos-Reason2-2B vs Granite 4.2 30B
- Cosmos-Reason2-2B vs Qwen3.5-2B
- Darwin-36B-Opus vs Granite 4.2 30B
- Darwin-36B-Opus vs Qwen3.5-2B
- DeepSeek-V3.2 vs Granite 4.2 30B
- DeepSeek-V3.2 vs Qwen3.5-2B
- DeepSeek V4.1 Flash vs Granite 4.2 30B
- DeepSeek V4.1 Flash vs Qwen3.5-2B
- DeepSeek-V4-Flash-0731 vs Granite 4.2 30B
- DeepSeek-V4-Flash-0731 vs Qwen3.5-2B
- DiffusionGemma 26B A4B IT vs Granite 4.2 30B
- DiffusionGemma 26B A4B IT vs Qwen3.5-2B
- Gemma 4 12B IT vs Granite 4.2 30B
- Gemma 4 12B IT vs Qwen3.5-2B
- Gemma 4 26B A4B IT vs Granite 4.2 30B
- Gemma 4 26B A4B IT vs Qwen3.5-2B
- Gemma 4 31B IT vs Granite 4.2 30B
- Gemma 4 31B IT vs Qwen3.5-2B
- Gemma 4 E2B IT vs Granite 4.2 30B
- Gemma 4 E2B IT vs Qwen3.5-2B
- Gemma 4 E4B IT vs Granite 4.2 30B
- Gemma 4 E4B IT vs Qwen3.5-2B
- GLM-4.5-Air vs Granite 4.2 30B
- GLM-4.5-Air vs Qwen3.5-2B
- GLM-4.7-Flash vs Granite 4.2 30B
- GLM-4.7-Flash vs Qwen3.5-2B
- GLM-5.3-Flash vs Granite 4.2 30B
- GLM-5.3-Flash vs Qwen3.5-2B
- GLM-5.3 vs Granite 4.2 30B
- GLM-5.3 vs Qwen3.5-2B
- gpt-oss-120b vs Granite 4.2 30B
- gpt-oss-120b vs Qwen3.5-2B
- gpt-oss-20b vs Granite 4.2 30B
- gpt-oss-20b vs Qwen3.5-2B
- Granite 4.2 30B vs Granite 4.2 3B
- Granite 4.2 30B vs Granite 4.2 8B
- Granite 4.2 30B vs Hy-Memory-30B-A3B
- Granite 4.2 30B vs Hy3
- Granite 4.2 30B vs Inkling
- Granite 4.2 30B vs Inkling-Small
- Granite 4.2 30B vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Granite 4.2 30B vs Kimi K3
- Granite 4.2 30B vs Kimi K3.1 Pro
- Granite 4.2 30B vs Kolibri-1
- Granite 4.2 30B vs Kronos
- Granite 4.2 30B vs Laguna M.1
- Granite 4.2 30B vs Laguna S 2.1
- Granite 4.2 30B vs Laguna XS 2.1
- Granite 4.2 30B vs LBS-27B
- Granite 4.2 30B vs LFM2.5-2.6B
- Granite 4.2 30B vs LFM3-1.7B
- Granite 4.2 30B vs LFM3-Audio-2B
- Granite 4.2 30B vs LFM3-Omni-2B
- Granite 4.2 30B vs LFM3-VL-2B
- Granite 4.2 30B vs Ling-3.0-tiny
- Granite 4.2 30B vs Ling-3.1-flash-1019
- Granite 4.2 30B vs MiMo-V2.6 Distill Qwen 9B
- Granite 4.2 30B vs MiniCPM-o 4.5
- Granite 4.2 30B vs MiniCPM-V 4.7 1B
- Granite 4.2 30B vs MiniCPM-V 4.7 35B-A3B
- Granite 4.2 30B vs MiniCPM5-2B
- Granite 4.2 30B vs MiniMax-M2.5
- Granite 4.2 30B vs MiniMax-M2.7
- Granite 4.2 30B vs MiniMax-M3.1-Flash
- Granite 4.2 30B vs Mistral Large 4
- Granite 4.2 30B vs Muse Glimmer 30B
- Granite 4.2 30B vs Nanbeige4.3-33B
- Granite 4.2 30B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Granite 4.2 30B vs Nemotron 3.5 Lightning 30B A3B
- Granite 4.2 30B vs Nemotron 3 Nano 30B A3B
- Granite 4.2 30B vs Nemotron 3 Nano 4B
- Granite 4.2 30B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Granite 4.2 30B vs Nemotron 3 Super 120B A12B
- Granite 4.2 30B vs Nemotron 3 Ultra 550B A55B
- Granite 4.2 30B vs occamy-1.0
- Granite 4.2 30B vs Olmo 3 7B Think
- Granite 4.2 30B vs Ornith-1.5-122B
- Granite 4.2 30B vs Ornith-1.5-35B-A3B
- Granite 4.2 30B vs Ornith-1.5-397B
- Granite 4.2 30B vs Ornith-1.5-9B
- Granite 4.2 30B vs Qwen-AgentWorld-35B-A3B
- Granite 4.2 30B vs Qwen3-30B-A3B-Instruct-2507
- Granite 4.2 30B vs Qwen3-4B-Instruct-2507
- Granite 4.2 30B vs Qwen3.5-0.8B
- Granite 4.2 30B vs Qwen3.5-122B-A10B
- Granite 4.2 30B vs Qwen3.5-397B-A17B
- Granite 4.2 30B vs Qwen3.5-4B
- Granite 4.2 30B vs Qwen3.5-9B
- Granite 4.2 30B vs Qwen3.6-27B
- Granite 4.2 30B vs Qwen3.6-35B-A3B
- Granite 4.2 30B vs Qwen3.8-27B
- Granite 4.2 30B vs Qwen3.8-Flash-Next
- Granite 4.2 30B vs Qwen3-Coder-30B-A3B-Instruct
- Granite 4.2 30B vs Qwen3-Coder-Next
- Granite 4.2 30B vs Qwen3-Omni-30B-A3B-Instruct
- Granite 4.2 30B vs Qwen3-VL-2B-Instruct
- Granite 4.2 30B vs Qwen3-VL-30B-A3B-Instruct
- Granite 4.2 30B vs Qwen3-VL-32B-Instruct
- Granite 4.2 30B vs Qwen3-VL-4B-Instruct
- Granite 4.2 30B vs Qwen3-VL-8B-Instruct
- Granite 4.2 30B vs Qwopus3.8-27B-Flash-V2
- Granite 4.2 30B vs Recursive Flint
- Granite 4.2 30B vs Ripple-65B Preview
- Granite 4.2 30B vs SmolLM3-3B
- Granite 4.2 30B vs Spark-X2.6-4B
- Granite 4.2 30B vs Swift 1.5 Qwen3.8-27B
- Granite 4.2 30B vs Swift 1.5 Qwen3.8-Flash-Next
- Granite 4.2 30B vs ThinkingCap (Qwen3.8 27B)
- Granite 4.2 30B vs Baidu Unlimited-OCR-2
- Granite 4.2 3B vs Qwen3.5-2B
- Granite 4.2 8B vs Qwen3.5-2B
- Hy-Memory-30B-A3B vs Qwen3.5-2B
- Hy3 vs Qwen3.5-2B
- Inkling-Small vs Qwen3.5-2B
- Inkling vs Qwen3.5-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Qwen3.5-2B
- Kimi K3.1 Pro vs Qwen3.5-2B
- Kimi K3 vs Qwen3.5-2B
- Kolibri-1 vs Qwen3.5-2B
- Kronos vs Qwen3.5-2B
- Laguna M.1 vs Qwen3.5-2B
- Laguna S 2.1 vs Qwen3.5-2B
- Laguna XS 2.1 vs Qwen3.5-2B
- LBS-27B vs Qwen3.5-2B
- LFM2.5-2.6B vs Qwen3.5-2B
- LFM3-1.7B vs Qwen3.5-2B
- LFM3-Audio-2B vs Qwen3.5-2B
- LFM3-Omni-2B vs Qwen3.5-2B
- LFM3-VL-2B vs Qwen3.5-2B
- Ling-3.0-tiny vs Qwen3.5-2B
- Ling-3.1-flash-1019 vs Qwen3.5-2B
- MiMo-V2.6 Distill Qwen 9B vs Qwen3.5-2B
- MiniCPM-o 4.5 vs Qwen3.5-2B
- MiniCPM-V 4.7 1B vs Qwen3.5-2B
- MiniCPM-V 4.7 35B-A3B vs Qwen3.5-2B
- MiniCPM5-2B vs Qwen3.5-2B
- MiniMax-M2.5 vs Qwen3.5-2B
- MiniMax-M2.7 vs Qwen3.5-2B
- MiniMax-M3.1-Flash vs Qwen3.5-2B
- Mistral Large 4 vs Qwen3.5-2B
- Muse Glimmer 30B vs Qwen3.5-2B
- Nanbeige4.3-33B vs Qwen3.5-2B
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs Qwen3.5-2B
- Nemotron 3.5 Lightning 30B A3B vs Qwen3.5-2B
- Nemotron 3 Nano 30B A3B vs Qwen3.5-2B
- Nemotron 3 Nano 4B vs Qwen3.5-2B
- Nemotron 3 Nano Omni 30B A3B Reasoning vs Qwen3.5-2B
- Nemotron 3 Super 120B A12B vs Qwen3.5-2B
- Nemotron 3 Ultra 550B A55B vs Qwen3.5-2B
- occamy-1.0 vs Qwen3.5-2B
- Olmo 3 7B Think vs Qwen3.5-2B
- Ornith-1.5-122B vs Qwen3.5-2B
- Ornith-1.5-35B-A3B vs Qwen3.5-2B
- Ornith-1.5-397B vs Qwen3.5-2B
- Ornith-1.5-9B vs Qwen3.5-2B
- Qwen-AgentWorld-35B-A3B vs Qwen3.5-2B
- Qwen3-30B-A3B-Instruct-2507 vs Qwen3.5-2B
- Qwen3-4B-Instruct-2507 vs Qwen3.5-2B
- Qwen3.5-0.8B vs Qwen3.5-2B
- Qwen3.5-122B-A10B vs Qwen3.5-2B
- Qwen3.5-2B vs Qwen3.5-397B-A17B
- Qwen3.5-2B vs Qwen3.5-4B
- Qwen3.5-2B vs Qwen3.5-9B
- Qwen3.5-2B vs Qwen3.6-27B
- Qwen3.5-2B vs Qwen3.6-35B-A3B
- Qwen3.5-2B vs Qwen3.8-27B
- Qwen3.5-2B vs Qwen3.8-Flash-Next
- Qwen3.5-2B vs Qwen3-Coder-30B-A3B-Instruct
- Qwen3.5-2B vs Qwen3-Coder-Next
- Qwen3.5-2B vs Qwen3-Omni-30B-A3B-Instruct
- Qwen3.5-2B vs Qwen3-VL-2B-Instruct
- Qwen3.5-2B vs Qwen3-VL-30B-A3B-Instruct
- Qwen3.5-2B vs Qwen3-VL-32B-Instruct
- Qwen3.5-2B vs Qwen3-VL-4B-Instruct
- Qwen3.5-2B vs Qwen3-VL-8B-Instruct
- Qwen3.5-2B vs Qwopus3.8-27B-Flash-V2
- Qwen3.5-2B vs Recursive Flint
- Qwen3.5-2B vs Ripple-65B Preview
- Qwen3.5-2B vs SmolLM3-3B
- Qwen3.5-2B vs Spark-X2.6-4B
- Qwen3.5-2B vs Swift 1.5 Qwen3.8-27B
- Qwen3.5-2B vs Swift 1.5 Qwen3.8-Flash-Next
- Qwen3.5-2B vs ThinkingCap (Qwen3.8 27B)
- Qwen3.5-2B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/granite-4-2-30b-vs-qwen3-5-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/granite-4-2-30b.json·/api/v1/tools/qwen3-5-2b.json - From a terminal
anchor compare granite-4-2-30b qwen3-5-2b(the CLI) - Over MCP
compare_tools {"a": "granite-4-2-30b", "b": "qwen3-5-2b"}at/mcp, no key