Can Qwen3.5 35B A3B run on Mac mini M4 64GB?

YES — Runs Great

C49Usable
Estimated — low-sample bucket· few comparable runs

Qwen3.5 35B A3B needs ~33.3 GB VRAM. Mac mini M4 64GB has 46.1 GB. With Q4_K_M quantization, expect ~7 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: Very lowStack: StandardBottleneck: Memory bandwidth
Share:

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 33.3 GB, 7.3 tok/s, Runs well
33.3 GB required46.1 GB available
72% VRAM used

Fit status

Runs well

Decode

7.3 tok/s

TTFT

26578 ms

Safe context

66K

Memory

33.3 GB / 46.1 GB

Memory breakdown

Weights21.3 GB
KV Cache4.1 GB
Runtime0.9 GB
Headroom6.9 GB

See how fast it feels

See how fast it feelsQwen3.5 35B A3B on Mac mini M4 64GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API. When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed. Key benefits of running locally: - Full privacy: your prompts never leave your machine - No per-token cost or rate limits - Works offline once the model is downloaded - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb: Model size Q4 (4-bit) Q8 (8-bit) FP16 7B params ~4.3 GB ~7.5 GB ~14 GB 13B params ~7.9 GB ~13.9 GB ~26 GB 70B params ~42.7 GB ~74.9 GB ~140 GB Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 7.3 tok/s decode · 26.6s TTFT (warm) · 18 tok/s prefill

What limits this setup

The model fits in shared memory, but shared-memory bandwidth is now the real limiter.

Fit does not mean dedicated-VRAM speed

Unified or shared memory can make a model technically fit, but sustained tokens per second may still trail a discrete high-bandwidth GPU with less total memory.

Shared-memory contention still exists

The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.

Best improvement path

Prioritize bandwidth, not only capacity

If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatCRuns well7.3 tok/s14497 ms66K
CodingCRuns well7.3 tok/s26578 ms66K
Agentic CodingCRuns well7.3 tok/s38658 ms66K
ReasoningCRuns well7.3 tok/s31410 ms66K
RAGCRuns well7.3 tok/s48323 ms66K

Quantization options

How Qwen3.5 35B A3B (35B params) fits at each quantization level on Mac mini M4 64GB (46.1 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
13.7 GB
LowC45
Q3_K_S
3
17.2 GB
LowC46
NVFP4
4
19.6 GB
MediumC47
Q4_K_M
4
21.3 GB
MediumC48
Q5_K_M
5
25.2 GB
HighC49
Q6_K
6
28.7 GB
HighC48
Q8_0Best for your GPU
8
37.5 GB
Very HighC48
F16
16
71.8 GB
MaximumF0

Get started

Copy-paste commands to run Qwen3.5 35B A3B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \ --hf-repo "unsloth/Qwen3.5-35B-A3B-GGUF" \ --hf-file "Qwen3.5-35B-A3B-GGUF-Q4_K_M.gguf" \ -c 4096 -ngl 99

アップグレードオプション

Qwen3.5 35B A3Bを快適に動かすハードウェア

Frequently asked questions

Can Mac mini M4 64GB run Qwen3.5 35B A3B?

Yes, Mac mini M4 64GB can run Qwen3.5 35B A3B with a C grade (Runs well). Expected decode speed: 7.3 tok/s.

How much VRAM does Qwen3.5 35B A3B need?

Qwen3.5 35B A3B (35B parameters) requires approximately 33.3 GB of memory with Q4_K_M quantization.

What is the best quantization for Qwen3.5 35B A3B?

The recommended quantization for Qwen3.5 35B A3B is Q4_K_M, which balances quality and memory efficiency.

What speed will Qwen3.5 35B A3B run at on Mac mini M4 64GB?

On Mac mini M4 64GB, Qwen3.5 35B A3B achieves approximately 7.3 tokens per second decode speed with a time-to-first-token of 26578ms using Q4_K_M quantization.

Can Mac mini M4 64GB run Qwen3.5 35B A3B for coding?

For coding workloads, Qwen3.5 35B A3B on Mac mini M4 64GB receives a C grade with 7.3 tok/s and 66K context.

What context window can Qwen3.5 35B A3B use on Mac mini M4 64GB?

On Mac mini M4 64GB, Qwen3.5 35B A3B can safely use up to 66K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

What should I upgrade first if Qwen3.5 35B A3B feels slow on Mac mini M4 64GB?

Prioritize bandwidth, not only capacity. If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.

Is unified memory on Mac mini M4 64GB as fast as VRAM for Qwen3.5 35B A3B?

Not always. Mac mini M4 64GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.

See all results for Mac mini M4 64GBSee all hardware for Qwen3.5 35B A3B
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/hf-unsloth--qwen3-5-35b-a3b-gguf-on-m4-mini-64gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: