OrcaCyber Nano 1.0 needs about 15.1 GB of memory at its main file (a 13.0 GB file) with an 8K context window, so it fits on a 16 GB GPU. This repository has 3 quants, from 2.1 GB (Q8_0) to 15.7 GB.
OrcaCyber Nano 1.0 – 1.9B parameter LLM with reasoning, tools, and vision
OrcaCyber Nano 1.0 is a 1.9 billion‑parameter language model. It supports reasoning, tool usage, and vision tasks. The model is available in GGUF format and can be run with llama.cpp.
Good at
- Reasoning tasks
- Tool integration
- Vision processing
Limits
- Requires at least 2.8 GB VRAM for Q8_0 at 8k context
- Large context not supported
- License is other, usage restrictions unknown
Best for
- Small‑scale inference on 8 GB GPUs
- Rapid prototyping of multimodal applications
- Educational demos of vision‑enabled LLMs
Who it’s for. Developers needing a compact multimodal model for local deployment. Ideal for projects that require reasoning, tool use, and basic vision capabilities without large hardware requirements.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q8_0 | 2.1 GB | 2.8 GB | Fits | Get file → | |
| — | 13.0 GB | 15.1 GB | Too big | Get file → | |
| — | 15.7 GB | 18.1 GB | Too big | Get file → |
For 8 GB VRAM, use the Q8_0 quantized file (2.06 GB). If more memory is available, the 12.99 GB or 15.7 GB files provide higher precision. Memory estimates are approximate.
What GPU do you need for OrcaCyber Nano 1.0?
These figures add the file size, an fp16 KV cache at an 8K context window 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 Q8_0 (2.1 GB file, about 2.8 GB in use).
- 6 GB VRAM: the best quant that fits is Q8_0 (2.1 GB file, about 2.8 GB in use).
- 8 GB VRAM: the best quant that fits is Q8_0 (2.1 GB file, about 2.8 GB in use).
- 12 GB VRAM: the best quant that fits is Q8_0 (2.1 GB file, about 2.8 GB in use).
- 16 GB VRAM: the best quant that fits is the main file (13.0 GB file, about 15.1 GB in use).
- 24 GB VRAM: the best quant that fits is the main file (15.7 GB file, about 18.1 GB in use).
Which OrcaCyber Nano 1.0 quant should you choose?
If memory is tight, the smallest file is Q8_0 at 2.1 GB, with the quality trade-offs that come with fewer bits. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about OrcaCyber Nano 1.0
How much VRAM does OrcaCyber Nano 1.0 need?
About 15.1 GB at its main file with an 8K context window. That is the 13.0 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 OrcaCyber Nano 1.0 on an 8 GB GPU?
Yes, with Q8_0: the 2.1 GB file needs about 2.8 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of OrcaCyber Nano 1.0 GGUF?
It depends on the quant: Q8_0 is 2.1 GB, file is 13.0 GB, file is 15.7 GB.
What context length does OrcaCyber Nano 1.0 support?
The GGUF header lists a trained context length of 262,144 tokens (256K).
Where can I download OrcaCyber Nano 1.0 GGUF?
The files are on Hugging Face in the orcarouter/OrcaCyber-Nano-1.0 repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does OrcaCyber Nano 1.0 use?
Hugging Face lists the license as other. 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 OrcaCyber Nano 1.0 on 8 GB VRAM?
Yes, the Q8_0 quantized file uses about 2.8 GB of VRAM at 8k context, fitting within 8 GB.
Does the model support vision tasks?
Yes, it has detected vision abilities and can process image inputs.
What license applies to this model?
The model is released under an 'other' license; check the repository for specific terms.