Abliterated needs about 20.4 GB of memory at Q3_K_M (a 19.1 GB file) with an 8K context window, so it fits on a 24 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 3.3 GB.
Abliterated – a 39.8B parameter mixture‑of‑experts model for coding tasks
Abliterated is a 39.8B parameter model derived from Recursive Flint. It supports reasoning, multi‑turn tool use, and code‑centric tasks such as bug fixing and feature implementation. The model is released under Apache‑2.0 and is available in a Q3_K_M GGUF quantization.
Good at
- Code debugging
- Feature implementation
- Tool‑enabled agentic tasks
Limits
- Requires ~20.4GB VRAM at 8k context
- No vision support
- License is Apache‑2.0
Best for
- Local code assistant
- Automated bug triage
- Test generation
Who it’s for. Developers and researchers needing a large, code‑focused language model that can run locally with llama.cpp. The model is suitable for environments with high VRAM GPUs and for users who prefer open‑source licensing.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_M | 19.1 GB | 20.4 GB | Too big | Get file → |
The only available quant is Q3_K_M, 19.1GB file size. It requires approximately 20.4GB VRAM at 8k context. For 8GB or 16GB VRAM GPUs, the model cannot be loaded. If a larger VRAM GPU is available, Q3_K_M is the recommended quant.
What GPU do you need for Abliterated?
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: the best quant that fits is Q3_K_M (19.1 GB file, about 20.4 GB in use).
Which Abliterated quant should you choose?
Q3_K_M (19.1 GB) is the middle option in this repository. 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 Abliterated
How much VRAM does Abliterated need?
About 20.4 GB at Q3_K_M with an 8K context window. That is the 19.1 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 Abliterated on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 20.4 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Abliterated GGUF?
It depends on the quant: Q3_K_M is 19.1 GB.
What context length does Abliterated support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.8 GB at 8K and 3.3 GB at 32K.
Where can I download Abliterated GGUF?
The files are on Hugging Face in the lilcheaty/flint-abliterated-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 Abliterated 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 Abliterated on 8GB VRAM?
No, the Q3_K_M quant requires about 20.4GB VRAM at 8k context.
Can I run Abliterated on 16GB VRAM?
No, the model needs more than 16GB VRAM to load the Q3_K_M quant.
Can I run Abliterated on 24GB VRAM?
Yes, 24GB VRAM is sufficient to load the Q3_K_M quant and run the model.