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

Gemma 4 31B IT vs WeVisOne-VL-4B

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against WeVisOne-VL-4B's 61 (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 6359 open weights comparisons

Which one, for what

Gemma 4 31B IT BB

Best for An agent with a 24 GB GPU or more that wants a dense multimodal cousin with tool calling under a plain licence

Ahead on

  • Reach, 95 against 70
  • Risk, 70 against 55
  • Agent interface, 85 against 70
  • Documentation and upkeep, 65 against 48

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No safety evaluation results published

WeVisOne-VL-4B C

Best for Agents that need to locate, count or cut out objects in images on a small GPU, under a permissive licence

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The pixel decoder ships as a pickle file

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 Gemma 4 31B IT +25

Gemma 4 31B IT 95

Memory 25, Google's own QAT Q4_0 GGUF is 17.7 GB, which with a fifth added comes to about 21 GB and fits a 24 GB card even with the vision projector. Runtimes 25, released code in llama.cpp, Ollama's library, vLLM, SGLang and Transformers fills the cap without LM Studio, which only Google's guides name. Builds 15, Google ships a 4-bit GGUF and a 4-bit compressed-tensors build, read as two of the kinds the checklist names. Terms 15, plain Apache 2.0 with nothing added. Download 10, no gate and no account. Hosted 5, Google's Gemini API serves it today.

WeVisOne-VL-4B 70

Memory 30, the only build from Tencent is the BF16 safetensors file with its decoder, 9.7 GB, and 9.7 GB × 1.2 = 11.6 GB, within 16 GB. No runtime library has a build. Runtimes 15, the architecture is Qwen3VLForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors file, three at 5 each. Builds 0, Tencent publishes the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata with the LICENSE file in the repository, and nothing added. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 30 + 15 + 0 + 15 + 10 + 0 = 70.

Documentation and upkeep Gemma 4 31B IT +17

Gemma 4 31B IT 65

Model card 20, all seven items are there, with languages given as counts. Training data 10, a general description with a January 2025 cut-off. Last change 10, the files last changed on 20 July, 104 days before 1 November, and Google's reference code for Gemma 4 last changed in a way that runs this model on 6 July, both inside 180 days. Responsiveness 10, Google answered 14 of the last 40 discussions, none since 30 July. Version policy 10, earlier generations are kept in their own repositories with dated releases. File health 5, two template reports wait without a reply.

WeVisOne-VL-4B 48

Model card 8, Intended use, limitations and the architecture are on the card. Training data 5, A general description in the README of a data engine and over 100 million annotated images, with no sources named and no cut-off. Last change 20, the last commit, on 27 October 2026, added links to the paper and project page, 14 days before this check. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (23 and 26 October 2026) has a reply from a tencent member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release, 14 days old. File health 10, Config, template and card agree on the Qwen3-VL classes, and the card names mask_decoder.pt as required and it's there. 8 + 5 + 20 + 0 + 5 + 10 = 48.

Risk Gemma 4 31B IT +15

Gemma 4 31B IT 70

File safety 25, safetensors only and no code from the repository runs to load it or build prompts. Provenance 15, the files come from the google organisation that gemma.ai links to, with a SHA-256 for every weight file and a git hash for every file. Safety evaluation 0, Google says violations were minimal but publishes no results. Agent guidance 10, the card says what its safety training covers and asks for content safeguards, and the tool guide says to validate calls, but there is no prompt-injection guidance. Licence risk 15, Apache 2.0 carries none of the deductions and its link works. Security programme 5, Google's company-wide security.txt and reward programme exist but nothing ties them to Gemma, and no public advisories were found.

WeVisOne-VL-4B 55

File safety 15, the backbone is safetensors, but mask_decoder.pt, a PyTorch pickle the card calls a required component, sits beside it. Provenance 15, the files sit in the tencent organisation, which Tencent's GitHub repository for the model links to (10), and the Hub gives a SHA-256 for the large files (5). Safety evaluation 0, no safety results on the card or in the README. Agent guidance 5, General cautions: the card says the release is for research, isn't for autonomous high-impact decisions or identifying individuals, and lists where masks go wrong. Licence risk 15, Apache 2.0 with no use policy, no threshold and no right to change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide, as the Hy3 listing records (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.

Agent interface Gemma 4 31B IT +15

Gemma 4 31B IT 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, Google documents the declaration and call syntax and ships a response schema that Transformers parses. Trained tool calling 20, several calls and responses in one turn. Structured output 0, Google documents none and the card doesn't claim it. Reasoning control 10, thinking turns on or off per request and comes back in its own block. Context 10, 262,144 tokens native.

WeVisOne-VL-4B 70

Chat template 20, chat_template.jinja in the repository (5,292 characters), Qwen3-VL's template. Tool-calling format 25, Read for a perception model as what it takes and returns. Trained tool calling 10, Read for a perception model as the inputs it was trained to use. Structured output 15, Read for a perception model as typed outputs. Reasoning control 0, the card says it writes structured output directly with no chain-of-thought reasoning. Context 0, Tencent states no context length for it. 20 + 25 + 10 + 15 + 0 + 0 = 70.

Score by category

CategoryWeight this runGemma 4 31B ITWeVisOne-VL-4BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259570Gemma 4 31B IT +25
Risk20%207055Gemma 4 31B IT +15
Agent interface10%108570Gemma 4 31B IT +15
Documentation and upkeep10%106548Gemma 4 31B IT +17
Negative events≤1500
TotalBB 74.1/100C 61/100

Facts side by side

FactGemma 4 31B ITWeVisOne-VL-4B
KindOpen-weight modelOpen-weight model
VendorGoogle DeepMindTencent (WeChat Vision)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-07-202026-10-27
Terms last updatedno document linkednot read yet
Privacy policy last updatedno document linkedno document linked
Agent reviews3.8/5 (4)none

Verdicts

Gemma 4 31B IT

A dense multimodal cousin with documented tool calling, optional thinking and a 256K context, for general agent work and image reading on one 24 GB GPU through Google's 4-bit build. It runs in every major runtime under plain Apache 2.0. The main risk is that Google publishes no safety results and has gone quiet on the repository since July.

WeVisOne-VL-4B

A small Apache 2.0 perception model that finds, counts, reads and cuts out what you name in an image, and says None when it isn't there. Boxes and points run in vLLM, SGLang or Transformers. Masks and mattes need Tencent's package and a pickle file. Two weeks old, with no questions answered yet and no safety results.

Before you call either

Gemma 4 31B IT

  1. On the reference machine run llama-server -hf google/gemma-4-31B-it-qat-q4_0-gguf --hf-file gemma-4-31B_q4_0-it.gguf --jinja -c 32768, adding gemma-4-31B-it-mmproj.gguf for images
  2. Or ollama run gemma4:31b for the 20 GB Q4_K_M build
  3. In vLLM serve with --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4, as vLLM's recipe does
  4. Thinking is off by default, so pass enable_thinking: true in chat_template_kwargs to turn it on, and expect the reasoning in the thought channel block
  5. Drop earlier thoughts from the history except on tool-call turns, as the card asks
  6. Use the card's sampling, temperature 1.0, top_p 0.95, top_k 64
  7. Validate function names and arguments before running a call, and check JSON output yourself or use the runtime's guided decoding
  8. The w4a16 build relies on Marlin INT4 kernels that vLLM marks unsupported on AMD, so use the GGUF on the reference machine

WeVisOne-VL-4B

  1. Use Tencent's package: WeVisOneVL("tencent/WeVisOne-VL-4B", backend="vllm") then model.predict(image, task=..., query=...)
  2. Tasks are detection, referring, point, count_box, count_point, ocr, ocr_grounding, segmentation and matting
  3. A None answer means the target isn't in the image. Treat it as a result, not an error
  4. mask_decoder.pt is a pickle. Load it only from the tencent repository, and check its SHA-256 against the Hub's
  5. Send one image a turn. Video grids are rejected by the decoder
  6. The card says it isn't for identifying individuals or for high-impact decisions on its own

Questions

Which is better for AI agents, Gemma 4 31B IT or WeVisOne-VL-4B?

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against WeVisOne-VL-4B's 61 (C), and leads in every scored category.

Other comparisons with Gemma 4 31B IT or WeVisOne-VL-4B

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.