SpawnPoint-Coder-7B needs about 5.7 GB of memory at Q4_K_M (a 4.7 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 2 quants, from 4.7 GB (Q4_K_M) to 8.1 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 1.9 GB.
SpawnPoint-Coder-7B – a 7.62B parameter coding model
SpawnPoint-Coder-7B is a 7.62B parameter Qwen2 model focused on coding and tool usage. It supports a 32768 token context and is released under the Apache‑2.0 license. The model is available in GGUF format for Ollama, llama.cpp and LM Studio.
Good at
- Coding tasks
- Tool integration
- JSON‑schema output
Limits
- No vision support
- Large memory requirement for 8k context
- No active development
Best for
- Generating Godot 4 game projects
- Creating card game designs
- Automating coding workflows
Who it’s for. Developers and hobbyists who need a dedicated coding assistant for game development or tool‑based workflows. The model is suitable for users with sufficient GPU or CPU memory to run 8k context inference.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 4.7 GB | 5.7 GB | Fits | Get file → | |
| Q8_0 | 8.1 GB | 9.1 GB | Too big | Get file → |
For 8 GB VRAM use the Q4_K_M quant (4.68 GB file, ~5.7 GB memory at 8k context). For 16 GB VRAM the Q8_0 quant (8.1 GB file, ~9.1 GB memory) provides higher precision. Memory estimates are approximate.
What GPU do you need for SpawnPoint-Coder-7B?
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: the best quant that fits is Q4_K_M (4.7 GB file, about 5.7 GB in use).
- 8 GB VRAM: the best quant that fits is Q4_K_M (4.7 GB file, about 5.7 GB in use).
- 12 GB VRAM: the best quant that fits is Q8_0 (8.1 GB file, about 9.1 GB in use).
Which SpawnPoint-Coder-7B quant should you choose?
Q4_K_M is the usual starting point for SpawnPoint-Coder-7B: it balances file size and quality well. Here it is a 4.7 GB file.
The Q8_0 file is 8.1 GB, about 1.7 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.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about SpawnPoint-Coder-7B
How much VRAM does SpawnPoint-Coder-7B need?
About 5.7 GB at Q4_K_M with an 8K context window. That is the 4.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 SpawnPoint-Coder-7B on an 8 GB GPU?
Yes, with Q4_K_M: the 4.7 GB file needs about 5.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of SpawnPoint-Coder-7B GGUF?
It depends on the quant: Q4_K_M is 4.7 GB, Q8_0 is 8.1 GB.
What context length does SpawnPoint-Coder-7B 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.5 GB at 8K and 1.9 GB at 32K.
Where can I download SpawnPoint-Coder-7B GGUF?
The files are on Hugging Face in the smoky1496/SpawnPoint-Coder-7B-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 SpawnPoint-Coder-7B 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.
Can I run SpawnPoint-Coder-7B on 8 GB VRAM?
Yes, using the Q4_K_M quant which requires about 5.7 GB of VRAM at 8k context.
Does the model support image inputs?
No, the model has no vision capabilities.
Is the model still actively developed?
No, Spawn Point is finished and no longer actively developed.