Step-5-Preview has 604.3B parameters (33B active per token). In BF16 its weights alone take 1119 GiB; quantized to 4-bit, about 337 GiB. Each 32K-token request adds 2.28 GiB of KV cache. Cheapest way to run it today: 8 × RTX A6000 (48 GB) at $2.57 per hour. It reads text, images and video, calls tools and lets you set its reasoning effort.
Weights plus the KV cache of one request (BF16 cache), in GiB. Add 1 to 3 GiB for the inference engine itself.
Weights format
Weights only
+ 8K context
+ 32K context
+ 128K context
+ 1M context
BF16 / FP16
1119
1120
1122
1128
1189
FP8 / INT8
561
561
563
570
631
4-bit (GGUF Q4_K_M)
337
338
339
346
407
How many GPUs to run Step-5-Preview
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
64 (several machines)
32 (several machines)
16 (several machines)
GeForce RTX 5090 32 GB
48 (several machines)
24 (several machines)
16 (several machines)
RTX PRO 6000 Blackwell 96 GB
16 (several machines)
7
4
Mac M5 Max 128 GB 96 GB usable
16 (several machines)
6
4
Ryzen AI Max+ 395 128 GB 96 GB usable
16 (several machines)
6
4
DGX Spark (GB10) 128 GB
16 (several machines)
5
3
NVIDIA H100 80 GB
24 (several servers)
16 (several servers)
6
NVIDIA H200 141 GB
16 (several servers)
5
3
NVIDIA B200 (HGX) 180 GB
8
4
3
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 Step-5-Preview today
For each GPU: the fewest cards that fit Step-5-Preview with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-10-16).
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: 92 layers · 23 full attention (4 KV × 192) · sparse attention, a summary per 8-token block · 69 sliding-window layers (512 tokens, 4 KV × 192). Its KV cache is 3.8× smaller than if every layer used full attention, because it keeps only a short window of tokens at full detail and compresses the rest of the sequence. Only 33B parameters are active per token, but all 604B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.65 GiB
0.33 GiB
32K tokens
2.28 GiB
1.15 GiB
128K tokens
8.82 GiB
4.45 GiB
1M tokens
69.8 GiB
35.3 GiB
Step-5-Preview VRAM FAQ
How much VRAM does Step-5-Preview need?
In BF16 the weights alone take 1119 GiB (1202 GB). In FP8 that is 561 GiB, and about 337 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 0.65 GiB at 8K tokens and 2.28 GiB at 32K (BF16 cache).
Can Step-5-Preview run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 16 RTX 4090s, spread over several machines. In 4-bit it needs 6 H100 GPUs.
Can Step-5-Preview run on an RTX 5090 (32 GB)?
No. Even in 4-bit it needs 16 RTX 5090s, spread over several machines.
Can Step-5-Preview run on a Mac?
Yes. In 4-bit (Q4_K_M with llama.cpp) it needs a Mac with 512 GB of unified memory, of which macOS gives the GPU about 384 GB, for one request with an 8K-token context. In 8-bit it does not fit on a single Mac.
Can Step-5-Preview run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
No. Even in 4-bit it needs 3 DGX Spark units or 4 Ryzen AI Max+ 395 machines (128 GB), linked over the network.
What is the cheapest way to run Step-5-Preview?
On 2026-10-16, the cheapest on-demand setup is 8 × RTX A6000 (48 GB) with Q4_K_M weights on Vast.ai, at $2.57 per hour (about $1,874.64 per month). Next: 8 × RTX 6000 Ada (48 GB) with Q4_K_M weights on Vast.ai, at $4.50 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Step-5-Preview need?
With one request and an 8K-token context: 24 in BF16, 16 in FP8 and 6 in 4-bit (vLLM, 90% of memory usable). Above 8 GPUs, that means several servers. Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
Can Step-5-Preview read images?
Yes. Step-5-Preview reads text, images and video. Images add tokens to the context, so they also add KV cache.
Does Step-5-Preview support tool calling?
Yes, Step-5-Preview supports tool (function) calling: it can ask your application to run a function and use the result.
Does Step-5-Preview have a thinking mode?
Adjustable reasoning effort. Reasoning tokens count toward the context and the KV cache.
Step-5-Preview 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/step-5-preview.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.