How much VRAM does UI-TARS-7B-DPO need?

Q4_K_M is exactly 4,683,071,424 bytes (4.36 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

How large is UI-TARS-7B-DPO's KV cache?

1.75 GiB at 32K context with an f16 cache, computed per layer from the model's architecture. Quantizing the cache to q8_0 roughly halves it.

ByteDance-Seed · vision language

UI-TARS-7B-DPO

ByteDance-Seed/UI-TARS-7B-DPO

UI-TARS-7B-DPO at Q4_K_M is exactly 4,683,071,424 bytes (4.36 GiB / 4.68 GB) — an effective 4.519 bits per weight, not the nominal 4. Its KV cache at 32K is 1.75 GiB.

From the file· summed from 1 file(s)From the file· KV per layer

Parameters

8.3B

Architecture

qwen2vl

28 layers

Context

32,768

native (config.json)

License

apache-2.0

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
IQ2_M	2.59 GiB	2,780,340,416	2.683	—	bartowski
Q2_K	2.81 GiB	3,015,938,240	2.910	—	bartowski
Q2_K	2.81 GiB	3,015,938,432	2.910	—	mradermacher
IQ3_XS	3.12 GiB	3,346,254,016	3.229	—	bartowski
Q3_K_S	3.25 GiB	3,492,366,528	3.370	—	bartowski
Q3_K_S	3.25 GiB	3,492,366,720	3.370	—	mradermacher
Q2_K_L	3.30 GiB	3,548,162,240	3.424	—	bartowski
IQ3_M	3.33 GiB	3,574,010,048	3.448	—	bartowski
Q3_K_M	3.55 GiB	3,808,389,312	3.675	—	bartowski
Q3_K_M	3.55 GiB	3,808,389,504	3.675	—	mradermacher
Q3_K_L	3.81 GiB	4,088,457,152	3.945	—	lmstudio-community
Q3_K_L	3.81 GiB	4,088,457,408	3.945	—	bartowski
Q3_K_L	3.81 GiB	4,088,457,600	3.945	—	mradermacher
IQ4_XS	3.93 GiB	4,218,470,592	4.070	—	bartowski
IQ4_XS	3.96 GiB	4,250,296,704	4.101	—	mradermacher
IQ4_NL	4.13 GiB	4,437,811,392	4.282	—	bartowski
Q4_0	4.14 GiB	4,444,119,232	4.288	—	bartowski
Q4_K_S	4.15 GiB	4,457,767,104	4.301	—	bartowski
Q4_K_S	4.15 GiB	4,457,767,296	4.301	—	mradermacher
Q4_K_M	4.36 GiB	4,683,071,424	4.519	—	lmstudio-community
Q4_K_M	4.36 GiB	4,683,071,680	4.519	—	bartowski
Q4_K_M	4.36 GiB	4,683,071,872	4.519	—	mradermacher
Q4_1	4.54 GiB	4,873,281,728	4.702	—	bartowski
Q4_K_L	4.74 GiB	5,087,561,920	4.909	—	bartowski
Q5_K_S	4.95 GiB	5,315,174,592	5.128	—	bartowski
Q5_K_S	4.95 GiB	5,315,174,784	5.128	—	mradermacher
Q5_K_M	5.07 GiB	5,444,829,376	5.253	—	bartowski
Q5_K_M	5.07 GiB	5,444,829,568	5.253	—	mradermacher
Q5_K_L	5.38 GiB	5,781,194,944	5.578	—	bartowski
Q6_K	5.82 GiB	6,254,196,672	6.034	—	lmstudio-community
Q6_K	5.82 GiB	6,254,196,928	6.034	—	bartowski
Q6_K	5.82 GiB	6,254,197,120	6.034	—	mradermacher
Q6_K_L	6.07 GiB	6,518,180,032	6.289	—	bartowski
Q8_0	7.54 GiB	8,098,523,072	7.814	—	lmstudio-community
Q8_0	7.54 GiB	8,098,523,328	7.814	—	bartowski
Q8_0	7.54 GiB	8,098,523,520	7.814	—	mradermacher
F16	14.19 GiB	15,237,851,328	14.702	—	bartowski
F16	14.19 GiB	15,237,851,520	14.702	—	mradermacher
F32	28.38 GiB	30,468,417,472	29.398	—	bartowski

KV cache by context

computed per layer

Context	KV cache (f16)●	Flat formula	Overstated by	Full / windowed / recurrent
4,096	0.22 GiB	0.22 GiB	—	28 / 0 / 0
8,192	0.44 GiB	0.44 GiB	—	28 / 0 / 0
16,384	0.88 GiB	0.88 GiB	—	28 / 0 / 0
32,768	1.75 GiB	1.75 GiB	—	28 / 0 / 0
65,536	3.50 GiB	3.50 GiB	—	28 / 0 / 0
131,072	7.00 GiB	7.00 GiB	—	28 / 0 / 0

Compare with

same modality, comparable size

vs Qwen3.5-9B vs gemma-4-12B-it vs Qwen3.5-4B vs Qwythos-9B-Claude-Mythos-5-1M vs Qwen3.5-0.8B vs gemma-4-E2B-it All alternatives →Will it fit on my card? →

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 4.34 GiB. The real file is 4.36 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json

Layers

Attention heads

KV heads

Head dim

128

Hidden size

3584

Vocab

152,064

Sliding window

32768

SWA period

—

MLA

Experts

—

Experts per token

—

use_sliding_window

false

This model declares a sliding window but sets use_sliding_window: false, so the window is not applied. Honouring the field without the flag understates KV for the whole family.

Questions people ask

How much VRAM does UI-TARS-7B-DPO need?: Q4_K_M is exactly 4,683,071,424 bytes (4.36 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is UI-TARS-7B-DPO's KV cache?: 1.75 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of UI-TARS-7B-DPO should I use?: Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.