Holo 3.1 35B A3B needs about 22.5 GB of memory at Q4_K_M (a 21.3 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 3 quants, from 0.2 GB to 69.4 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 2.7 GB.
Holo 3.1 35B A3B – a large vision‑language model for local computer‑use agents
Holo 3.1 35B A3B is a 35‑billion‑parameter vision‑language model built on Qwen 3.5. It supports multimodal input and is optimized for local deployment via GGUF quantizations. The model is licensed under Apache‑2.0 and is suitable for computer‑use agent tasks.
Good at
- Vision‑language reasoning
- Computer‑use agent automation
- Mobile and desktop UI grounding
Limits
- Large VRAM requirement for full precision
- No text‑only mode without vision
- Requires Apache‑2.0 compliant usage
Best for
- Local desktop automation scripts
- Mobile UI testing agents
- Enterprise workflow assistants
Who it’s for. Developers and researchers building local agents that need vision and language understanding. The model is ideal for teams that can host it on GPUs with sufficient VRAM and want a fully open‑source solution.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.2 GB | 1.4 GB | Fits | Get file → | |
| Q4_K_M | 21.3 GB | 22.5 GB | Too big | Get file → | |
| BF16 | 69.4 GB | 70.5 GB | Too big | Get file → |
For 8 GB VRAM, use the Q4_K_M quantization (21.3 GB file, ~22.5 GB VRAM at 8 k context). For 16 GB VRAM, BF16 (69.38 GB file, ~70.5 GB VRAM) is available but may exceed memory. The unknown quant is only 0.19 GB but requires 1.4 GB VRAM at 8 k context.
What GPU do you need for Holo 3.1 35B A3B?
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.2 GB file, about 1.4 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.2 GB file, about 1.4 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.2 GB file, about 1.4 GB in use).
- 12 GB VRAM: the best quant that fits is the main file (0.2 GB file, about 1.4 GB in use).
- 16 GB VRAM: the best quant that fits is the main file (0.2 GB file, about 1.4 GB in use).
- 24 GB VRAM: the best quant that fits is Q4_K_M (21.3 GB file, about 22.5 GB in use).
- 32 GB VRAM: the best quant that fits is Q4_K_M (21.3 GB file, about 22.5 GB in use).
- 48 GB VRAM: the best quant that fits is Q4_K_M (21.3 GB file, about 22.5 GB in use).
Which Holo 3.1 35B A3B quant should you choose?
Q4_K_M is the usual starting point for Holo 3.1 35B A3B: it balances file size and quality well. Here it is a 21.3 GB file.
If memory is tight, the smallest file is the first one in the table at 0.2 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 Holo 3.1 35B A3B
How much VRAM does Holo 3.1 35B A3B need?
About 22.5 GB at Q4_K_M with an 8K context window. That is the 21.3 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 Holo 3.1 35B A3B on an 8 GB GPU?
Yes, with the smaller files: the 0.2 GB file needs about 1.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Holo 3.1 35B A3B GGUF?
It depends on the quant: file is 0.2 GB, Q4_K_M is 21.3 GB, BF16 is 69.4 GB.
What context length does Holo 3.1 35B A3B support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.7 GB at 8K and 2.7 GB at 32K.
Where can I download Holo 3.1 35B A3B GGUF?
The files are on Hugging Face in the Hcompany/Holo-3.1-35B-A3B-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 Holo 3.1 35B A3B 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 Holo 3.1 35B A3B on 8 GB VRAM?
Yes, using the Q4_K_M quantization will fit within 8 GB VRAM with an estimated 22.5 GB usage at 8 k context, which is above 8 GB, so it will not fit. A smaller quant or model size is needed.
What license does the model use?
The model is released under the Apache‑2.0 license.
Does the model support vision?
Yes, it includes vision capabilities as part of its multimodal design.