Acrobat could not find its way around the file: the index at the end that lists where every page lives is missing or wrong. That is usually a download or attachment that was cut short, not ruined content. Get a fresh copy first; if there isn’t one, rebuild the structure from what is left.
Runs in this tab, on pdf-lib, qpdf (WebAssembly) and pdf.js, so your file is read from your own device and never sent anywhere. Check it yourself
How do I fix it?
1Check the size against what you expectedA few kilobytes where you expected megabytes means the transfer failed. Download it again or ask the sender to resend it — that fixes it outright.
2Try a more forgiving readerDrag the file into Chrome, Edge, Firefox or Safari. Browsers rebuild small errors quietly; if it opens there, print it to a new PDF or save a copy.
3Rebuild the structureRepair PDF rebuilds the missing index from the rest of the file and saves a clean copy, keeping text, fonts and links. It runs in your browser, so the file is not uploaded.
4If only some pages survive, keep thoseWhen the damage is deeper, the repair copies across every page that still has its content and tells you how many came back.
5Stop it happening againSend large PDFs as a link or a ZIP rather than a raw attachment, let cloud files finish syncing before opening them, and keep the original until the copy has been checked.
Why does this happen?
The download or attachment is incomplete. The index a PDF reader needs sits at the end of the file, so a transfer that stops early removes exactly the part Acrobat looks for first.
The file was altered in transit. An old FTP transfer in text mode, a mail gateway that re-encodes attachments, or security software that rewrites files can change bytes a PDF depends on.
It was saved while something went wrong. An app that crashed, a laptop that slept, or a USB stick pulled out mid-save can leave a file half-written.
Cloud sync handed over a placeholder. Sync apps can show a file that has not finished downloading, or keep a conflicted copy that is only partly there.
The software that made it broke the rules. Some generators write PDFs whose internal offsets are wrong. Forgiving readers cope; Acrobat, which checks more strictly, refuses.
Questions
Didn’t Acrobat already try to repair it?
Yes. Acrobat quietly repairs small problems when it opens a file; this message means its own attempt failed. A tool that rebuilds the whole structure from scratch often succeeds where that quick fix gave up.
Why does the PDF open in Chrome but not in Acrobat?
Browsers’ PDF engines are more tolerant and rebuild minor errors silently. Acrobat checks more strictly. The file has a real fault, but a small one — rebuilding it gives you a copy every reader accepts.
Can a PDF with this error be recovered?
Usually, as long as the file isn’t empty. What is lost is only what isn’t in the file: a transfer cut off at 70% loses the pages after the cut, but what came before can normally be rebuilt.
Is it safe to use an online PDF repair tool?
Only if the file stays with you. A PDF you are trying to rescue is often the only copy of something important; a repair that runs in your browser works on your device, so nothing is uploaded or kept.
What is Adobe Acrobat error 109?
“There was a problem reading this document (109)” means Acrobat hit a structural error it couldn’t get past — the same family of damage as this message. Open the file in a browser to check the content survives, then repair it so Acrobat accepts it.
Why is a PDF I downloaded from a website corrupted?
The download stopped early, or the site sent an error page under a .pdf name. Compare its size with what the site states, and download again; if it still fails, the file on the site may itself be broken.