Hy4 Flash has 220.3B parameters (11.3B active per token). In BF16 its weights alone take 409 GiB; quantized to 4-bit, about 123 GiB. Each 32K-token request adds 0.45 GiB of KV cache. Cheapest way to run it today: 4 × GeForce RTX 3090 (24 GB) at $0.436 per hour. It reads text, images and video, 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 Hy4 Flash
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
FP8 (native)
BF16 / FP16
8-bit
4-bit
GeForce RTX 4090 24 GB
Not on this GPU
16 (several machines)
7
4
GeForce RTX 5090 32 GB
Not on this GPU
16 (several machines)
5
3
RTX PRO 6000 Blackwell 96 GB
Not on this GPU
4
2
1
Mac M5 Max 128 GB 96 GB usable
Not on this GPU
4
2
1
Ryzen AI Max+ 395 128 GB 96 GB usable
Not on this GPU
4
2
1
DGX Spark (GB10) 128 GB
Not on this GPU
3
2
1
NVIDIA H100 80 GB
3
5
3
2
NVIDIA H200 141 GB
2
3
2
1
NVIDIA B200 (HGX) 180 GB
2
2
1
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. Not on this GPU: the official FP8 weights do not run there (llama.cpp needs a GGUF version, and vLLM needs a GPU with FP8 support).
Cheapest way to run Hy4 Flash today
For each GPU: the fewest cards that fit Hy4 Flash with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-11-22).
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.
vLLM and SGLang apply these defaults unless a request sets its own. With llama.cpp, pass them yourself: --temp 0.9 --top-p 1
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 512 latent experts + 1 shared · MLA (512 + 64) on 42 layers: 12 sparse-attention layers (indexer keys per 4-token block) + 30 sliding-window layers (512 tokens) · 63B Engram tables in RAM · image input. Its KV cache is 3.3× 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 11.3B parameters are active per token, but all 220B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.12 GiB
0.07 GiB
32K tokens
0.45 GiB
0.26 GiB
128K tokens
1.75 GiB
1.02 GiB
1M tokens
13.9 GiB
8.08 GiB
Hy4 Flash VRAM FAQ
How much VRAM does Hy4 Flash need?
In BF16 the weights alone take 409 GiB (439 GB). In FP8 that is 205 GiB, and about 123 GiB with 4-bit quantization (Q4_K_M); the official FP8 checkpoint is 266 GiB. Each request then adds KV cache: 0.12 GiB at 8K tokens and 0.45 GiB at 32K (BF16 cache).
Can Hy4 Flash run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 4 RTX 4090s. In 4-bit it fits on a single RTX PRO 6000 Blackwell (96 GB).
Can Hy4 Flash run on an RTX 5090 (32 GB)?
No. Even in 4-bit it needs 3 RTX 5090s.
Can Hy4 Flash run on a Mac?
Yes. In 4-bit (Q4_K_M with llama.cpp) it needs a Mac with 128 GB of unified memory or more, of which macOS gives the GPU about 96 GB, for one request with an 8K-token context. In 8-bit (Q8_0) it needs 256 GB or more.
Can Hy4 Flash run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
Yes. In Q4_K_M (123 GiB with an 8K-token context) it fits on a DGX Spark (128 GB) and on a Ryzen AI Max+ 395 with 128 GB, whose GPU gets up to 96 GB, with llama.cpp and one request.
What is the cheapest way to run Hy4 Flash?
On 2026-11-22, the cheapest on-demand setup is 4 × GeForce RTX 3090 (24 GB) with Q4_K_M weights on Vast.ai, at $0.436 per hour (about $318.28 per month). Next: 7 × RTX A4000 (16 GB) with Q4_K_M weights on Vast.ai, at $0.616 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Hy4 Flash need?
With one request and an 8K-token context: 5 in BF16, 3 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 Hy4 Flash read images?
Yes. Hy4 Flash reads text, images and video. Images add tokens to the context, so they also add KV cache.
Does Hy4 Flash support tool calling?
Yes, Hy4 Flash supports tool (function) calling: it can ask your application to run a function and use the result.
Does Hy4 Flash have a thinking mode?
Adjustable reasoning effort. Reasoning tokens count toward the context and the KV cache.
What temperature should I use with Hy4 Flash?
The official defaults are temperature 0.9, top-p 1.
Hy4 Flash 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/hy4-flash.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.