Veloxy Titan 32B Vision 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 11 quants, from 10.7 GB (Q2_K) to 28.6 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.
Veloxy Titan 32B Vision – multimodal vision and deep reasoning model
Veloxy Titan 32B Vision is a 26.9B parameter multimodal model built on the qwen35 architecture. It combines a 27‑layer Vision Transformer with a 32B reasoning backbone. The model is trained on 262144 context tokens and licensed under apache-2.0.
Good at
- Vision‑to‑code generation
- Technical schematic analysis
- Pixel‑level UI parsing
Limits
- No vision support in some quant variants
- Large VRAM requirement for high context
- Requires 8k context for full capability
Best for
- Generating UI components from screenshots
- Extracting data from technical diagrams
- Converting Figma exports to code
Who it’s for. Developers needing automated UI/UX reverse engineering or technical diagram interpretation. Researchers working on multimodal reasoning tasks with a large context window.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 10.7 GB | 13.4 GB | Too big | Get file → | |
| Q3_K_S | 12.1 GB | 14.7 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.2 GB | 17.8 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 → | |
| 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 → | |
| Q8_0 | 28.6 GB | 31.2 GB | Too big | Get file → |
For 8 GB VRAM, use Q2_K (file size 10.71 GB, estimated 13.4 GB memory). For 12 GB VRAM, Q3_K_S (12.07 GB, 14.7 GB). For 16 GB VRAM, Q4_K_M (16.55 GB, 19.2 GB). Memory estimates are approximate.
What GPU do you need for Veloxy Titan 32B Vision?
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: 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 Q8_0 (28.6 GB file, about 31.2 GB in use).
Which Veloxy Titan 32B Vision quant should you choose?
Q4_K_M is the usual starting point for Veloxy Titan 32B Vision: it balances file size and quality well. Here it is a 16.5 GB file.
The Q8_0 file is 28.6 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 10.7 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 Veloxy Titan 32B Vision
How much VRAM does Veloxy Titan 32B Vision 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 Vision on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 13.4 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Veloxy Titan 32B Vision GGUF?
It depends on the quant: Q2_K is 10.7 GB, Q3_K_S is 12.1 GB, Q3_K_M is 13.3 GB, Q3_K_L is 14.3 GB, IQ4_XS is 15.2 GB, Q4_K_S is 15.6 GB and 5 more.
What context length does Veloxy Titan 32B Vision 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 Vision GGUF?
The files are on Hugging Face in the mradermacher/Veloxy-Titan-32B-Vision-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 Vision 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 Vision on 8 GB VRAM?
Use the Q2_K quant; it requires about 13.4 GB of VRAM at 8k context, which is slightly above 8 GB but may fit with lower context.
Does the model support vision tasks?
Yes, it is a multimodal model with vision, coding, and reasoning abilities.
What license does the model use?
The model is released under the apache-2.0 license.