Nemotron 3 Nano 30B-A3B on Apple M2 Pro (32 GB)
Can the Apple M2 Pro (32 GB) run Nemotron 3 Nano 30B-A3B?
Yes, it runs well
Runs well. At Q3_K_M it needs about 17.8 GB of 21.4 GB usable, with an estimated speed of 39.0 tok/s.
- Best quant
Q3_K_M- Generation speed
- 39.0 tok/s
- Prompt processing
- 1,205 tok/s
- First token (1K prompt)
- 0.9 s
- Largest safe context
- 256K
Download Nemotron 3 Nano 30B-A3B
Quickest · Ollama
One command downloads a ready-to-run version and starts a chat.
ollama run nemotron-3-nano:30bQuantized files · GGUF
Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.
huggingface.co/ggml-org/NVIDIA-Nemotron-3-Nano-30B-A3B-GGUF (opens in a new tab)
ollama run hf.co/ggml-org/NVIDIA-Nemotron-3-Nano-30B-A3B-GGUFOriginal weights · Hugging Face
Full-precision files from NVIDIA, for fine-tuning, vLLM, Transformers.
huggingface.co/nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 (opens in a new tab)
Official repo · GitHub
Reference code, inference scripts and docs from NVIDIA. The weights themselves download from Hugging Face.
github.com/NVIDIA-NeMo/Nemotron (opens in a new tab)
git clone https://github.com/NVIDIA-NeMo/NemotronHow the A grade is scored
Every result gets up to 100 points from four parts. The points decide the letter grade.
| Model quality | 29.1 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 14.8 / 15 | |
| Memory use | 15.0 / 15 | |
| Total | 83.9 / 100 | 83 ptsGreat (A) · 83 of 100 points: Model quality 29.1/45, Memory fit 25.0/25, Speed 14.8/15, Memory use 15.0/15 |
Every quantization on the Apple M2 Pro (32 GB)
| Quant | Memory needed | Available | Speed | Fit | Grade · points | Download |
|---|---|---|---|---|---|---|
Q2_K | 15.0 GB | 21.4 GB | 49.6 tok/s | Runs well | 79 ptsGreat (A) · 79 of 100 points: Model quality 24.3/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 | GGUF files (opens in a new tab) |
Q3_K_M | 17.8 GB | 21.4 GB | 39.0 tok/s | Runs well | 83 ptsGreat (A) · 83 of 100 points: Model quality 29.1/45, Memory fit 25.0/25, Speed 14.8/15, Memory use 15.0/15 | GGUF files (opens in a new tab) |
Q4_K_M | 21.6 GB | 21.4 GB | 25.7 tok/s | Runs with offload | 69 ptsGood (B) · 69 of 100 points: Model quality 32.9/45, Memory fit 10.0/25, Speed 12.0/15, Memory use 15.0/15 | GGUF (opens in a new tab) |
Q5_K_M | 24.8 GB | 21.4 GB | 21.2 tok/s | Heavy offload | 63 ptsGood (B) · 63 of 100 points: Model quality 33.6/45, Memory fit 4.0/25, Speed 10.9/15, Memory use 15.0/15 | GGUF files (opens in a new tab) |
Q6_K | 28.3 GB | 21.4 GB | — | Won't run | 10 ptsWon't run (F) · 10 of 100 points: Model quality 10.3/45, Memory fit 0.0/25, Speed 0.0/15, Memory use 0.0/15 | GGUF files (opens in a new tab) |
Q8_0 | 35.8 GB | 21.4 GB | — | Won't run | 10 ptsWon't run (F) · 10 of 100 points: Model quality 10.4/45, Memory fit 0.0/25, Speed 0.0/15, Memory use 0.0/15 | GGUF (opens in a new tab) |
F16 | 65.5 GB | 21.4 GB | — | Won't run | 10 ptsWon't run (F) · 10 of 100 points: Model quality 10.4/45, Memory fit 0.0/25, Speed 0.0/15, Memory use 0.0/15 | GGUF (opens in a new tab) Original weights (opens in a new tab) |
Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.
Other hardware that runs it
- 89 ptsExcellent (S) · 89 of 100 points: Model quality 34.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 Apple M4 Max (64 GB)
- 89 ptsExcellent (S) · 89 of 100 points: Model quality 34.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 NVIDIA RTX PRO 6000 Blackwell
- 88 ptsExcellent (S) · 88 of 100 points: Model quality 34.3/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 14.6/15 Apple M1 Max (64 GB)
- 88 ptsExcellent (S) · 88 of 100 points: Model quality 33.6/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 NVIDIA GeForce RTX 5090
- 87 ptsExcellent (S) · 87 of 100 points: Model quality 32.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 14.6/15 Apple M4 Pro (48 GB)
- 86 ptsExcellent (S) · 86 of 100 points: Model quality 32.9/45, Memory fit 24.0/25, Speed 15.0/15, Memory use 15.0/15 AMD Radeon RX 7900 XTX
Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.