Qwen3.6-35B-A3B vs Qwen3-VL-32B-Instruct

Qwen3.6-35B-A3B

A fast mixture-of-experts cousin with 3B active parameters for coding and tool calling, with image and video input, in every major runtime under plain Apache 2.0. Ollama's 4-bit build needs about 28 GB. The main risk is that nobody at Alibaba maintains it, with no safety results, no security contact and no replies to tool-calling reports.

Qwen3-VL-32B-Instruct

The largest dense Qwen3-VL cousin, for harder work on screenshots, documents, charts and video, needing about 25 GB from Alibaba's Q4_K_M GGUF with its vision file, in every major runtime under plain Apache 2.0. It has no thinking mode or published safety work, and only one provider was found serving it, so plan to run it yourself.

Qwen3.6-35B-A3B

1. Start it with ollama run qwen3.6:35b (Q4_K_M, 23 to 24 GB on disk, about 28 GB in memory)
2. On the reference machine use vllm serve Qwen/Qwen3.6-35B-A3B --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, BF16, since vLLM doesn't document FP8 compute on gfx1151
3. Use the qwen3_coder tool-call parser and the qwen3 reasoning parser in vLLM 0.19.0 or SGLang 0.5.10 or later
4. Thinking is on by default and /nothink isn't supported, so pass enable_thinking as false in chat_template_kwargs for short tasks, or preserve_thinking as true to keep earlier reasoning
5. Card sampling for thinking is temperature 1.0, top_p 0.95, top_k 20, presence_penalty 1.5, and for non-thinking temperature 0.7, top_p 0.8
6. Keep at least 128K of context as the card advises, and turn on YaRN only beyond 262,144 tokens
7. Validate JSON output yourself or use the runtime's guided decoding, since the model card documents none

Qwen3-VL-32B-Instruct

1. Start it with llama-server -hf Qwen/Qwen3-VL-32B-Instruct-GGUF:Q4_K_M --jinja -c 32768, or ollama run qwen3-vl:32b-instruct
2. In Ollama the plain qwen3-vl:32b tag is the Thinking edition, so name 32b-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
8. If you pulled the FP8 build before 22 October 2025, pull it again, since the earlier files were the Thinking edition's