Nanonets OCR S needs about 2.7 GB of memory at Q4_K_M (a 1.9 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 36 quants, from 0.8 GB (IQ1_S) to 6.2 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.2 GB.
Nanonets OCR S – image‑to‑markdown OCR model
Nanonets OCR S converts images into structured markdown, extracting LaTeX equations, images, signatures, watermarks, checkboxes, and complex tables. It is built on Qwen2.5‑VL‑3B and trained on over 250,000 diverse pages. The model outputs content ready for downstream LLM processing.
Good at
- LaTeX equation recognition
- Image and signature tagging
- Complex table extraction
Limits
- No vision support beyond image‑to‑markdown
- Requires 8 k context for full functionality
- Apache‑2.0 license
Best for
- Document digitization
- Legal and financial form processing
- Academic paper conversion
Who it’s for. Developers building document‑intelligence pipelines and researchers needing structured markdown from scanned documents. The model is suitable for integration with LLMs that consume markdown input.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ1_S | 0.8 GB | 1.6 GB | Fits | Get file → | |
| IQ1_M | 0.9 GB | 1.7 GB | Fits | Get file → | |
| IQ2_XXS | 0.9 GB | 1.8 GB | Fits | Get file → | |
| IQ2_XS | 1.0 GB | 1.8 GB | Fits | Get file → | |
| IQ2_S | 1.1 GB | 1.9 GB | Fits | Get file → | |
| IQ2_M | 1.1 GB | 1.9 GB | Fits | Get file → | |
| Q2_K_S | 1.2 GB | 2.0 GB | Fits | Get file → | |
| Q2_K | 1.3 GB | 2.1 GB | Fits | Get file → | |
| Q2_K | 1.3 GB | 2.1 GB | Fits | Get file → | |
| IQ3_XXS | 1.3 GB | 2.1 GB | Fits | Get file → | |
| IQ3_XS | 1.4 GB | 2.2 GB | Fits | Get file → | |
| Q3_K_S | 1.5 GB | 2.3 GB | Fits | Get file → | |
| Q3_K_S | 1.5 GB | 2.3 GB | Fits | Get file → | |
| IQ3_S | 1.5 GB | 2.3 GB | Fits | Get file → | |
| IQ3_M | 1.5 GB | 2.3 GB | Fits | Get file → | |
| Q3_K_M | 1.6 GB | 2.4 GB | Fits | Get file → | |
| Q3_K_M | 1.6 GB | 2.4 GB | Fits | Get file → | |
| Q3_K_L | 1.7 GB | 2.5 GB | Fits | Get file → | |
| Q3_K_L | 1.7 GB | 2.5 GB | Fits | Get file → | |
| IQ4_XS | 1.7 GB | 2.5 GB | Fits | Get file → | |
| IQ4_XS | 1.8 GB | 2.6 GB | Fits | Get file → | |
| IQ4_NL | 1.8 GB | 2.6 GB | Fits | Get file → | |
| Q4_0 | 1.8 GB | 2.6 GB | Fits | Get file → | |
| Q4_K_S | 1.8 GB | 2.6 GB | Fits | Get file → | |
| Q4_K_S | 1.8 GB | 2.6 GB | Fits | Get file → | |
| Q4_K_M | 1.9 GB | 2.7 GB | Fits | Get file → | |
| Q4_K_M | 1.9 GB | 2.7 GB | Fits | Get file → | |
| Q4_1 | 2.0 GB | 2.8 GB | Fits | Get file → | |
| Q5_K_S | 2.2 GB | 3.0 GB | Fits | Get file → | |
| Q5_K_S | 2.2 GB | 3.0 GB | Fits | Get file → | |
| Q5_K_M | 2.2 GB | 3.0 GB | Fits | Get file → | |
| Q5_K_M | 2.2 GB | 3.0 GB | Fits | Get file → | |
| Q6_K | 2.5 GB | 3.3 GB | Fits | Get file → | |
| Q6_K | 2.5 GB | 3.3 GB | Fits | Get file → | |
| Q8_0 | 3.3 GB | 4.1 GB | Fits | Get file → | |
| F16 | 6.2 GB | 7.0 GB | Fits | Get file → |
For 8 GB VRAM, use IQ1_S (0.79 GB, 1.6 GB memory) or IQ1_M (0.85 GB, 1.7 GB memory). If 12 GB VRAM is available, IQ2_S (1.06 GB, 1.9 GB memory) or Q2_K_S (1.2 GB, 2 GB memory) provide better quality. Higher quants such as Q5_K_S (2.17 GB, 3 GB memory) require 16 GB VRAM or more.
What GPU do you need for Nanonets OCR S?
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 Q6_K (2.5 GB file, about 3.3 GB in use).
- 6 GB VRAM: the best quant that fits is Q8_0 (3.3 GB file, about 4.1 GB in use).
- 8 GB VRAM: the best quant that fits is F16 (6.2 GB file, about 7.0 GB in use).
Which Nanonets OCR S quant should you choose?
Q4_K_M is the usual starting point for Nanonets OCR S: it balances file size and quality well. Here it is a 1.9 GB file.
The Q8_0 file is 3.3 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 IQ1_S at 0.8 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 Nanonets OCR S
How much VRAM does Nanonets OCR S need?
About 2.7 GB at Q4_K_M with an 8K context window. That is the 1.9 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 Nanonets OCR S on an 8 GB GPU?
Yes, with F16: the 6.2 GB file needs about 7.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Nanonets OCR S GGUF?
It depends on the quant: IQ1_S is 0.8 GB, IQ1_M is 0.9 GB, IQ2_XXS is 0.9 GB, IQ2_XS is 1.0 GB, IQ2_S is 1.1 GB, IQ2_M is 1.1 GB and 30 more.
What context length does Nanonets OCR S support?
The GGUF header lists a trained context length of 128,000 tokens (125K). The KV cache grows with the context you use: about 0.3 GB at 8K and 1.2 GB at 32K.
Where can I download Nanonets OCR S GGUF?
The files are on Hugging Face in the prithivMLmods/Nanonets-OCR-s-AIO-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 Nanonets OCR S 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 Nanonets OCR S on 8 GB VRAM?
Yes, the IQ1_S quant uses 0.79 GB file size and estimates 1.6 GB VRAM at 8 k context.
Does the model support multiple languages?
The model is trained on diverse documents but language support is not specified in the facts.
Is the model licensed for commercial use?
It is released under the apache-2.0 license, which allows commercial use.