ThinkingCap Qwen3.8 27B VRAM requirements
ThinkingCap Qwen3.8 27B needs about 18.3 GB of VRAM at Q4_K_M with 8K context, so it fits a 24 GB card such as the RTX 3090 or the RTX 4090. ThinkingCap Qwen3.8 27B has 27.8B parameters. With the same 8K context and one request it needs 29.5 GB at FP8 and 58.0 GB at FP16/BF16. The published weights take 51.7 GB (BF16). The smallest setup here that holds it at Q4_K_M with an 8K context is the RTX 3090 (24 GB), which runs it with up to 83K tokens of context.
18.3 GB at Q4_K_M, 8K context, one request
- FP8
- 29.5 GB
- FP16 / BF16
- 58.0 GB
- Published weights
- 51.7 GB
- Smallest setup, Q4_K_M
- RTX 3090 (24 GB)
Worked example: ThinkingCap Qwen3.8 27B with 32K tokens
Inputs: ThinkingCap Qwen3.8 27B · Q4_K_M weights · 32,768 tokens of context · one request · FP16 KV cache
- Weights (27.8B at Q4_K_M)
- 15.7 GB
- KV cache (64 KB per token)
- 2.00 GB
- Buffers and runtime (0.5 GB + 10%)
- 2.27 GB
- Total
- 19.9 GB
The smallest setup here that holds it is the RTX 3090 (24 GB), with about 4.08 GB to spare. Change the inputs in the calculator
What makes ThinkingCap Qwen3.8 27B's memory use different
48 of its 64 layers keep a fixed-size linear-attention state, so the cache grows by 64 KB per token where caching every layer would take 256 KB.
Per token of context it adds 64 KB of FP16 cache; Granite 4.2 30B (29.3B), the nearest-sized model here with plain full attention, adds 256 KB, so ThinkingCap Qwen3.8 27B needs 25% as much.
Its architecture and size match Qwen3.6 27B, Qwen3.8 27B, so every memory figure on this page is the same for those models.
How much VRAM does ThinkingCap Qwen3.8 27B need?
ThinkingCap Qwen3.8 27B needs 18.3 GB at Q4_K_M, 31.3 GB at Q8_0 and 58.0 GB at FP16 with 8,192 tokens of context and one request. Each total below is the weights plus the FP16 KV cache and the runtime overhead (0.5 GB plus 10%), and each row opens the calculator with that setting. What the GGUF names mean.
| Precision | Weights | Total | Smallest setup |
|---|---|---|---|
| As published (BF16) | 51.7 GB | 58.0 GB | 2× RTX 5090 (64 GB) |
| FP16 / BF16 | 51.7 GB | 58.0 GB | 2× RTX 5090 (64 GB) |
| FP8 / INT8 | 25.9 GB | 29.5 GB | RTX 5090 (32 GB) |
| INT4 (AWQ / GPTQ) | 13.7 GB | 16.2 GB | RTX 3090 (24 GB) |
| GGUF Q8_0 | 27.5 GB | 31.3 GB | RTX 5090 (32 GB) |
| GGUF Q6_K | 21.2 GB | 24.4 GB | RTX 5090 (32 GB) |
| GGUF Q5_K_M | 18.3 GB | 21.2 GB | RTX 3090 (24 GB) |
| GGUF Q4_K_M | 15.7 GB | 18.3 GB | RTX 3090 (24 GB) |
| GGUF IQ4_XS | 14.1 GB | 16.5 GB | RTX 3090 (24 GB) |
| GGUF Q3_K_M | 12.6 GB | 15.0 GB | RTX 4060 Ti 16GB |
| GGUF IQ3_XXS | 10.7 GB | 12.8 GB | RTX 4060 Ti 16GB |
| GGUF Q2_K | 10.8 GB | 13.0 GB | RTX 4060 Ti 16GB |
Fine-tuning ThinkingCap Qwen3.8 27B? ThinkingCap Qwen3.8 27B VRAM for LoRA, QLoRA and full training.
ThinkingCap Qwen3.8 27B GGUF files on Hugging Face
The 5 GGUF files llama.cpp picks for ThinkingCap Qwen3.8 27B with -hf <repo>:<QUANT>, with the bytes the Hugging Face file list reported on 2026-09-29. Each total is that file plus the FP16 KV cache and 0.5 GB + 10%, one request. "vs estimate" compares the file with the bits-per-weight size the table above uses.
| Quant | File | Size | vs estimate | 8K | 32K | 128K |
|---|---|---|---|---|---|---|
| IQ4_XS | bottlecapai/ | 14.4 GB15,475,951,712 bytes | +2% | 16.9 GB | 18.6 GB | 25.2 GB |
| Q4_K_M | bottlecapai/ | 16.2 GB17,442,400,352 bytes | +4% | 18.9 GB | 20.6 GB | 27.2 GB |
| Q6_K | bottlecapai/ | 22.2 GB23,860,566,112 bytes | +5% | 25.5 GB | 27.1 GB | 33.7 GB |
| Q8_0 | bottlecapai/ | 27.1 GB29,047,085,152 bytes | −2% | 30.8 GB | 32.5 GB | 39.1 GB |
| F16 | bottlecapai/ | 50.9 GB54,657,734,368 bytes | −2% | 57.0 GB | 58.7 GB | 65.3 GB |
GB here is GiB (1024³ bytes), as everywhere on this site; Hugging Face shows the Q4_K_M file as 17.4 GB, in 10⁹ bytes.
ThinkingCap Qwen3.8 27B on a 16 or 24 GB GPU
ThinkingCap is BottleCap AI’s fine-tune of Qwen3.8-27B that, on its model card, cuts reasoning tokens by 37% on average while holding 85.8% average accuracy against the base model’s 86.6%. Its config and its 55,563,006,776 bytes of safetensors are Qwen3.8 27B’s, so the memory math is too: only 16 of the 64 layers keep a KV cache, 2.00 GB at 32K and 8.00 GB at 128K for one request in FP16. Fewer thinking tokens fill less of that cache per answer; the weights are the same size.
On a 24 GB card such as the RTX 4090, BottleCap’s own Q4_K_M file (17,442,400,352 bytes, 16.2 GB) needs 18.9 GB at 8K and fits up to about 74K tokens with 0.5 GB free; its IQ4_XS (14.4 GB) goes to about 103K. Neither fits a 16 GB card: IQ4_XS already needs 16.9 GB at 8K. On 16 GB the community builds below do: mradermacher’s i1-Q3_K_M (12.6 GB) holds about 16K tokens, i1-IQ3_M about 27K and i1-Q2_K (10.1 GB) about 56K, at a quality cost BottleCap has not measured.
The BottleCap files carry the MTP head, which llama.cpp v0.4.1 or newer uses for self-speculative decoding with --spec-type draft-mtp; for images, load the 931,146,272-byte (888 MB) mmproj file from the same repo, which adds that much to every total. The GGUF repo is open; the safetensors repo asks you to request access, and both are under the PolyForm Small Business 1.0.0 license. Ollama’s library has no ThinkingCap tag. The smaller GGUF builds, with the totals this page’s method gives:
| Quant | File | Size | 8K | 32K | 128K |
|---|---|---|---|---|---|
| i1-Q2_K | mradermacher/ | 10.1 GB10,864,593,472 bytes | 12.2 GB | 13.8 GB | 20.4 GB |
| i1-IQ3_M | mradermacher/ | 11.9 GB12,768,332,352 bytes | 14.1 GB | 15.8 GB | 22.4 GB |
| IQ4_XS-MIX (3.92 bpw) | vmarcelo/ | 12.5 GB13,402,105,856 bytes | 14.8 GB | 16.4 GB | 23.0 GB |
| i1-Q3_K_M | mradermacher/ | 12.6 GB13,500,738,112 bytes | 14.9 GB | 16.5 GB | 23.1 GB |
| i1-IQ4_XS | mradermacher/ | 14.3 GB15,309,040,192 bytes | 16.7 GB | 18.4 GB | 25.0 GB |
BottleCap’s Q4_K_M is 1,531,470,176 bytes (1.43 GB) smaller than ggml-org’s Qwen3.8-27B Q4_K_M: it is an importance-matrix build with its own per-tensor precision layout. mradermacher’s i1-IQ3_M and vmarcelo’s IQ4_XS-MIX are estimated here with the nearest bits-per-weight row (Q3_K_M, IQ4_XS); the file sizes are exact. File sizes from the Hugging Face file lists, read on ; totals as in the table above, one request, FP16 KV cache.
Which ThinkingCap Qwen3.8 27B GGUF fits a 16, 24, 32, 48 or 80 GB GPU or a Mac
From the file sizes above: the largest file that fits each machine with an 8K context and 0.5 GB left free, the longest context it then has room for, and the longest context for Q4_K_M (16.2 GB). One request, FP16 KV cache.
| Hardware | Largest GGUF, 8K | Its longest context | Q4_K_M, longest context |
|---|---|---|---|
| RTX 5060 Ti 16GB | None fits | — | No |
| RTX 4090 (24 GB) | Q4_K_M, 16.2 GB | 74K | 74K |
| RTX 5090 (32 GB) | Q8_0, 27.1 GB | 17K | 190K |
| L40S (48 GB) | Q8_0, 27.1 GB | 256,000 | 256K (full) |
| H100 SXM (80 GB) | F16, 50.9 GB | 256K (full) | 256K (full) |
| M4 Pro Mac (64 GB, 48 GB usable) | Q8_0, 27.1 GB | 256,000 | 256K (full) |
| M4 Max Mac (128 GB, 96 GB usable) | F16, 50.9 GB | 256K (full) | 256K (full) |
Run ThinkingCap Qwen3.8 27B with llama.cpp
llama-server -hf bottlecapai/ThinkingCap-Qwen3.8-27B-GGUF:Q4_K_M -c 75776 ThinkingCap-Qwen3.8-27B-Q4_K_M.gguf, 17.4 GB, from bottlecapai/
ThinkingCap Qwen3.8 27B at 8K, 32K, 128K and 256K (full) tokens of context
16 of its 64 layers use full attention and 48 are linear-attention layers with no growing cache. Each extra token of context adds 64 KB of FP16 cache per request. The last column is the smallest setup here, one card or a group, that holds it at Q4_K_M. How the KV cache works.
| Context | KV cache, FP16 | Total at Q4_K_M | Total at Q8_0 | Smallest setup, Q4_K_M |
|---|---|---|---|---|
| 8K tokens | 512 MB | 18.3 GB | 31.3 GB | RTX 3090 (24 GB) |
| 32K tokens | 2.00 GB | 19.9 GB | 32.9 GB | RTX 3090 (24 GB) |
| 128K tokens | 8.00 GB | 26.5 GB | 39.5 GB | RTX 5090 (32 GB) |
| 256K tokens | 16.0 GB | 35.3 GB | 48.3 GB | M4 Pro Mac (64 GB, 48 GB usable) |
How fast ThinkingCap Qwen3.8 27B writes
Tokens per second for one request with 8,192 tokens of context, estimated from memory bandwidth. A dash means it does not fit on one card. Try other settings in the speed calculator.
| Hardware | Bandwidth | Q4_K_M | FP8 |
|---|---|---|---|
| RTX 3060 12GB | 360 GB/s | — | — |
| RTX 4090 | 1,008 GB/s | 31–43 | — |
| RTX 5090 | 1,792 GB/s | 52–75 | 33–46 |
| M4 Max Mac (128 GB) | 546 GB/s | 17–23 | 10–14 |
| M3 Ultra Mac Studio (512 GB) | 819 GB/s | 25–35 | 16–21 |
| H100 SXM | 3,350 GB/s | 92–135 | 59–85 |
| H200 | 4,800 GB/s | 124–188 | 82–120 |
Longest context on one GPU
How many tokens of context ThinkingCap Qwen3.8 27B fits on a single card with one request, an FP16 KV cache and 0.5 GB left free. "Full" means the model's whole context window fits.
| GPU | Memory | Q4_K_M | Q8_0 | FP8 |
|---|---|---|---|---|
| RTX 3060 | 12 GB | No | No | No |
| RTX 4060 Ti 16GB | 16 GB | No | No | No |
| RTX 3090 / 4090 | 24 GB | 83K | No | No |
| RTX 5090 | 32 GB | 200K | 10K | 36K |
| A100 40GB | 40 GB | 256K (full) | 127K | 153K |
| Mac, 64 GB unified memory | 48 GB | 256K (full) | 243K | 256K (full) |
| L40S / RTX 6000 Ada | 48 GB | 256K (full) | 243K | 256K (full) |
| A100 / H100 80GB | 80 GB | 256K (full) | 256K (full) | 256K (full) |
| Mac, 128 GB unified memory | 96 GB | 256K (full) | 256K (full) | 256K (full) |
| H200 | 141 GB | 256K (full) | 256K (full) | 256K (full) |
| B200 | 180 GB | 256K (full) | 256K (full) | 256K (full) |
Model details
- Parameters
- 27.8B (27,781,427,952)
- Layers
- 16 of its 64 layers use full attention and 48 are linear-attention layers with no growing cache
- Attention cache
- 4 KV heads × 256
- Context length
- 262,144 tokens
- Published weights
- 51.7 GB (BF16)
- On Hugging Face
- bottlecapai/
ThinkingCap-Qwen3.8-27B - Reported benchmarks
- None published in the model card for GPQA, MMLU-Pro or LiveCodeBench.
Why this estimate looks this way
At Q4_K_M and an 8K-token context, ThinkingCap Qwen3.8 27B uses 15.7 GB for weights, 512 MB for its FP16 KV cache and 2.12 GB for estimated runtime overhead, totaling 18.3 GB. The overhead is a 0.5 GB base plus 10% of weights and cache.
Its attention layout matters for long context: 16 of its 64 layers use full attention and 48 are linear-attention layers with no growing cache. The FP16 cache grows by about 64 KB per additional token per request.
The architecture and published checkpoint size come from the model's config.json and weight files. These are estimates rather than measured peak memory; inference engines can reserve extra buffers or preallocate the full configured cache.
ThinkingCap Qwen3.8 27B next to similar-sized models
The three models here closest to it in parameter count, at Q4_K_M with 8,192 tokens of context.
| Model | Parameters | Total | KV per token | Smallest setup |
|---|---|---|---|---|
| ThinkingCap Qwen3.8 27B | 27.8B | 18.3 GB | 64 KB | RTX 3090 (24 GB) |
| Qwen3.6 27B | 27.8B | 18.3 GB | 64 KB | RTX 3090 (24 GB) |
| Qwen3.8 27B | 27.8B | 18.3 GB | 64 KB | RTX 3090 (24 GB) |
| Hemmingway-1 27B | 27.3B | 18.0 GB | 64 KB | RTX 3090 (24 GB) |
ThinkingCap Qwen3.8 27B VRAM questions
How much VRAM do I need to run ThinkingCap Qwen3.8 27B locally?
About 18.3 GB at Q4_K_M with an 8K context and one request, by the bits-per-weight estimate, and 58.0 GB at BF16. The Q4_K_M GGUF ThinkingCap-Qwen3.8-27B-Q4_K_M.gguf in bottlecapai/
Can I run ThinkingCap Qwen3.8 27B on a 24 GB GPU?
Yes. On the RTX 4090 (24 GB), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q4_K_M (16.2 GB), with up to 74K tokens of context.
Which quantization of ThinkingCap Qwen3.8 27B fits in 16 GB of VRAM?
The RTX 5060 Ti 16GB alone cannot hold it: the smallest listed GGUF, IQ4_XS at 14.4 GB, needs 16.9 GB with an 8K context.
Can I run ThinkingCap Qwen3.8 27B on a Mac?
On the M4 Pro Mac (64 GB, 48 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q8_0 (27.1 GB), with up to 256,000 tokens of context. Q4_K_M (16.2 GB) runs with its full 256K-token context. On the M4 Max Mac (128 GB, 96 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is F16 (50.9 GB), with its full 256K-token context. By default macOS lets the GPU use about 75% of unified memory.
How much more VRAM does ThinkingCap Qwen3.8 27B need for 32K or 128K tokens of context?
Its FP16 KV cache is 512 MB at 8K, 2.00 GB at 32K, 8.00 GB at 128K for one request, so 128K adds 7.50 GB over 8K, plus 10% overhead. A q8_0 cache
Why does ThinkingCap Qwen3.8 27B use more VRAM than its GGUF file size?
The file holds only the weights. At Q4_K_M with an 8K context: 16.2 GB of weights (the file's 17,442,400,352 bytes) + 512 MB of FP16 KV cache + 2.17 GB of compute buffers and runtime (0.5 GB + 10%) = 18.9 GB.
Badge for your model card
Paste it into a Hugging Face or GitHub README; it shows the Q4_K_M total above and links to this page. Q8_0 and FP16 badges.
Numbers read from the model files on Hugging Face on . Compare it with other models in the reproducible model and GPU report.