Veloxy Titan 32B needs about 19.2 GB of memory at Q4_K_M (a 16.5 GB file) with an 8K context window, so it fits on a 24 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 8.7 GB.
Veloxy Titan 32B – a 32B hybrid backbone for deep reasoning and agentic tasks
Veloxy Titan 32B is a 32B-class hybrid backbone model built on Qwen architecture. It supports coding, reasoning, and tool use with a 262144 token context window. The model is released under the apache-2.0 license.
Good at
- Coding
- Reasoning
- Tool use
Limits
- Context limited to 262144 tokens
- Requires ~19.2 GB VRAM at 8k context
- No vision support
Best for
- Complex coding tasks
- Long-horizon agentic planning
- Tool‑driven workflows
Who it’s for. Developers and researchers needing a dense model for advanced reasoning and tool integration. The model is suitable for environments with sufficient GPU memory and no requirement for vision input.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 16.5 GB | 19.2 GB | Too big | Get file → |
The only available quant is Q4_K_M with a file size of 16.55 GB. It requires approximately 19.2 GB of VRAM at an 8k context length. This is the recommended quant for systems with 20 GB or more VRAM.
What GPU do you need for Veloxy Titan 32B?
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: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: the best quant that fits is Q4_K_M (16.5 GB file, about 19.2 GB in use).
Which Veloxy Titan 32B quant should you choose?
Q4_K_M is the usual starting point for Veloxy Titan 32B: it balances file size and quality well. Here it is a 16.5 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Veloxy Titan 32B
How much VRAM does Veloxy Titan 32B need?
About 19.2 GB at Q4_K_M with an 8K context window. That is the 16.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 Veloxy Titan 32B on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 19.2 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Veloxy Titan 32B GGUF?
It depends on the quant: Q4_K_M is 16.5 GB.
What context length does Veloxy Titan 32B support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 2.2 GB at 8K and 8.7 GB at 32K.
Where can I download Veloxy Titan 32B GGUF?
The files are on Hugging Face in the zveloxy/Veloxy-Titan-32B repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Veloxy Titan 32B 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 Veloxy Titan 32B on 8 GB VRAM?
No, the Q4_K_M quant requires about 19.2 GB of VRAM at 8k context.
Does Veloxy Titan 32B support vision?
The model does not include vision capabilities.
What is the maximum context length for Veloxy Titan 32B?
The maximum context length is 262144 tokens.