on

Can the Apple M1 (8 GB) run Phi-3.5 Vision Instruct?

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

Yes, but slowly (far over GPU memory limit)

Slow (far over GPU memory limit). At Q3_K_M it needs about 6.3 GB of 5.4 GB usable, with an estimated speed of 19.1 tok/s.

Best quant
Q3_K_M
Generation speed
19.1 tok/s
Prompt processing
388 tok/s
First token (1K prompt)
2.6 s
Largest safe context
5K

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

On macOS

Docker Model Runner

Command line + local API · runs on llama.cpp, vLLM

  • Splits the model between GPU memory and system RAM, which this setup needs.
  • Handy if you already work in Docker.
docker model run hf.co/microsoft/Phi-3.5-vision-instruct

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.5 Vision Instruct

Original weights · Hugging Face

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

huggingface.co/microsoft/Phi-3.5-vision-instruct (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 31Basic quality (D) · 31 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 43/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q3_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 Slowfar over GPU memory limit
How well it runs on the Apple M1 (8 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.14.4 / 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.4.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.10.4 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score43.7 / 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 (8 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 5.9 GB 5.4 GB 24.3 tok/s Slowfar over GPU memory limit 26Basic quality (D) · 26 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 42/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q3_K_M 6.3 GB 5.4 GB 19.1 tok/s Slowfar over GPU memory limit 31Basic quality (D) · 31 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 43/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q4_K_M 6.8 GB 5.4 GB — Won't run 36Basic quality (D) · 36 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 4/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 7.2 GB 5.4 GB — Won't run 36Basic quality (D) · 36 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 4/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 7.7 GB 5.4 GB — Won't run 37Basic quality (D) · 37 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 8.6 GB 5.4 GB — Won't run 38Basic quality (D) · 38 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 12.6 GB 5.4 GB — Won't run 38Basic quality (D) · 38 of 100: how capable the model is at F16, whatever it runs on. Match score 5/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.5 Vision Instruct need on the M1 8GB?

At Q3_K_M it needs about 6.3 GB. The M1 8GB has 5.4 GB usable.

How fast is Phi-3.5 Vision Instruct on the M1 8GB?

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

Which quantization of Phi-3.5 Vision Instruct should I use on the M1 8GB?

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

Was this page helpful?