Imagine v12 needs about 3.0 GB of memory at Q4_K_M (a 0.9 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 4 quants, from 0.8 GB (Q4_0) to 1.4 GB (Q8_0).
Specialized SQL generation model with built‑in identity
Imagine v12 is a 1.35B parameter model fine‑tuned for schema‑grounded SQL. It outputs PostgreSQL wrapped in sentinel blocks and requires no external LLM or API. The model is released under apache‑2.0 and runs locally.
Good at
- SQL generation from natural language
- Schema‑aware query construction
- Identity‑aware responses
Limits
- No vision support
- Requires 8k context for full performance
- No external API needed
Best for
- Embedded database tooling
- Local SQL assistant
- Automated query generation
Who it’s for. Developers needing a lightweight, locally deployable SQL model. The model is ideal for on‑premise data pipelines and applications that require consistent identity and no cloud dependency.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_0 | 0.8 GB | 2.9 GB | Fits | Get file → | |
| Q4_K_M | 0.9 GB | 3.0 GB | Fits | Get file → | |
| Q5_K_M | 1.0 GB | 3.1 GB | Fits | Get file → | |
| Q8_0 | 1.4 GB | 3.5 GB | Fits | Get file → |
For 8 GB VRAM, Q4_0 (0.78 GB, 2.9 GB memory at 8k context) is recommended. If 12 GB VRAM is available, Q4_K_M (0.87 GB, 3 GB memory) or Q5_K_M (1 GB, 3.1 GB memory) can be used. Q8_0 (1.43 GB, 3.5 GB memory) offers the highest precision but needs more VRAM.
What GPU do you need for Imagine v12?
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 Q8_0 (1.4 GB file, about 3.5 GB in use).
Which Imagine v12 quant should you choose?
Q4_K_M is the usual starting point for Imagine v12: it balances file size and quality well. Here it is a 0.9 GB file.
The Q8_0 file is 1.4 GB, about 1.6 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 Q4_0 at 0.8 GB, with the quality trade-offs that come with fewer bits. The usual sweet spot between file size and quality, and the quant most people start with.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Imagine v12
How much VRAM does Imagine v12 need?
About 3.0 GB at Q4_K_M with an 8K context window. That is the 0.9 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 Imagine v12 on an 8 GB GPU?
Yes, with Q8_0: the 1.4 GB file needs about 3.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Imagine v12 GGUF?
It depends on the quant: Q4_0 is 0.8 GB, Q4_K_M is 0.9 GB, Q5_K_M is 1.0 GB, Q8_0 is 1.4 GB.
What context length does Imagine v12 support?
The GGUF header lists a trained context length of 16,384 tokens (16K). The KV cache grows with the context you use: about 1.6 GB at 8K and 3.2 GB at 16K.
Where can I download Imagine v12 GGUF?
The files are on Hugging Face in the Interchained/imagine-v12 repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Imagine v12 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 Imagine v12 on 8 GB VRAM?
Yes, using Q4_0 or Q4_K_M quantizations will fit within 8 GB VRAM with approximate memory usage of 2.9–3 GB at 8k context.
Does Imagine v12 support image inputs?
No, the model has no vision capabilities and only processes text.
Is a system prompt required to identify the model?
No, the model has a trained identity and does not need a system prompt to state its name.