on

Can the Apple M3 Ultra (512 GB) run MiniCPM3 4B?

38Basic quality (D) · 38 of 100: how capable the model is at F16, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At F16 it needs about 39.8 GB of 384 GB usable, with an estimated speed of 49.9 tok/s.

Best quant
F16
Generation speed
49.9 tok/s
Prompt processing
4,326 tok/s
First token (1K prompt)
0.3 s
Largest safe context
32K

Best app to run it on the Apple M3 Ultra (512 GB)

On macOS

LM Studio

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

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

Open MiniCPM3 4B in LM Studio

  • MLX LM Runs the MLX build, typically 20–35% faster than GGUF for a model with 4.1B active parameters on Apple silicon.
  • Jan Runs the MLX build, typically 20–35% faster than GGUF for a model with 4.1B active parameters on Apple silicon.

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 MiniCPM3 4B

Recommended for the Apple M3 Ultra (512 GB): F16. Every other quantization has its own download link in the table below.

Quantized files · GGUF

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

Download the F16 file (opens in a new tab)

huggingface.co/openbmb/MiniCPM3-4B-GGUF (opens in a new tab)

ollama run hf.co/openbmb/MiniCPM3-4B-GGUF:FP16

Original weights · Hugging Face

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

huggingface.co/openbmb/MiniCPM3-4B (opens in a new tab)

No sign-in needed.

How it’s rated

Quality 38Basic quality (D) · 38 of 100: how capable the model is at F16, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at F16, 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 M3 Ultra (512 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.17.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.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.2.4 / 15
Match score59.5 / 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 M3 Ultra (512 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 33.2 GB 384 GB 349 tok/s Runs great 26Basic quality (D) · 26 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 33.6 GB 384 GB 275 tok/s Runs great 31Basic quality (D) · 31 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 34.1 GB 384 GB 213 tok/s Runs great 36Basic quality (D) · 36 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 34.5 GB 384 GB 176 tok/s Runs great 36Basic quality (D) · 36 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 34.9 GB 384 GB 148 tok/s Runs great 37Basic quality (D) · 37 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 35.9 GB 384 GB 108 tok/s Runs great 38Basic quality (D) · 38 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 39.8 GB 384 GB 49.9 tok/s Runs great 38Basic quality (D) · 38 of 100: how capable the model is at F16, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking. 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

Quick answers

How much memory does MiniCPM3 4B need on the M3 Ultra 512GB?

At F16 it needs about 39.8 GB. The M3 Ultra 512GB has 384 GB usable.

How fast is MiniCPM3 4B on the M3 Ultra 512GB?

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

Which quantization of MiniCPM3 4B should I use on the M3 Ultra 512GB?

F16. 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.

Was this page helpful?