We thank the reviewer for their feedback, which highlights our contributions in terms of benchmarking and methods along the concept of vision-based document retrieval first introduced in this work.
**(W1) Benchmark Samples:** Figure 3 (right) and Figure 6 illustrate two varied query-page pairs present in ViDoRe, and an additional document example is given in Figure 5. Furthermore, the modalities, thematics, and languages of our benchmark are detailed in Table 1 and provide a comprehensive understanding of the benchmark's scope. Note that the ViDoRe benchmark can be easily visualized using the HuggingFace dataset viewer, which we will link to in the final manuscript. Encouraged by the reviewer, we have added additional query-page illustrations in the appendix.
**(W2) Retrieval Candidate Space Clarification:** The retrieval candidate space for each ViDoRe subtask is explicitly defined in Table 1, detailing the language, number of queries, number of candidate documents and giving a brief modality and thematic overview of each of the subtasks.
**(W3) ColPali Model Details:** As indicated throughout the paper, ColPali produces multiple vector embeddings for each page and for each queries. As indicated in the reviewer’s summary, we leverage the Late Interaction operation to match the (N_q) multiple query vectors to the (N_d) document vectors to produce a scalar matching score. This operation is detailed in Sec 4.1 L284, illustrated in Figure 1, and mentioned throughout the paper. We believe clearing up this potential misunderstanding immediately explains all other remarks under this bullet point, as it should thus appear more clearly how document representations are generated (L280-283, Fig. 1, L378), to what correspond N_q and N_d (L284-288), and the fact neither <bos>, <eos>, nor pooling is necessary since all token embeddings are used. Pooling for the single-vector BiPali is detailed L363. We have clarified the notations (L286) and further re-explicited that all token embeddings are kept (L280). We note that our codebase is made fully available, and has since the paper’s release led to multiple successful replication attempts.
**(W4) Broader Evaluation:** The ViDoRe benchmark is already quite exhaustive, and it does in fact already include multiple popular publicly available datasets (DocVQA, InfoVQA, TAT-DQA, ArxivQA) (L194), in addition to several other custom tasks spanning various languages and modalities. The reviewer suggests using datasets from the VLM2Vec paper but they are partially redundant with ViDoRe - some of the most relevant subtasks are already included in our benchmark (InfoVQA, DocVQA) -, and the preprint was released one week after the ICLR deadline. As for MP-DocVQA, this dataset is an extension of DocVQA in which a few additional context pages are added to the correct gold page. This dataset is originally designed for multi-page VQA, and since we have repurposed DocVQA for retrieval and already consider 500 pages as potential candidates for each query, we believe this task to be redundant, hence why it is not included in the current version of ViDoRe.
We believe the 10 current ViDoRe subtasks that cover multiple languages (French, English), modalities (pure text, tables, figures, infographics, mixed-modality documents) and topics, are already a fairly diverse set of experiments and highly correlate with model performance. We acknowledge the VLM2Vec benchmarking efforts are complementary to the research direction introduced in this paper and have added a mention in the future work section.
**Questions**
**Page-Level Retrieval Capability:** As made clear thoughout the paper, yes, ColPali retrieves at a page-level granularity. DUDE is out of the scope of this work, as it is intended for multi-page QA and features multi-hop questions that necessitate multiple pages to be answered, as well as questions with no answers within the corpus. It is also largely similar to DocVQA which is already included in our benchmark. MP-DocVQA is mentioned in (W4).
**Text Retrieval Functionality:** ColPali generates embeddings for both text (using only a LLM) and images (by feeding soft tokens produced by a vision model to the LLM) in a shared embedding space. As a result, beyond text-to-image retrieval, it is natively capable of performing text-to-text retrieval (similar to ColBERT), as well as image to image matching. Although we are aware of successful efforts in this direction, benchmarking this is beyond the scope of this paper which focuses on text-to-document image retrieval, which we believe has the potential to truly transform current document RAG practices This is being confirmed by the significant enthusiasm we have observed from both the industrial and academic community since the release of our preprint.
We hope that under the light of our clarifications, the reviewer will reconsider their assessment of our paper and their score, and thank them once again for their review.