How much VRAM does Qwopus3.6-27B-v2-MTP-GGUF need?

Q4_K_M is exactly 9,374,507,456 bytes (8.73 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

Jackrong · text

Qwopus3.6-27B-v2-MTP-GGUF

Jackrong/Qwopus3.6-27B-v2-MTP-GGUF

Qwopus3.6-27B-v2-MTP-GGUF at Q4_K_M is exactly 9,374,507,456 bytes (8.73 GiB / 9.37 GB) — an effective 2.745 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)

Parameters

27.3B

Architecture

qwen35

Context

—

native (config.json)

License

—

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
Q4_K_M	8.73 GiB	9,374,507,456	2.745	866	infosave
Q5_K_M	10.08 GiB	10,825,474,496	3.170	866	infosave
Q8_0	14.91 GiB	16,011,972,800	4.689	866	infosave
F16	28.05 GiB	30,121,054,400	8.820	866	infosave

Compare with

same modality, comparable size

vs Qwen3-Coder-30B-A3B-Instruct vs Qwen3.6-27B vs Qwen3.8-27B vs gemma-4-12B-it-qat-q4_0-unquantized vs gemma-4-E4B-it vs Qwen3-30B-A3B-Thinking-2507 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 14.31 GiB. The real file is 8.73 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

Architecture unavailable — this repository is gated and no ungated mirror was found. Exact file sizes above are still authoritative; only the KV math needs the config.

Questions people ask

How much VRAM does Qwopus3.6-27B-v2-MTP-GGUF need?: Q4_K_M is exactly 9,374,507,456 bytes (8.73 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of Qwopus3.6-27B-v2-MTP-GGUF 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.