Rule out four causes in order: incomplete download, wrong file type, password lock, damaged structure. Each takes under a minute to check. Only the last one needs a tool. Damaged files usually recover through Repair PDF.
Adobe throws a generic error. Preview says the file cannot be opened. Chrome shows a blank tab. None of them says which of the four problems you have, and the fix is different for each. Work through them in order, cheapest check first.
The download was cut short
A dropped connection or a closed browser tab can save a file that looks complete but is missing bytes at the end. The download indicator shows 100 percent because it thought it was done. The file lands in your Downloads folder with the correct name and icon. Only when you try to open it does the reader find that the last chunk is missing, and with it the index at the end of the file that says where every object is.
Check the file size against the source
Right-click the file, look at the size, compare to what the source page or email claimed. A 200KB file that should be 8MB is a cut-off download.
Try downloading again
On a stable connection, right-click the source link and pick Save link as. Watch the download to completion this time.
If the source is gone, try repair
Sometimes you cannot re-download. Run the partial file through the browser-based Repair PDF tool, which rebuilds the missing index from the objects that did arrive. Pages that never downloaded cannot come back.
The file is not a PDF at all
A file name and its declared application/pdf media type are only labels, and they get attached to the wrong bytes. A web server sends an HTML error page with a .pdf name in the URL. An email client saves a text attachment as .pdf. Someone renames a Word document by hand. The file has a PDF extension, but the bytes inside are something else, and a PDF reader refuses them.
%PDF. If you see something else (HTML tags, plain English text, garbage characters), the file is not a PDF regardless of what its name says.The fix is upstream. Go back to the source, check what it served, and download the real file. If a website is serving HTML error pages under PDF URLs, contact whoever manages that site.
The file is password-protected
A password prompt at open time means the file is encrypted and the reader is asking for the key. The file is fine; you just do not have the password yet.
Two flavours of password exist. Knowing which one matters, because they behave differently.
Blocks viewing entirely
- Reader prompts for a password immediately
- Zero content is visible until you enter it
- Content is encrypted; only the password opens it
- Fix: get the password from the sender
- Then remove it with Unlock PDF
Blocks specific actions
- File opens normally, no prompt at all
- Print or copy buttons are greyed out
- Restriction, not encryption
- Removable without knowing the password
- Also handled by Unlock PDF with the password field left empty
If your file has an open password and you do not know it, the only way in is guessing. Current PDFs use AES-256, which has no shortcut, so a recovery tool can only try candidate passwords quickly. That finds a dictionary word or a short password and nothing stronger. What you can do about a forgotten PDF password covers the rest. For a file someone sent you, ask them to reshare the password or reissue the file without protection.
The file is damaged
A PDF is a small database of interconnected objects. If any of the pointers in that database get corrupted, the whole file becomes unreadable even though most of the content is still intact. This happens when files are transferred over unreliable connections, saved by buggy software, or edited by tools that produce slightly out-of-spec output.
Try repair even if you are not sure the file is corrupted. It writes a new file and leaves the original alone. The guide to fixing a corrupted PDF goes through what a rebuild can and cannot recover, case by case.
Rare causes worth knowing
Once in a while none of the four causes above applies and the file still will not open. Two edge cases account for most of the remainder.
The reader is outdated
PDFs from newer software occasionally use features an older reader does not understand. If a file opens fine in Chrome or Preview but Adobe Reader refuses it, update Adobe or use a different reader. Files exported from recent design software are the usual source.
The file uses a signature or form technology your reader dropped
XFA forms, deprecated in the PDF spec but still present in some government and legal templates, are no longer supported by all readers. Adobe Reader on desktop still handles them. Modern Chrome and Preview do not. If the source is a government form, opening in Adobe Reader specifically often solves it.
"Acrobat failed to connect to a DDE server"
This one belongs apart from the rest, because it is not about the file. Every other cause on this page is something wrong with the document. This is Windows failing to hand the document over.
Dynamic Data Exchange is an old Windows mechanism for passing a filename to a program that is already running. It is why double-clicking a second PDF opens a tab in the Acrobat you already have rather than starting another copy. When that handover fails, Windows reports that it could not reach the DDE server and the file never gets as far as being read. The same document will usually open without complaint if you drag it onto an Acrobat window that is already open.
Four things cause it, in roughly the order worth trying.
- Acrobat closed its window and left itself running. Open Task Manager, end every
Acrobat.exeandAcroRd32.exelisted, and try again. This alone accounts for most cases. - Protected Mode, Acrobat's sandbox, runs a second process, and on some machines the two lose track of each other. Under Preferences and then Security (Enhanced), clear "Enable Protected Mode at startup", restart Acrobat and see whether the error goes with it.
- An interrupted Acrobat update can leave the registry entry that tells Windows how to reach it pointing at something no longer there. Repairing the installation from Acrobat's Help menu rewrites that entry.
- Another program is in the middle. Opening a PDF from inside Outlook, Word or a document management client routes the request through that program's own handler. If the file opens by double-click but not from the other application, the fault is in the other application.
None of this touches the document, so there is nothing to repair and nothing to convert. If you need to read the file now and would rather not work through the list, open Acrobat first and use File then Open, or drop the file into a browser window, which does not involve DDE at all.
Habits that prevent the problem
On a slow or unreliable connection, keep the browser open until the download bar clears, and compare the byte count with what the source lists before you open the file.
Save a password the moment it arrives. One sent by email is easy to lose, so paste it into your password manager next to the file's name.
Before you edit or convert a PDF, keep an untouched copy. Repair can only rebuild from the bytes it is given, and it cannot recreate a clean original.
Repair a PDF that will not open
Rebuilds the structure when the file is damaged, and re-renders the pages when it cannot. Nothing is uploaded.
Common questions
Details that come up while diagnosing.
01Why will my PDF not open?
Four common causes: the download was cut short and the file is incomplete, it is not actually a PDF despite the name, it is password-protected, or it is slightly damaged. Each has a specific fix. They usually rule themselves out in under a minute if you work through them in order.
02How do I know if the download was incomplete?
Compare the file size with what the source lists first. If the size looks plausible, open the file in a text editor and look at the end: a complete PDF finishes with %%EOF, and a cut-off download usually stops partway through an object instead.
03Can I rescue a damaged PDF?
Often. A repair tool rebuilds the file structure, which fixes damage to the index and the object layout. It cannot recover pages whose bytes never arrived, and an encrypted file needs its password before any repair can read it.
04What if the PDF asks for a password I do not have?
Ask the sender for it. A forgotten open password can only be guessed, and against AES-256 with a password that is not guessable there is no practical way in. If the sender is unavailable, ask whoever produced the file to regenerate it without protection.
05The file opens in Chrome but not Adobe. Why?
Adobe Reader is stricter about PDF spec compliance. Some files from newer or older tools produce output that Chrome tolerates and Adobe rejects. Updating Adobe usually fixes it, or you can standardise the file by running it through repair or resaving from Chrome's PDF viewer.
06Does PDFslime upload files during repair?
No. Repair runs entirely in your browser. The parser scans the bytes inside the tab, pdf-lib writes the new file there, and nothing is sent to a server.
07What does "Acrobat failed to connect to a DDE server" mean?
That Windows could not hand the filename to Acrobat, not that anything is wrong with the PDF. Ending every lingering Acrobat.exe in Task Manager fixes most cases, and opening the file from inside Acrobat bypasses the mechanism entirely.