Most people open a long PDF and start reading from page one. By page twelve they’ve lost the thread. By page twenty they’re skimming. By page forty they’re looking for a summary that doesn’t exist.

There’s a faster way. Claude — Anthropic’s AI assistant — can read a dense PDF alongside you and pull out exactly what you need in minutes, not hours. This is how I handle client reports, research papers, and technical documentation that I don’t have time to read cover to cover.

What Claude Can Actually Do With a PDF

Claude accepts PDF uploads directly in its interface (available on Claude.ai with a paid plan, or via the API). Once uploaded, you can ask it anything about the document:

• Summarise the entire document in plain language
• Extract every action item or recommendation
• Find specific data points: numbers, dates, names, decisions
• Compare two sections that contradict each other
• Rewrite the executive summary in plain English for a non-technical audience
• List every risk or caveat mentioned in the document

What makes Claude particularly useful for dense reports is that it reads the whole document before answering — it doesn’t just match keywords. Ask it “what are the three biggest risks mentioned in this report?” and it will synthesise across sections, not just quote the paragraph that contains the word “risk.”

Step 1: Prepare the PDF

Before uploading, a quick check saves time later.

Make sure the PDF is text-based, not scanned. Claude can read text embedded in a PDF; it cannot read a scanned image of a document (a photo of printed pages saved as PDF). To check: try selecting text in the PDF with your cursor. If you can highlight and copy individual words, it’s text-based. If your cursor turns into a crosshair and selects rectangles, it’s a scanned image — you’ll need to run it through OCR first (Adobe Acrobat has a free web tool; so does Smallpdf).

For very long documents (over 100 pages), consider splitting into sections if Claude hits its context limit. A 50-page financial report, a 60-page technical specification, or an 80-page research paper all typically fall within Claude’s context window without splitting.

Step 2: Upload and Set Context

In Claude.ai, click the paperclip icon in the chat input and upload your PDF. Then write your first message — and this is where most people underuse the tool.

Don’t just ask “summarise this.” Give Claude context about what you need and why:

• Your role: “I’m a project manager reviewing this vendor proposal”
• Your goal: “I need to brief my director in 10 minutes”
• What to emphasise: “Focus on pricing, delivery timelines, and any conditions or exclusions”

A prompt like “I’m reviewing this 45-page vendor proposal as a procurement manager. Summarise the key commercial terms, highlight any conditions or exclusions buried in the document, and flag anything that looks non-standard or risky.” will produce a dramatically more useful output than a one-word instruction.

Step 3: Use the Right Prompts for the Right Output

Different documents need different extraction strategies. Here are the prompts I use most often:

For a research paper or academic report:
“What is the main argument of this paper? What evidence does it use to support it? What are the limitations the authors acknowledge? What are the practical implications for someone working in [your field]?”

For a financial or business report:
“List every specific number, metric, or KPI mentioned. Identify any year-over-year changes. Flag any risks, caveats, or disclaimers. What decisions or recommendations does the report make?”

For a legal or compliance document:
“What are my obligations under this document? What are the deadlines? What happens if I don’t comply? Highlight any clauses that are unusually broad or that I should get a second opinion on.”

For a technical specification:
“List the system requirements. Identify any dependencies. What are the stated limitations? Are there any contradictions between sections?”

For meeting minutes or a transcript:
“List every action item, who it’s assigned to, and the deadline. List every decision made. List any open questions that weren’t resolved.”

Step 4: Follow Up to Go Deeper

Claude remembers the document for the entire conversation. After the initial extraction, you can drill down:

• “Can you find the exact page and quote where it mentions the penalty clause?”
• “You mentioned three risks — expand on the second one. What specifically does the document say about it?”
• “Rewrite the executive summary you gave me as a five-bullet briefing I can paste into a Slack message.”
• “Is there anything in section 4 that contradicts what section 2 says about the timeline?”

This back-and-forth is where Claude becomes genuinely more useful than a static summary tool. You can interrogate the document the way you’d interrogate a colleague who had read it thoroughly.

Real Example: A 50-Page Client Report

I recently used this on a 52-page market research report a client sent over. They needed a briefing for a board meeting in two hours.

First prompt: summarise the key findings and any strategic recommendations in plain language.
Second prompt: list every data point that supports or contradicts their current strategy.
Third prompt: rewrite the top three findings as a three-slide deck outline with one headline and two supporting bullets per slide.

Total time: 18 minutes. The briefing was more thorough than if I’d read the report myself under time pressure — because Claude doesn’t skim, doesn’t get tired, and doesn’t miss footnotes.

Limitations Worth Knowing

Claude is excellent at synthesis and explanation. It is less reliable for tasks that require absolute precision:

• Exact quotes: Claude sometimes paraphrases slightly when asked to quote. If you need verbatim text for a contract or legal matter, always verify against the original.
• Complex tables and charts: Data in image-based charts (bar graphs, pie charts) inside PDFs may not be read correctly. Text-based tables are fine.
• Very long documents over 200 pages: You may hit context limits. Split the document into logical sections and process each separately.

For most professional use cases — reports, proposals, research, specifications — these limitations rarely matter. The value is in rapid synthesis and structured extraction, not in replacing the source document.

The Workflow in Summary

Upload the PDF. Tell Claude who you are and what you need. Ask for the extraction that matches your use case. Follow up to drill down. Use the output to brief, decide, or delegate.

A document that would take 90 minutes to read carefully takes 10 minutes to extract what you actually need. For anyone who regularly receives long reports, proposals, or research documents, that’s a real and repeatable time saving — not a one-off trick.

Related reading

• Claude Pro vs ChatGPT Plus: A Decision Tree for Picking the Right $20
• How I Turn a Customer Sales Call Into a Case Study in Under an Hour Using Granola, Claude, and Notion
• How to Use ElevenLabs to Turn a Blog Post Into a Podcast Episode in One Hour