---
type: "post"
id: "dr-pixel-open-source-deep-research-agent-that-74e244"
slug: "dr-pixel-open-source-deep-research-agent-that-74e244"
title: "DR Pixel: open-source deep research agent that retrieves and reasons over rendered page images instead of OCR text"
description: "DR Pixel is an open-source deep-research agent that retrieves rendered document pages and reasons over page images rather than converting papers into OCR text first."
retrieval_nugget: "DR Pixel is an open-source deep-research agent that retrieves rendered document pages and reasons over page images rather than converting papers into OCR text first. Its authors report stronger benchmark performance than OCR-based baselines with fewer tool calls, offering teams a testable alternative for research workflows over visually dense PDFs."
published_at: "2026-11-04"
updated_at: "2026-11-04"
record_date: "2026-11-04"
date_kind: "published_at"
topics: ["agents","retrieval","multimodal"]
entities: ["DR Pixel","DRPixelBench","GPT-5.4","Gemini-3.5-Flash","Qwen3.6-27B","ViDoRe-V3","arXiv"]
related_patterns: []
novelty_label: "new_fact"
what_changed: "DR Pixel adds an open-source research agent that retrieves and reasons directly over rendered page images, with a 1.06M-page corpus and benchmark gains; prior coverage addressed image-based PDF search and OCR retrieval."
prior_refs: []
source_url: "https://arxiv.org/abs/2611.03097"
source_urls: ["https://arxiv.org/abs/2611.03097"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:dr-pixel-open-source-deep-research-agent-that-74e244"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/dr-pixel-open-source-deep-research-agent-that-74e244/","markdown":"https://newruntime.com/posts/dr-pixel-open-source-deep-research-agent-that-74e244.md","json":"https://newruntime.com/posts/dr-pixel-open-source-deep-research-agent-that-74e244.json"}
related_shifts: ["document-processing-shifts-from-hand-crafted-ocr-pipelines-to-llm"]
markdown_url: "https://newruntime.com/posts/dr-pixel-open-source-deep-research-agent-that-74e244.md"
---

# DR Pixel: open-source deep research agent that retrieves and reasons over rendered page images instead of OCR text

## Retrieval answer

DR Pixel is an open-source deep-research agent that retrieves rendered document pages and reasons over page images rather than converting papers into OCR text first. Its authors report stronger benchmark performance than OCR-based baselines with fewer tool calls, offering teams a testable alternative for research workflows over visually dense PDFs.

## Summary
DR Pixel is an open-source deep-research agent that retrieves rendered document pages and reasons over page images rather than converting papers into OCR text first. Its authors report stronger benchmark performance than OCR-based baselines with fewer tool calls, offering teams a testable alternative for research workflows over visually dense PDFs.

## What happened
“DR Pixel: Page-Native Deep Research with Vision-Language Models” was submitted to arXiv on November 2, 2026. The authors—Tiansheng Hu, Yichuan Wang, James V. Talwar, Nicholas Tomlin, Chen Zhao and Sewon Min—present DR Pixel as an open-source, end-to-end multimodal deep-research agent. Its central architectural choice is to use rendered page images as both the retrieval and reasoning unit. Rather than extract a document into OCR text, split that text into chunks, and retrieve chunks, the agent searches for pages and lets a vision-language model inspect the visual page directly.

The work focuses on scientific papers, where relevant evidence can reside in prose but also in tables, charts, equations and page layout. The authors say DR Pixel operates over a corpus of 1.06 million pages. The supplied discovery material further describes that corpus as 99,055 papers indexed with Qwen3-VL-Embedding-8B, although the primary abstract only establishes the page count. The distinction matters: the paper’s main claim concerns the value of retaining pages as visual evidence, not merely the choice of embedding model.

To evaluate the approach, the authors introduce DRPixelBench, a benchmark of questions over scientific papers that require reasoning across text, figures, tables and equations. The abstract says page-native research outperforms OCR-based baselines across GPT-5.4, Gemini-3.5-Flash and Qwen3.6-27B without additional training, while requiring fewer tool calls. The supplied discovery summary gives a more precise estimate: 5.1 to 5.6 points better than OCR pipelines and 20 to 30% fewer tool calls. Those figures are consistent with the supplied material, but the available primary-source excerpt does not provide the full score tables or evaluation protocol.

The paper also studies training an agent for this setting. The authors argue that teacher trajectories used in agentic supervised fine-tuning can contain both useful actions and redundant or failed attempts. Their proposed counterfactual credit reweighting assigns weight to each reasoning or action step based on its counterfactual contribution to the final answer. They report roughly a 15-point gain in retrieval recall and more than a 10-point gain in final accuracy on DRPixelBench, along with gains over an untrained baseline on four existing benchmarks. On out-of-distribution ViDoRe-V3, the paper says DR Pixel comes within 1.8 points of an oracle given the gold pages directly.

The source does not describe a hosted product, a price, API limits, hardware requirements, deployment instructions, or licensing terms. It calls the system open source, but the supplied primary excerpt does not include a repository URL. This is therefore a research release and an architectural result, not evidence of a production service that teams can adopt without further validation.

## What the archive adds
We have not covered this before; it opens a new thread.

## Trend signal
No supplied pattern genuinely fits this page-native retrieval result closely enough to support a pattern claim.

## Why it matters
Most document-research systems make text the canonical representation early in the pipeline. That is convenient for search infrastructure, but it can flatten information whose meaning depends on spatial relationships. A table may lose row and column associations, a chart may separate from its legend, and equations can be damaged or ambiguously represented by extraction. Scientific PDFs make those weaknesses unusually visible, which is why this is a useful result even before it is a general product story.

DR Pixel proposes retaining the page as an evidence object. For a team building a research assistant, that suggests a concrete comparison: evaluate an OCR-and-chunk pipeline against retrieval over rendered pages on questions that require tables, figures, citations or mathematical notation. Fewer tool calls could also matter operationally, because agent cost and latency often accumulate through repeated searching and inspection rather than answer generation alone.

That does not mean OCR should be discarded. OCR supports accessibility, text search, editing and workflows where visual layout is not important. Image retrieval and vision-language inference can introduce their own latency and cost. The practical implication is narrower: teams should not assume that text extraction is always the best lossless representation for document research.

## What happens next
- **Research-agent builders will publish more direct comparisons of OCR and page-image retrieval on multimodal document questions.** (6 months, 65%). Watch for: evaluations that report accuracy, tool calls, latency and inference cost on the same corpus.
- **Production document systems will retain hybrid pipelines rather than fully replace OCR with page images.** (12 months, 70%). Watch for: systems that use text for broad recall and page images for evidence verification.

## Limits and uncertainty
This is an arXiv submission, not a peer-reviewed publication or an independent replication. The available source establishes reported benchmark outcomes, but not their statistical uncertainty, detailed baseline configuration, inference cost, latency, rendering setup, or reproducibility under a production workload. It also does not show that the approach is better for contracts, invoices, low-quality scans, multilingual files, or documents where text alone captures the relevant evidence.

The paper’s results concern scientific-paper research and a benchmark designed for mixed visual and textual evidence. Its conclusion that OCR-then-retrieve can be unnecessary or suboptimal should be read in that context. Open-source status likewise does not establish maintenance quality, security, licensing suitability, or an operational deployment path.

## Skill to build now
Create a small evaluation set from documents your team already researches: include questions answerable only from a table, chart, page layout or equation, alongside ordinary text questions. Run your current OCR-and-chunk pipeline and a page-image retrieval prototype against the same set. Record evidence accuracy, number of retrieval actions, latency and cost per completed answer. That comparison will reveal whether visual pages contain material your present representation is losing.

## Reader takeaway
DR Pixel is evidence that rendered pages can be a stronger retrieval-and-reasoning unit than OCR text for complex scientific documents. The result is promising for builders of research agents, but it is not yet proof that production OCR pipelines should be replaced. Test the trade-off on document types and questions that matter to your team.

## Open question
Can page-native retrieval retain its reported accuracy advantage on real enterprise document collections while meeting acceptable cost, latency and auditability requirements?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Agents](https://newruntime.com/topics/agents.md): Explore the agents topic hub.
- topic hub: [Retrieval](https://newruntime.com/topics/retrieval.md): Explore the retrieval topic hub.
- topic hub: [Multimodal](https://newruntime.com/topics/multimodal.md): Explore the multimodal topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)