MiniCPM OCR 1.0 needs about 1.4 GB of memory at Q4_K_M (a 0.5 GB file) with an 8K context window, so it fits on a 4 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 1.6 GB.
MiniCPM OCR 1.0 – a compact OCR and reasoning model
MiniCPM OCR 1.0 is a 0.752 billion‑parameter model based on the qwen35 architecture. It supports reasoning, tools, and vision tasks. The model is released under the Apache‑2.0 license.
Good at
- OCR and text extraction
- Reasoning with tools
- Vision‑based queries
Limits
- Requires 1.4 GB VRAM at 8 k context
- No dedicated vision hardware required
- License is Apache‑2.0
Best for
- Document OCR in low‑resource environments
- Chatbots needing image understanding
- Embedded vision applications
Who it’s for. Developers building lightweight OCR or vision‑enabled assistants who need a small, open‑source model. The model is suitable for edge devices with limited VRAM.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.5 GB | 1.4 GB | Fits | Get file → |
The only available quant is Q4_K_M, 0.53 GB in size. It needs about 1.4 GB VRAM at 8 k context. This is suitable for systems with 4–8 GB VRAM. For larger contexts, memory usage will increase proportionally.
What GPU do you need for MiniCPM OCR 1.0?
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 Q4_K_M (0.5 GB file, about 1.4 GB in use).
Which MiniCPM OCR 1.0 quant should you choose?
Q4_K_M is the usual starting point for MiniCPM OCR 1.0: it balances file size and quality well. Here it is a 0.5 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about MiniCPM OCR 1.0
How much VRAM does MiniCPM OCR 1.0 need?
About 1.4 GB at Q4_K_M with an 8K context window. That is the 0.5 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 MiniCPM OCR 1.0 on an 8 GB GPU?
Yes, with Q4_K_M: the 0.5 GB file needs about 1.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of MiniCPM OCR 1.0 GGUF?
It depends on the quant: Q4_K_M is 0.5 GB.
What context length does MiniCPM OCR 1.0 support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.6 GB at 32K.
Where can I download MiniCPM OCR 1.0 GGUF?
The files are on Hugging Face in the weareapexcreators/MiniCPM-OCR-1.0-LocalAI repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does MiniCPM OCR 1.0 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 MiniCPM OCR 1.0 on 4 GB VRAM?
The Q4_K_M quant requires approximately 1.4 GB VRAM at 8 k context, so 4 GB VRAM is sufficient for typical use.
Does the model support image input?
Yes, the model has vision capabilities and can process images for OCR tasks.
Is the model open source?
It is released under the Apache‑2.0 license, making it free to use and modify.