Skip to main content

Why won’t my PDF open?

A PDF usually fails to open because the file is incomplete or damaged, the browser has not downloaded it correctly, or the selected PDF reader cannot process it. Start by saving the PDF to your device and opening it in a different reader; this separates a file problem from the browser, app and device-specific issues covered in the wider opening and viewing problems section. A password request is different from corruption: it means the document is protected and requires the correct credentials.

Where the PDF opening process can fail

Read Parse Decrypt Decode Display Valid PDF opens normally Truncated corrupt structure Password needs a key Unsupported file is fine, app can’t decode
“Won’t open” can fail at different stages — a broken structure, a missing password, or a viewer that can’t decode a perfectly valid file — and the stage tells you the fix.

Opening a PDF is not a single action. The file must first reach your device intact, the operating system must send it to a suitable application, and that application must interpret the PDF’s internal structure. A failure at any one of those stages can produce the same visible result: nothing opens.

The most useful distinction is whether the failure follows the file or stays with the browser, reader or device. If one PDF fails everywhere while other PDFs work, suspect that file. If several valid PDFs fail in one application but open elsewhere, suspect the application or its settings.

The downloaded file is incomplete, damaged or not really a PDF

A .pdf filename does not by itself prove that the file contains valid PDF data. A website, email system or person can give the wrong extension to another file type. A download can also stop early, leaving only part of the original document on your device.

A complete PDF has an internal structure that tells a reader where its objects, pages and other document data are stored. If a transfer cuts off part of that structure, the reader may report that the file is damaged, unsupported or unreadable. It may also appear to start opening before producing an error.

Signs that point to the file include:

  • The same PDF fails in a browser, a desktop reader and another device.
  • A newly downloaded copy has a different file size from the copy provided by the sender.
  • The file is 0 KB, which means it contains no document data.
  • The download ended unexpectedly or the connection was interrupted.
  • The sender cannot open their own copy.
  • The reader reports that the file type is unsupported or the document is damaged.
  • The file was recovered from failing storage or taken from an incomplete email attachment.

A damaged PDF generally cannot be restored just by renaming it or changing its default application. The reliable solution is usually to obtain another copy or ask the document owner to recreate it from the original source.

The website or browser has not delivered the usable file

When you click a PDF link, the browser may display the document in a built-in viewer, download it, hand it to another application or show an intermediate sign-in page. This creates several failure points before a PDF reader even sees the document.

For example, an expired session may return a web page instead of the requested PDF. The downloaded item can still have a .pdf filename even though its contents are a login or error response. A website may also have a broken link, a server problem or access rules that prevent the full file from downloading.

Browser symptoms often include:

  • The PDF works after you download it but not inside the browser tab.
  • The link fails in one browser but works in another.
  • The tab stays blank, displays a loading spinner or repeatedly downloads the file.
  • A local PDF opens in the browser, but the PDF on one particular website does not.
  • Opening the link in a private window or after signing in again changes the result.
  • The file opens after you use Save link as rather than clicking the link normally.

Browser PDF viewers support most ordinary documents, but a PDF with unusual content may render incorrectly or fail in one viewer while opening in a full desktop reader. If the document works after being saved locally, the original file is probably usable and the problem lies in browser display, website delivery or the handoff between the browser and another app.

The PDF reader or file association is failing

Your device needs an application capable of interpreting PDF files. Modern browsers, dedicated readers and many operating systems include this ability, but the application selected by default may be outdated, damaged or incorrectly associated with .pdf files.

A reader problem is more likely when several unrelated PDFs fail in the same application. The application might not start, it may crash immediately, or the operating system may report that no app is available to open the file. On Windows and macOS, you can test this without changing the permanent default by choosing Open with and selecting another reader.

Reader-specific failures can result from:

  • An outdated application that needs its current updates.
  • A damaged or incomplete reader installation.
  • An incorrect default application for .pdf files.
  • A browser extension interfering with the built-in PDF viewer.
  • A security product or third-party plug-in conflicting with the reader.
  • A document feature that one viewer does not support correctly.
  • Insufficient free storage or memory on the device.

If a different reader opens the same file, the PDF is not necessarily corrupt. The first reader may simply be unable to process that document or may need to be updated, repaired or reset.

Security or access controls are stopping the document

A PDF can be valid but intentionally unavailable to you. A document-open password prevents anyone without that password from viewing the contents. Organization-managed files may also require a particular account, permission or approved application.

A password prompt is evidence that the reader has recognized the file well enough to identify its protection. Entering random passwords, renaming the file or moving it to another folder will not remove that protection. Request the document-open password from the owner through a secure channel.

How to identify which failure applies to your PDF

Use controlled tests instead of changing several settings at once. Each test should answer one question: is the problem attached to the file, the website, the reader or this particular device?

Test Result What it indicates
Open a different, known-good PDF in the same reader The other PDF opens The original file or its download is the likely problem
Open a different, known-good PDF in the same reader The other PDF also fails The reader, device or file association is the likely problem
Save the failing PDF locally and open the saved copy The saved copy opens The browser’s inline viewer or website handoff is failing
Open the same file in another reader It opens The first reader or its configuration is failing
Open the same file on another device It still fails The file is probably incomplete, damaged or inaccessible
Download the file again The new copy opens The first download was incomplete or altered
Ask the sender to open their original copy Their copy also fails The source document needs to be recreated
The reader requests a password The prompt appears consistently The PDF is protected, not necessarily damaged

Check the simplest evidence before reinstalling software. Look at the filename and file size, confirm that the download has finished, and make sure you are opening the downloaded document rather than a temporary preview or web shortcut. If the attachment came from email or cloud storage, save it to a normal local folder before testing it.

Next, open another PDF that you know works. Use a document from a trusted source rather than another attachment from the same message or website. If both documents fail, the shared factor is probably the application or device. If only the original fails, concentrate on the file and how it was delivered.

Then try the problem file in one alternative viewer. This is a diagnostic test, not a reason to install many applications. A browser and a dedicated PDF reader are usually enough to reveal whether the failure is viewer-specific.

Pay attention to the exact result:

  • “File is damaged” or “unsupported file type” points toward invalid, incomplete or non-PDF data.
  • A password prompt points toward document security.
  • “Access denied” or a sign-in page points toward permissions, an expired session or security controls.
  • No app is associated with this file points toward an operating-system setting.
  • The app crashes with several PDFs points toward the installation, a plug-in or a software conflict.
  • The browser tab fails but the local copy opens points toward browser display or website delivery.
  • The file opens but shows an empty page is a viewing or rendering symptom rather than a complete opening failure.

On a phone or tablet, repeat the same logic before assuming the operating system is incompatible. Save the PDF, confirm that it appears in the device’s file manager, and try opening it from there. If the file works on a computer but not on one mobile device, continue with the guidance for that operating system rather than attempting to repair the document.

Fix the file, browser or reader identified by the tests

Apply the fix to the stage that failed. Repeatedly downloading a damaged source file will not repair it, while reinstalling a reader will not fix an expired website session. Keep an untouched copy of the original document until you know which action is necessary.

Replace an incomplete or damaged PDF

Download the PDF again from the original source and allow the transfer to finish before opening it. If possible, use a stable connection and save the new copy under a different filename so that you do not accidentally retest the earlier incomplete file.

If the PDF arrived as an attachment, ask the sender to compare the attachment with their original. They should open the original before sending it again. Compressing the file into a ZIP archive or sharing it through a trusted file-transfer service can help avoid attachment handling problems, but it cannot repair a source file that was already damaged.

When every copy fails in every reader, ask the owner to recreate the PDF from the source document. Exporting the original word-processing, spreadsheet, presentation or design file again is safer than trying to reconstruct missing PDF data. If no source document exists, recovery may be limited and could lose pages, forms, signatures, annotations or attachments.

Do not change the extension from another format to .pdf. Renaming changes the filename, not the file’s internal structure.

Bypass a browser or website display failure

Save the document to your device instead of relying on the inline browser viewer. Depending on the browser, right-click or Control-click the link and choose Save link as, Download linked file or the equivalent command. Open the saved file directly in a PDF reader.

If that works, you can continue using the downloaded copy while investigating the browser. Update the browser, reload the page, sign in again where required, and test the link in another supported browser. Browser extensions can interfere with downloads or built-in viewers, so a private window or the browser’s troubleshooting mode can provide a useful comparison.

If no browser can retrieve the file, the website may be returning a broken link, an authorization error or an incomplete response. Contact the site owner rather than changing your PDF software.

Repair the reader or correct the default application

Update the PDF reader before making deeper changes. Reader updates can include compatibility, stability and security fixes. Close the application fully after updating it, reopen it and test both a known-good PDF and the problem file.

On Windows, you can set a preferred reader under Settings > Apps > Default apps by searching for the .pdf file type. You can also right-click one PDF and use Open with for a one-time test. On macOS, select the file in Finder, choose File > Get Info, select a reader under Open with, and use Change All only if you want that application to handle every PDF.

If the reader still fails with several valid documents, use its built-in repair option where available or reinstall it from its official source. Remove or disable unneeded third-party plug-ins if the failure began after installing one. Avoid downloading supposed PDF repair utilities from pop-ups or unfamiliar websites.

For a protected document, obtain the correct password or permission from the owner. For a file blocked as suspicious, verify its origin before proceeding. A reliable PDF reader can help you test and view ordinary documents, but it should not be used to bypass passwords, organizational access controls or security warnings.

Source: PDF opening, damage, browser testing, reader updates and default-handler guidance from Why can’t I open a PDF and Opening PDFs, Adobe; browser-viewer behavior and troubleshooting from View and edit PDF files using Firefox’s built-in viewer, Mozilla Support; security guidance from Protected Mode troubleshooting in Adobe Acrobat, Adobe; operating-system file associations from Change Default Apps in Windows, Microsoft Support, and Choose an app to open a file on Mac, Apple Support; PDF file-structure information from the PDF Reference, Third Edition, Adobe. Page last checked 2 October 2026.