Dots.Ocr needs about 1.9 GB of memory at Q4_K_M (a 1.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 11 quants, from 0.9 GB (Q3_K_S) to 3.6 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.9 GB.
Multilingual document layout parsing with a 1.78B vision‑language model
Dots.Ocr is a 1.78B‑parameter VLM based on Qwen2. It unifies layout detection, content recognition, and reading order in a single model. The model supports over 100 languages and outputs structured JSON with bounding boxes and formatted text.
Good at
- Document layout parsing
- Multilingual OCR
- Table and formula extraction
Limits
- No vision support in some quantizations
- Large VRAM needed for high‑quality quant
- License is MIT
Best for
- Academic paper parsing
- Financial report extraction
- Slide deck analysis
Who it’s for. Developers building document processing pipelines that need a single model for layout, OCR, and reading order. Researchers requiring multilingual document understanding with a compact foundation.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_S | 0.9 GB | 1.6 GB | Fits | Get file → | |
| Q3_K_M | 0.9 GB | 1.7 GB | Fits | Get file → | |
| Q3_K_L | 1.0 GB | 1.7 GB | Fits | Get file → | |
| Q4_K_S | 1.1 GB | 1.8 GB | Fits | Get file → | |
| Q4_K_M | 1.1 GB | 1.9 GB | Fits | Get file → | |
| Q5_K_S | 1.3 GB | 2.0 GB | Fits | Get file → | |
| Q5_K_M | 1.3 GB | 2.0 GB | Fits | Get file → | |
| Q6_K | 1.5 GB | 2.2 GB | Fits | Get file → | |
| Q8_0 | 1.9 GB | 2.6 GB | Fits | Get file → | |
| BF16 | 3.6 GB | 4.3 GB | Fits | Get file → | |
| F16 | 3.6 GB | 4.3 GB | Fits | Get file → |
For 8 GB VRAM, use Q4_K_S (file size 1.07 GB, estimated 1.8 GB memory). For 12 GB VRAM, Q5_K_M (1.29 GB, 2 GB memory) or Q6_K (1.46 GB, 2.2 GB memory). For 16 GB VRAM, Q8_0 (1.89 GB, 2.6 GB memory) or BF16 (3.56 GB, 4.3 GB memory).
What GPU do you need for Dots.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: the best quant that fits is Q8_0 (1.9 GB file, about 2.6 GB in use).
- 6 GB VRAM: the best quant that fits is BF16 (3.6 GB file, about 4.3 GB in use).
Which Dots.Ocr quant should you choose?
Q4_K_M is the usual starting point for Dots.Ocr: it balances file size and quality well. Here it is a 1.1 GB file.
The Q8_0 file is 1.9 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 Q3_K_S at 0.9 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 Dots.Ocr
How much VRAM does Dots.Ocr need?
About 1.9 GB at Q4_K_M with an 8K context window. That is the 1.1 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 Dots.Ocr on an 8 GB GPU?
Yes, with BF16: the 3.6 GB file needs about 4.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Dots.Ocr GGUF?
It depends on the quant: Q3_K_S is 0.9 GB, Q3_K_M is 0.9 GB, Q3_K_L is 1.0 GB, Q4_K_S is 1.1 GB, Q4_K_M is 1.1 GB, Q5_K_S is 1.3 GB and 5 more.
What context length does Dots.Ocr support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.9 GB at 32K.
Where can I download Dots.Ocr GGUF?
The files are on Hugging Face in the prithivMLmods/dots.ocr-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 Dots.Ocr use?
Hugging Face lists the license as mit. 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 Dots.Ocr on 8 GB VRAM?
Yes, using Q4_K_S or Q3_K_S quantizations, which require approximately 1.8 GB of VRAM at 8 k context.
Does Dots.Ocr support image input?
Yes, it is a vision‑language model and can process images for layout and OCR tasks.