← All modelsMODEL CHECK

Can I run Nemotron 3 Nano 30B-A3B?

Nemotron 3 Nano 30B-A3B by NVIDIA needs around 32 GB of RAM at the recommended 4-bit quantization (19.2 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~160 tok/s on a Apple M-series Max.

Reading your hardware signals…

Real-world notes

Nemotron 3 Nano is a mixture-of-experts model from NVIDIA aimed at people who want strong chat, reasoning, and coding from a local box without paying full dense-model costs. The trick is in the name: it carries 31.6B parameters total but only routes about 3.6B of them per token, so it generates at the speed of a tiny model while thinking with a much larger one. The catch every MoE newcomer learns the hard way is that you still have to load the whole thing. At a 4-bit quant that is roughly 19 GB of weights, and you want at least 32 GB of RAM, which rules out a 12 GB card like an RTX 3060 entirely.

In daily use the active-parameter trick really shows. On an RTX 4090 it streams at around 393 tokens per second, which is absurdly fast for a model this capable, and even an Apple Silicon M Max sits near 160 tokens per second on unified memory. CPU-only on DDR5 drops to about 23 tokens per second, usable for batch jobs but not interactive chat. The headline feature is the 1,000K context window, but treat that as a billboard number: at just 128K of context the full memory footprint climbs to about 50 GB, so on a 32 GB machine you are realistically working with a few tens of thousands of tokens, not a million.

Against its peers, Gemma 4 31B is the more flexible pick if you need vision, since Nemotron 3 Nano is text-only, and Granite 4.0 H Small is a comparable-size dense alternative if you would rather not deal with MoE memory quirks. What Nemotron does best is throughput-per-quality: nothing else in this size class generates this fast while still handling multi-step reasoning. One caution before you build on it: the NVIDIA Open Model license is open-weight, not true open-source, so read the terms carefully rather than assuming Apache-style freedom for commercial use.

Specifications

Parameters31.6B (3.6B active)
Context window1M tokens
ProviderNVIDIA
LicenseNVIDIA Open Model
Released2025-12
Best forChat, Reasoning, Coding

Size by quantization

QuantizationBits/weightDownloadMin RAMQuality
Q2_K3.3513.2 GB24 GBNoticeable loss
Q4_K_MRecommended4.8519.2 GB32 GBRecommended
Q5_K_M5.6522.3 GB32 GBHigh
Q8_08.533.6 GB48 GBNear-original
F161663.2 GB96 GBOriginal

Sizes are estimates from parameter count × bits per weight; real GGUF builds vary slightly. · Data updated: 2026-06-11 · How we calculate these numbers →

Memory needed by context length

ContextKV cache (est.)Total memory (Q4)
4K tokens~1.0 GB~20.2 GB
8K tokens~1.9 GB~21.1 GB
32K tokens~7.8 GB~27.0 GB
128K tokens~31.1 GB~50.3 GB

The KV cache grows with context length — a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.

Estimated speed by hardware

HardwareBandwidth~Speed
NVIDIA RTX 3060 12GB360 GB/sWon't fit in VRAM
NVIDIA RTX 4090 24GB1008 GB/s~393 tok/s
Apple M-series (base)100 GB/s~39 tok/s
Apple M-series Pro270 GB/s~105 tok/s
Apple M-series Max410 GB/s~160 tok/s
CPU only (dual-channel DDR5)60 GB/s~23 tok/s

Token generation is memory-bandwidth bound: tok/s ≈ bandwidth × 0.85 ÷ model size at Q4. Real-world numbers vary by runtime and context length.

Run it locally

The easiest path is Ollama — one command and you're chatting:

ollama run nemotron-3-nano:30b

Frequently asked questions