Qwen 3.5: When Text, Vision, and Video Understand Each Other

Alibaba's Qwen 3.5 (397B) is the first truly native multimodal open-weight model — not a language model with a vision plugin, but a single architecture that thinks in text, images, and video simultaneously.

May 4, 20268 min readJakub Rusinowski

Most "multimodal" AI models are a lie — or at least an overstatement.

What they actually are: a language model with an image encoder attached. The image encoder (typically a CLIP variant) converts visual inputs into token embeddings that the language model then processes. The image understanding happens in a separate module that was designed and trained independently from the language reasoning.

This architecture works, but it has systematic weaknesses. The vision encoder and the language model were trained on different data with different objectives. They're aligned through fine-tuning, but they don't truly share a common understanding of the world. This is why current multimodal models often fail at tasks that require tight integration of visual and linguistic reasoning — like reading text embedded in complex diagrams, understanding temporal sequences in video, or reasoning about spatial relationships between objects described across multiple images.

Qwen 3.5, released by Alibaba in April 2026, takes a different approach.

Native Multimodal Architecture

Qwen 3.5 was designed from the beginning as a unified model for text, image, and video. Rather than attaching a vision encoder to a language model, Alibaba trained a single transformer architecture on all three modalities simultaneously.

The key difference is in the attention mechanism. In a standard multimodal model, image tokens influence language token processing indirectly — through the output of the vision encoder being projected into the language model's embedding space. In Qwen 3.5, image tokens, video frame tokens, and text tokens participate in the same attention layers from the first layer forward.

This means the model's internal representations for concepts are shared across modalities. When Qwen 3.5 processes the concept "the error in the graph," it's not translating between a visual understanding of a graph and a linguistic understanding of an error — they're the same representation from the model's perspective.

The practical result: Qwen 3.5 significantly outperforms adapter-based multimodal models on tasks requiring tight cross-modal reasoning.

Benchmark Performance

BenchmarkQwen 3.5 397BGPT-4oGemini 2.0 Pro
MMLU (text)92.1%88.7%90.9%
MMBench (vision)91.8%83.4%88.2%
Video-MME78.4%72.1%76.8%
OCR-Bench89.3%81.2%84.7%
HumanEval (code)96.5%90.2%87.4%

The Video-MME score is particularly notable. Video-MME tests a model's ability to answer questions about video content — understanding temporal sequences, tracking objects across frames, reasoning about causality in visual events. At 78.4%, Qwen 3.5 397B leads every model it's been compared against on this benchmark.

OCR-Bench (reading text in images) is another strong showing at 89.3%. This is where native multimodal architecture really matters: reading embedded text requires tight integration of visual pattern recognition and linguistic understanding, which is exactly what shared attention mechanisms enable.

The Practical Scale Problem

Qwen 3.5 397B requires approximately 200 GB of VRAM to run at Q4_K_M quantization. For local deployment, that means:

  • 3× H100 80GB GPUs (total: 240 GB VRAM)
  • 4× A100 80GB GPUs (total: 320 GB VRAM)
  • Specialized multi-GPU consumer rigs with NVLink

For most users, the 14B and 72B variants hit the sweet spot:

Qwen 3.5 14B — 9 GB VRAM, native image support, ~72 t/s on RTX 4070 Ti. Best for developers who want multimodal capability on a single consumer GPU. Qwen 3.5 72B — 42 GB VRAM, full vision + video support, enterprise-ready. Runs on a 2× RTX 4090 setup or a single H100 80GB.
# Run Qwen 3.5 14B locally
ollama run qwen3.5:14b

# Run Qwen 3.5 72B locally (requires 40+ GB VRAM)
ollama run qwen3.5:72b

Real-World Multimodal Use Cases

Document analysis with embedded charts: Send a PDF page screenshot. Qwen 3.5 reads the text, understands the charts, and synthesizes them — not separately, but as an integrated document. Ask "what does the Q3 revenue chart tell us about the conclusion in the third paragraph?" and it can answer coherently. Video summary: Send a 2-minute product demo video (processed as sampled frames). Qwen 3.5 can describe what happens, identify the key moments, and answer specific questions about what was shown. Code + UI debugging: Share a screenshot of a broken UI alongside the relevant code. The model can visually identify the layout problem and cross-reference it with the code to pinpoint the cause — treating the screenshot and code as one integrated context. Data extraction from images: OCR has traditionally required specialized models. Qwen 3.5's 89.3% OCR-Bench score makes it viable for extracting structured data from photos of receipts, forms, and handwritten notes without a separate OCR pipeline.

The Apache 2.0 License

All Qwen 3.5 variants are released under Apache 2.0 — the most permissive license available for a frontier-quality model. You can:

  • Deploy commercially without restrictions
  • Redistribute modified versions
  • Use without attribution requirements in most contexts
  • Fine-tune and distribute the fine-tuned model

For businesses evaluating open-weight models, Apache 2.0 eliminates the legal complexity that comes with the Llama license, Gemma license, or proprietary research licenses. It's clean, familiar, and legally unambiguous.

Why Native Multimodal Is the Future

The adapter-based multimodal model architecture is a transitional approach. It worked as a fast path to add vision to existing language models, but it's architecturally limited.

Native multimodal models like Qwen 3.5 represent the direction the field is moving. As training on multi-modal data becomes the default, and as hardware catches up to enable training these models at scale, the performance advantages of native architectures will compound.

Qwen 3.5 is the clearest demonstration yet of what native multimodal looks like in practice. On every visual benchmark, it outperforms adapter-based models of similar scale. The gap is largest on tasks requiring tight text-vision integration — which is exactly where you'd expect a native architecture to win.


Explore Qwen 3.5 variants and hardware requirements → Model Library Check what hardware you need → Hardware Analyzer