c4ai-command-r-plus needs about 65.4 GB of memory at Q4_K_M (a 62.8 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 10 quants, from 40.7 GB (IQ3_XXS) to 207.6 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.
c4ai-command-r-plus is a 104B-parameter Command R model in GGUF format, quantized by grapevine-AI. Its trained context length is 128K tokens. The repository has 10 quant files, from 40.7 GB (IQ3_XXS) to 207.6 GB (F16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ3_XXS | 40.7 GB | 43.3 GB | Too big | Get file → | |
| IQ3_XS | 43.6 GB | 46.2 GB | Too big | Get file → | |
| IQ3_S | 46.0 GB | 48.6 GB | Too big | Get file → | |
| IQ3_M | 47.7 GB | 50.3 GB | Too big | Get file → | |
| IQ4_XS | 56.2 GB (2 parts) | 58.8 GB | Too big | Get file → | |
| Q4_K_S | 59.6 GB (2 parts) | 62.3 GB | Too big | Get file → | |
| Q4_K_M | 62.8 GB (2 parts) | 65.4 GB | Too big | Get file → | |
| Q5_K_M | 73.6 GB (2 parts) | 76.3 GB | Too big | Get file → | |
| F16 | 207.6 GB (6 parts) | 210.3 GB | Too big | Get file → | |
| F16 | 207.6 GB (5 parts) | 210.3 GB | Too big | Get file → |
What GPU do you need for c4ai-command-r-plus?
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: no quant fits at an 8K context.
- 32 GB VRAM: no quant fits at an 8K context.
- 48 GB VRAM: the best quant that fits is IQ3_XS (43.6 GB file, about 46.2 GB in use).
Which c4ai-command-r-plus quant should you choose?
Q4_K_M is the usual starting point for c4ai-command-r-plus: it balances file size and quality well. Here it is a 62.8 GB file.
If memory is tight, the smallest file is IQ3_XXS at 40.7 GB, with the quality trade-offs that come with fewer bits. 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 c4ai-command-r-plus
How much VRAM does c4ai-command-r-plus need?
About 65.4 GB at Q4_K_M with an 8K context window. That is the 62.8 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 c4ai-command-r-plus on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 43.3 GB, so you would need a larger GPU or CPU offloading.
What is the file size of c4ai-command-r-plus GGUF?
It depends on the quant: IQ3_XXS is 40.7 GB, IQ3_XS is 43.6 GB, IQ3_S is 46.0 GB, IQ3_M is 47.7 GB, IQ4_XS is 56.2 GB, Q4_K_S is 59.6 GB and 4 more.
What context length does c4ai-command-r-plus support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 2.1 GB at 8K and 8.6 GB at 32K.
Where can I download c4ai-command-r-plus GGUF?
The files are on Hugging Face in the grapevine-AI/c4ai-command-r-plus-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 c4ai-command-r-plus use?
Hugging Face lists the license as cc-by-nc-4.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.