Holo4 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. Longer context needs more: at 32K tokens the KV cache alone adds about 2.7 GB.
Holo4‑35B‑A3B: 35B vision‑language model with 262k‑token context
Holo4‑35B‑A3B is a 35B‑parameter vision‑language model built on Qwen3.6‑MoE. It supports large context up to 262,144 tokens and can process screenshots and tool results via the hai‑agents harness. The model is released under Apache‑2.0.
Good at
- Vision‑language reasoning
- Tool‑aware interaction
- Long‑context handling
Limits
- Requires 8‑bit Q4_K_M quant for 21.3 GB file
- Approx. 22.5 GB VRAM at 8k context
- No native vision support beyond screenshots
Best for
- Automated desktop workflows
- Code generation with tool calls
- Complex visual task planning
Who it’s for. Developers building agentic systems that need to interpret screenshots and execute UI actions. Researchers testing large‑context vision‑language models. Teams requiring a model that can handle 262k‑token context for detailed reasoning.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 21.3 GB | 22.5 GB | Too big | Get file → |
For 8 GB VRAM use Q4_K_M quant, file size 21.3 GB, memory estimate 22.5 GB at 8k context. For larger VRAM budgets, consider higher‑precision quantizations if available. Memory estimates are approximate.
What GPU do you need for Holo4 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: 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 (21.3 GB file, about 22.5 GB in use).
Which Holo4 35B A3B quant should you choose?
Q4_K_M is the usual starting point for Holo4 35B A3B: it balances file size and quality well. Here it is a 21.3 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Holo4 35B A3B
How much VRAM does Holo4 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 Holo4 35B A3B on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 22.5 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Holo4 35B A3B GGUF?
It depends on the quant: Q4_K_M is 21.3 GB.
What context length does Holo4 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 Holo4 35B A3B GGUF?
The files are on Hugging Face in the Hcompany/Holo4-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 Holo4 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 Holo4‑35B‑A3B on 8 GB VRAM?
No. The Q4_K_M quant requires about 22.5 GB VRAM at 8k context, exceeding 8 GB.
Does the model support image input?
It processes screenshots sent via the harness, not raw image files.
What license applies to this model?
The model is released under the Apache‑2.0 license.