Copilot Unable to Read PDF File: 6 Fixes That Actually Work

If Microsoft Copilot refuses to open your PDF and throws errors like “The file appears to be empty, corrupted, or in a format I can’t read,” you are dealing with a known issue that affects both the desktop app and the web version. This guide walks you through every working fix so you can get Copilot reading your PDFs again.

Copilot Unable to Read PDF File

Why Copilot Cannot Read Your PDF

On Windows 11, Copilot does not work as a standalone PDF reader. It relies on the Microsoft Edge WebView2 Runtime to extract text from documents. When that runtime is outdated or corrupted, Copilot fails to read even healthy PDFs. Beyond the runtime, three other common causes trigger this error:

  • Image-based or scanned PDFs contain no selectable text. Copilot cannot extract content it cannot see as text, even if the visual looks fine.
  • Encrypted or password-protected PDFs block access at the file level before Copilot can even attempt to read them.
  • Corrupted files or incomplete uploads cause Copilot to report the file as empty even when it opens normally in a PDF viewer.
  • SharePoint Restricted Search settings or missing Copilot license permissions block file access for agent-based setups.

Fix 1: Check Whether Your PDF Contains Selectable Text

The most common reason Copilot fails silently is that the PDF holds scanned images of pages rather than actual text. Copilot Chat in Microsoft 365 sometimes handles these files, but the desktop app and Agent Builder almost always fail with image-only PDFs.

Steps to verify:

  1. Open the PDF in Microsoft Edge by right-clicking the file and selecting Open with > Microsoft Edge.
  2. Try to click and drag to select a word on the page.
  3. If nothing highlights, the PDF is image-based and needs OCR processing before Copilot can use it.
  4. If text highlights normally, the file itself is fine and the problem lies elsewhere.

How to fix an image-based PDF:

  • Run the file through an OCR tool such as Adobe Acrobat, Microsoft Lens, or a free online OCR service to produce a text-searchable version.
  • Alternatively, convert the content to .docx, .txt, or .html format, all of which Copilot handles reliably.

Fix 2: Remove PDF Encryption or Sensitivity Labels

Copilot cannot open password-protected PDFs or files tagged with sensitivity labels like “Confidential” or “Restricted.” The encryption prevents the WebView2 engine from reading the file content at all.

Steps:

  1. Open the PDF in Adobe Acrobat or another PDF editor.
  2. Go to File > Properties > Security and check whether any password protection or permissions restrictions are applied.
  3. Remove the encryption and save an unprotected copy.
  4. If your organization applies Microsoft Information Protection (MIP) sensitivity labels, contact your IT admin to adjust the label or export a version without restrictions.
  5. Upload the unprotected copy to Copilot and try again.

Fix 3: Re-Upload the File to OneDrive

A failed or partial upload to OneDrive causes Copilot to report the file as empty or corrupted, even when the original file on your device is completely healthy. Drag-and-drop into the Copilot chat interface is also unreliable in some app versions and can silently fail.

Steps:

  1. Open OneDrive in your browser.
  2. Locate the problematic PDF and delete it.
  3. Re-upload the file using the Upload button rather than drag-and-drop.
  4. Wait for the upload to complete fully, then try opening it in Copilot using the file picker button inside the chat input, not by dragging.

Fix 4: Update Microsoft Edge and the Copilot App

An outdated Edge browser carries unfixed PDF parsing bugs that directly affect Copilot’s ability to read files. Similarly, an outdated Copilot app may fail to hand off the file correctly to the underlying engine.

Update Microsoft Edge:

  1. Open Microsoft Edge.
  2. Click the three-dot menu at the top right.
  3. Go to Settings > About Microsoft Edge.
  4. Edge automatically checks for updates and installs them. Wait for the process to finish.
  5. Restart Edge after the update completes.

Update the Copilot app:

  1. Open the Microsoft Store.
  2. Click Library in the left sidebar.
  3. Find Microsoft Copilot in the list and click Update if one is available.
  4. Restart your PC after updating.

Fix 5: Reset the Copilot App

Copilot builds up a local cache of settings and temporary data over time. After system updates or extended use, this cache can become corrupted and interfere with how the app handles file attachments. Resetting the app clears that state completely without affecting your Microsoft account or data.

Steps:

  1. Press Win + I to open Settings.
  2. Go to Apps > Installed apps.
  3. Search for Copilot in the list.
  4. Click the three-dot menu next to it and select Advanced options.
  5. Scroll down and click Reset, then confirm.
  6. Relaunch Copilot and test with your PDF.

Fix 6: Update the WebView2 Runtime

Because Copilot depends on the Microsoft Edge WebView2 Runtime to parse and render PDFs, an outdated runtime is a direct cause of reading failures. Updating or repairing it often resolves errors that persist even after updating Edge itself.

Repair the runtime:

  1. Press Win + I and go to Apps > Installed apps.
  2. Search for Microsoft Edge WebView2 Runtime.
  3. Click the three-dot menu and select Modify.
  4. Choose Repair and let the process complete.

Update via Windows Terminal:

  1. Open Windows Terminal or Command Prompt as Administrator.
  2. Run the following command: winget upgrade Microsoft.EdgeWebView2
  3. Wait for the upgrade to finish, then restart your PC.

Bonus step: If the PDF still fails to load after updating the runtime, temporarily set Microsoft Edge as your default PDF viewer. Go to Settings > Apps > Default apps, search for .pdf, and assign Edge as the handler. This removes any interference from third-party PDF readers that may be blocking Copilot’s engine. You can revert this setting afterward.

Quick Bypass: Use Copilot on the Web

If none of the above fixes resolve the issue immediately and you need results now, the web version of Copilot at copilot.microsoft.com processes PDFs through your browser’s own engine rather than the local app. This sidesteps the WebView2 dependency entirely.

  1. Open your browser and go to copilot.microsoft.com.
  2. Sign in with your Microsoft account.
  3. Click the attachment icon in the chat input and upload your PDF.

If Copilot reads the file here but not in the desktop app, the problem is with your local installation rather than the file itself, and the fixes above will address it.

For Copilot Agent Builder: Additional Checks

If you are building an agent with Copilot Studio Agent Builder and pointing it at a SharePoint folder full of PDFs, the fixes above still apply, but two additional settings control whether the agent can access the files at all.

Check Restricted SharePoint Search:

Restricted SharePoint Search blocks agents from using any SharePoint location as a knowledge source, regardless of file format or permissions. If this setting is enabled in your tenant, the agent reads only from the title metadata rather than the actual file content. Verify and disable this setting in your SharePoint admin center.

Verify Copilot permissions:

Confirm that Copilot has the correct access rights to the SharePoint folder and that the files are marked as available for knowledge ingestion. Even correctly formatted, text-based PDFs fail to load if the permission chain is broken.

Related Guides

Copilot’s inability to read PDF files usually traces back to one of four causes: image-based PDFs without OCR, file encryption, a corrupted WebView2 runtime, or incomplete uploads. Work through the fixes in order, starting with checking your PDF for selectable text, since that alone resolves most cases. If the problem appeared suddenly across all files without any change on your end, check for an outage via the Microsoft 365 Service Status page and submit feedback through Copilot > Send Feedback > Report a problem so the engineering team can investigate.

Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

    Leave a Reply