Fix Adobe Acrobat Error 14 — "There Was a Problem Reading This Document (14)"
Acrobat error 14 is a read failure on a specific object or stream within the PDF. Here are all causes and step-by-step recovery methods.
Adobe Acrobat Error 14 — "There was a problem reading this document (14)" — is an object-level read failure. Unlike Error 109 (stream parsing) or Error 110 (save failure), Error 14 fires when Acrobat locates an object in the cross-reference table but cannot read the object data at that location. The file structure knows the object exists but the data is wrong.
What Error 14 Means Specifically
PDF files contain an object table (cross-reference table or cross-reference stream) listing the byte offset of every object in the file. Error 14 fires when Acrobat reads an offset from this table, jumps to that byte position in the file, and finds unexpected data — either wrong object number, a different object type than expected, or corrupted bytes. This is most commonly caused by: byte-offset corruption from a partial file transfer, a PDF editor that rewrote objects without updating the cross-reference table, or a PDF generator that computed wrong object offsets.
Fix 1 — Try Chrome's PDF Viewer
Chrome's PDFium uses a linear scan approach for corrupt PDFs — rather than relying on the cross-reference table to jump to objects, it can scan the file sequentially to find objects. This makes it resilient to exactly the offset-corruption that causes Error 14. Drag the file onto a Chrome tab. If it opens (even partially), print to PDF from Chrome to create a clean re-written version. Chrome's linear scan recovery works on the majority of Error 14 cases.
Fix 2 — Re-download the File
Error 14 is the most common error from a partially transferred file where the first several hundred kilobytes downloaded correctly (enough to read the cross-reference table) but the object data later in the file was cut short. The cross-reference table correctly reports object offsets, but those locations now contain truncated data. Verify file size matches what was expected, then re-download on a stable connection. This resolves Error 14 in roughly 40% of cases.
Fix 3 — Run Through FixMyPDF
Upload the file to FixMyPDF's compressor at Low compression. Our processor scans objects sequentially rather than using the offset table, recovering what data it can, and then writes a fresh PDF with a correct cross-reference table and accurate byte offsets. This rebuilds the structural integrity that Error 14 indicates is missing. The re-processed file will open cleanly in Acrobat. Objects that were genuinely unreadable will be missing from the output — typically a small number of the total pages or images.
Fix 4 — LibreOffice Draw Recovery
LibreOffice Draw's PDF importer also uses tolerant object scanning. Open the damaged PDF in LibreOffice Draw. Even if some pages have rendering issues, most content is usually recovered. From LibreOffice: File → Export as PDF to re-write a structurally clean PDF. This is particularly effective for text-heavy PDFs where even partial object recovery gives you 95%+ of the content. Compare page counts of the recovered export vs the original to identify any missing sections.
Try Compress PDF Now — Free
Browser-based, private, and instant. No account or software required.
Open Compress PDF