on

Can the Apple M1 Ultra (128 GB) run Phi-3 Medium 128K Instruct?

45Fair quality (C) · 45 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At Q6_K it needs about 21.4 GB of 96.0 GB usable, with an estimated speed of 42.0 tok/s.

Best quant
Q6_K
Generation speed
42.0 tok/s
Prompt processing
933 tok/s
First token (1K prompt)
1.1 s
Largest safe context
128K

Best app to run it on the Apple M1 Ultra (128 GB)

On macOS

LM Studio

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

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

Open Phi-3 Medium 128K Instruct 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 Phi-3 Medium 128K Instruct

Recommended for the Apple M1 Ultra (128 GB): Q6_K. 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 phi3:14b-medium-128k-instruct-q6_K

Quantized files · GGUF

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

Download the Q6_K file (opens in a new tab)

huggingface.co/bartowski/Phi-3-medium-128k-instruct-GGUF (opens in a new tab)

ollama run hf.co/bartowski/Phi-3-medium-128k-instruct-GGUF:Q6_K

Original weights · Hugging Face

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

huggingface.co/microsoft/Phi-3-medium-128k-instruct (opens in a new tab)

No sign-in needed.

How it’s rated

Quality 45Fair quality (C) · 45 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q6_K, 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 M1 Ultra (128 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.20.5 / 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.5.1 / 15
Match score65.6 / 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 M1 Ultra (128 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 15.5 GB 96.0 GB 99.5 tok/s Runs great 32Basic quality (D) · 32 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 16.8 GB 96.0 GB 78.3 tok/s Runs great 38Basic quality (D) · 38 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 18.5 GB 96.0 GB 60.6 tok/s Runs great 43Fair quality (C) · 43 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 19.9 GB 96.0 GB 50.0 tok/s Runs great 44Fair quality (C) · 44 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 21.4 GB 96.0 GB 42.0 tok/s Runs great 45Fair quality (C) · 45 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 24.8 GB 96.0 GB 30.8 tok/s Runs great 46Fair quality (C) · 46 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 37.9 GB 96.0 GB 14.2 tok/s Runs well 46Fair quality (C) · 46 of 100: how capable the model is at F16, whatever it runs on. Match score 63/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

Quick answers

How much memory does Phi-3 Medium 128K Instruct need on the M1 Ultra 128GB?

At Q6_K it needs about 21.4 GB. The M1 Ultra 128GB has 96.0 GB usable.

How fast is Phi-3 Medium 128K Instruct on the M1 Ultra 128GB?

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

Which quantization of Phi-3 Medium 128K Instruct should I use on the M1 Ultra 128GB?

Q6_K. 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?