Blog

Why is my PDF not opening? Find the actual cause

A PDF that will not open has one of six causes, and they need different fixes. How to tell which one you have, in about ten seconds.

A PDF that will not open has one of six causes, and every guide you will find lists all six as things to try. You do not have to try them. The cause is almost always visible in the first and last few hundred bytes of the file, so you can find out which one you have and skip the other five.

The first thing to establish is which side the problem is on, because that split decides everything else.

Is it the file, or is it the app?

Here is a test that takes five seconds and settles it.

Drag the file onto a web browser window. Chrome, Edge, Firefox and Safari all have a PDF reader built in, and it is completely separate from whatever else is installed on your machine.

  • It opens in the browser. The file is fine. Your problem is the app or the device you were using, and the whole second half of this post is for you.
  • It does not open in the browser either. The file is the problem, and the first half is for you.

That one test eliminates half the internet’s advice in one move.

The six causes, and what each one looks like

Cause What is actually wrong Does it open in a browser?
Not a PDF The file is an HTML page, an image or a Word file wearing a .pdf name No
Unfinished download It starts like a PDF and stops partway No
Empty file Zero bytes. A name and nothing else No
Password protected Nothing is broken. It is locked Opens, then asks for a password
Damaged structure It arrived whole and its internal index is wrong No
Nothing wrong with it The file is valid Yes

The last row is the most common one by a long way, and it is the one no troubleshooting article covers, because it is not about PDFs at all.

The file side

It is not a PDF, and this is the single most common cause

A PDF always begins with the five characters %PDF-. If those are not there, nothing will ever open it as a PDF, however the file is named.

What it usually turns out to be is an HTML page. You clicked a download link, the site quietly redirected you to a login screen or an expired-link page, and your browser saved that page under the filename you were expecting. You now have invoice.pdf on your desktop that is, byte for byte, a web page saying “please sign in”.

The other regulars are images and Office files that were renamed rather than exported. Changing a file extension from .docx to .pdf changes the label on the box and nothing inside it. Word files are ZIP archives underneath, so a renamed .docx is a ZIP, and a PDF reader opening a ZIP produces exactly the error you are seeing.

The fix is to go back to where the file came from and download it properly, or to open the original in the program that made it and use Export or Save As PDF. There is no repair tool for this, because nothing is broken.

The download stopped partway

This one has a mechanism worth knowing, because it explains something that seems unreasonable.

A PDF keeps its index at the end of the file, not the beginning. That index, called the cross-reference table, lists where every object in the document sits. A reader opens a PDF by jumping to the end, reading the index, and then jumping to whatever it needs.

So a PDF that is 80 percent downloaded has no index. The reader has nowhere to start, and it fails completely rather than showing you the pages that did arrive. This is different from a half-downloaded image, which shows the top half, and it is why “it downloaded most of the way” does not help you at all.

The giveaway is the marker %%EOF, which every complete PDF ends with. Header present, %%EOF missing, means the transfer died.

The fix is to download it again. Delete the broken copy first, because browsers and chat apps will happily hand you the same cached fragment twice.

It is locked, not broken

A password protected PDF looks like a broken one if your reader reports the failure badly. It is not damaged, and no repair tool will help, because the content is encrypted and the encryption is doing its job.

Bank and government statements are the usual case, and they are often locked with something you already know: a date of birth, a customer reference, the last digits of an account number. If someone sent it to you, the password was probably sent separately, in a second message or by text.

The structure is damaged

Header present, %%EOF present, and the cross-reference table in between disagrees with where the objects actually are. This happens when something wrote the file back incorrectly after an edit, or when the file was damaged in storage or transfer.

The fix is to find an earlier copy, which is almost always easier than repair. Check your sent mail, the original source, or a backup. Failing that, Acrobat and the free open source tool qpdf will both try to rebuild a broken index and can often recover most of the content.

Find out which one you have

Rather than working through that list, drop the file into our checker. It reads the header, the end marker and the structure, and tells you which of the six cases you are in and what to do about it.

It takes any file, not just PDFs, which is the point: the most common cause is a file that is not a PDF, and a tool that only accepted valid PDFs would refuse every file worth explaining. It runs entirely in your browser, so a document you cannot open is not a document you have to upload somewhere to diagnose.

The app side: when the file is fine

If it opens in a browser, stop looking at the file. Here is what is actually happening, by situation.

Why a PDF will not open on a laptop or PC

Usually there is no PDF reader installed, or the file association is pointing at a program that cannot read one. Right click the file, choose Open With, and pick your browser. If that works, set it as the default and the problem is over.

On Windows, a PDF downloaded from the internet or received by email may also open into a blank or greyed out window because of Protected View, a sandbox that Acrobat and Office apply to files from outside your machine. There is normally a bar at the top offering to enable editing.

Why a PDF will not open on a phone

Android does not always ship a PDF reader. This is the cause far more often than anything else, and the error message never says so. Install one, or open the file through the Files app, or open it in Chrome. On a phone, Google Drive will also display a PDF without needing anything else installed.

On iPhone, Files and Books both read PDFs and are always present, so a PDF that will not open on an iPhone is usually a file problem rather than an app one. Check the file side of this post instead.

Why a PDF will not open in WhatsApp

Three causes, in order of how often they happen.

  1. The download has not actually finished. The preview appears before the file has fully arrived. Tap the document itself rather than the preview and wait for the progress ring to complete.
  2. WhatsApp has no permission to store files. Without storage access it cannot write the document down, and it cannot hand a file it has not saved to another app. Check WhatsApp’s permissions in your phone settings.
  3. There is no app to hand it to. WhatsApp does not read PDFs itself on every platform. It passes the file to whatever reader is installed, and if none is, nothing happens. This is the Android case above wearing a different hat.

Why a PDF will not download in WhatsApp or Telegram

Different problem from not opening. A download that will not start or will not complete is usually storage, connection, or the file no longer being on the server. Chat platforms do not keep media forever, so an old document in a long thread may simply not be there any more.

The fix in every case is the same and it is worth doing first: ask the sender to send it again, ideally as a fresh upload rather than a forward, or as a link to a cloud folder. A forward can point at the same expired media the original did.

Why a PDF will not open in WhatsApp Web

WhatsApp Web downloads the file to your computer and hands it to your browser or your desktop reader. So this is the laptop case, not a WhatsApp case. Find the file in your Downloads folder and open it from there, and if that fails, drag it onto a browser window.

The short version

If it opens in a browser, the file is fine and you are fixing the wrong thing. If it does not, the cause is in the bytes, and you can find out which one it is in about ten seconds rather than working through a list of six.

Further reading