"There was a problem reading this document (109)".
Acrobat showed "There was a problem reading this document (109)." while opening or rendering your PDF, which points to a malformed object or an inconsistent cross-reference rather than a missing file. FileFix rebuilds the document from what it can validate and shows page and object counts first. A one-time $12 USD — and only if the repair works.
Free preview — pay only if you download ($12 USD)
Your files auto-delete — delete them sooner anytime
No person looks at your file as part of repair
Uploading your file.
Keep this tab open while the file transfers. Large files can take longer.
Starting upload...
Recovering what we can.
- Upload received
- Repair in progress
- Result ready
Analyzing your file...
Here's what we recovered.
Review the watermarked preview before checkout.
Repair your file
Choose a supported file to see what can be repaired before checkout.
Simulated checkout — no payment is processed.
Optional — we'll email your private download link.
You preview before you pay. If the download is materially worse than the preview you approved, we'll refund you.
Your files auto-delete — delete them sooner anytime
No person looks at your file as part of repair
We couldn't recover this one.
The file is too damaged to rebuild, so there is nothing to preview and no charge.
What stopped you continuing? One tap tells us why.
Try a deep repair
The repair engine can try a longer pass on the file you already uploaded.
Machine-only processing; no human views files; nothing is sent to an outside AI.
Have another clip from the same device?
A healthy video recorded on the same device — ideally the same settings — gives the repair engine a template to rebuild from. It can unlock repairs that fail on their own.
Unrepaired files are kept encrypted for up to 30 days, then deleted.
FileFix can't fix that kind of file yet.
Right now we repair video, audio, document, and image files (MP4, MOV, M4V, MKV, AVI, TS, MTS, M2TS, MPG, MPEG, VOB, 3GP, WebM, FLV, M4A, WAV, MP3, AAC, FLAC, OGG, OPUS, AIFF, XLSX, DOCX, PPTX, ODT, ZIP, RAR, PDF, AI, HEIC, and HEIF). We're adding support for more formats over time.
Something went wrong.
The request could not be completed.
Why this happens
Acrobat's error 109 is a read error: the application located the file and began parsing it, but hit an object or cross-reference entry that did not agree with the rest of the document. A page can display while a later object fails, which is why some PDFs open part way before the message appears.
Common causes are a truncated save, a stale cross-reference offset from an incremental update, or a malformed object stream introduced during export or transfer. The damaged pointer, not the whole document, is usually what stops the reader.
FileFix runs recovery-aware rewrite paths that rebuild the cross-reference structure and reserialize the objects it can read, then reopens each candidate without recovery mode. Only a candidate with at least one readable page is offered, and the summary states the validated page and object counts it contains.
What we can and can't recover
We can usually fix
- PDFs that show "the file is damaged and could not be repaired"
- PDFs Chrome or Edge won't open ("Failed to load PDF document")
- Files cut off mid-download or mid-save
- PDFs with a broken cross-reference table or trailer
We can't fix
- Password-protected or encrypted PDFs
- Genuinely empty (0-byte) files
- Deleted or formatted files (that's data recovery, a different job)
- Pages whose content was never written to disk
How it works
-
Upload Drop the file in. It uploads over an encrypted connection. The repair runs automatically — no person looks at your file.
-
Free watermarked preview You see watermarked pages from the repaired PDF and the recovered page count.
-
Pay & download If the preview shows what you need, unlock the repaired PDF for a one-time $12 USD.
You see watermarked pages from the repaired PDF and the recovered page count before you decide anything — so you never guess.
See what's recoverable.
Free watermarked page preview · private & auto-deleted
Browse by problem
Questions
Readers process objects as they are referenced. Earlier pages can render from valid objects while a later damaged object or cross-reference entry triggers the read error, so a partial open does not mean the rest is unrecoverable.
Not necessarily. The message reports a parsing inconsistency, not proof that pages are gone. FileFix rebuilds from the objects still present and shows how many validated pages the repaired file contains before you pay.
If Acrobat cannot open the document, its Save will not help. Upload the untouched file so the engine can work from the original bytes rather than a partially rewritten copy.