baidu.Qianfan OCR needs about 4.4 GB of memory at F16 (a 2.7 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 6 quants, from 1.8 GB (F16) to 4.7 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.8 GB.
baidu.Qianfan OCR is a 4.42B-parameter Qianfan model in GGUF format, quantized by DevQuasar. Its trained context length is 32K tokens. The repository has 6 quant files, from 1.8 GB (F16) to 4.7 GB (F16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| F16 | 1.8 GB | 3.5 GB | Fits | Get file → | |
| F16 | 2.2 GB | 4.0 GB | Fits | Get file → | |
| F16 | 2.7 GB | 4.4 GB | Fits | Get file → | |
| F16 | 3.2 GB | 4.9 GB | Fits | Get file → | |
| F16 | 3.6 GB | 5.3 GB | Fits | Get file → | |
| F16 | 4.7 GB | 6.4 GB | Fits | Get file → |
What GPU do you need for baidu.Qianfan 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 F16 (2.2 GB file, about 4.0 GB in use).
- 6 GB VRAM: the best quant that fits is F16 (3.6 GB file, about 5.3 GB in use).
- 8 GB VRAM: the best quant that fits is F16 (4.7 GB file, about 6.4 GB in use).
Which baidu.Qianfan OCR quant should you choose?
F16 (2.7 GB) is the middle option in this repository. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
If memory is tight, the smallest file is F16 at 1.8 GB, with the quality trade-offs that come with fewer bits. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about baidu.Qianfan OCR
How much VRAM does baidu.Qianfan OCR need?
About 4.4 GB at F16 with an 8K context window. That is the 2.7 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 baidu.Qianfan OCR on an 8 GB GPU?
Yes, with F16: the 4.7 GB file needs about 6.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of baidu.Qianfan OCR GGUF?
It depends on the quant: F16 is 1.8 GB, F16 is 2.2 GB, F16 is 2.7 GB, F16 is 3.2 GB, F16 is 3.6 GB, F16 is 4.7 GB.
What context length does baidu.Qianfan OCR support?
The GGUF header lists a trained context length of 32,768 tokens (32K). 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 baidu.Qianfan OCR GGUF?
The files are on Hugging Face in the DevQuasar/baidu.Qianfan-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 baidu.Qianfan 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.