Holo4 27B needs about 19.5 GB of memory at Q4_K_M (a 16.9 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.6 GB.
Holo4‑27B: 27B vision‑language model for computer‑use tasks
Holo4‑27B is a 27B dense VLM built on Qwen3.8‑27B. It supports vision, code, and tool calls and can interact with screenshots and tool results. The model is optimized for web, desktop, and mobile environments.
Good at
- Vision‑enabled computer tasks
- Tool‑aware UI automation
- Code generation and debugging
Limits
- No Mixture of Experts
- License cc‑by‑nc‑4.0 limits commercial use
- Requires 8‑k context for full memory usage
Best for
- Automated UI testing
- Desktop workflow automation
- Computer‑vision assisted coding
Who it’s for. Developers and researchers needing a vision‑enabled LLM for interactive desktop or web tasks. The model is suitable for building agents that can read screenshots, execute clicks, and run code.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 16.9 GB | 19.5 GB | Too big | Get file → |
The Q4_K_M quant is 16.88 GB and needs about 19.5 GB of VRAM at 8‑k context. For 8 GB VRAM use a lower‑rank quant if available; otherwise the model cannot run. For 16 GB VRAM the Q4_K_M is suitable.
What GPU do you need for Holo4 27B?
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.9 GB file, about 19.5 GB in use).
Which Holo4 27B quant should you choose?
Q4_K_M is the usual starting point for Holo4 27B: it balances file size and quality well. Here it is a 16.9 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Holo4 27B
How much VRAM does Holo4 27B need?
About 19.5 GB at Q4_K_M with an 8K context window. That is the 16.9 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 27B on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 19.5 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Holo4 27B GGUF?
It depends on the quant: Q4_K_M is 16.9 GB.
What context length does Holo4 27B 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 Holo4 27B GGUF?
The files are on Hugging Face in the Hcompany/Holo4-27B-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 27B use?
Hugging Face lists the license as cc-by-nc-4.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‑27B on 8 GB VRAM?
No, the Q4_K_M quant requires approximately 19.5 GB VRAM at 8‑k context. A lower‑rank quant would be needed for 8 GB VRAM.
Does Holo4‑27B support text‑only tasks?
Yes, it can handle text tasks, but its primary strengths are vision‑enabled computer use.
Is the model licensed for commercial use?
The model is licensed cc‑by‑nc‑4.0, which allows non‑commercial use only.