Carnice V3 needs about 20.5 GB of memory at Q4_K_M (a 17.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 28 quants, from 0.0 GB to 54.7 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 8.7 GB.
Carnice V3 – 27.3B Qwen3.8‑27B model with vision and tool support
Carnice V3 is a 27.3B parameter Qwen3.8‑27B model merged with a rank‑64 rsLoRA. It supports text, image input, and tool calls via XML function‑call envelopes. The model is released under Apache‑2.0 and requires a recent llama.cpp build for quantized inference.
Good at
- Vision‑enabled text generation
- Tool‑aware dialogue with XML contracts
- Multi‑token prediction for faster output
Limits
- Requires 8‑k context for memory estimates
- No formal behavioral quality gate passed
- Not suitable for unattended high‑stakes use
Best for
- Multimodal chat agents
- Tool‑driven automation scripts
- Research on MTP speculative decoding
Who it’s for. Developers building agents that need image understanding and structured tool calls. Use with caution in production; perform independent evaluation and runtime controls.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 2.7 GB | Fits | Get file → | |
| IQ2_XXS | 9.4 GB | 12.1 GB | Too big | Get file → | |
| IQ2_XS | 10.0 GB | 12.7 GB | Too big | Get file → | |
| IQ2_S | 10.3 GB | 13.0 GB | Too big | Get file → | |
| IQ2_M | 10.9 GB | 13.6 GB | Too big | Get file → | |
| Q2_K | 11.8 GB | 14.5 GB | Too big | Get file → | |
| IQ3_XXS | 12.6 GB | 15.3 GB | Too big | Get file → | |
| Q2_K_L | 13.1 GB | 15.8 GB | Too big | Get file → | |
| IQ3_XS | 13.3 GB | 16.0 GB | Too big | Get file → | |
| Q3_K_S | 13.7 GB | 16.4 GB | Too big | Get file → | |
| IQ3_M | 13.9 GB | 16.6 GB | Too big | Get file → | |
| Q3_K_M | 14.6 GB | 17.3 GB | Too big | Get file → | |
| Q3_K_L | 15.3 GB | 18.0 GB | Too big | Get file → | |
| IQ4_XS | 15.6 GB | 18.2 GB | Too big | Get file → | |
| IQ4_NL | 16.3 GB | 19.0 GB | Too big | Get file → | |
| Q4_0 | 16.3 GB | 19.0 GB | Too big | Get file → | |
| Q3_K_XL | 16.4 GB | 19.1 GB | Too big | Get file → | |
| Q4_K_S | 16.7 GB | 19.4 GB | Too big | Get file → | |
| Q4_K_M | 17.8 GB | 20.5 GB | Too big | Get file → | |
| Q4_1 | 17.8 GB | 20.5 GB | Too big | Get file → | |
| Q4_K_L | 18.7 GB | 21.4 GB | Too big | Get file → | |
| Q5_K_S | 19.7 GB | 22.4 GB | Too big | Get file → | |
| Q5_K_M | 20.8 GB | 23.4 GB | Too big | Get file → | |
| Q5_K_L | 21.5 GB | 24.2 GB | Too big | Get file → | |
| Q6_K | 23.5 GB | 26.1 GB | Too big | Get file → | |
| Q6_K_L | 24.1 GB | 26.8 GB | Too big | Get file → | |
| Q8_0 | 29.1 GB | 31.8 GB | Too big | Get file → | |
| BF16 | 54.7 GB (2 parts) | 57.3 GB | Too big | Get file → |
For 8‑GB VRAM, use Q4_K_M (17.77 GB) or Q4_K_S (16.71 GB). For 12‑GB VRAM, Q4_K_L (18.72 GB) or Q5_K_S (19.68 GB) are suitable. For 16‑GB VRAM, Q5_K_M (20.75 GB) or Q5_K_L (21.54 GB) provide higher quality. Memory estimates are approximate.
What GPU do you need for Carnice V3?
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: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 12 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
- 16 GB VRAM: the best quant that fits is IQ3_XS (13.3 GB file, about 16.0 GB in use).
- 24 GB VRAM: the best quant that fits is Q5_K_M (20.8 GB file, about 23.4 GB in use).
- 32 GB VRAM: the best quant that fits is Q8_0 (29.1 GB file, about 31.8 GB in use).
- 48 GB VRAM: the best quant that fits is Q8_0 (29.1 GB file, about 31.8 GB in use).
Which Carnice V3 quant should you choose?
Q4_K_M is the usual starting point for Carnice V3: it balances file size and quality well. Here it is a 17.8 GB file.
The Q8_0 file is 29.1 GB, about 1.6 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 the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Carnice V3
How much VRAM does Carnice V3 need?
About 20.5 GB at Q4_K_M with an 8K context window. That is the 17.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 Carnice V3 on an 8 GB GPU?
Yes, with the smaller files: the 0.0 GB file needs about 2.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Carnice V3 GGUF?
It depends on the quant: file is 0.0 GB, IQ2_XXS is 9.4 GB, IQ2_XS is 10.0 GB, IQ2_S is 10.3 GB, IQ2_M is 10.9 GB, Q2_K is 11.8 GB and 22 more.
What context length does Carnice V3 support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 2.2 GB at 8K and 8.7 GB at 32K.
Where can I download Carnice V3 GGUF?
The files are on Hugging Face in the bartowski/kai-os_Carnice-V3-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 Carnice V3 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 Carnice V3 on 8 GB VRAM?
Yes, with the Q4_K_M quant (17.77 GB) or Q4_K_S (16.71 GB) you can fit the model on 8 GB VRAM using llama.cpp with speculative decoding enabled.
Does Carnice V3 support image input?
Yes, the model includes multimodal projector files and supports image input via the mmproj files.
Is Carnice V3 safe for production agents?
The release notes advise against unattended, destructive, or high‑stakes use without independent evaluation and runtime controls.