Can Command R 35B run on Mac mini M4 64GB?

YES — Runs Great

A73Great

▲Estimated — low-sample bucket· few comparable runs

Command R 35B needs ~31.6 GB VRAM. Mac mini M4 64GB has 46.1 GB. With Q4_K_M quantization, expect ~4 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: Very lowStack: StandardBottleneck: Memory bandwidth

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 31.6 GB, 7.9 tok/s, Runs well

31.6 GB required46.1 GB available

69% VRAM used

Fit status

Runs well

Decode

7.9 tok/s

TTFT

24439 ms

Safe context

111K

Memory

31.6 GB / 46.1 GB

Memory breakdown

Weights21.3 GB

KV Cache2.4 GB

Runtime0.9 GB

Headroom6.9 GB

See how fast it feels

See how fast it feelsCommand R 35B on Mac mini M4 64GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API.

When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed.

Key benefits of running locally:
 - Full privacy: your prompts never leave your machine
 - No per-token cost or rate limits
 - Works offline once the model is downloaded
 - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb:

 Model size Q4 (4-bit) Q8 (8-bit) FP16
 7B params ~4.3 GB ~7.5 GB ~14 GB
 13B params ~7.9 GB ~13.9 GB ~26 GB
 70B params ~42.7 GB ~74.9 GB ~140 GB

Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 7.9 tok/s decode · 24.4s TTFT (warm) · 20 tok/s prefill

What limits this setup

The model fits in shared memory, but shared-memory bandwidth is now the real limiter.

Fit does not mean dedicated-VRAM speed

Unified or shared memory can make a model technically fit, but sustained tokens per second may still trail a discrete high-bandwidth GPU with less total memory.

Shared-memory contention still exists

The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.

Best improvement path

Prioritize bandwidth, not only capacity

If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	A	Runs well	4.0 tok/s	26094 ms	111K
Coding	A	Runs well	4.0 tok/s	47840 ms	111K
Agentic Coding	A	Runs well	4.0 tok/s	69585 ms	111K
Reasoning	A	Runs well	4.0 tok/s	56538 ms	111K
RAG	A	Runs well	4.0 tok/s	86981 ms	111K

Quantization options

How Command R 35B (35B params) fits at each quantization level on Mac mini M4 64GB (46.1 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	13.7 GB	Low	A71
Q3_K_S	3	17.2 GB	Low	A72
NVFP4	4

Get started

Copy-paste commands to run Command R 35B on your machine.

Run

ollama run command-r

Your hardware

More models your Mac mini M4 64GB can run

Model	Params	Grade	Decode	Capabilities
👁 Moonshot AI Kimi Linear 48B A3B	48B	A	5.3 tok/s

Frequently asked questions

See all results for Mac mini M4 64GB See all hardware for Command R 35B

URL: https://willitrunai.com/can-run/command-r-35b-on-m4-mini-64gb

⇱