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 these tell you what actually happened, and the fix depends entirely on which of four specific things went wrong. Work through them in order and you land on the right answer fast.
Cause 1: 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 discover that the last chunk is not really there.
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 Repair PDF to see what can be salvaged.
Cause 2: it is not actually a PDF
Files get mislabeled all the time. 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 actual bytes inside are something else, and PDF readers refuse to open non-PDF content.
%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, look at the file it actually served, and download the real one. If a website is serving HTML error pages under PDF URLs, contact whoever manages that site.
Cause 3: the file is password-protected
A password prompt at open time is not really "the file will not open". It means the file is encrypted and needs the password. The reader is doing its job; you just do not have the key 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
- AES-256 encryption, cannot be recovered
- 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 a blank password
If your file has an open password and you do not know it, no legitimate tool can recover it. Modern PDF encryption is genuine cryptography. Ask the sender to reshare the password, or ask them to reissue the file without protection.
Cause 4: 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 is fast, non-destructive (writes a new file, keeps the original), and either succeeds or reports honestly.
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. This is more common than you would think for files exported from recent design software.
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.
Habits that prevent the problem
Watch the download to completion. On slow or spotty connections, keep the browser open until the download bar disappears cleanly.
Check file sizes against expectations. When something feels off, look at the byte count before opening.
Save passwords the moment you receive them. A password sent by email is easy to lose. Paste it into your password manager next to the file's name.
Keep an original before editing. If you plan to edit or convert a PDF, save a clean copy of the source first. That way you always have a starting point to return to if the working copy breaks.
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 on your machine with what the source lists. A partial download is usually much smaller than expected. If the source lists 8MB and you have 200KB, the download was cut short.
03Can I rescue a damaged PDF?
Often. Opening it in a repair tool rebuilds the file structure, which fixes many mild corruptions. Repair cannot recover pages that were truly missing from the source, but structural rebuilds work in most cases.
04What if the PDF asks for a password I do not have?
Ask the sender for the password. Modern PDF encryption is AES-256 and cannot be recovered by any legitimate tool. If the sender is unavailable, ask them to regenerate the file 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 using WebAssembly. The file is read into local memory, parsed and rebuilt locally, and never sent to a server.