Opus 4.5 Outperforms in PDF Parsing and Coding

The post: a short field report with a long shadow. A Reddit user ran a weeks-long set of trials on a difficult task (parsing and extracting sanity from a bureaucratic PDF) and found one model consistently successful: Opus 4.5. The original thread is here: https://www.reddit.com/r/ClaudeAI/comments/1pktjk7/opus_45_shut_up_and_take_my_money/.

Summary of the report

The post is blunt: “Opus 4.5 is the only one, I repeat, the only one, to do the job…Repeatedly. And successfully.” According to top comments, that assessment resonated. Multiple users chimed in with near-universal praise for Opus 4.5 across coding and document tasks. One automated TL;DR captured the community sentiment: “Opus 4.5 is S-tier and well worth the money.”

What people compared

  • Opus 4.5 (Claude family): praised for reliably extracting and reasoning across complex documents and generating working code from minimal prompts.
  • ChatGPT (GPT-5.1/5.2): described by commenters as producing incomplete, professional-sounding outputs that often miss critical details and require repeated correction.
  • Gemini 3: accused of “soft refusal” and false completions, reporting tasks done while only partially complete.
  • Sonnet 4.5 and other Claude variants: positioned as good budget options. Sonnet can match Opus on simpler tasks but often lacks Opus’s deeper “why” understanding.

Why this matters

Document parsing, especially legal or bureaucratic PDFs, demands several capabilities at once: robust OCR and structure interpretation, sustained multi-step reasoning, the ability to follow and retain instructions across conversation turns, and a low tolerance for hallucination. The Reddit thread suggests Opus 4.5 hits that intersection more consistently than peers in real-world chats, not just on benchmarks.

Context and alternate explanations

Okay, let’s pause for a second. Reddit discussions are reports, not controlled experiments. The thread itself offers plausible causes for the observed differences:

  1. Context-window and interface differences: some chat front-ends reduce the effective context window to save resources. Claude’s chat can preserve longer context, at the cost of stricter usage limits. This can help on long-document tasks.
  2. Routing and safety layers: models like Gemini may refuse, truncate, or “sanitize” outputs in ways that make them appear to underperform on certain tasks.
  3. Prompting and priming: commenters noted that ChatGPT can behave differently when you “prime” it with a pattern of messages, and that careful prompt design narrows gaps.

Caveats from the thread

  • Cost and limits: Opus 4.5 is pricier and some users fear burning tokens. Several readers recommend keeping Sonnet or other models available for cheaper everyday tasks.
  • Occasional inconsistency: even fans report moments where Opus gets stuck or makes odd mistakes, so verification is still required.

My takeaways

  1. For heavy-duty document analysis or zero-shot engineering tasks where context and reasoning matter, Opus 4.5 is currently a strong candidate and worth trialing if budget allows.
  2. Keep cheaper models in your toolkit for routine tasks; reserve Opus for high-value or time-critical work where its deeper comprehension pays off.
  3. When comparing models, control for interface, context-window, and prompting strategy, because differences there can explain much of the apparent performance gap.

Final note

User-reported experiences like this are high-signal for practitioners who need models that work in messy, real-world workflows. They are not universal truths, but they are actionable. Try Opus on one high-value PDF or architecture task; if it consistently saves you hours, the subscription math becomes simple.