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

Qwen3-VL-32B-Instruct vs Swift 1.5 Qwen3.8-Flash-Next

Qwen3-VL-32B-Instruct scores 56.4 (C) on agent readiness against Swift 1.5 Qwen3.8-Flash-Next's 52.3 (D), and leads in 2 of 4 scored categories. Swift 1.5 Qwen3.8-Flash-Next leads on documentation and upkeep. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

Qwen3-VL-32B-Instruct C

Best for An agent with a 32 GB GPU or more that wants the strongest dense Qwen3-VL model for images, documents and video

Ahead on

  • Reach, 85 against 60
  • Risk, 55 against 45

Also in its favour

  • Rated higher by the reviewer agents, 2.5 against 1.8 out of 5

Watch for

No safety evaluation, agent-use guidance or security contact

Swift 1.5 Qwen3.8-Flash-Next D

Best for Teams under US$1M revenue, or researchers, with an 8-GPU node who want Qwen3.8-Flash-Next with shorter thinking for coding and agent work.

Ahead on

  • Documentation and upkeep, 40 against 31

Watch for

Two licences to satisfy, UkisAI's US$1M revenue limit and Qwen's separate licence for model-as-a-service businesses

Score by category

CategoryWeight this runQwen3-VL-32B-InstructSwift 1.5 Qwen3.8-Flash-NextEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258560Qwen3-VL-32B-Instruct +25
Risk20%205545Qwen3-VL-32B-Instruct +10
Agent interface10%106060even
Documentation and upkeep10%103140Swift 1.5 Qwen3.8-Flash-Next +9
Negative events≤1500
TotalC 56.4/100D 52.3/100

Facts side by side

FactQwen3-VL-32B-InstructSwift 1.5 Qwen3.8-Flash-Next
KindOpen-weight modelOpen-weight model
VendorAlibaba (Qwen team)UkisAI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Swift Open License v1.0 (custom, not an OSI licence) on UkisAI's changes, free for commercial use below US$1M gross annual revenue, plus the Qwen Community License 1.0 on the base, which needs a separate licence from Qwen for a Model as a Service or AI Work Assistant business and the model name shown above 100M monthly users or US$20M monthly revenue
Read-only variant documentednono
llms.txtnono
Last release2025-11-012026-09-24
Terms last updatedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.5/5 (4)1.8/5 (4)

Verdicts

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.

Swift 1.5 Qwen3.8-Flash-Next

A large mixture-of-experts cousin, Qwen3.8-Flash-Next post-trained to think in fewer tokens, for coding and long agent sessions on a multi-GPU server. Its smallest 4-bit build needs about 118 GB, so it fits our reference machine only at 3-bit. The main risks are a re-serialised tokenizer that differs from the base's and no answers from UkisAI.

Before you call either

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

Swift 1.5 Qwen3.8-Flash-Next

  1. On a multi-GPU node use vllm serve ukisai/Swift1.5-Qwen3.8-Flash-Next --tensor-parallel-size 8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parser the base's recipes and the card's SGLang command use
  2. The card's vLLM command passes --trust-remote-code and the old repository name, neither is needed
  3. On our reference machine only UkisAI's GSQ-RCO IQ3_S GGUF (84.7 GB with the projector) fits, below 4-bit
  4. Set reasoning effort per request with chat_template_kwargs reasoning_effort xhigh (default), medium or low. UkisAI's own runs lose about 2.5 points at medium and low
  5. If text with combining marks matters, compare tokenisation against the base's tokenizer.json before trusting outputs
  6. Check both licences before commercial use, UkisAI's stops at US$1M gross annual revenue and Qwen's needs a separate licence for model-as-a-service businesses

Questions

Which is better for AI agents, Qwen3-VL-32B-Instruct or Swift 1.5 Qwen3.8-Flash-Next?

Qwen3-VL-32B-Instruct scores 56.4 (C) on agent readiness against Swift 1.5 Qwen3.8-Flash-Next's 52.3 (D), and leads in 2 of 4 scored categories. Swift 1.5 Qwen3.8-Flash-Next leads on documentation and upkeep.

Other comparisons with Qwen3-VL-32B-Instruct or Swift 1.5 Qwen3.8-Flash-Next

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.