Free · runs in your browser · no sign-up

LLM VRAM calculator for local models

This LLM VRAM calculator estimates 4.92 GiB–5.42 GiB for Qwen2.5-7B-Instruct Q4_K_M at 8,192 tokens. A VRAM calculator for LLM local inference; demand only until you pick a GPU.

This LLM VRAM calculator, including a GGUF checkpoint, adds weight bytes from the selected checkpoint, KV cache from that model's attention layout, and runtime overhead. The result is an estimate. See the methodology, the KV cache calculator, the model list, and the GPU list.

GPU and model pages

Choose a GPU or unified-memory machine and how many. A short current list appears next.

Device type

Pick a GPU or unified-memory machine. Candidate models appear immediately.

Workload

Context length primarily affects KV cache memory.

Advanced settings
Runtime

Engine and KV cache type for this estimate.

Off: GGUF, Q8-class, and other filters stay strict. On: a replacement is shown with requested, used, and reason.

Workload

Overhead scenario and the prefill workspace.

Topology

How the model is split across devices. Memory is not added together.

Replica count is an advanced deployment option. Quantity is nodes or GPUs, not replicas.

Budget

System reserve and safety margin. An empty number keeps the previous value.

GiB (2^30 bytes)

%

Device and workload

Pick a GPU or unified-memory machine. Candidate models appear immediately.

Popular hardware

Full-resident weight estimates use total parameters, including inactive MoE experts.

Pick a device to list candidate models. You do not need to choose a model first.

How the estimate works

Read the full methodology

Memory for local inference is the sum of the parts below, compared with the memory your device can actually use.

  1. Weights

    Bytes of the selected weight files (GGUF or safetensors), not a parameter-count guess. MoE models count every expert.

  2. KV cache

    Grows with context length and concurrent sequences, using each architecture's own attention layout.

  3. Runtime overhead

    Engine workspace and buffers, shown as a range for llama.cpp, vLLM, SGLang and other engines.

  4. Usable memory

    Device capacity minus an OS and display reserve. Two GPUs are never simply added together.

Proven deployments

View all: Deployment Recipes

Maintainer-measured setups. These are exact hardware and runtime recipes, not generic memory estimates.

DeepSeek-V4.1-Flash
2× NVIDIA DGX Spark (GB10, 128 GB unified)
Measured by upstream maintainer
Quant:EXL3 2.9 bpw (mul1)(2.9 bpw)
Runtime:vLLM· TP2
Offload:Engram n-gram tables (shards 47+48) → NVME
Tested:
  • ✓ generation
  • ✓ 262,144 context
  • ✓ tool calling
  • ✓ vision
  • ✓ speculative decoding
Measured:31.6 tok/s· 1 stream

2-node DGX Spark setup serving DeepSeek-V4.1-Flash with vLLM tensor-parallel size 2 over ConnectX-7 RoCE, EXL3 2.9 bpw mul1 weights, and native NVMe-resident Engram tables.

DeepSeek-V4.1-Flash
3× NVIDIA DGX Spark (GB10, 128 GB unified)
Measured by upstream maintainer
Quant:Native MXFP4 MoE + FP8 Dense
Runtime:SGLang· TP3
Offload:Engram n-gram tables (189 GiB) → NVME
Tested:
  • ✓ generation
  • ✓ ~208K Tested (256K cfg)
  • ✓ tool calling
  • ✓ vision
  • ✓ speculative decoding
Measured:37.9 tok/s· 1 stream

3-node DGX Spark cluster running native MXFP4 experts and FP8 dense weights with SGLang TP=3 over ConnectX-7 RoCE triangle, with NVMe-resident Engram tables.

DeepSeek-V4.1-Flash
4× NVIDIA DGX Spark (GB10, 128 GB unified)
Measured by upstream maintainer
Quant:Native MXFP4 MoE + FP8 Dense (TP=4)
Runtime:SGLang· TP4
Offload:Engram n-gram tables (189 GiB) → NVME
Tested:
  • ✓ generation
  • ✓ 1,048,576 context
  • ✓ tool calling
  • ✓ vision
  • ✓ speculative decoding
Measured:45.4 tok/s· 1 stream

4-node DGX Spark cluster running native MXFP4 MoE and FP8 dense weights with SGLang TP=4, verified 1M context needle test, and 8M pinned KV token pool.

Qwen3.8-27B
1× GeForce RTX 5090 32GB (desktop)
Measured by upstream maintainer
Quant:NVFP4 safetensors(4 bpw)
Runtime:vLLM
Tested:
  • ✓ generation
  • ✓ 262,144 context
  • ✓ tool calling
  • ✓ speculative decoding
Measured:160 tok/s· 1 stream

Single NVIDIA RTX 5090 (32 GB, sm_120) deployment serving RadixArk/Qwen3.8-27B-NVFP4 with vLLM 0.27.1, native 256K context, TurboQuant 4-bit KV cache, and MTP-3 speculative decoding.

Popular models

View all: Models

Popular hardware

View all: Hardware

Latest model support

Popular comparisons

View all: Compare