LLM

What GPU do I need to run Qwen/Qwen3-32B?

A 32.8B language model for chat and instruction-following. 32.8B parameters, published in BF16. View on Hugging Face

32.8B
Parameters
BF16
Native precision
40K tokens (40,960)
Context length
Apache 2.0
License
Text
Modality
Alibaba (Qwen)
Organization

Qwen3-32B is published by Qwen on Hugging Face, with 4,883,027 downloads and 740 likes to date. It's a Qwen3ForCausalLM model built for text-generation, published natively in BF16.

What Qwen3-32B is

Qwen3-32B is a 32.8B-parameter language model published by Alibaba (Qwen) on Hugging Face. It is released under Apache 2.0.

License note: fully permissive, no gating and no usage restrictions. Facts in this section are sourced from Qwen3-32B's Hugging Face model card, not benchmarked by Aquanode.

What it's used for

  • Chat assistants
  • Instruction following
  • Synthetic data generation

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)
BF1661.0 GB73.2 GBA1001$1.31/hr
cheaper alt.RTX A50004$0.704/hr
FP8 (quantized)30.5 GB36.6 GBL401$0.759/hr
cheaper alt.RTX 5060 Ti3$0.435/hr
INT4 (quantized)15.3 GB18.3 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-32B at its published (BF16) precision: 1× A100, at $1.31/hr per GPU ($1.31/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Qwen3-32B: 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.

Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 262,144 bytes at 16-bit.

ContextKV cache, one sequence
4K1.0 GB
32K8.0 GB
40K (model maximum)10.0 GB

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

Qwen3-32B: common questions

Can Qwen3-32B run on a single GPU?

Yes, but not on a desktop card. At BF16 it needs 73.2 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest live single-card fit is a 80.0 GB A100 at $1.31/hr.

What is the least VRAM Qwen3-32B can run in?

18.3 GB, at INT4 (quantized), which fits a 24 GB card, against 73.2 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-32B lower the GPU bill?

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

How to run Qwen3-32B

Run Qwen3-32B with vLLM

From Qwen/Qwen3-32B's own deployment docs.

vllm serve Qwen/Qwen3-32B --enable-reasoning --reasoning-parser deepseek_r1

Source: https://huggingface.co/Qwen/Qwen3-32B/raw/main/README.md

Run Qwen3-32B with Ollama

Verified against Ollama's own library listing.

ollama run qwen3:32b

Source: https://ollama.com/library/qwen3:32b

Deploy Qwen3-32B on Aquanode

Aquanode has no one-click deploy template for Qwen3-32B; you install the inference engine yourself with the commands below. Aquanode sells GPU pods billed per second, not a hosted inference API.

  1. Launch a bare GPU pod sized to the requirement above (1× A100 or larger).
  2. Open a terminal on the pod, or save one of the commands above as a startup script so it runs automatically the first time the pod boots.
  3. Run the command and connect to the resulting endpoint.
Launch a GPU pod

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

More Qwen3 models

All 105 Qwen3 models: VRAM and GPU requirements

Lineage

Quantized and fine-tuned versions

Alternatives at this size

Other models for text-generation within about a third of Qwen3-32B's 32.8B parameters, from other model lines.

More on Qwen3-32B

Related reading: A100 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.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

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