Workflow 7 min read 20 October 2026

Repairing Corrupt PDFs: Causes, Tools, and Recovery Techniques

PDF files can become unreadable due to incomplete downloads, storage failures, encoding errors, or software bugs. This guide covers the most common corruption causes, how PDF parsers attempt recovery, and the command-line and GUI tools (qpdf, Ghostscript, mutool, Acrobat) available to repair damaged files.

A PDF file that opens correctly today can become unreadable tomorrow. Incomplete downloads, storage device failures, file system corruption, truncated email attachments, and software bugs all produce corrupted PDFs. Whether the file shows a blank page, displays a parser error, or simply refuses to open, there are usually several recovery options — ranging from built-in viewer repair to dedicated command-line tools — before concluding that the file is unrecoverable. This guide covers the most common PDF corruption causes, how PDF parsers attempt automatic recovery, and the step-by-step recovery process using free and commercial tools including qpdf, Ghostscript, mutool (MuPDF), and Adobe Acrobat Pro.

Common causes of PDF corruption

Understanding why a PDF is corrupt helps choose the right repair approach: Incomplete download / truncated file — The most common corruption cause. A PDF downloaded over an unreliable connection may be missing its final bytes. Since the cross-reference table (xref) and trailer are at the end of the file, a truncated PDF may have all its content objects intact but no way to locate them. Symptoms: "Unable to open file", "could not read cross-reference table", or only partial page display. Fix: the PDF parser must attempt to rebuild the xref from the file's objects. Storage corruption — Sectors on an SSD or HDD that contain PDF data become unreadable (bad sectors, magnetic deterioration). Corrupt bytes within the PDF can damage specific objects — image streams, font programs, the xref table. Symptoms: specific pages render incorrectly or trigger errors; images appear garbled; page count is wrong. Fix: byte-level repair followed by object-level recovery. Broken incremental update — PDFs that have been edited and saved with incremental updates append new content to the end. If an incremental update is incomplete (save interrupted), the xref for the update is invalid. The original content may be intact. Symptoms: file opens but missing recent annotations or form data. Fix: strip the broken update back to the last valid state. Invalid cross-reference table — Byte offsets in the xref table pointing to wrong positions in the file. This happens with tools that modify PDF bytes without updating the xref (manual hex edits, buggy PDF processors). Symptoms: wrong objects displayed, parser errors, garbled content. Fix: rebuild xref from object scanning. Font stream corruption — Embedded font programs (Type 1, TrueType, CFF, OpenType) with corrupt data. The PDF structure may be intact but individual characters display as boxes or incorrect glyphs. Fix: re-embed fonts if the source document is available; remove and re-export if not. Encoding errors — PDFs created with incorrect encoding or non-standard operators. Some tools produce technically invalid PDFs that major viewers parse by guessing the intent; strict parsers refuse them. Fix: pass through a lenient parser that normalises the structure.

Recovery tools and techniques

1. Try multiple PDF viewers first — Before attempting repair, try opening the PDF in several different viewers: Adobe Acrobat Reader, Chrome, Firefox (PDF.js), macOS Preview, Foxit Reader. Each has a different parser with different error tolerance. A file that fails in Acrobat may open in Chrome; one that fails in both may succeed in mutool. Chrome and Firefox's PDF.js have particularly lenient parsers that recover from many malformed structures. 2. qpdf — the first tool to try — qpdf is a command-line tool that performs structural transformation of PDFs. Its --recover option attempts to rebuild the cross-reference table by scanning the file for valid PDF objects: qpdf --recovery input.pdf output.pdf qpdf also provides diagnostic information: qpdf --check input.pdf reports xref errors, encryption issues, and structural problems. If the xref is the only issue and the content objects are intact, qpdf's recovery succeeds reliably. 3. Ghostscript — structural normalisation — Ghostscript processes PDF by rendering it through its interpreter and writing new PDF output. This regenerates the entire file structure: gs -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=output.pdf input.pdf Ghostscript is more aggressive than qpdf — it will silently skip objects it cannot parse and continue. The output PDF may be smaller than expected if some objects were unrecoverable. Add -dPDFSETTINGS=/prepress to preserve image quality. 4. mutool (MuPDF) — lenient parsing — mutool from the MuPDF library has a lenient parser useful for recovery: mutool clean -gggg input.pdf output.pdf The -gggg flag performs aggressive garbage collection, removing unreferenced objects and writing a clean output file. 5. Adobe Acrobat Pro — File > Open (Acrobat will attempt repair and prompt if it detects corruption). Also: File > Save As to force a full file rebuild. For advanced recovery: preflight (Tools > Print Production > Preflight) can identify specific structural errors. 6. Recovery services for severe corruption — For PDFs damaged by storage failure (large sectors of random bytes), tool-based recovery may not be sufficient. Commercial services like PDF2Go Repair or specialist data recovery firms may recover more content through byte-level analysis.

Prevention and backup strategies

Verify PDF integrity on creation — Run qpdf --check on PDFs generated by automated pipelines to catch corruption before distribution. In Python pipelines, verify that the output file is a valid PDF: use pypdf to open and read the page count as a smoke test. Store PDFs with checksums — Calculate SHA-256 hashes of important PDFs at creation time and store them alongside the files. This detects bit-rot (storage degradation) and verifies download integrity. PDF/A for archival PDFs — PDF/A files have additional self-consistency requirements (embedded fonts, ICC profiles in XMP metadata) that catch some classes of corruption. veraPDF validation of PDF/A files provides a more thorough structural check than qpdf's basic verification. Avoid simultaneous writes — Never write a PDF to a network share or cloud storage while simultaneously opening it in a PDF viewer. This causes file locking conflicts that produce corrupt incremental updates. Always close Acrobat before an automated process writes to the same file. Re-sign after repair — If a repaired PDF contains digital signatures, those signatures are now invalid — the repair process modified the byte ranges covered by the signature hash. Remove the signatures and re-sign if signature validity is required.

Frequently asked questions

Can I recover a PDF if I only have a partial download?

Sometimes. If the PDF is linearized (Fast Web View), the first page's data is near the beginning of the file — a partial download that includes the linearization hint tables and first-page section may allow the first page to be recovered even if subsequent pages are missing. For non-linearized PDFs, the xref table is at the end of the file. If the download is truncated before the xref, qpdf's --recovery option attempts to rebuild it by scanning for valid object markers ("%obj" sequences) throughout the available data. If the file is more than 50% complete, recovery of at least partial content is often possible. If the file is less than 20% complete, recovery is unlikely without the content bytes for the specific page you need.

My PDF opens but some pages are blank — is this a corruption issue?

Blank pages in an otherwise functional PDF are usually not corruption. Common causes: (1) White-filled boxes covering the page content — a common result of incorrect white-out or annotation cover operations. Open in Acrobat and use Edit > Select All to see if anything invisible is selected. (2) Content stream rendering with a zero-width clipping path — all content is clipped to an empty region. qpdf --qdf can expose this. (3) Font not embedded — pages with text in a non-embedded font may render blank in strict viewers that refuse to substitute. Check File > Properties > Fonts in Acrobat. (4) ICC colour space issues — pages with out-of-gamut colours may render blank on some CMYK-only print paths. (5) Content on an invisible layer — OCG (optional content group) set to off by default hides all layer content. Check View > Show/Hide > Navigation Panes > Layers in Acrobat.

Does repairing a PDF invalidate its digital signature?

Yes. A PDF digital signature covers specific byte ranges of the PDF file (specified in the signature dictionary's /ByteRange entry). Any modification to the file — including structural repair by qpdf, Ghostscript, or any other tool — changes bytes outside the original byte ranges, causing the signature verification to fail with a "document has been modified" error. This is the correct and expected behaviour: the signature was valid for the original file, not the repaired copy. If the repaired PDF needs to be treated as authentically signed, the options are: (1) re-sign with a new signature after repair; (2) attach the repaired version to a new signed document with a declaration explaining the repair; (3) for legal purposes, document the repair chain of custody. There is no way to preserve a signature through a structural repair.

Try it yourself

Everything in this article can be done directly in the free PDFTheGuide editor — no account required.

Edit PDF Compress PDF Merge PDF Open editor