on

Can the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB) run Phi-4 (14B)?

60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well

Runs well. At Q4_K_M it needs about 12.5 GB of 16.0 GB usable, with an estimated speed of 25.1 tok/s.

Best quant
Q4_K_M
Generation speed
25.1 tok/s
Prompt processing
1,411 tok/s
First token (1K prompt)
0.7 s
Largest safe context
16K

Best app to run it on the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB)

On Linux

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

  • One command with Ollama’s own build of this model.
  • Serves an OpenAI-compatible API that other apps and coding tools can use.
ollama run phi4:14b-q4_K_M
  • LM Studio Point-and-click: search, download and chat in one window.
  • 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-4 (14B)

Recommended for the NVIDIA RTX Spark N1X (6144-core GPU) (32 GB): Q4_K_M. 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 phi4:14b-q4_K_M

Quantized files · GGUF

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

Download the Q4_K_M (Q4_K_S) file (opens in a new tab)

huggingface.co/microsoft/phi-4-gguf (opens in a new tab)

ollama run hf.co/microsoft/phi-4-gguf:Q4_K_S

Original weights · Hugging Face

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

huggingface.co/microsoft/phi-4 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/microsoft/PhiCookBook (opens in a new tab)

Microsoft’s official Phi cookbook: setup, inference and fine-tuning guides.

git clone https://github.com/microsoft/PhiCookBook

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q4_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 Runs well
How well it runs on the NVIDIA RTX Spark N1X (6144-core GPU) (32 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.27.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.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.11.9 / 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 score79.2 / 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 NVIDIA RTX Spark N1X (6144-core GPU) (32 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 9.4 GB 16.0 GB 41.1 tok/s Runs great 44Fair quality (C) · 44 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 10.8 GB 16.0 GB 32.4 tok/s Runs great 53Fair quality (C) · 53 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q3_K_L) (opens in a new tab)
Q4_K_M 12.5 GB 16.0 GB 25.1 tok/s Runs well 60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q4_K_S) (opens in a new tab)
Q5_K_M 14.0 GB 16.0 GB 20.7 tok/s Runs welltight fit 62Good quality (B) · 62 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q5_K_S) (opens in a new tab)
Q6_K 15.6 GB 16.0 GB 17.4 tok/s Runs welltight fit 63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 19.1 GB 16.0 GB 10.8 tok/s Slowfar over GPU memory limit 64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 33.0 GB 16.0 GB — Won't run 64Good quality (B) · 64 of 100: how capable the model is at F16, whatever it runs on. Match score 8/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

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?