Can the NVIDIA H200 NVL run Grok-1 (314B)?

Yes, it runs well (tight fit)

Runs well (tight fit). At Q2_K it needs about 135 GB of 141 GB usable, with an estimated speed of 83.2 tok/s.

Best quant: Q2_K
Generation speed: 83.2 tok/s
Prompt processing: 1,005 tok/s
First token (1K prompt): 1.0 s
Largest safe context: 8K

Best app to run it on the NVIDIA H200 NVL

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

Point-and-click: search, download and chat in one window.

Open Grok-1 (314B) in LM Studio

llama.cpp Usually the first to support new model architectures.
Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

Point-and-click: search, download and chat in one window.

Open Grok-1 (314B) in LM Studio

llama.cpp Usually the first to support new model architectures.
Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

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 Grok-1 (314B)

Recommended for the NVIDIA H200 NVL: Q2_K. Every other quantization has its own download link in the table below.

Quantized files · GGUF

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

Download the Q2_K files (opens in a new tab)

huggingface.co/Arki05/Grok-1-GGUF (opens in a new tab)

ollama run hf.co/Arki05/Grok-1-GGUF

Original weights · Hugging Face

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

huggingface.co/xai-org/grok-1 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/xai-org/grok-1 (opens in a new tab)

git clone https://github.com/xai-org/grok-1

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

How it’s rated

Quality 35Basic quality (D) · 35 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q2_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 welltight fit: How well it runs on the NVIDIA H200 NVL: 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.	15.8 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	24.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.	15.0 / 15
Match score	69.8 / 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 H200 NVL

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	135 GB	141 GB	83.2 tok/s	Runs welltight fit	35Basic quality (D) · 35 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q3_K_M`	164 GB	141 GB	—	Won't run	42Fair quality (C) · 42 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q4_K_M`	201 GB	141 GB	—	Won't run	47Fair quality (C) · 47 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q5_K_M`	233 GB	141 GB	—	Won't run	48Fair quality (C) · 48 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q6_K`	267 GB	141 GB	—	Won't run	49Fair quality (C) · 49 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q8_0`	343 GB	141 GB	—	Won't run	50Fair quality (C) · 50 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`F16`	638 GB	141 GB	—	Won't run	50Fair quality (C) · 50 of 100: how capable the model is at F16, whatever it runs on. Match score 6/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

42Fair quality (C) · 42 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. Apple M3 Ultra (256 GB) Q3_K_M · 12.5 tok/s · Runs well (tight fit)
35Basic quality (D) · 35 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. Apple M2 Ultra (192 GB) Q2_K · 15.4 tok/s · Runs well (tight fit)
42Fair quality (C) · 42 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. Apple M3 Ultra (512 GB) Q3_K_M · 12.5 tok/s · Runs well
48Fair quality (C) · 48 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. AMD Instinct MI350X Q5_K_M · 63.2 tok/s · Runs great
47Fair quality (C) · 47 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. AMD Instinct MI325X Q4_K_M · 59.1 tok/s · Runs great
47Fair quality (C) · 47 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GB300 Grace Blackwell Ultra Desktop Superchip Q4_K_M · 75.6 tok/s · Runs great

Quick answers

How much memory does Grok-1 (314B) need on the NVIDIA H200 NVL 141GB?

At Q2_K it needs about 135 GB. The NVIDIA H200 NVL 141GB has 141 GB usable.

How fast is Grok-1 (314B) on the NVIDIA H200 NVL 141GB?

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

Which quantization of Grok-1 (314B) should I use on the NVIDIA H200 NVL 141GB?

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