TA

UI TARS 72B DPO

TarsGGUF by lmstudio-communityUpdated 2025-01-23
Download on Hugging Face
Parameters72.7B
Context32K
Layers80
Architectureqwen2vl
Smallest quant39.5 GB
Quick answer

UI TARS 72B DPO needs about 50.6 GB of memory at Q4_K_M (a 47.4 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 4 quants, from 39.5 GB (Q3_K_L) to 77.3 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 10.7 GB.

UI TARS 72B DPO is a 72.7B-parameter Tars model in GGUF format, quantized by lmstudio-community. Its trained context length is 32K tokens. The repository has 4 quant files, from 39.5 GB (Q3_K_L) to 77.3 GB (Q8_0).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q3_K_L39.5 GB 42.7 GB
Too big Get file →
Q4_K_M47.4 GB 50.6 GB
Too big Get file →
Q6_K64.3 GB (2 parts) 67.5 GB
Too big Get file →
Q8_077.3 GB (2 parts) 80.4 GB
Too big Get file →

What GPU do you need for UI TARS 72B 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: 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: no quant fits at an 8K context.
  • 32 GB VRAM: no quant fits at an 8K context.
  • 48 GB VRAM: the best quant that fits is Q3_K_L (39.5 GB file, about 42.7 GB in use).

Which UI TARS 72B DPO quant should you choose?

Q4_K_M is the usual starting point for UI TARS 72B DPO: it balances file size and quality well. Here it is a 47.4 GB file.

The Q8_0 file is 77.3 GB, about 1.6 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 39.5 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

Architectureqwen2vl
Parameters72.7B
Layers80
Trained context32,768 tokens
KV cache (fp16)320 KB per token

Source

Quantized bylmstudio-community
FamilyTars
Licenseapache-2.0
Downloads (HF)182
Last updated2025-01-23

Frequently asked questions about UI TARS 72B DPO

How much VRAM does UI TARS 72B DPO need?

About 50.6 GB at Q4_K_M with an 8K context window. That is the 47.4 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 72B DPO on an 8 GB GPU?

Not at an 8K context. The smallest file needs about 42.7 GB, so you would need a larger GPU or CPU offloading.

What is the file size of UI TARS 72B DPO GGUF?

It depends on the quant: Q3_K_L is 39.5 GB, Q4_K_M is 47.4 GB, Q6_K is 64.3 GB, Q8_0 is 77.3 GB.

What context length does UI TARS 72B 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 2.7 GB at 8K and 10.7 GB at 32K.

Where can I download UI TARS 72B DPO GGUF?

The files are on Hugging Face in the lmstudio-community/UI-TARS-72B-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 72B 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.

Other GGUFs of UI-TARS-72B-DPO

Similar models

Browse all →

More from lmstudio-community

All by lmstudio-community →

More Tars models

All Tars →

Other large models

All large models →