Clover 35B A3B Preview APEX I NanoPlus V2.1 needs about 13.7 GB of memory at its main file (a 12.6 GB file) with an 8K context window, so it fits on a 16 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 2.7 GB.
Clover 35B A3B Preview APEX I NanoPlus V2.1 – a 35B‑parameter MoE language model
Clover 35B A3B Preview APEX I NanoPlus V2.1 is a 34.7B‑parameter mixture‑of‑experts model with 3B active parameters per token. It supports a 128K context window and is optimized for reasoning and tool use. The model is released under the Apache‑2.0 license.
Good at
- Large context reasoning
- Tool‑based task execution
- Block diffusion generation
Limits
- 128K context only, no vision support
- Requires >13.7 GB VRAM for 8K context
- Single quant file only
Best for
- Long‑form content creation
- Complex problem solving
- Automated workflow integration
Who it’s for. Developers and researchers needing a high‑capacity, text‑only language model with advanced reasoning and tool‑use capabilities. The model is suitable for applications that can accommodate its large memory footprint and specialized architecture.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 12.6 GB | 13.7 GB | Too big | Get file → |
The available GGUF file is 12.56 GB and requires approximately 13.7 GB of VRAM at 8K context. For systems with 16 GB or more VRAM, this quant is suitable. No other quantizations are provided.
What GPU do you need for Clover 35B A3B Preview APEX I NanoPlus V2.1?
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 the main file (12.6 GB file, about 13.7 GB in use).
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Clover 35B A3B Preview APEX I NanoPlus V2.1
How much VRAM does Clover 35B A3B Preview APEX I NanoPlus V2.1 need?
About 13.7 GB at its main file with an 8K context window. That is the 12.6 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 Clover 35B A3B Preview APEX I NanoPlus V2.1 on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 13.7 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Clover 35B A3B Preview APEX I NanoPlus V2.1 GGUF?
It depends on the quant: file is 12.6 GB.
What context length does Clover 35B A3B Preview APEX I NanoPlus V2.1 support?
The GGUF header lists a trained context length of 131,072 tokens (128K). 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 Clover 35B A3B Preview APEX I NanoPlus V2.1 GGUF?
The files are on Hugging Face in the IsValorum/Clover-35B-A3B-Preview-APEX-I-NanoPlus-V2.1-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 Clover 35B A3B Preview APEX I NanoPlus V2.1 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?
No. The model requires about 13.7 GB of VRAM at 8K context, which exceeds 8 GB.
Does Clover support vision or image inputs?
No. Clover is a text‑only model and does not support vision.
How many active parameters does Clover use per token?
Clover uses approximately 3 B active parameters per token.