PDF won't open? What corruption really means, and what repair can do

How a PDF breaks in the first place

Corruption is rarely mysterious. The common causes, in rough order of frequency:

• Interrupted transfer or save — the download stopped early, the email attachment was truncated, the app was killed mid-save. The file simply ends before its data does.
• Wrong transfer mode or re-encoding — old FTP text-mode transfers and some messaging apps altering bytes in transit.
• Storage faults — failing USB sticks and SD cards quietly returning garbage for some sectors.
• Buggy generators — software that writes almost-valid PDFs, which strict viewers reject and lenient ones open. If a file opens in the browser but fails in another app, this is usually the story.

Why “broken index, intact contents” is the common case

A PDF ends with a lookup table — a directory telling the viewer at which byte position each object (each page, font, image) lives, plus a trailer saying where that table starts. Because this critical machinery sits at the end of the file, the most common accident — truncation — destroys the directory while leaving the actual page data, stored earlier in the file, untouched. The viewer isn't saying “your data is gone”; it is saying “I've lost the map to it”.

That is exactly the case repair tools are built for: scan the whole file, find every surviving object directly, and rebuild the directory. When the map was the only casualty, recovery is total — every page returns. When actual page data was destroyed, an honest repair returns what survived: 19 pages of a 20-page report is usually far more useful than zero.

A sensible order of things to try

1. Re-obtain the file if you possibly can. Re-download it, ask the sender to resend, check the original source. A fresh intact copy beats the best repair.
2. Try a different viewer. Browsers are notably tolerant of malformed PDFs. If Chrome or Firefox opens it, the file is malformed rather than gutted — print-to-PDF or re-save from there produces a clean copy.
3. Run a repair tool — one that scans and rebuilds, and tells you in plain terms what it found and what it recovered. Our Repair tool does a health check first, then the rebuild, in your browser.
4. Calibrate expectations by cause. Truncated download → often full recovery. Failing memory stick → partial. File deliberately overwritten or a fragment from data recovery → little to nothing; no tool can rebuild bytes that no longer exist anywhere.

Special case: it's not corrupt, it's encrypted

“The file is damaged” and “the file needs a password” look similar at a glance and get mixed up constantly. An encrypted PDF (see our guide to PDF passwords) is perfectly intact — just unreadable without the key. If the source is a bank, insurer or government office, suspect a password before corruption; the code is often your date of birth or ID number, stated in the covering email. Repair tools cannot and should not “fix” encryption.

Not losing files this way again

• Verify the download finished (size roughly matching the stated size) before deleting the source or the email.
• Don't treat a cheap USB stick as the only home of anything that matters.
• Keep the original before any bulk operation — compressing, merging, converting — so an interrupted batch can't take the sole copy with it.
• When a file matters for years (contracts, certificates), store it twice: local plus a backup you trust.

Keep reading