What GPU do I need to run nvidia/NVIDIA-Nemotron-Parse-v1.1?
957M parameters, published in F32. View on Hugging Face
Set up NVIDIA-Nemotron-Parse-v1.1NVIDIA-Nemotron-Parse-v1.1 is published by nvidia on Hugging Face, with 141,019 downloads and 171 likes to date. It's a NemotronParseForConditionalGeneration model built for image-text-to-text, published natively in F32.
VRAM required & cheapest live GPU fit
Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.
| Precision | Weight size | Required VRAM | Cheapest live fit | GPUs needed | Est. $/hr (full fit) |
|---|---|---|---|---|---|
| FP32 | 3.6 GB | 4.3 GB | V100 | 1 | $0.088/hr |
| FP8 (quantized) | 0.9 GB | 1.1 GB | RTX 4070 Super | 1 | $0.121/hr |
| INT4 (quantized) | 0.4 GB | 0.5 GB | RTX 4070 Super | 1 | $0.121/hr |
A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.
INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.
Cheapest way to run NVIDIA-Nemotron-Parse-v1.1 at its published (F32) precision: 1× V100, at $0.088/hr per GPU ($0.088/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
NVIDIA-Nemotron-Parse-v1.1: KV cache by context length
The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.
KV-cache size for NVIDIA-Nemotron-Parse-v1.1 is not published for this architecture, so no figure is shown.
NVIDIA-Nemotron-Parse-v1.1: common questions
How much VRAM does NVIDIA-Nemotron-Parse-v1.1 need?
4.3 GB at FP32, 1.1 GB at FP8 (quantized), 0.5 GB at INT4 (quantized). All of those sit under 6 GB, the smallest capacity this page reasons about, so VRAM is not what limits where this model runs. The 3.6 GB of weights plus inference overhead is the whole requirement.
Can NVIDIA-Nemotron-Parse-v1.1 run in 16-bit instead of FP32?
Yes. Its published weights are FP32, 3.6 GB, or 4.3 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 1.8 GB, or 2.1 GB with overhead. How much accuracy the cast costs is model-specific and is not measured here.
How many copies of NVIDIA-Nemotron-Parse-v1.1 fit on one V100?
3, by VRAM alone. That card carries 16.0 GB and one copy needs 4.3 GB at FP32, on a live rate of $0.088/hr for the whole card. Throughput is not modelled here, so 3 copies is not 3 times the requests served.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
Alternatives at this size
Other models for image-text-to-text within about a third of NVIDIA-Nemotron-Parse-v1.1's 957M parameters, from other model lines.
- Qwen3.5-0.8B (873M, BF16)
- GLM-OCR (1.3B, BF16)
- surya-ocr-2 (686M, BF16)
- GOT-OCR2_0 (716M, BF16)
- HunyuanOCR (1.1B, BF16)
More on NVIDIA-Nemotron-Parse-v1.1
Fits on an 8 GB GPU at FP32: every model that fits in 8 GB.
Best vision-language models: how NVIDIA-Nemotron-Parse-v1.1 ranks against the rest.
Best OCR and document parsing models: how NVIDIA-Nemotron-Parse-v1.1 ranks against the rest.
Related reading: V100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.
