There was a problem reading this document (131)
Acrobat showed "There was a problem reading this document (131)" after it encountered inconsistent PDF objects or cross-reference data. Upload the PDF for an independent rebuild and see page and object counts from any validated result before you decide. A one-time $12 — and only if the repair works.
Free preview — pay only if you download ($12)
Your files auto-delete within 48 hours
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 a few minutes.
Starting upload...
Recovering what we can.
Analyzing your file...
Here's what we recovered.
Review the watermarked preview before checkout. Previews are capped at 90 seconds.
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.
Download repaired fileYou preview before you pay. If the download is materially worse than the preview you approved, we'll refund you.
Good news — your file isn't damaged. No charge.
There's nothing to repair. If it still looks broken, the issue may be the player, codec, or viewer on your device rather than the file itself.
We couldn't recover this one.
The file is too damaged to rebuild, so there is nothing to preview and no charge. You can try another file.
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.
FileFix can't fix that kind of file yet.
Right now we repair video, audio, and document files (MP4, MOV, M4V, MKV, AVI, TS, MTS, M2TS, MPG, MPEG, VOB, 3GP, WebM, M4A, WAV, MP3, AAC, FLAC, OGG, AIFF, XLSX, DOCX, ZIP, and PDF). We're adding support for more formats over time.
Something went wrong.
The request could not be completed.
Why this happens
Acrobat error 131 is a parsing failure tied to an object, stream, or cross-reference entry that does not agree with the rest of the PDF. The reader can stop at that inconsistency while other page objects remain readable.
Truncated saves, stale offsets, and malformed object streams can produce this error. A recovery-aware rewrite can reserialize readable objects and construct a consistent cross-reference structure around them.
FileFix validates rebuilt candidates without recovery mode and only reports the page and object counts actually present in the selected result.
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 exactly what we recovered — page and object counts and a short excerpt of recovered text.
-
Pay & Download If the summary shows what you need, unlock the repaired PDF for a one-time $12.
You see a recovery summary built from your actual file before you decide anything — so you never guess.
See what's recoverable.
Free recovery summary · files auto-delete within 48 hours
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.