llmrun
z-labQwen 3.5DFlashDraftModel

Qwen3.5 35B A3B DFlash — Hardware Requirements & GPU Compatibility

Chat

Qwen3.5 35B A3B DFlash is a 35B-parameter open language model from z-lab in the Qwen 3.5 family. It supports a context window of up to 262,144 tokens. At BF16 it needs about 70.32 GB of VRAM — see which GPUs and Macs can run it below.

35B params · dense262K contextMIT705 downloads6 likes

Qwen3.5 35B A3B DFlash runs on a 96 GB+ Mac or a workstation GPU

Best local pick → Mac Studio (M3 Ultra, 96GB) · BF16 · 70.4 GB · ~83 tok/s

Macs from96 GB BF16 · ~83 tok/s

MIT

Not set up for it?

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run Qwen3.5 35B A3B DFlash

One recommended way. Every other method, OS and quant is in the step-by-step guide.

Recommended

vLLM
one command · needs vLLM installed
$vllm serve z-lab/Qwen3.5-35B-A3B-DFlash --max-model-len 16384 --tensor-parallel-size 8

vLLM repo with its own quantisation

Download: Weights on Hugging Face

install, OS, other quants

Other ways

each opens step-by-step

Run in cloud

Fits on RTX PRO 6000 (96 GB) (25 GB headroom) · BF16

Generation speed
~178 tok/s
generation speed
Cost per 1M output tokens
$1.92
per 1M output tokens

How Much VRAM Does Qwen3.5 35B A3B DFlash Need?

Select a quantization level; the listed hardware adheres to it.

QuantizationVRAM+32KRuns on
70.3 GB70.6 GB16-bit · bfloat — Brain floating point 16 — preferred for trainingRuns on RTX PRO 5000 Blackwell 72 GB
est.calculated, no published file yet

Selected BF16

Brain floating point 16

70.4GBat 16K context

Weights
70.0 GB
KV cache
0.1 GB
Overhead
0.3 GB

Server-class: ~70.4 GB at 16K context · one RTX PRO 5000 Blackwell 72 GB

Or rent RTX PRO 6000 from $1.23/hr.

Which Hardware Can Run Qwen3.5 35B A3B DFlash?

BF16 · 70.3 GB

Qwen3.5 35B A3B DFlash (BF16) requires 70.3 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 92+ GB is recommended. Using the full 262K context window can add up to 2.1 GB, bringing total usage to 72.5 GB. No consumer GPU has enough memory. 30 devices with unified memory can run Qwen3.5 35B A3B DFlash, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB), Mac Studio (M3 Ultra, 96GB).

By VRAM tier · typical GPUs and Macs at BF16

Consumer GPUs (up to 32 GB) and Macs up to 64 GB: too small for this model (needs ≥ 70.4 GB)8 GB tier →12 GB tier →16 GB tier →24 GB tier →Macs →

Alternatives to Qwen3.5 35B A3B DFlash

Qwen 3.5 family · 34 models →

Similar models

6
ModelScoreVRAMWhy it is similar
MiniCPM V 4.7 35B A3BOpenBMB—22.1 GBsame size
Llm Jp 4.1 33B Thinkingllm-jp—22.5 GBsame size
Agnes 3.0 FlashAgnes-AI—22.1 GBsame size
Ornith 1.5 35B A3Bornith-ai—22 GBsame size
Agents A1InternScience—21.5 GBsame size
Intern S2 PreviewInternLM—73.2 GBsame size

Specifications

Publisher
z-lab
Family
Qwen 3.5
Parameters
35B
Active parameters
3B per token
Architecture
DFlashDraftModel
Context Length
262,144 tokens
Vocabulary Size
248,320
Release Date
2026-03-02
License
MIT

Frequently Asked Questions

How much VRAM does Qwen3.5 35B A3B DFlash need?

Qwen3.5 35B A3B DFlash requires 70.3 GB of VRAM at BF16. Full 262K context adds up to 2.1 GB (72.5 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 35B × 16 bits ÷ 8 = 70 GB

KV Cache + Overhead ≈ 0.3 GB (at 2K context + ~0.3 GB framework)

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

KV Cache + Overhead ≈ 2.5 GB (at full 262K context)

VRAM usage by quantization

70.3 GB
72.5 GB

Learn more about VRAM estimation →

Can NVIDIA GeForce RTX 5090 run Qwen3.5 35B A3B DFlash?

No — Qwen3.5 35B A3B DFlash requires at least 70.3 GB at BF16, which exceeds the NVIDIA GeForce RTX 5090's 32 GB of VRAM.

Can I run Qwen3.5 35B A3B DFlash on a Mac?

Yes — Mac Studio (M3 Ultra, 96GB) and 20 other Macs can run Qwen3.5 35B A3B DFlash. Apple Silicon uses unified memory, so the model shares RAM with the system. At BF16 you need at least 70.3 GB of usable unified memory (RAM minus macOS overhead).

Can I run Qwen3.5 35B A3B DFlash locally?

Yes — Qwen3.5 35B A3B DFlash can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Qwen3.5 35B A3B DFlash?

At BF16, Qwen3.5 35B A3B DFlash can reach ~350 tok/s on AMD Instinct MI350X. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = 1000 ÷ (active GB ÷ (bandwidth GB/s × efficiency) × 1000 + layers × routing ms)

Mixture-of-Experts: just the active experts get read for each token, along with a fixed routing cost per layer.

Example: NVIDIA B200 → 6.0 GB active ÷ (8000 × 0.65) = 1.16 ms, plus 8 layers × 0.055 ms = 0.44 ms, so 1000 ÷ 1.60 ms = ~625 tok/s

Estimated speed at BF16 (70.3 GB)

~625 tok/s
~625 tok/s
~429 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of Qwen3.5 35B A3B DFlash?

At BF16, the download is about 70.00 GB.

Which GPUs can run Qwen3.5 35B A3B DFlash?

No single consumer GPU has enough VRAM to run Qwen3.5 35B A3B DFlash at BF16 (70.3 GB). Multi-GPU or professional hardware is required.

Which devices can run Qwen3.5 35B A3B DFlash?

30 devices with unified memory can run Qwen3.5 35B A3B DFlash at BF16 (70.3 GB), including ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB), GMKtec EVO-X2 (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.