← Reddit

how to improve pdf reading skills and OCR

Reddit · lizabeans · August 2, 2026
A lawyer working with Claude reports challenges with OCR processing for scanned documents and maintaining context across documents longer than 100 pages. Token consumption and session cutoffs create workflow inefficiencies, requiring the creation of multiple fragmented chats and projects that do not retain information across sessions. The user seeks workflow optimization suggestions while operating on the Claude Pro plan with weekly usage between 60-80%.

Detailed Analysis

A Reddit thread in r/ClaudeAI surfaces a practical pain point that many legal and knowledge-work professionals encounter when using Claude for document-heavy workflows: the friction between scanned PDF OCR, long-document context limits, and Anthropic's usage-based session caps on the Pro plan. The original poster, a lawyer, describes a common workflow — uploading scanned petitions and case files into Claude via chat or Projects, asking for drafting help and document analysis — and running into two compounding problems. First, scanned PDFs require OCR processing before Claude can meaningfully parse them, which consumes significantly more tokens than text-native PDFs. Second, documents exceeding 100 pages strain context windows, forcing users to either lose continuity across multiple chats or lean on Anthropic's Projects feature to persist context, which itself becomes token-expensive at scale. With weekly usage already sitting at 60-80% of the Pro plan's allowance, the user hits session cutoffs before finishing complex, multi-session legal analysis.

This scenario is illustrative of a broader tension in how Claude and comparable LLM products are architected versus how real-world professional workflows actually operate. Legal, medical, and compliance work often involves large volumes of unstructured, scanned physical documents — meaning OCR quality and token efficiency aren't peripheral concerns but core determinants of whether an AI tool is usable at all. Claude's context window (up to 200K tokens on Claude 3.5/3.7 models, and larger on some enterprise tiers) is generous compared to many competitors, but OCR'd text from scanned documents is often noisier and more token-dense than clean digital text, meaning effective usable context shrinks in practice. Projects, Anthropic's feature for persisting files and instructions across conversations, helps with continuity but doesn't solve the fundamental problem that each new chat within a Project still re-processes context from scratch, consuming tokens repeatedly rather than genuinely "remembering" prior sessions in a stateful way.

The friction described here also highlights the gap between consumer-tier subscription plans (Pro, at $20/month) and the actual token throughput needed for professional-grade document analysis. Power users in fields like law routinely bump against Pro plan rate limits, which pushes many toward Claude's API access (pay-per-token, no weekly caps) or the higher Max tier, both of which offer more predictable scaling for heavy workloads but at meaningfully higher cost and technical complexity — a nontrivial hurdle for non-technical professionals. This is a recurring theme in AI adoption within regulated, document-intensive industries: the tools are powerful enough to meaningfully accelerate legal drafting and case analysis, but the packaging (context limits, session caps, OCR fidelity) hasn't fully caught up to how professionals actually work with hundreds of pages of scanned exhibits, deposition transcripts, and filings.

More broadly, this thread reflects an ongoing industry-wide challenge: as LLMs get marketed for "document intelligence" and enterprise use cases, the reality of ingesting messy, real-world inputs — scanned faxes, low-resolution court filings, multi-hundred-page discovery documents — remains a bottleneck distinct from raw model capability. Anthropic, along with OpenAI and Google, continues to expand context windows and improve multimodal document understanding (including native PDF vision capabilities that reduce reliance on separate OCR pipelines), but users without engineering resources still lack clear guidance on optimizing workflows — e.g., pre-processing PDFs with dedicated OCR tools before upload, chunking documents strategically, or using the API for cost-effective bulk processing. The gap between what's technically possible and what's accessible to a non-technical Pro-tier user underscores that usability and workflow tooling, not just raw model intelligence, remain a key frontier for AI companies targeting professional verticals like legal services.

Read original article →