Darwin 36B Opus 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.
Darwin 36B Opus – a 36‑billion‑parameter MoE language model
Darwin 36B Opus is a 36‑billion‑parameter mixture‑of‑experts model based on Qwen3.6‑35B‑A3B. It combines a base parent and a reasoning‑distilled parent, achieving 88.4% on GPQA Diamond. The model supports 262,144‑token context and is released under Apache‑2.0.
Good at
- Reasoning
- Tool use
- Large context handling
Limits
- No vision support
- Requires high VRAM for full precision
- Large memory footprint for higher quants
Best for
- Complex reasoning tasks
- Tool‑integrated workflows
- Long‑form content generation
Who it’s for. Developers and researchers needing a high‑capacity, reasoning‑capable language model for CPU or GPU deployment. The model is suitable for applications that can accommodate its large memory demands and benefit from its extensive context length.
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 (12.94 GB file, 14.1 GB memory at 8 k context) or Q3_K_S (15.18 GB file, 16.4 GB memory). For 16 GB VRAM, Q4_K_S (19.89 GB file, 21.1 GB memory) or Q4_K_M (21.17 GB file, 22.3 GB memory) are suitable. Higher quants require more VRAM.
What GPU do you need for Darwin 36B Opus?
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 Darwin 36B Opus quant should you choose?
Q4_K_M is the usual starting point for Darwin 36B Opus: 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
Source
Frequently asked questions about Darwin 36B Opus
How much VRAM does Darwin 36B Opus 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 Darwin 36B Opus 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 Darwin 36B Opus 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 Darwin 36B Opus 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 Darwin 36B Opus GGUF?
The files are on Hugging Face in the mradermacher/Darwin-36B-Opus-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 Darwin 36B Opus 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 Darwin 36B Opus on 8 GB VRAM?
Use the Q2_K or Q3_K_S quant, which require about 14–16 GB of VRAM at 8 k context. The model will run but may need swapping or lower batch size.
Does Darwin 36B Opus support vision tasks?
No, the model has no vision capabilities. It is a purely text‑based language model.
What license applies to Darwin 36B Opus?
The model is released under the Apache‑2.0 license.