Nemotron 3 Nano 30B-A3B VRAM requirements
Nemotron 3 Nano 30B-A3B needs about 20.1 GB of VRAM at Q4_K_M with 8K context, so it fits a 24 GB card such as the RTX 3090 or the RTX 4090. Nemotron 3 Nano 30B-A3B has 31.6B parameters, of which about 3.5B are used per token; all 128 experts still have to be in memory. With the same 8K context and one request it needs 32.9 GB at FP8 and 65.3 GB at FP16/BF16. The published weights take 58.8 GB (BF16). The smallest setup here that holds it at Q4_K_M with an 8K context is the RTX 3090 (24 GB), which runs it with its full 256K-token context.
20.1 GB at Q4_K_M, 8K context, one request
- FP8
- 32.9 GB
- FP16 / BF16
- 65.3 GB
- Published weights
- 58.8 GB
- Smallest setup, Q4_K_M
- RTX 3090 (24 GB)
Worked example: Nemotron 3 Nano 30B-A3B with 32K tokens
Inputs: Nemotron 3 Nano 30B-A3B · Q4_K_M weights · 32,768 tokens of context · one request · FP16 KV cache
- Weights (31.6B at Q4_K_M)
- 17.8 GB
- KV cache (6 KB per token)
- 192 MB
- Buffers and runtime (0.5 GB + 10%)
- 2.30 GB
- Total
- 20.3 GB
The smallest setup here that holds it is the RTX 3090 (24 GB), with about 3.72 GB to spare. Change the inputs in the calculator
Can I run Nemotron 3 Nano 30B-A3B on…
- RTX 4090: Yes, Q4_K_M
- RTX 3090: Yes, Q4_K_M
- RTX 5090: Yes, up to Q6_K
- RTX 3060 12GB: --n-cpu-moe 30
- RTX 4060 Ti 16GB: Only Q2_K
- RTX 5060 Ti 16GB: Only Q2_K
- RTX 4070 12GB: --n-cpu-moe 30
- RTX 5080 16GB: Only Q2_K
- RTX 4080 Super 16GB: Only Q2_K
- RX 7900 XTX: Yes, Q4_K_M
What makes Nemotron 3 Nano 30B-A3B's memory use different
46 of its 52 layers keep a fixed-size Mamba or feed-forward state, so the cache grows by 6 KB per token where caching every layer would take 52 KB.
Per token of context it adds 6 KB of FP16 cache; Granite 4.2 30B (29.3B), the nearest-sized model here with plain full attention, adds 256 KB, so Nemotron 3 Nano 30B-A3B needs 2% as much.
As a mixture-of-experts model it reads about 1.97 GB of its 17.8 GB Q4_K_M weights per generated token (11%), so it writes like a much smaller model while needing memory for all of them.
Running Nemotron 3 Nano 30B-A3B with experts in system RAM
llama.cpp's --n-cpu-moe N keeps the experts of the first N layers in RAM. For the measured
Q4_K_M GGUF with 32K tokens of context, the smallest N
that fits each card, and the speed with 89.6 GB/s of system RAM.
Plan the offload for another GPU.
The VRAM here can sit below the 20.3 GB of the worked example because it counts the file's measured
bytes, keeps the input embedding (token_embd) in system RAM as llama.cpp does and adds a flat 1 GB of buffers, where the
estimate above adds 0.5 GB plus 10% to the preset's weights.
| GPU | --n-cpu-moe | VRAM used | In system RAM | Tokens/s |
|---|---|---|---|---|
| RTX 5060 Ti 16GB 16 GB | 21 | 15.4 GB | 8.70 GB | 29–49 |
| RTX 4090 24 GB | 0 (all on the GPU) | 23.8 GB | 231 MB | 94–167 |
| RTX 5090 32 GB | 0 (all on the GPU) | 23.8 GB | 231 MB | 150–279 |
In system RAM counts the offloaded experts plus the input embedding (token_embd), which stays in RAM even with --n-cpu-moe 0.
How much VRAM does Nemotron 3 Nano 30B-A3B need?
Nemotron 3 Nano 30B-A3B needs 20.1 GB at Q4_K_M, 34.9 GB at Q8_0 and 65.3 GB at FP16 with 8,192 tokens of context and one request. Each total below is the weights plus the FP16 KV cache and the runtime overhead (0.5 GB plus 10%), and each row opens the calculator with that setting. What the GGUF names mean.
| Precision | Weights | Total | Smallest setup |
|---|---|---|---|
| As published (BF16) | 58.8 GB | 65.3 GB | A100 80GB |
| FP16 / BF16 | 58.8 GB | 65.3 GB | A100 80GB |
| FP8 / INT8 | 29.4 GB | 32.9 GB | M4 Pro Mac (64 GB, 48 GB usable) |
| INT4 (AWQ / GPTQ) | 15.6 GB | 17.7 GB | RTX 3090 (24 GB) |
| GGUF Q8_0 | 31.2 GB | 34.9 GB | M4 Pro Mac (64 GB, 48 GB usable) |
| GGUF Q6_K | 24.1 GB | 27.1 GB | RTX 5090 (32 GB) |
| GGUF Q5_K_M | 20.8 GB | 23.5 GB | RTX 3090 (24 GB) |
| GGUF Q4_K_M | 17.8 GB | 20.1 GB | RTX 3090 (24 GB) |
| GGUF IQ4_XS | 16.0 GB | 18.1 GB | RTX 3090 (24 GB) |
| GGUF Q3_K_M | 14.4 GB | 16.4 GB | RTX 3090 (24 GB) |
| GGUF IQ3_XXS | 12.1 GB | 13.9 GB | RTX 4060 Ti 16GB |
| GGUF Q2_K | 12.3 GB | 14.1 GB | RTX 4060 Ti 16GB |
Fine-tuning Nemotron 3 Nano 30B-A3B? Nemotron 3 Nano 30B-A3B VRAM for LoRA, QLoRA and full training.
Nemotron 3 Nano 30B-A3B GGUF files on Hugging Face
The 8 GGUF files llama.cpp picks for Nemotron 3 Nano 30B-A3B with -hf <repo>:<QUANT>, with the bytes the Hugging Face file list reported on 2026-09-29. Each total is that file plus the FP16 KV cache and 0.5 GB + 10%, one request. "vs estimate" compares the file with the bits-per-weight size the table above uses.
| Quant | File | Size | vs estimate | 8K | 32K | 128K |
|---|---|---|---|---|---|---|
| Q2_K | bartowski/ | 16.8 GB18,082,750,688 bytes | +37% | 19.1 GB | 19.2 GB | 19.8 GB |
| IQ4_XS | unsloth/ | 16.9 GB18,168,955,680 bytes | +6% | 19.2 GB | 19.3 GB | 19.9 GB |
| Q3_K_M | unsloth/ | 18.6 GB20,007,397,152 bytes | +30% | 21.0 GB | 21.2 GB | 21.8 GB |
| Q4_K_M | ggml-org/ | 20.9 GB22,421,827,488 bytes | +17% | 23.5 GB | 23.7 GB | 24.3 GB |
| Q5_K_M | unsloth/ | 24.4 GB26,149,294,368 bytes | +17% | 27.3 GB | 27.5 GB | 28.1 GB |
| Q6_K | unsloth/ | 31.2 GB33,508,167,456 bytes | +29% | 34.9 GB | 35.0 GB | 35.7 GB |
| Q8_0 | ggml-org/ | 31.3 GB33,585,500,064 bytes | ±0% | 35.0 GB | 35.1 GB | 35.7 GB |
| BF16 | ggml-org/ | 58.8 GB63,181,509,024 bytes | ±0% | 65.3 GB | 65.4 GB | 66.1 GB |
GB here is GiB (1024³ bytes), as everywhere on this site; Hugging Face shows the Q4_K_M file as 22.4 GB, in 10⁹ bytes.
Which Nemotron 3 Nano 30B-A3B GGUF fits a 16, 24, 32, 48 or 80 GB GPU or a Mac
From the file sizes above: the largest file that fits each machine with an 8K context and 0.5 GB left free, the longest context it then has room for, and the longest context for Q4_K_M (20.9 GB). One request, FP16 KV cache. Where nothing fits, the --n-cpu-moe table above keeps experts in system RAM.
| Hardware | Largest GGUF, 8K | Its longest context | Q4_K_M, longest context |
|---|---|---|---|
| RTX 5060 Ti 16GB | None fits | — | No |
| RTX 4090 (24 GB) | Q3_K_M, 18.6 GB | 256K (full) | 4K |
| RTX 5090 (32 GB) | Q5_K_M, 24.4 GB | 256K (full) | 256K (full) |
| L40S (48 GB) | Q8_0, 31.3 GB | 256K (full) | 256K (full) |
| H100 SXM (80 GB) | BF16, 58.8 GB | 256K (full) | 256K (full) |
| M4 Pro Mac (64 GB, 48 GB usable) | Q8_0, 31.3 GB | 256K (full) | 256K (full) |
| M4 Max Mac (128 GB, 96 GB usable) | BF16, 58.8 GB | 256K (full) | 256K (full) |
Nemotron 3 Nano 30B-A3B at 8K, 32K, 128K and 256K (full) tokens of context
6 of its 52 layers use full attention and 46 are Mamba or feed-forward layers with no growing cache. Each extra token of context adds 6 KB of FP16 cache per request. The last column is the smallest setup here, one card or a group, that holds it at Q4_K_M. How the KV cache works.
| Context | KV cache, FP16 | Total at Q4_K_M | Total at Q8_0 | Smallest setup, Q4_K_M |
|---|---|---|---|---|
| 8K tokens | 48 MB | 20.1 GB | 34.9 GB | RTX 3090 (24 GB) |
| 32K tokens | 192 MB | 20.3 GB | 35.1 GB | RTX 3090 (24 GB) |
| 128K tokens | 768 MB | 20.9 GB | 35.7 GB | RTX 3090 (24 GB) |
| 256K tokens | 1.50 GB | 21.7 GB | 36.5 GB | RTX 3090 (24 GB) |
How fast Nemotron 3 Nano 30B-A3B writes
Tokens per second for one request with 8,192 tokens of context, estimated from memory bandwidth and the parameters read per token. A dash means it does not fit on one card. Try other settings in the speed calculator.
| Hardware | Bandwidth | Q4_K_M | FP8 |
|---|---|---|---|
| RTX 3060 12GB | 360 GB/s | — | — |
| RTX 4090 | 1,008 GB/s | 115–208 | — |
| RTX 5090 | 1,792 GB/s | 181–343 | — |
| M4 Max Mac (128 GB) | 546 GB/s | 68–118 | 43–74 |
| M3 Ultra Mac Studio (512 GB) | 819 GB/s | 97–173 | 63–109 |
| H100 SXM | 3,350 GB/s | 273–557 | 199–382 |
| H200 | 4,800 GB/s | 333–713 | 252–505 |
Longest context on one GPU
How many tokens of context Nemotron 3 Nano 30B-A3B fits on a single card with one request, an FP16 KV cache and 0.5 GB left free. "Full" means the model's whole context window fits.
| GPU | Memory | Q4_K_M | Q8_0 | FP8 |
|---|---|---|---|---|
| RTX 3060 | 12 GB | No | No | No |
| RTX 4060 Ti 16GB | 16 GB | No | No | No |
| RTX 3090 / 4090 | 24 GB | 256K (full) | No | No |
| RTX 5090 | 32 GB | 256K (full) | No | No |
| A100 40GB | 40 GB | 256K (full) | 256K (full) | 256K (full) |
| Mac, 64 GB unified memory | 48 GB | 256K (full) | 256K (full) | 256K (full) |
| L40S / RTX 6000 Ada | 48 GB | 256K (full) | 256K (full) | 256K (full) |
| A100 / H100 80GB | 80 GB | 256K (full) | 256K (full) | 256K (full) |
| Mac, 128 GB unified memory | 96 GB | 256K (full) | 256K (full) | 256K (full) |
| H200 | 141 GB | 256K (full) | 256K (full) | 256K (full) |
| B200 | 180 GB | 256K (full) | 256K (full) | 256K (full) |
Model details
- Parameters
- 31.6B (31,577,937,344)
- Experts
- 128 routed experts, all loaded
- Active per token
- 3.5B
- Layers
- 6 of its 52 layers use full attention and 46 are Mamba or feed-forward layers with no growing cache
- Attention cache
- 2 KV heads × 128
- Context length
- 262,144 tokens
- Published weights
- 58.8 GB (BF16)
- On Hugging Face
- nvidia/
NVIDIA-Nemotron-3-Nano-30B-A3B-BF16
Why this estimate looks this way
At Q4_K_M and an 8K-token context, Nemotron 3 Nano 30B-A3B uses 17.8 GB for weights, 48 MB for its FP16 KV cache and 2.28 GB for estimated runtime overhead, totaling 20.1 GB. The overhead is a 0.5 GB base plus 10% of weights and cache.
This is a mixture-of-experts model: all 128 experts contribute to the 31.6B parameters held in memory, even though only about 3.5B parameters run per token. Using only active parameters would understate VRAM.
Its attention layout matters for long context: 6 of its 52 layers use full attention and 46 are Mamba or feed-forward layers with no growing cache. The FP16 cache grows by about 6 KB per additional token per request.
The architecture and published checkpoint size come from the model's config.json and weight files. These are estimates rather than measured peak memory; inference engines can reserve extra buffers or preallocate the full configured cache.
Nemotron 3 Nano 30B-A3B next to similar-sized models
The three models here closest to it in parameter count, at Q4_K_M with 8,192 tokens of context.
| Model | Parameters | Total | KV per token | Smallest setup |
|---|---|---|---|---|
| Nemotron 3 Nano 30B-A3B | 31.6B, 3.5B active | 20.1 GB | 6 KB | RTX 3090 (24 GB) |
| Gemma 4 31B | 31.3B | 21.9 GB | 80 KB | RTX 3090 (24 GB) |
| GLM-4.7 Flash | 31.2B, 3B active | 20.3 GB | 53 KB | RTX 3090 (24 GB) |
| Xing 4.0 29B-A4B | 31.2B, 4B active | 20.2 GB | 45 KB | RTX 3090 (24 GB) |
Nemotron 3 Nano 30B-A3B VRAM questions
How much VRAM do I need to run Nemotron 3 Nano 30B-A3B locally?
About 20.1 GB at Q4_K_M with an 8K context and one request, by the bits-per-weight estimate, and 65.3 GB at BF16. The Q4_K_M GGUF NVIDIA-Nemotron-3-Nano-30B-A3B-Q4_K_M.gguf in ggml-org/
Can I run Nemotron 3 Nano 30B-A3B on a 24 GB GPU?
Yes. On the RTX 4090 (24 GB), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q3_K_M (18.6 GB), with its full 256K-token context.
Which quantization of Nemotron 3 Nano 30B-A3B fits in 16 GB of VRAM?
The RTX 5060 Ti 16GB alone cannot hold it: the smallest listed GGUF, Q2_K at 16.8 GB, needs 19.1 GB with an 8K context. With llama.cpp's --n-cpu-moe 21 and the Q4_K_M GGUF it uses 15.4 GB on the card and 8.70 GB of system RAM at 32K tokens.
Can I run Nemotron 3 Nano 30B-A3B on a Mac?
On the M4 Pro Mac (64 GB, 48 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q8_0 (31.3 GB), with its full 256K-token context. On the M4 Max Mac (128 GB, 96 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is BF16 (58.8 GB), with its full 256K-token context. By default macOS lets the GPU use about 75% of unified memory.
How much more VRAM does Nemotron 3 Nano 30B-A3B need for 32K or 128K tokens of context?
Its FP16 KV cache is 48 MB at 8K, 192 MB at 32K, 768 MB at 128K for one request, so 128K adds 720 MB over 8K, plus 10% overhead. A q8_0 cache
Why does Nemotron 3 Nano 30B-A3B use more VRAM than its GGUF file size?
The file holds only the weights. At Q4_K_M with an 8K context: 20.9 GB of weights (the file's 22,421,827,488 bytes) + 48 MB of FP16 KV cache + 2.59 GB of compute buffers and runtime (0.5 GB + 10%) = 23.5 GB.
Does Nemotron 3 Nano 30B-A3B need less VRAM because only 3.5B parameters are active?
No. All 128 experts stay loaded, so the Q4_K_M file takes 20.9 GB. The active parameters decide speed: each generated token reads about 1.97 GB of them.
Badge for your model card
Paste it into a Hugging Face or GitHub README; it shows the Q4_K_M total above and links to this page. Q8_0 and FP16 badges.
Numbers read from the model files on Hugging Face on . Compare it with other models in the reproducible model and GPU report.