Qwen2.5 Coder 1.5B Instruct on Apple M2 Pro (16 GB)

Can the Apple M2 Pro (16 GB) run Qwen2.5 Coder 1.5B Instruct?

Yes, it runs great

Runs great. At Q8_0 it needs about 3.3 GB of 10.7 GB usable, with an estimated speed of 69.9 tok/s.

Best quant: Q8_0
Generation speed: 69.9 tok/s
Prompt processing: 2,738 tok/s
First token (1K prompt): 0.4 s
Largest safe context: 32K

Best app to run it on the Apple M2 Pro (16 GB)

On macOS

LM Studio

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

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

Open Qwen2.5 Coder 1.5B Instruct in LM Studio

MLX LM Runs the MLX build, typically 35–90% faster than GGUF for a model with 1.5B active parameters on Apple silicon.
Ollama One command with Ollama’s own build of this model.

Want an agent? Qwen2.5 Coder 1.5B Instruct supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

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 Qwen2.5 Coder 1.5B Instruct

Recommended for the Apple M2 Pro (16 GB): Q8_0. 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 qwen2.5-coder:1.5b-instruct-q8_0

Quantized files · GGUF

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

Download the Q8_0 file (opens in a new tab)

huggingface.co/Qwen/Qwen2.5-Coder-1.5B-Instruct-GGUF (opens in a new tab)

ollama run hf.co/Qwen/Qwen2.5-Coder-1.5B-Instruct-GGUF:Q8_0

Original weights · Hugging Face

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

huggingface.co/Qwen/Qwen2.5-Coder-1.5B-Instruct (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Alibaba. The weights themselves download from Hugging Face.

github.com/QwenLM/Qwen3-Coder (opens in a new tab)

Qwen’s coder repo, renamed from Qwen2.5-Coder to Qwen3-Coder.

git clone https://github.com/QwenLM/Qwen3-Coder

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

How it’s rated

Quality 26Basic quality (D) · 26 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q8_0, 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 M2 Pro (16 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.	11.7 / 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.	7.2 / 15
Match score	58.9 / 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 M2 Pro (16 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	2.3 GB	10.7 GB	225 tok/s	Runs great	18Basic quality (D) · 18 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 (opens in a new tab)
`Q3_K_M`	2.4 GB	10.7 GB	177 tok/s	Runs great	21Basic quality (D) · 21 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	2.6 GB	10.7 GB	137 tok/s	Runs great	24Basic quality (D) · 24 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	2.8 GB	10.7 GB	113 tok/s	Runs great	25Basic quality (D) · 25 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	3.0 GB	10.7 GB	95.2 tok/s	Runs great	25Basic quality (D) · 25 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	3.3 GB	10.7 GB	69.9 tok/s	Runs great	26Basic quality (D) · 26 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	4.8 GB	10.7 GB	32.2 tok/s	Runs great	26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 60/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

26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4060 F16 · 50.9 tok/s · Runs great
26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking. Intel Arc B580 F16 · 65.1 tok/s · Runs great
26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3060 12GB F16 · 67.3 tok/s · Runs great
26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 SUPER F16 · 94.3 tok/s · Runs great
26Basic quality (D) · 26 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. Apple M4 Pro (24 GB) F16 · 44.0 tok/s · Runs great
26Basic quality (D) · 26 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 (16 GB) Q8_0 · 41.9 tok/s · Runs great

Quick answers

How much memory does Qwen2.5 Coder 1.5B Instruct need on the M2 Pro 16GB?

At Q8_0 it needs about 3.3 GB. The M2 Pro 16GB has 10.7 GB usable.

How fast is Qwen2.5 Coder 1.5B Instruct on the M2 Pro 16GB?

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

Which quantization of Qwen2.5 Coder 1.5B Instruct should I use on the M2 Pro 16GB?

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