Command R 35B (v01) on Apple M5 Ultra (256 GB)

Can the Apple M5 Ultra (256 GB) run Command R 35B (v01)?

Yes, it runs great

Runs great. At Q4_K_M it needs about 48.0 GB of 192 GB usable, with an estimated speed of 36.3 tok/s.

Best quant: Q4_K_M
Generation speed: 36.3 tok/s
Prompt processing: 668 tok/s
First token (1K prompt): 1.5 s
Largest safe context: 115K

Best app to run it on the Apple M5 Ultra (256 GB)

On macOS

LM Studio

Desktop app · runs on llama.cpp, MLX · use the MLX build

Runs the MLX build, typically up to 10% faster than GGUF for a model with 35B active parameters on Apple silicon.
Point-and-click: search, download and chat in one window.

Open Command R 35B (v01) in LM Studio

Ollama One command with Ollama’s own build of this model.
llama.cpp Usually the first to support new model architectures.

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Command R 35B (v01)

Recommended for the Apple M5 Ultra (256 GB): Q4_K_M. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run command-r:35b-v0.1-q4_K_M

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q4_K_M file (opens in a new tab)

huggingface.co/bartowski/c4ai-command-r-v01-GGUF (opens in a new tab)

ollama run hf.co/bartowski/c4ai-command-r-v01-GGUF:Q4_K_M

Original weights · Hugging Face

Full-precision files from Cohere, for fine-tuning, vLLM, Transformers.

huggingface.co/CohereLabs/c4ai-command-r-v01 (opens in a new tab)

Free Hugging Face account needed: accept the license on the model page and the download starts right away.

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 51Fair quality (C) · 51 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q4_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great: How well it runs on the Apple M5 Ultra (256 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	23.1 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	14.3 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	5.8 / 15
Match score	68.1 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Apple M5 Ultra (256 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	40.7 GB	192 GB	59.6 tok/s	Runs great	37Basic quality (D) · 37 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q3_K_M`	43.8 GB	192 GB	46.9 tok/s	Runs great	45Fair quality (C) · 45 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	48.0 GB	192 GB	36.3 tok/s	Runs great	51Fair quality (C) · 51 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	51.5 GB	192 GB	30.0 tok/s	Runs well	52Fair quality (C) · 52 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	55.4 GB	192 GB	25.2 tok/s	Runs well	53Fair quality (C) · 53 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	63.8 GB	192 GB	18.5 tok/s	Runs well	54Fair quality (C) · 54 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	96.7 GB	192 GB	8.5 tok/s	Slow	54Fair quality (C) · 54 of 100: how capable the model is at F16, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	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

53Fair quality (C) · 53 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell Q6_K · 43.6 tok/s · Runs great
45Fair quality (C) · 45 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q3_K_M · 81.3 tok/s · Runs well (tight fit)
51Fair quality (C) · 51 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (64 GB) Q4_K_M · 16.5 tok/s · Runs well
51Fair quality (C) · 51 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking. Apple M1 Max (64 GB) Q4_K_M · 12.1 tok/s · Runs well
51Fair quality (C) · 51 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (128 GB) Q4_K_M · 16.5 tok/s · Runs well
45Fair quality (C) · 45 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Pro (48 GB) Q3_K_M · 10.7 tok/s · Runs well (tight fit)

Quick answers

How much memory does Command R 35B (v01) need on the M5 Ultra 256GB?

At Q4_K_M it needs about 48.0 GB. The M5 Ultra 256GB has 192 GB usable.

How fast is Command R 35B (v01) on the M5 Ultra 256GB?

About 36.3 tok/s at Q4_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Command R 35B (v01) should I use on the M5 Ultra 256GB?

Q4_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

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.