Split 31B needs about 51.4 GB of memory at Q4_K_M (a 18.7 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 24 quants, from 0.0 GB to 25.2 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 128.8 GB.
30.7B‑parameter gemma4 model for roleplay
Split 31B is a 30.7 billion‑parameter gemma4 model trained on 262144 context tokens. It is released under the apache‑2.0 license and supports roleplay tasks. The model is available in multiple GGUF quantizations.
Good at
- Roleplay dialogue
- Long‑form text generation
- Context‑heavy conversations
Limits
- Requires large VRAM (≈50 GB for Q4_0 at 8 k context)
- No vision support
- License is apache‑2.0
Best for
- Chatbots needing deep context
- Creative writing assistants
- Simulated character interactions
Who it’s for. Developers building chat or roleplay applications that need extensive context handling. The model is suitable for users with high‑end GPUs and who prefer open‑source licensing.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 32.7 GB | Too big | Get file → | |
| IQ1_S | 7.2 GB | 39.9 GB | Too big | Get file → | |
| IQ1_M | 7.7 GB | 40.4 GB | Too big | Get file → | |
| IQ2_XXS | 8.7 GB | 41.4 GB | Too big | Get file → | |
| IQ2_XS | 9.5 GB | 42.2 GB | Too big | Get file → | |
| IQ2_S | 10.2 GB | 42.9 GB | Too big | Get file → | |
| IQ2_M | 10.9 GB | 43.6 GB | Too big | Get file → | |
| Q2_K_S | 11.0 GB | 43.7 GB | Too big | Get file → | |
| Q2_K | 11.9 GB | 44.6 GB | Too big | Get file → | |
| IQ3_XXS | 12.1 GB | 44.8 GB | Too big | Get file → | |
| IQ3_XS | 13.1 GB | 45.8 GB | Too big | Get file → | |
| IQ3_S | 13.8 GB | 46.5 GB | Too big | Get file → | |
| Q3_K_S | 13.8 GB | 46.5 GB | Too big | Get file → | |
| IQ3_M | 14.4 GB | 47.1 GB | Too big | Get file → | |
| Q3_K_M | 15.3 GB | 48.0 GB | Too big | Get file → | |
| Q3_K_L | 16.6 GB | 49.3 GB | Too big | Get file → | |
| IQ4_XS | 16.7 GB | 49.4 GB | Too big | Get file → | |
| Q4_0 | 17.7 GB | 50.4 GB | Too big | Get file → | |
| Q4_K_S | 17.8 GB | 50.5 GB | Too big | Get file → | |
| Q4_K_M | 18.7 GB | 51.4 GB | Too big | Get file → | |
| Q4_1 | 19.5 GB | 52.2 GB | Too big | Get file → | |
| Q5_K_S | 21.3 GB | 54.0 GB | Too big | Get file → | |
| Q5_K_M | 21.8 GB | 54.6 GB | Too big | Get file → | |
| Q6_K | 25.2 GB | 57.9 GB | Too big | Get file → |
For 8 GB VRAM, the smallest available quant is IQ1_S at 7.16 GB file size but still requires ≈39.9 GB VRAM at 8 k context. For moderate VRAM (≈16 GB), use Q4_0 (17.7 GB file, ≈50.4 GB VRAM). For larger GPUs, Q4_K_M or Q5_K_M offer higher quality with ≈51.4 GB or ≈54.6 GB VRAM respectively. Estimates are approximate.
What GPU do you need for Split 31B?
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_M (15.3 GB file, about 48.0 GB in use).
Which Split 31B quant should you choose?
Q4_K_M is the usual starting point for Split 31B: it balances file size and quality well. Here it is a 18.7 GB file.
If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Split 31B
How much VRAM does Split 31B need?
About 51.4 GB at Q4_K_M with an 8K context window. That is the 18.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 Split 31B on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 32.7 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Split 31B GGUF?
It depends on the quant: file is 0.0 GB, IQ1_S is 7.2 GB, IQ1_M is 7.7 GB, IQ2_XXS is 8.7 GB, IQ2_XS is 9.5 GB, IQ2_S is 10.2 GB and 18 more.
What context length does Split 31B support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 32.2 GB at 8K and 128.8 GB at 32K.
Where can I download Split 31B GGUF?
The files are on Hugging Face in the mradermacher/Split-31B-i1-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 Split 31B 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.
Is there a CPU‑only option?
The GGUF files can be loaded in llama.cpp on CPU, but performance will be slow and memory usage high.
Does the model support vision?
No, Split 31B is a text‑only model; no mmproj files are provided.