BigBang Aquila 35B Merged Abliterated needs about 22.3 GB of memory at Q4_K_M (a 21.2 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 11 quants, from 12.9 GB (Q2_K) to 36.9 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 2.7 GB.
BigBang Aquila 35B Merged Abliterated – a 34.7B parameter Qwen3.6‑35B‑A3B based model
BigBang Aquila 35B Merged Abliterated is a 34.7B parameter Qwen3.6‑35B‑A3B derived model. It uses a DARE‑TIES merge and OrthoBot abliteration to reduce refusal directions. The model is text‑only, with the vision tower removed.
Good at
- Large context handling
- Text‑only inference
- Mixture‑of‑experts architecture
Limits
- No vision support
- Requires transformers>=5.12
- Large VRAM for higher quants
Best for
- Long‑form text generation
- Context‑heavy dialogue
- Research prototyping
Who it’s for. Developers and researchers needing a large, text‑only LLM with a 262144 token context window. The model is suitable for applications that can tolerate the higher VRAM demands of larger quants.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 12.9 GB | 14.1 GB | Too big | Get file → | |
| Q3_K_S | 15.2 GB | 16.4 GB | Too big | Get file → | |
| Q3_K_M | 16.8 GB | 17.9 GB | Too big | Get file → | |
| Q3_K_L | 18.1 GB | 19.3 GB | Too big | Get file → | |
| IQ4_XS | 18.9 GB | 20.1 GB | Too big | Get file → | |
| Q4_K_S | 19.9 GB | 21.1 GB | Too big | Get file → | |
| Q4_K_M | 21.2 GB | 22.3 GB | Too big | Get file → | |
| Q5_K_S | 24.0 GB | 25.2 GB | Too big | Get file → | |
| Q5_K_M | 24.7 GB | 25.9 GB | Too big | Get file → | |
| Q6_K | 28.5 GB | 29.7 GB | Too big | Get file → | |
| Q8_0 | 36.9 GB | 38.1 GB | Too big | Get file → |
For 8 GB VRAM, use Q2_K (file size 12.94 GB, estimated 14.1 GB memory). For 16 GB VRAM, Q4_K_S (19.89 GB, 21.1 GB memory) or Q5_K_S (23.98 GB, 25.2 GB memory) are suitable. Higher quants like Q8_0 require 36.9 GB file size and 38.1 GB memory, suitable only on high‑end GPUs.
What GPU do you need for BigBang Aquila 35B Merged 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: the best quant that fits is Q2_K (12.9 GB file, about 14.1 GB in use).
- 24 GB VRAM: the best quant that fits is Q4_K_M (21.2 GB file, about 22.3 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K (28.5 GB file, about 29.7 GB in use).
- 48 GB VRAM: the best quant that fits is Q8_0 (36.9 GB file, about 38.1 GB in use).
Which BigBang Aquila 35B Merged Abliterated quant should you choose?
Q4_K_M is the usual starting point for BigBang Aquila 35B Merged Abliterated: it balances file size and quality well. Here it is a 21.2 GB file.
The Q8_0 file is 36.9 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.
If memory is tight, the smallest file is Q2_K at 12.9 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about BigBang Aquila 35B Merged Abliterated
How much VRAM does BigBang Aquila 35B Merged Abliterated need?
About 22.3 GB at Q4_K_M with an 8K context window. That is the 21.2 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 BigBang Aquila 35B Merged Abliterated on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 14.1 GB, so you would need a larger GPU or CPU offloading.
What is the file size of BigBang Aquila 35B Merged Abliterated GGUF?
It depends on the quant: Q2_K is 12.9 GB, Q3_K_S is 15.2 GB, Q3_K_M is 16.8 GB, Q3_K_L is 18.1 GB, IQ4_XS is 18.9 GB, Q4_K_S is 19.9 GB and 5 more.
What context length does BigBang Aquila 35B Merged 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.7 GB at 8K and 2.7 GB at 32K.
Where can I download BigBang Aquila 35B Merged Abliterated GGUF?
The files are on Hugging Face in the mradermacher/BigBang-Aquila-35B-Merged-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 BigBang Aquila 35B Merged 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 this model on 8 GB VRAM?
Use the Q2_K quant, which has a file size of 12.94 GB and estimated memory usage of 14.1 GB at 8k context.
Does this model support vision?
No, the vision tower was dropped during abliteration; the checkpoint is text‑only.
What license applies?
The model is licensed under apache-2.0.