Command A+ has 218.8B parameters (25B active per token). In BF16 its weights alone take 407 GiB; quantized to 4-bit, about 123 GiB. Each 32K-token request adds 1.38 GiB of KV cache. Cheapest way to run it today: 6 × GeForce RTX 3090 (24 GB) at $0.726 per hour. It reads text and images, calls tools and lets you set its reasoning effort.
Read every day from Hugging Face. Split files are added together; vision projectors are left out.
How many GPUs to run Command A+
Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.
GPU
BF16 / FP16
8-bit
4-bit
GeForce RTX 4090 24 GB
24 (several machines)
16 (several machines)
6
GeForce RTX 5090 32 GB
16 (several machines)
8
5
RTX PRO 6000 Blackwell 96 GB
5
3
2
Mac M5 Max 128 GB 96 GB usable
5
3
2
Ryzen AI Max+ 395 128 GB 96 GB usable
5
3
2
DGX Spark (GB10) 128 GB
4
2
1
NVIDIA H100 80 GB
7
4
2
NVIDIA H200 141 GB
4
2
2
NVIDIA B200 (HGX) 180 GB
3
2
1
8-bit: FP8 with vLLM (INT8 on GPUs without FP8), Q8_0 with llama.cpp. 4-bit: AWQ / GPTQ with vLLM, Q4_K_M with llama.cpp, both counted at the Q4_K_M size.
Cheapest way to run Command A+ today
For each GPU: the fewest cards that fit Command A+ with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-10-30).
On-demand prices from AWS, Google Cloud, Azure, RunPod, Vast.ai, Oracle Cloud, OVHcloud, Scaleway, Verda, Akash and UpCloud, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.
Reasoning. Adjustable reasoning effort. Reasoning tokens take context and KV cache like any other token: leave room for them.
KV cache: how memory grows with context
Architecture: MoE 128 experts + shared · 8 global layers (no position embedding) + 24 sliding-window layers (4096 tokens), GQA 8 KV × 128 · vision encoder. Its KV cache is 2.9× smaller than if every layer used full attention, because most layers only keep a short window of recent tokens. Only 25B parameters are active per token, but all 219B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.63 GiB
0.31 GiB
32K tokens
1.38 GiB
0.69 GiB
128K tokens
4.38 GiB
2.19 GiB
195.3125K tokens
6.48 GiB
3.24 GiB
Command A+ VRAM FAQ
How much VRAM does Command A+ need?
In BF16 the weights alone take 407 GiB (438 GB). In FP8 that is 205 GiB, and about 123 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 0.63 GiB at 8K tokens and 1.38 GiB at 32K (BF16 cache).
Can Command A+ run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 6 RTX 4090s. In 4-bit it fits on a single DGX Spark (GB10) (128 GB).
Can Command A+ run on an RTX 5090 (32 GB)?
No. Even in 4-bit it needs 5 RTX 5090s.
Can Command A+ run on a Mac?
Yes. In 4-bit (Q4_K_M with llama.cpp) it needs a Mac with 192 GB of unified memory or more, of which macOS gives the GPU about 144 GB, for one request with an 8K-token context. In 8-bit (Q8_0) it needs 512 GB.
Can Command A+ run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
Yes. On a DGX Spark (128 GB) it fits in Q4_K_M (124 GiB with an 8K-token context); on a Ryzen AI Max+ 395 with 128 GB, whose GPU gets up to 96 GB, it does not fit even in 4-bit, with llama.cpp and one request.
What is the cheapest way to run Command A+?
On 2026-10-30, the cheapest on-demand setup is 6 × GeForce RTX 3090 (24 GB) with Q4_K_M weights on Vast.ai, at $0.726 per hour (about $529.98 per month). Next: 8 × NVIDIA L4 (24 GB) with 4-bit weights on Vast.ai, at $0.832 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Command A+ need?
With one request and an 8K-token context: 7 in BF16, 4 in FP8 and 2 in 4-bit (vLLM, 90% of memory usable). Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
Can Command A+ read images?
Yes. Command A+ reads text and images. Images add tokens to the context, so they also add KV cache.
Does Command A+ support tool calling?
Yes, Command A+ supports tool (function) calling: it can ask your application to run a function and use the result.
Does Command A+ have a thinking mode?
Adjustable reasoning effort. Reasoning tokens count toward the context and the KV cache.
Command A+ VRAM badge
For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/command-a-plus.json.
Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.