on

Can the NVIDIA RTX PRO 6000 Blackwell run Llama Guard 4 12B?

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

Yes, it runs great

Runs great. At Q6_K it needs about 15.6 GB of 96.0 GB usable and makes one decision in about 119 ms.

Best quant
Q6_K
Time per decision
119 ms
Decisions per second
8.4/s
Input assumed
512 tokens
Returns
Fixed labels

Best app to run it on the NVIDIA RTX PRO 6000 Blackwell

On Windows

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • On Windows it runs through WSL2.
vllm serve meta-llama/Llama-Guard-4-12B
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • Sentence Transformers A few lines of Python with Transformers or Sentence Transformers; easiest for scripts and notebooks.

On Linux

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
vllm serve meta-llama/Llama-Guard-4-12B
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
  • Docker Model Runner Handy if you already work in Docker.

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 Llama Guard 4 12B

Original weights · Hugging Face

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

huggingface.co/meta-llama/Llama-Guard-4-12B (opens in a new tab)

Free Hugging Face account needed: request access on the model page, and Meta approves it (usually within minutes to a few hours).

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

How it’s rated

Quality 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q6_K, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: S 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great
How well it runs on the NVIDIA RTX PRO 6000 Blackwell: 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.

PrecisionEditorial precision tier from the model’s published benchmarks, scaled by the quantization or precision used.29.4 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.25.0 / 25
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.13.7 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.12.0 / 15
Match score80.1 / 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 PRO 6000 Blackwell

Quant Memory needed Available Time per decision Runs Quality Download
Q4_K_M 13.1 GB 96.0 GB 105 ms Runs great 62Good quality (B) · 62 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. All files (opens in a new tab)
Q5_K_M 14.3 GB 96.0 GB 112 ms Runs great 64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 15.6 GB 96.0 GB 119 ms Runs great 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 18.5 GB 96.0 GB 137 ms Runs well 66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 29.8 GB 96.0 GB 212 ms Runs well 66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

Times are for one request with a 512-token input and about 6 tokens written. Batching servers process many requests at once.

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.