CanItRun Logocanitrun.

Step 3.7 Flash

Step 3.7 Flash needs roughly 136.7 GB VRAM at Q4_K_M quantization (445.2 GB at FP16). 20 GPUs we track can run it fully in VRAM at 8k context.

20 GPUs run this natively · 2 with CPU offload

StepFun198B params11B active (MoE)256k contextApache 2.0Commercial use ok

Step 3.7 Flash is a Mixture of Experts (MoE) large language model with 198B total parameters but only 11B active per token developed by StepFun. Released in June 2026, it supports text and vision inputs with a 256K context window, released under the Apache 2.0 license, allowing commercial use. Multimodal successor to Step 3.5 Flash, retaining the 196B language backbone and adding an approximately 1.8B-parameter vision encoder with low, medium, and high reasoning levels. StepFun reports SWE-bench Pro 56.3 and Terminal-Bench 2.1 59.5. Official GGUF releases are about 105-112 GB before the roughly 4 GB vision projector and runtime overhead; StepFun also provides an NVFP4 checkpoint.

To run Step 3.7 Flash locally, you need approximately 136.7 GB of VRAM at Q4_K_M quantization with 8k context. 20 of the GPUs we track can run it fully in VRAM, with a further 2 able to offload to system RAM. At Q4_K_M it requires 136.7 GB — more than any single consumer GPU. A multi-GPU server or 80 GB datacenter GPU is required. At Q8_K_M (237.4 GB), you get near-FP16 quality while still fitting on large server or multi-GPU setups. FP16 requires 445.2 GB, limiting it to datacenter-class hardware with 80 GB+ VRAM. As a MoE model, inference speed depends on active parameters (11B) rather than total size, so once it fits in VRAM it runs noticeably faster than dense models of the same parameter count.

Step 3.7 Flash is designed for reasoning and problem-solving. Thanks to its MoE architecture with only 11B active parameters, it delivers strong quality while keeping inference latency manageable for local use.

VRAM at each quantization

Step 3.7 Flash natively supports a longer context window, but the table below is capped at 8k for comparability — KV cache grows linearly with context length.

QuantWeightsKV cacheTotal
FP32792.0 GB1.51 GB888.7 GB
BF16396.0 GB1.51 GB445.2 GB
FP16396.0 GB1.51 GB445.2 GB
Q8_0210.5 GB1.51 GB237.4 GB
Q6_K162.6 GB1.51 GB183.8 GB
Q5_K_M141.0 GB1.51 GB159.6 GB
Q4_K_M120.6 GB1.51 GB136.7 GB
Q3_K_M95.2 GB1.51 GB108.4 GB
Q2_K75.4 GB1.51 GB86.2 GB
NVFP4reccuda99.0 GB1.51 GB112.6 GB

KV cache is calculated at 8k context (FP16). Note that NVFP4 only runs on CUDA GPUs. Turn on TurboQuant in the calculator above for lower KV cache estimates.

Benchmarks

GPUs that run Step 3.7 Flash natively (20)

Plus 2 GPUs that run it with CPU offload (slower)

Notes

Multimodal successor to Step 3.5 Flash, retaining the 196B language backbone and adding an approximately 1.8B-parameter vision encoder with low, medium, and high reasoning levels. StepFun reports SWE-bench Pro 56.3 and Terminal-Bench 2.1 59.5. Official GGUF releases are about 105-112 GB before the roughly 4 GB vision projector and runtime overhead; StepFun also provides an NVFP4 checkpoint.

Hugging Face ↗Released 2026-06-01

How to run Step 3.7 Flash locally

816244880160320

NVFP4 needs 112.6 GBneeds multiple datacenter-class GPUs (80 GB+ each).

vLLM (NVFP4)

vllm serve stepfun-ai/Step-3.7-Flash-NVFP4

llama.cpp

./llama-mtmd-cli -m Step-3.7-Flash-Q3_K_L.gguf --mmproj Step-3.7-Flash-mmproj-f16.gguf -c 32768 -ngl 99

LM Studio: The official Q3/Q4 GGUF weights are roughly 102-112 GB, plus a roughly 4 GB vision projector and runtime overhead. Vision support requires a compatible multimodal llama.cpp/LM Studio build.

Why this quantization? StepFun's NVFP4 checkpoint is the most practical official GPU build and preserves the multimodal stack. Community-friendly Q3/Q4 GGUFs are alternatives for large unified-memory machines, but their projector and KV-cache costs must be included.

Who is Step 3.7 Flash for?

Teams running multimodal coding and computer-use agents on Blackwell systems or large unified-memory workstations.

Best for

  • Screenshot-to-code and visual software tasks
  • Long-horizon coding agents
  • Tool use with adjustable reasoning effort

Not ideal for

  • Ordinary consumer GPUs
  • Users who do not need vision over the smaller Step 3.5 deployment
  • Full 256K context on memory-constrained systems

Frequently asked questions

What are the VRAM requirements for Step 3.7 Flash?
Step 3.7 Flash requires approximately 136.7 GB of VRAM at Q4_K_M quantization, 237.4 GB at Q8, and 445.2 GB at FP16. These numbers assume 8k context window; VRAM scales linearly with context length due to the KV cache.
How many parameters does Step 3.7 Flash have?
Step 3.7 Flash has 198 billion total parameters, but only 11 billion are active per token thanks to its Mixture of Experts (MoE) architecture. This makes inference significantly faster than the total parameter count suggests.
Can Step 3.7 Flash run on a 16 GB GPU?
No. At Q4_K_M, Step 3.7 Flash needs 136.7 GB of VRAM — more than 16 GB. You will need a multi-GPU server.
Can Step 3.7 Flash run on a 24 GB GPU?
No. Even at Q4_K_M, Step 3.7 Flash needs 136.7 GB. Consider a multi-GPU server with 80 GB+ total VRAM.
What is the smallest quantization for Step 3.7 Flash that fits in 24 GB of VRAM?
Step 3.7 Flash cannot fit in 24 GB of VRAM at any standard quantization level. The minimum needed is 86.2 GB at Q2_K.
What GPU do I need to run Step 3.7 Flash locally?
You need a multi-GPU server. At Q4_K_M, Step 3.7 Flash needs 136.7 GB VRAM, more than any single consumer GPU. Consider 2–4× H100 or A100 GPUs.