Gemma3 Python 22k 1B_merged needs about 1.7 GB of memory at Q4_K_M (a 1.0 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 6 quants, from 0.9 GB (Q3_K_M) to 2.6 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.9 GB.
Gemma3 Python 22k 1B_merged is a 1.3B-parameter Gemma model in GGUF format, quantized by theprint. Its trained context length is 32K tokens. The repository has 6 quant files, from 0.9 GB (Q3_K_M) to 2.6 GB (F16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_M | 0.9 GB | 1.6 GB | Fits | Get file → | |
| Q4_K_M | 1.0 GB | 1.7 GB | Fits | Get file → | |
| Q5_K_M | 1.1 GB | 1.8 GB | Fits | Get file → | |
| Q6_K | 1.3 GB | 2.1 GB | Fits | Get file → | |
| Q8_0 | 1.4 GB | 2.1 GB | Fits | Get file → | |
| F16 | 2.6 GB | 3.3 GB | Fits | Get file → |
What GPU do you need for Gemma3 Python 22k 1B_merged?
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: the best quant that fits is F16 (2.6 GB file, about 3.3 GB in use).
Which Gemma3 Python 22k 1B_merged quant should you choose?
Q4_K_M is the usual starting point for Gemma3 Python 22k 1B_merged: it balances file size and quality well. Here it is a 1.0 GB file.
The Q8_0 file is 1.4 GB, about 1.4 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_M at 0.9 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
Source
Frequently asked questions about Gemma3 Python 22k 1B_merged
How much VRAM does Gemma3 Python 22k 1B_merged need?
About 1.7 GB at Q4_K_M with an 8K context window. That is the 1.0 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 Gemma3 Python 22k 1B_merged on an 8 GB GPU?
Yes, with F16: the 2.6 GB file needs about 3.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Gemma3 Python 22k 1B_merged GGUF?
It depends on the quant: Q3_K_M is 0.9 GB, Q4_K_M is 1.0 GB, Q5_K_M is 1.1 GB, Q6_K is 1.3 GB, Q8_0 is 1.4 GB, F16 is 2.6 GB.
What context length does Gemma3 Python 22k 1B_merged support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.9 GB at 32K.
Where can I download Gemma3 Python 22k 1B_merged GGUF?
The files are on Hugging Face in the theprint/Gemma3-Python-22k-1B-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 Gemma3 Python 22k 1B_merged use?
Hugging Face lists the license as mit. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.