What GPU do I need to run Qwen/Qwen3.5-35B-A3B-Base?

36.0B parameters, published in BF16. View on Hugging Face

36.0B
Parameters
BF16
Native precision
Qwen3_5MoeForConditionalGeneration
Architecture
image-text-to-text
Pipeline

Qwen3.5-35B-A3B-Base is published by Qwen on Hugging Face, with 97,728 downloads and 144 likes to date. It's a Qwen3_5MoeForConditionalGeneration model built for image-text-to-text, published natively in BF16.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF1667.0 GB80.4 GBRTX PRO 6000 WS1$1.62/hr
cheaper alt.RTX A50004$0.704/hr
FP8 (quantized)33.5 GB40.2 GBL401$0.759/hr
cheaper alt.RTX 4000 SFF Ada3$0.594/hr
INT4 (quantized)16.7 GB20.1 GBRTX A50001$0.176/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run Qwen3.5-35B-A3B-Base at its published (BF16) precision: 1× RTX PRO 6000 WS, at $1.62/hr per GPU ($1.62/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Qwen3.5-35B-A3B-Base: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Hybrid: only the full-attention layers cache per token; the other layers keep a fixed-size state. Cached per token: 20,480 bytes at 16-bit.

ContextKV cache, one sequence
4K0.08 GB
32K0.63 GB
128K2.5 GB
256K (model maximum)5.0 GB

Computed from the layer, head and window counts in the model's own configuration (Qwen/Qwen3.5-35B-A3B-Base), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Qwen3.5-35B-A3B-Base: common questions

Can Qwen3.5-35B-A3B-Base run on a single GPU?

Yes, but not on a desktop card. At BF16 it needs 80.4 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest live single-card fit is a 96.0 GB RTX PRO 6000 WS at $1.62/hr.

What is the least VRAM Qwen3.5-35B-A3B-Base can run in?

20.1 GB, at INT4 (quantized), which fits a 24 GB card, against 80.4 GB at BF16. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing Qwen3.5-35B-A3B-Base lower the GPU bill?

Yes. At BF16 the cheapest live fit is one RTX PRO 6000 WS at $1.62/hr. At INT4 (quantized) it drops to one RTX A5000 at $0.176/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Qwen3.5 models

All 43 Qwen3.5 models: VRAM and GPU requirements

Lineage

Quantized and fine-tuned versions

Alternatives at this size

Other models for image-text-to-text within about a third of Qwen3.5-35B-A3B-Base's 36.0B parameters, from other model lines.

More on Qwen3.5-35B-A3B-Base

Related reading: RTX PRO 6000 WS pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Submit the job. Everything after that is ours.

Sign up in 60 seconds. Pay for the GPU minutes you actually use.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.