Document Retrieval-Aware Chunking (D-RAC): Universal Retrieval-Aware Ingestion of Enterprise Documents via PDF Normalization and Multimodal Markdown Conversion
Uday Allu, Abhivanth Sivaprakash, Pratik Singh, Aman Manocha
Yellow.ai
Published September 21, 2026 · on the feed September 22, 2026 · ▲ 65 · arXiv 2609.24220
The abstract
Retrieval-Augmented Generation (RAG) systems over enterprise knowledge bases must ingest heterogeneous document formats -- PDFs, Word documents, presentations, and scans -- whose content is locked inside complex visual layouts, multi-column pages, and dense tables. Rule-based extraction and OCR destroy reading order, flatten tables, and lose heading hierarchy, while fully agentic chunking over extracted text incurs high token costs and hallucination risk. We present Document Retrieval-Aware Chunking (D-RAC), an extension of our Web Retrieval-Aware Chunking (W-RAC) framework to arbitrary document formats. D-RAC first normalizes any input document into PDF, exploiting the fact that virtually every format has a faithful, deterministic PDF rendering. A single multimodal LLM pass then converts rendered pages into retrieval-optimized Markdown -- rewriting tables as self-contained prose statements and preserving heading hierarchy -- after which chunking proceeds exactly as in W-RAC: deterministic parsing into ID-addressable units followed by lightweight LLM-based chunk planning over identifiers rather than text. Source text is never regenerated during chunking, preserving W-RAC's cost, determinism, and observability benefits while unlocking every renderable format as a first-class input. On the 236-document, 795-page PDF subset of the RAG-Multi-Corpus benchmark spanning five enterprise domains, D-RAC converts and chunks the entire corpus in 72 minutes with zero errors, producing 1,748 retrieval-ready chunks. Compared to agentic chunking with frontier LLMs, D-RAC reduces chunking-stage output tokens by 95.7%, cutting chunking cost by 77.8% (GPT-4.1 pricing) to 85.6% (Gemini 2.5 Pro pricing) and chunking time by 75%. D-RAC scales linearly to documents of 500+ pages.
The Brief
3:04A short podcast summary of the paper. Written and voiced by AI.
Transcript
Document Retrieval-Aware Chunking (D-RAC). Universal Retrieval-Aware Ingestion of Enterprise Documents via PDF Normalization and Multimodal Markdown Conversion. By Uday Allu and three others, from Yellow dot A I. Published on the twenty-first of September. No code repository is linked to it.
A retrieval-augmented generation system over an enterprise knowledge base has to ingest whatever documents the enterprise holds: PDFs, Word documents, presentations, scans. Their content is locked inside complex visual layouts, pages with several columns, and dense tables. The usual tools each fail in their own way. Rule-based extraction and OCR destroy the reading order, flatten the tables, and lose the hierarchy of headings. Fully agentic chunking over the extracted text avoids some of that, but costs a great many tokens and carries a risk of hallucination.
Document Retrieval-Aware Chunking, D-RAC, extends the authors' earlier Web Retrieval-Aware Chunking framework, W-RAC, from web content to documents of any format. Its first move exploits a simple fact: virtually every format has a faithful, deterministic rendering as a PDF. So D-RAC first normalizes any input document into a PDF, and from that point every format looks the same.
A single pass of a multimodal LLM then converts the rendered pages into Markdown optimized for retrieval. Tables are rewritten as self-contained statements in prose, and the heading hierarchy is preserved.
From there, chunking proceeds exactly as in W-RAC. The Markdown is parsed deterministically into units that can each be addressed by an ID. A lightweight LLM then plans the chunks, working over those identifiers rather than over the text. Source text is never regenerated during chunking. That keeps the benefits W-RAC already had, in cost, determinism and observability, while opening every renderable format as a first-class input.
The test set is the PDF subset of the RAG-Multi-Corpus benchmark: two hundred and thirty-six documents, seven hundred and ninety-five pages, spanning five enterprise domains. D-RAC converts and chunks the whole corpus in seventy-two minutes with zero errors, producing one thousand seven hundred and forty-eight chunks ready for retrieval.
Against agentic chunking with frontier LLMs, D-RAC cuts output tokens at the chunking stage by ninety-five point seven percent. Chunking cost falls by seventy-seven point eight percent at GPT four point one pricing, and by eighty-five point six percent at Gemini two point five Pro pricing. Chunking time drops by seventy-five percent. And D-RAC scales linearly to documents of more than five hundred pages.
The savings trace back to one rule: during chunking, source text is never regenerated. The document is converted to Markdown in a single multimodal pass, and after that the model planning the chunks handles only identifiers, which is why the output tokens shrink so sharply against agentic chunking, where the text itself passes through the model. Normalizing everything to a PDF first is the other half. It is what lets one pipeline, built for the web, take in every format that can be rendered.
Paper Quest · 7 chapters · about 40 min
Play this paper
Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.
Chapter 1 🧩 · The problem
A company's knowledge is locked in messy files. Getting it out cleanly is the wall.
You build retrieval over a company's documents: PDFs, Word files, slides and scans, full of multi-column pages and dense tables.
The road ahead
- 1 · The problem ~7 min Company documents hide their structure in layouts, and both cheap extraction and costly model rewriting break down when you feed them to retrieval.
- 2 · What came before ~3 min
- 3 · The key idea ~8 min Render every format to PDF, convert its pages once with a multimodal model, then plan chunks by pointing at unit IDs instead of rewriting text.
- 4 · Choose your own research ~3 min
- 5 · Build the method ~8 min Four steps: render to PDF, convert pages to Markdown once, parse into ID-tagged units, and let a small model group the IDs into chunks.
- 6 · The experiment ~6 min You’ll guess: Compared to agentic chunking with frontier LLMs, by how much did this pipeline cut output tokens at the chunking stage?
- 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Free, with Google or an email address. Your stars and progress are kept.