VirbiusGuard needs about 1.9 GB of memory at Q4_K_M (a 0.5 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 12 quants, from 0.3 GB (Q2_K) to 1.5 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 3.8 GB.
0.6B Qwen3Guard-based LLM for safe input filtering
VirbiusGuard is a 0.6B Qwen3ForCausalLM model fine‑tuned for input safety. It classifies inputs as safe or one of ten unsafe categories and returns a JSON result. The model is available in multiple GGUF quantizations.
Good at
- Detects jailbreak and agent tool misuse
- Classifies 10 unsafe categories
- Returns strict JSON output
Limits
- No vision support
- Requires 8k context for full accuracy
- Apache‑2.0 license
Best for
- Deploying safety guardrails in chat applications
- Filtering user input for compliance
- Running on low‑VRAM devices with quantized models
Who it’s for. Developers building chatbots or agents who need reliable input filtering. The model is suitable for environments where strict JSON output and low resource usage are required.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 0.3 GB | 1.8 GB | Fits | Get file → | |
| Q3_K_S | 0.4 GB | 1.8 GB | Fits | Get file → | |
| Q3_K_M | 0.4 GB | 1.9 GB | Fits | Get file → | |
| Q3_K_L | 0.4 GB | 1.9 GB | Fits | Get file → | |
| IQ4_XS | 0.5 GB | 1.9 GB | Fits | Get file → | |
| Q4_K_S | 0.5 GB | 1.9 GB | Fits | Get file → | |
| Q4_K_M | 0.5 GB | 1.9 GB | Fits | Get file → | |
| Q5_K_S | 0.5 GB | 2.0 GB | Fits | Get file → | |
| Q5_K_M | 0.6 GB | 2.0 GB | Fits | Get file → | |
| Q6_K | 0.6 GB | 2.1 GB | Fits | Get file → | |
| Q8_0 | 0.8 GB | 2.2 GB | Fits | Get file → | |
| F16 | 1.5 GB | 2.9 GB | Fits | Get file → |
For 8 GB VRAM, use Q4_K_M (0.48 GB file, ~1.9 GB memory). If VRAM is limited to 4 GB, Q2_K (0.35 GB file, ~1.8 GB memory) is recommended. For higher fidelity, Q5_K_M (0.55 GB file, ~2 GB memory) can be used on 8 GB VRAM systems.
What GPU do you need for VirbiusGuard?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is F16 (1.5 GB file, about 2.9 GB in use).
Which VirbiusGuard quant should you choose?
Q4_K_M is the usual starting point for VirbiusGuard: it balances file size and quality well. Here it is a 0.5 GB file.
The Q8_0 file is 0.8 GB, about 1.7 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is Q2_K at 0.3 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about VirbiusGuard
How much VRAM does VirbiusGuard need?
About 1.9 GB at Q4_K_M with an 8K context window. That is the 0.5 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run VirbiusGuard on an 8 GB GPU?
Yes, with F16: the 1.5 GB file needs about 2.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of VirbiusGuard GGUF?
It depends on the quant: Q2_K is 0.3 GB, Q3_K_S is 0.4 GB, Q3_K_M is 0.4 GB, Q3_K_L is 0.4 GB, IQ4_XS is 0.5 GB, Q4_K_S is 0.5 GB and 6 more.
What context length does VirbiusGuard support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.9 GB at 8K and 3.8 GB at 32K.
Where can I download VirbiusGuard GGUF?
The files are on Hugging Face in the mradermacher/VirbiusGuard-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does VirbiusGuard use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run VirbiusGuard on 8 GB VRAM?
Yes, Q4_K_M or Q5_K_M quantizations fit within 8 GB VRAM with the estimated memory usage.
Does the model support vision inputs?
No, VirbiusGuard is a text‑only model and does not process images.
What license applies to this model?
The model is released under the Apache‑2.0 license.