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. This repository has 24 quants, from 0.0 GB to 22.1 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.
Veloxy Titan 32B – 26.9B parameter hybrid backbone for coding, reasoning, and tools
Veloxy Titan 32B is a 26.9B parameter model built on the qwen35 architecture. It supports a 262144 token context window and is trained for coding, reasoning, and tool use. The model is released under the apache-2.0 license.
Good at
- Coding tasks
- Complex reasoning
- Tool integration
Limits
- Large VRAM requirement
- No vision support
- No active parameter count specified
Best for
- Developers building agentic systems
- Researchers needing deep reasoning
- Tool‑enabled code generation
Who it’s for. Engineers and researchers who need a large, text‑only model with strong coding and reasoning capabilities. The model is suitable for on‑premise deployment in high‑performance workstations or data‑center environments.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 2.7 GB | Fits | Get file → | |
| IQ1_S | 7.1 GB | 9.8 GB | Too big | Get file → | |
| IQ1_M | 7.6 GB | 10.3 GB | Too big | Get file → | |
| IQ2_XXS | 8.4 GB | 11.1 GB | Too big | Get file → | |
| IQ2_XS | 9.1 GB | 11.7 GB | Too big | Get file → | |
| IQ2_S | 9.4 GB | 12.0 GB | Too big | Get file → | |
| IQ2_M | 10.0 GB | 12.7 GB | Too big | Get file → | |
| Q2_K_S | 10.2 GB | 12.9 GB | Too big | Get file → | |
| Q2_K | 10.7 GB | 13.4 GB | Too big | Get file → | |
| IQ3_XXS | 11.2 GB | 13.8 GB | Too big | Get file → | |
| IQ3_XS | 12.0 GB | 14.6 GB | Too big | Get file → | |
| Q3_K_S | 12.1 GB | 14.7 GB | Too big | Get file → | |
| IQ3_S | 12.4 GB | 15.1 GB | Too big | Get file → | |
| IQ3_M | 12.6 GB | 15.2 GB | Too big | Get file → | |
| Q3_K_M | 13.3 GB | 15.9 GB | Too big | Get file → | |
| Q3_K_L | 14.3 GB | 17.0 GB | Too big | Get file → | |
| IQ4_XS | 15.1 GB | 17.7 GB | Too big | Get file → | |
| Q4_0 | 15.5 GB | 18.2 GB | Too big | Get file → | |
| Q4_K_S | 15.6 GB | 18.2 GB | Too big | Get file → | |
| Q4_K_M | 16.5 GB | 19.2 GB | Too big | Get file → | |
| Q4_1 | 17.1 GB | 19.7 GB | Too big | Get file → | |
| Q5_K_S | 18.7 GB | 21.3 GB | Too big | Get file → | |
| Q5_K_M | 19.2 GB | 21.9 GB | Too big | Get file → | |
| Q6_K | 22.1 GB | 24.7 GB | Too big | Get file → |
For 8 GB VRAM, use IQ1_S (file size 7.15 GB, estimated memory 9.8 GB). For 12 GB VRAM, IQ2_S (file size 9.36 GB, estimated memory 12 GB). For 24 GB VRAM, Q6_K (file size 22.08 GB, estimated memory 24.7 GB). Estimates are approximate.
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: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 12 GB VRAM: the best quant that fits is IQ2_S (9.4 GB file, about 12.0 GB in use).
- 16 GB VRAM: the best quant that fits is Q3_K_M (13.3 GB file, about 15.9 GB in use).
- 24 GB VRAM: the best quant that fits is Q5_K_M (19.2 GB file, about 21.9 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K (22.1 GB file, about 24.7 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.
If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
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?
Yes, with the smaller files: the 0.0 GB file needs about 2.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Veloxy Titan 32B GGUF?
It depends on the quant: file is 0.0 GB, IQ1_S is 7.1 GB, IQ1_M is 7.6 GB, IQ2_XXS is 8.4 GB, IQ2_XS is 9.1 GB, IQ2_S is 9.4 GB and 18 more.
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.1 GB at 8K and 8.6 GB at 32K.
Where can I download Veloxy Titan 32B GGUF?
The files are on Hugging Face in the mradermacher/Veloxy-Titan-32B-i1-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 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?
The smallest quant that fits is IQ1_S, which requires about 9.8 GB of VRAM at 8 k context. 8 GB VRAM is insufficient.
Does Veloxy Titan 32B support vision?
No, the model has no vision capabilities.