A useful PDF summary should explain what the document says without hiding its qualifications or inventing details. This guide shows a document-upload workflow, prompts you can adapt, and checks to make before trusting the result. Instructions are based on Microsoft documentation reviewed October 19, 2026; the examples below are suggested exercises, not reported hands-on test results.
How to summarize a PDF in Copilot
Open Microsoft Copilot and sign in if prompted. For an organization account, use the Copilot experience your workplace provides. If you are new to the interface, start with our Copilot beginner guide.
Select the plus (+) button and Add images or files, then choose the PDF. Wait for the attachment to appear before sending a prompt. Ask for a summary of that specific file, then refine the answer with follow-up questions in the same conversation. Microsoft lists PDF as supported and currently documents limits of 50 MB per file and 20 files per conversation. Source: Microsoft file-upload guidance.
First prompt: “Summarize the attached PDF in five bullets for someone who has not read it. Include the main purpose, key findings, recommendations and important limitations. Use only information in the attachment. If you cannot read part of it, say which part.”
Read the summary alongside the PDF. If an important section is missing, ask about that section by its heading. Avoid assuming that a fluent answer means every page was processed correctly.
Choose the kind of summary you actually need
For a quick reading decision, request the central argument and intended audience. For a meeting, request decisions and unanswered questions. For a research paper, keep methods, results and limitations separate. Giving the summary a job makes it easier to judge whether the answer is useful.
Executive brief: “Using this PDF only, write a 150-word brief for a project manager. Separate the problem, evidence, proposed action and unresolved risks. Do not turn suggestions into approved decisions.”
Action list: “Extract action items into a table with task, named owner and stated deadline. Write ‘not specified’ when the document gives no owner or date. Do not assign them yourself.”
Research overview: “Summarize the research question, method, sample, main results and limitations under separate headings. Distinguish the authors’ conclusions from your interpretation.”
Numbers check: “List the important quantities with their units, time periods and the section where each appears. Preserve ranges and uncertainty. Do not calculate missing values.”
A simple way to check the answer
Use a short, nonconfidential PDF for your first attempt. Before uploading it, write down three facts you can verify: one number, one conclusion and one limitation. Compare the generated summary with those facts. This gives you a concrete check rather than relying on how polished the writing sounds.
For example, imagine a report says a pilot involved 12 stores, sales rose 8% during the pilot, and seasonality was not controlled. A summary that claims the program caused an 8% increase across the whole business overstates the evidence. Ask Copilot to preserve both the pilot scope and the limitation. This is an illustrative example, not a result from a tested PDF.
Check names, dates, percentages and negative statements directly in the original. Ask for section headings or short supporting excerpts, but verify those too. Page numbering in a viewer may differ from the printed page numbers, so a page citation alone is not proof.
What if the PDF is scanned?
Try selecting and copying a sentence from the PDF. If you cannot select text, it may be an image-based scan, although that test is not conclusive. Blurry pages, rotated scans and complex layouts can make extraction less reliable. Do not assume every scanned PDF will work equally well in every Copilot experience.
If Copilot cannot read the content reliably, use an authorized OCR tool to create a searchable copy. OCR converts pictured text into machine-readable text. Check the OCR output for mistakes before summarizing, especially columns, decimal points and names. Keep the original available for comparison.
File uploaded, but the summary is poor
First ask Copilot to identify the document title and list its section headings. Compare those with the PDF. If they do not match, start a new conversation and attach the intended document again. For a long report, request section-by-section summaries, then ask for a combined overview that preserves conflicting findings.
If the upload itself fails, check file size and format first. Our Copilot upload troubleshooting guide covers that separate problem. A successful upload and an accurate summary are two different things.
Free access, work accounts and OneDrive
Do not buy a subscription solely because one document produces a weak summary. First check the file and the available features in your account. Our Copilot free versus paid guide explains the account distinctions.
OneDrive also has a separate Copilot file-summary workflow in eligible accounts. Microsoft describes selecting a supported file and choosing its Copilot summary action. That interface is different from attaching a local file in chat; follow the instructions for the product you are actually using. Source: Microsoft OneDrive guidance.
Before sharing the summary
Upload only documents you are authorized to share with the service and follow your organization’s data rules. Remove unnecessary personal information from a practice document. Keep the summary labeled as a summary, retain a link to the original, and review it before sending it to someone who will make a decision from it.