WeChat Open-Sources WeVisOne-VL: Detection, Masks and Matting in a Single VLM

The WeChat team has released WeVisOne-VL, an open vision-language model that combines detection, segmentation, object counting, OCR and matting. It can localize a target at any level of precision, from a point or a box to a mask or an alpha matte. The mechanics are simple. A lightweight pixel decoder is attached to the VLM through a special <OBJ> token, and the output is produced by ordinary next-token prediction. The authors claim leading results on more than 30 benchmarks. • Training: three SFT stages, then RL on a mixture of tasks • The model refuses to answer if the object is not in the image • Code and weights are open

AI-processed from Hugging Face Daily Papers; edited by Hamidun News
WeChat Open-Sources WeVisOne-VL: Detection, Masks and Matting in a Single VLM
Source: Hugging Face Daily Papers. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceHugging Face Daily Papers ↗
Editor-in-Chief
Trainingthree SFT stages, then RL on a mixture of tasks
Key metric #2The model refuses to answer if the object is not in the image
Key metric #3Code and weights are open

The WeChat team has released WeVisOne-VL (WeChat Vision All-in-One), an open vision-language model. It covers the full range of precise-vision tasks at once: object detection, localization from a text description, counting, OCR, segmentation and matting. According to the authors, the model delivers leading results on more than 30 benchmarks, both at the object level and at the level of individual pixels. They also stress that it reliably refuses to answer when the requested object is not in the picture.

Where ordinary VLMs lose precision

Large multimodal models are good at describing what is in a photo. When the task is to show exactly where an item is, count identical objects or trace an outline, quality drops noticeably. The WeVisOne-VL authors name this as the main problem: existing VLMs remain unreliable at fine-grained visual perception.

In practice, the industry works around this by stitching components together. A language model handles understanding, a separate detector produces boxes, a separate segmentation network produces masks, and an OCR engine reads text. Each link needs its own interfaces, and errors accumulate along the chain. WeVisOne-VL tries to collapse this pipeline into a single model with a unified output format.

The <OBJ> token as a bridge to pixels

The core idea is that everything reduces to structured next-token prediction. The model outputs points and boxes as an ordinary sequence of characters with coordinates. For pixel-level results, the architecture adds a lightweight pixel decoder that connects through a special <OBJ> token. The logic is this: when the model decides it needs to highlight a specific instance, it emits this token, and the decoder turns the associated representation into a mask or an alpha matte.

This design saves compute: the VLM itself does the heavy lifting, and the decoder stays small. The decoder works at the instance level, meaning each detected object gets its own pixel output. An alpha matte is needed where a binary mask is not enough: hair, fur, glass, semi-transparent edges. It is used when cutting out objects for compositing and graphics.

Key characteristics:

  • Tasks: detection, referring localization, counting, OCR, segmentation, matting
  • Output granularity: points, boxes, masks, alpha mattes
  • Architectural addition: a lightweight pixel decoder and a special <OBJ> token
  • Training: a three-stage SFT curriculum, then RL on a mixture of tasks
  • Evaluation: more than 30 benchmarks covering object-level and pixel-level tasks
  • Behavior when the target is absent: consistent refusal on queries about nonexistent objects
  • Availability: open release for the community

How the model was taught not to make things up

Training has two phases. First comes a three-stage SFT curriculum in which task difficulty increases gradually. Then the model is fine-tuned with RL on a mixture of tasks, so that a single policy does not degrade in detection, segmentation or OCR.

The authors put particular emphasis on queries where the target object does not exist. For detectors and grounding models this is a classic pain point: ask for a "red car" in a frame with no cars, and many systems will still draw a box. In production, such false positives cost more than misses. That is why the authors treat the ability to honestly say "it's not here" as a condition for moving from demo VLMs to systems for real-world use.

Where this will be useful in practice

The first candidates for adoption are image and video editors that need a fast selection mask and a high-quality matte, as well as apps built on image search and object counting. Document workflows with OCR and field localization are also in scope, as is robotics, where it is not enough to recognize an item and the system must also indicate its position.

For developers, the main advantage is openness. Instead of a chain of three or four models, you can test one and compare it with your current pipeline on your own data. The claimed results on 30+ benchmarks are worth checking exactly this way: on your own frames, with real queries about absent objects and with latency taken into account. For WeChat, this is also a signal that the Tencent ecosystem is serious about open multimodal perception models, not just chat interfaces.

Story

Key Questions Answered

Where ordinary VLMs lose precision?

Large multimodal models are good at describing what is in a photo. When the task is to show exactly where an item is, count identical objects or trace an outline, quality drops noticeably. The WeVisOne-VL authors name this as the main problem: existing VLMs remain unreliable at fine-grained visual perception. In practice, the industry works around this by stitching components together. A language model handles understanding, a separate detector produces boxes, a separate segmentation network produces masks, and an OCR engine reads text. Each link needs its own interfaces, a

What are the key details on The <OBJ> token as a bridge to pixels?

The core idea is that everything reduces to structured next-token prediction. The model outputs points and boxes as an ordinary sequence of characters with coordinates. For pixel-level results, the architecture adds a lightweight pixel decoder that connects through a special <OBJ> token. The logic is this: when the model decides it needs to highlight a specific instance, it emits this token, and the decoder turns the associated representation into a mask or an alpha matte. This design saves compute: the VLM itself does the heavy lifting, and the decoder stays small. The dec

How the model was taught not to make things up?

Training has two phases. First comes a three-stage SFT curriculum in which task difficulty increases gradually. Then the model is fine-tuned with RL on a mixture of tasks, so that a single policy does not degrade in detection, segmentation or OCR. The authors put particular emphasis on queries where the target object does not exist. For detectors and grounding models this is a classic pain point: ask for a "red car" in a frame with no cars, and many systems will still draw a box. In production, such false positives cost more than misses. That is why the authors treat the ab

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Hands-On AI Engineering

Build & Ship Production AI Apps with Vibe Coding

Join Zhemal Khamidun's hands-on Vibe Coding Intensive at hamidun.com/vibecoding — master Claude Code, Cursor, and autonomous agentic workflows.

Explore Vibe Coding →Vibe Academy Platform
What do you think?
Loading comments…