UI TARS 7B DPO needs about 5.7 GB of memory at Q4_K_M (a 4.7 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 4 quants, from 4.1 GB (Q3_K_L) to 8.1 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 1.9 GB.
UI TARS 7B DPO – a vision‑language model for native GUI agent tasks
UI TARS 7B DPO is a 7.62 billion‑parameter model based on Qwen2VL. It is finetuned for perception, reasoning, grounding, and action in graphical user interfaces. The model supports vision and runs in GGUF format via llama.cpp.
Good at
- Vision‑based GUI interaction
- End‑to‑end task automation
- Human‑like perception and reasoning
Limits
- No vision support beyond GUI tasks
- Requires 8 k context for full performance
- License is apache‑2.0
Best for
- Automating desktop applications
- Building GUI agents
- Testing UI workflows
Who it’s for. Developers and researchers building autonomous agents that interact with software interfaces. The model is suitable for projects needing integrated perception, reasoning, and action without external workflow engines.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_L | 4.1 GB | 5.1 GB | Fits | Get file → | |
| Q4_K_M | 4.7 GB | 5.7 GB | Fits | Get file → | |
| Q6_K | 6.3 GB | 7.2 GB | Tight | Get file → | |
| Q8_0 | 8.1 GB | 9.1 GB | Too big | Get file → |
For 8 GB VRAM, use Q4_K_M (file size 4.68 GB, estimated memory 5.7 GB). For 12 GB VRAM, Q6_K (6.25 GB, 7.2 GB). For 16 GB VRAM, Q8_0 (8.1 GB, 9.1 GB). Estimates are approximate.
What GPU do you need for UI TARS 7B DPO?
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: the best quant that fits is Q4_K_M (4.7 GB file, about 5.7 GB in use).
- 8 GB VRAM: the best quant that fits is Q6_K (6.3 GB file, about 7.2 GB in use).
- 12 GB VRAM: the best quant that fits is Q8_0 (8.1 GB file, about 9.1 GB in use).
Which UI TARS 7B DPO quant should you choose?
Q4_K_M is the usual starting point for UI TARS 7B DPO: it balances file size and quality well. Here it is a 4.7 GB file.
The Q8_0 file is 8.1 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 Q3_K_L at 4.1 GB, with the quality trade-offs that come with fewer bits. A reasonable choice when a 4-bit file will not fit, mostly on larger models. Quality loss is noticeable but often acceptable.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about UI TARS 7B DPO
How much VRAM does UI TARS 7B DPO need?
About 5.7 GB at Q4_K_M with an 8K context window. That is the 4.7 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 UI TARS 7B DPO on an 8 GB GPU?
Yes, with Q6_K: the 6.3 GB file needs about 7.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of UI TARS 7B DPO GGUF?
It depends on the quant: Q3_K_L is 4.1 GB, Q4_K_M is 4.7 GB, Q6_K is 6.3 GB, Q8_0 is 8.1 GB.
What context length does UI TARS 7B DPO support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.5 GB at 8K and 1.9 GB at 32K.
Where can I download UI TARS 7B DPO GGUF?
The files are on Hugging Face in the lmstudio-community/UI-TARS-7B-DPO-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 UI TARS 7B DPO 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 UI TARS 7B DPO on 8 GB VRAM?
Yes, the Q4_K_M quantization uses about 5.7 GB of VRAM at 8 k context, fitting within an 8 GB budget.
Does the model support text‑only tasks?
The model is designed for vision‑language tasks and does not provide specialized text‑only optimizations.
What license applies to this model?
The model is released under the apache‑2.0 license.