LG AI Research, South Korea · Released July 29, 2026
K-EXAONE 2.0 750B-A37B has 749.4B parameters (37B active per token). In BF16 its weights alone take 1395 GiB; quantized to 4-bit, about 421 GiB. Each 32K-token request adds 2.54 GiB of KV cache. Cheapest way to run it today: 7 × NVIDIA A100 80GB at $4.41 per hour. It calls tools and has a thinking mode you can switch off.
Read every day from Hugging Face. Split files are added together; vision projectors are left out.
How many GPUs to run K-EXAONE 2.0 750B-A37B
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
96 (several machines)
48 (several machines)
24 (several machines)
GeForce RTX 5090 32 GB
64 (several machines)
32 (several machines)
16 (several machines)
RTX PRO 6000 Blackwell 96 GB
16 (several machines)
8
5
Mac M5 Max 128 GB 96 GB usable
16 (several machines)
8
5
Ryzen AI Max+ 395 128 GB 96 GB usable
16 (several machines)
8
5
DGX Spark (GB10) 128 GB
16 (several machines)
6
4
NVIDIA H100 80 GB
24 (several servers)
16 (several servers)
7
NVIDIA H200 141 GB
16 (several servers)
6
4
NVIDIA B200 (HGX) 180 GB
16 (several servers)
5
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 K-EXAONE 2.0 750B-A37B today
For each GPU: the fewest cards that fit K-EXAONE 2.0 750B-A37B 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.
vLLM and SGLang apply these defaults unless a request sets its own. With llama.cpp, pass them yourself: --temp 1 --top-p 0.95
Reasoning. Thinking mode you can switch on or off. With vLLM or SGLang, set it per request: "chat_template_kwargs": {"enable_thinking": false} turns it off, true on. Reasoning tokens take context and KV cache like any other token: leave room for them.
KV cache: how memory grows with context
Architecture: MoE 256 experts + 1 shared · 20 global layers + 58 sliding-window layers (57 × 128 tokens, 1 × 4096), GQA 8 KV × 128. Its KV cache is 3.8× smaller than if every layer used full attention, because most layers only keep a short window of recent tokens. Only 37B parameters are active per token, but all 749B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.67 GiB
0.33 GiB
32K tokens
2.54 GiB
1.27 GiB
128K tokens
10.0 GiB
5.02 GiB
256K tokens
20.0 GiB
10.0 GiB
K-EXAONE 2.0 750B-A37B VRAM FAQ
How much VRAM does K-EXAONE 2.0 750B-A37B need?
In BF16 the weights alone take 1395 GiB (1498 GB). In FP8 that is 699 GiB, and about 421 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 0.67 GiB at 8K tokens and 2.54 GiB at 32K (BF16 cache).
Can K-EXAONE 2.0 750B-A37B run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 24 RTX 4090s, spread over several machines. In 4-bit it needs 7 H100 GPUs.
Can K-EXAONE 2.0 750B-A37B run on an RTX 5090 (32 GB)?
No. Even in 4-bit it needs 16 RTX 5090s, spread over several machines.
Can K-EXAONE 2.0 750B-A37B run on a Mac?
No single Mac holds it, even in 4-bit: it needs 422 GiB with an 8K-token context, and the largest Mac (512 GB) gives its GPU about 384 GB.
Can K-EXAONE 2.0 750B-A37B run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
No. Even in 4-bit it needs 4 DGX Spark units or 5 Ryzen AI Max+ 395 machines (128 GB), linked over the network.
What is the cheapest way to run K-EXAONE 2.0 750B-A37B?
On 2026-10-30, the cheapest on-demand setup is 7 × NVIDIA A100 80GB with 4-bit weights on Vast.ai, at $4.41 per hour (about $3,219.30 per month). Next: 5 × RTX PRO 6000 Blackwell (96 GB) with Q4_K_M weights on Vast.ai, at $6.67 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does K-EXAONE 2.0 750B-A37B need?
With one request and an 8K-token context: 24 in BF16, 16 in FP8 and 7 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.
Does K-EXAONE 2.0 750B-A37B support tool calling?
Yes, K-EXAONE 2.0 750B-A37B supports tool (function) calling: it can ask your application to run a function and use the result.
Does K-EXAONE 2.0 750B-A37B have a thinking mode?
Thinking mode you can switch on or off. With vLLM or SGLang, set it per request with "chat_template_kwargs": {"enable_thinking": false} (or true). Reasoning tokens count toward the context and the KV cache.
What temperature should I use with K-EXAONE 2.0 750B-A37B?
The official defaults are temperature 1, top-p 0.95.
K-EXAONE 2.0 750B-A37B 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/k-exaone-2-0.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.