Next Ocr needs about 6.7 GB of memory at Q4_K_M (a 5.0 GB file) with an 8K context window, so it fits on a 8 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 4.8 GB.
Compact OCR AI with math and table understanding
Next OCR 8B is an 8‑billion parameter model optimized for optical character recognition. It supports multilingual OCR and excels at extracting structured content such as tables, forms, and formulas.
Good at
- Accurate text extraction including math
- Multilingual OCR across 30+ languages
- Efficient inference with small model size
Limits
- No vision support beyond OCR
- Requires 8‑k context for full memory estimate
- License is apache‑2.0
Best for
- Document digitization
- Invoice and receipt processing
- Multilingual OCR pipelines
Who it’s for. Developers building document intelligence solutions that need fast, accurate OCR with support for mathematical and tabular data. Suitable for enterprise document management and data extraction workflows.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 5.0 GB | 6.7 GB | Fits | Get file → |
The Q4_K_M quantized file is 5.03 GB. It requires approximately 6.7 GB of VRAM at 8 k context. For 8 GB VRAM systems, this quant is suitable. If VRAM is lower, consider using a different quantization not listed here.
What GPU do you need for Next Ocr?
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: the best quant that fits is Q4_K_M (5.0 GB file, about 6.7 GB in use).
Which Next Ocr quant should you choose?
Q4_K_M is the usual starting point for Next Ocr: it balances file size and quality well. Here it is a 5.0 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Next Ocr
How much VRAM does Next Ocr need?
About 6.7 GB at Q4_K_M with an 8K context window. That is the 5.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 Next Ocr on an 8 GB GPU?
Yes, with Q4_K_M: the 5.0 GB file needs about 6.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Next Ocr GGUF?
It depends on the quant: Q4_K_M is 5.0 GB.
What context length does Next Ocr support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 1.2 GB at 8K and 4.8 GB at 32K.
Where can I download Next Ocr GGUF?
The files are on Hugging Face in the Lamapi/next-ocr-Q4_K_M-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 Next Ocr 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 Next OCR on 8 GB VRAM?
Yes, the Q4_K_M quantized file requires about 6.7 GB of VRAM at 8 k context, fitting within an 8 GB GPU.
Does Next OCR support vision tasks beyond OCR?
No, it is specialized for OCR and does not include general vision capabilities.
What license applies to Next OCR?
The model is released under the apache‑2.0 license.