NVIDIA Nemotron 3.5 Parse is a dedicated, downloadable roughly 631-million-parameter document image parser for OCR, reading order, semantic layout regions and bounding-box extraction. It is not the larger Nemotron 3.5 Bolt or Super VL conversational model. The first-party repository records an exact 40-character SHA, one recognized main Safetensors weight artifact and NVIDIA OpenMDW v1.1 licensing, checked by Open Model Weights on 20 October 2026. The source config declares 16,384 positional tokens, but this is not a validated capacity for arbitrary PDF documents. NVIDIA's published ParseBench scores are producer evaluations; OMW has not run this model or independently measured OCR accuracy, latency or VRAM.
WHY IT MATTERS
RAG ingestion usually fails before generation if document text, regions or reading order are extracted incorrectly. A purpose-built parser can support more inspectable downstream source chunks.
A 631M-class checkpoint creates a different hardware design space than enormous vision-language systems, but its actual deployment footprint must still be measured with the image encoder and page preprocessing.
MODEL-SELECTION VIEW
Strong fit when…
- Document ingestion that needs text plus layout coordinates, not only a natural-language summary of a page.
- Comparison against rule-based OCR and vision-language extraction on dense reports, tables, charts and forms.
- Teams building source-linked search indexes from page images with traceable region geometry.
Important considerations
- Bounding boxes require conversion from normalized coordinates to original page geometry, and table/chart semantics may need additional postprocessing.
- The supported OCR language list and publisher scores do not prove accuracy on handwriting, low-quality scans or unusually formatted documents.
- Custom inference code and tokenizer license attribution need independent review alongside OpenMDW model-weight rights.
What the parser actually returns
Nemotron 3.5 Parse focuses on recognizing document text and classifying visual page regions such as lines, charts or tables while retaining normalized bounding boxes and reading order. These are intermediate extraction artifacts intended for search indexing, content conversion or quality review, not direct answers to arbitrary user questions.
Applications must convert geometry into page pixels and decide how to combine regions, preserve headings and assign references. A coordinate rectangle does not itself prove that the text inside it is correctly recognized, and a page-level summary may hide errors that become important in downstream RAG.
Vision encoder, decoder and practical preprocessing
NVIDIA describes C-RADIOv4-SO400M for image encoding connected through a visual-sequence adapter to a ten-layer mBART decoder. Its instructions support dynamically shaped rectangular pages and task tokens that separate text extraction from layout regions. These details are operational contracts rather than interchangeable components of any generic vision chat pipeline.
Source-based inference examples cover Transformers and a specialized vLLM integration. Pin the documented code revision and processor behavior, including image resizing, language tokenization and coordinate normalization. The config's 16,384-token limit is a source field and not an independently tested promise for all document dimensions.
Charts, tables and reading-order accuracy
A page with columns, footnotes or overlapping graphical labels can be more difficult than a clean paragraph. Test region sequences and coordinate overlap directly, then reconstruct the desired reading order before indexing. Parsing failure can create apparently coherent but factually incomplete chunks if a chart label is separated from its legend.
For tables, check merged cells, column headers, numerical units and carry-over across pages. For charts, compare extracted labels and data points against the original image where postprocessing is required. Treat the parser as one component in an extraction pipeline rather than automatic proof of machine-readable truth.
What the NVIDIA benchmark numbers mean
NVIDIA's card reports ParseBench mean 75.20 and a chart-category score of 64.40. It also presents OCR evaluations such as IndicVisionBench and MOSCAR; the latter involves simpler synthetic text renderings. Each evaluation has its own input normalization, datasets and scoring method.
These are developer-produced results, not independently replicated Open Model Weights measurements. Do not compare the headline score with a different benchmark or claim uniform accuracy across scripts, handwriting, low-resolution scans or complex tables. Sample held-out documents from the deployment domain and compare against manually reviewed transcriptions.
Weights, licensing and complete hardware costs
The official repository includes a recognized Safetensors model artifact and an OpenMDW Agreement version 1.1 license file. NVIDIA additionally distinguishes MIT attribution for the tokenizer. Preserve these specific obligations; neither OpenMDW nor MIT for a component implies all associated inference libraries or model weights use the same terms.
The publisher describes roughly 631 million trainable parameters. Weight-only arithmetic does not include processor tensors, intermediate image features, activations or serving allocations, and can substantially underestimate memory under multi-page or concurrent workloads. Benchmark exact resolution, precision and batch sizes before promising local-device fit.
Using Parse safely as the start of a RAG pipeline
Use document-level source IDs and page coordinates when passing OCR output into a downstream embedding or reranking system. Keep original images for audit and retain extraction confidence or human corrections where available. The derived text must not be treated as a trusted instruction channel for an agent.
Our assessment: choose Parse when geometry-aware extraction is the bottleneck, the 8B Embed checkpoint when initial semantic document discovery is the bottleneck, and the distinct 8B Rerank checkpoint when the relevant evidence appears in the retrieved set but is ordered poorly. These three model roles are complementary, not substitutes.
IMPLEMENTATION & EVALUATION
How to evaluate Nemotron 3.5 Parse 631M before deployment
Practical source-grounded evaluation plan for the exact nvidia/Nemotron-3.5-Parse revision, not an Open Model Weights runtime or benchmark execution.
STEP 01Pin exact model, tokenizer and inference code
Check the official model SHA, processor, task tokens, OpenMDW and tokenizer attribution separately.
REPRODUCIBLE ACCEPTANCE TESTArchive the reproducible revision manifest and one representative page input with its recognized regions.
WHAT CAN GO WRONGAn unreviewed custom-code update can change output schemas or introduce parsing regressions.
STEP 02Create source-linked page extraction fixtures
Choose multi-column pages, chart labels, forms, tables, low-resolution scans and multilingual cases.
REPRODUCIBLE ACCEPTANCE TESTStore expected reading order, region geometry, original page image and human-reviewed text.
WHAT CAN GO WRONGA plausible OCR transcript can omit an entire page region without an obvious syntax error.
STEP 03Evaluate region and numeric fidelity
Measure text errors, missed bounding boxes, header association and table cell structure per document type.
REPRODUCIBLE ACCEPTANCE TESTTrack manually checked errors and stop deployment if important numeric or coordinate fields fail.
WHAT CAN GO WRONGPublisher benchmark aggregates cannot predict the accuracy of an unfamiliar report format.
STEP 04Monitor end-to-end RAG ingestion
Carry page IDs and original image references through chunking, embedding and access-control checks.
REPRODUCIBLE ACCEPTANCE TESTDemonstrate correct citations, private-document access rules, extraction fallbacks and revision rollback.
WHAT CAN GO WRONGA visually convincing generated answer can conceal an OCR error introduced many steps earlier.
Proposed tests, not OMW benchmark results. Read the official model card at the pinned source revision ↗ Inspect OMW field evidence ↗
FAQ
Questions people ask about Nemotron 3.5 Parse 631M.
Is Nemotron 3.5 Parse a general conversation model?
No. It is a specialist document image parser for OCR text, structural regions and coordinates; answering arbitrary user questions requires other components.
Can it read tables and charts?
NVIDIA documents chart and table-related outputs, but extracting reliable numeric structures can require postprocessing and manual checks on complex pages.
How many parameters does Parse have?
NVIDIA's model card identifies 630,800,496 trainable parameters, commonly described as 631 million. That count is not a measured runtime memory requirement.
How large is its context window?
The checked config contains 16,384 positional tokens; this should not be advertised as a tested capacity for any arbitrary number of PDF pages or image pixels.
Is Parse available for commercial use?
NVIDIA describes commercial and non-commercial uses subject to OpenMDW v1.1. Review the full weight agreement plus tokenizer and custom-runtime dependencies.
Were OCR benchmarks replicated independently?
No. ParseBench, MOSCAR and language-specific results currently cited on this page are publisher-reported; local-document error rates require a separate evaluation.