Can DeepSeek OCR run on the H100 PCIe?
Yes. At 8K context the best fit is F16, using about 6.6 GB of the 76.0 GB usable on the H100 PCIe. Estimated speed ceiling: ~995 tokens/sec.
Memory by quant and context
| Quant | 4K ctx | 8K ctx | Max tok/s (est., 8K) |
|---|---|---|---|
| 2-bit (Q2_K) | 2.0 GB Fits | 2.3 GB Fits | 4674 |
| 3-bit (Q3_K_M) | 2.4 GB Fits | 2.6 GB Fits | 3586 |
| 4-bit (Q4_K_M) • | 2.7 GB Fits | 2.9 GB Fits | 2998 |
| 5-bit (Q5_K_M) | 3.1 GB Fits | 3.3 GB Fits | 2460 |
| 6-bit (Q6_K) | 3.4 GB Fits | 3.7 GB Fits | 2138 |
| 8-bit (Q8_0) • | 3.8 GB Fits | 4.0 GB Fits | 1871 |
| 16-bit (F16/BF16) • | 6.4 GB Fits | 6.6 GB Fits | 995 |
• real GGUF file size from sabafallah/DeepSeek-OCR-GGUF. Speed is a bandwidth ceiling (2000 GB/s), not a benchmark. Methodology.
More
DeepSeek OCR on every GPU and Mac · Every model that runs on the H100 PCIe · Other models that fit 64 GB VRAM · Try other settings in the calculator
Data: Hugging Face Hub (deepseek-ai/DeepSeek-OCR), NVIDIA specs. Data as of 2026-11-17.