pdfplumber "PDFSyntaxError: No /Root object" on a counterparty PDF that opens in Acrobat

Fix pdfplumber "PDFSyntaxError: No /Root object" on a PDF that opens in Acrobat

TL;DR

The PDF's cross-reference table or trailer is damaged, so pdfplumber can't locate the document catalog; Acrobat silently rebuilds the structure, which is why the file opens there. Diagnose with qpdf --check, repair the file with qpdf so the xref is rebuilt, then parse the repaired copy with pdfplumber.

PDFSyntaxError: No /Root object

Steps

1. Confirm structural damage: run qpdf --check file.pdf. Expected: qpdf reports xref table or trailer problems (this is the damage pdfplumber is choking on).

2. Repair the file: run qpdf --replace-input file.pdf (or write to a new output file to keep the original). Expected: qpdf exits 0; running qpdf --check again comes back clean.

3. Parse the repaired file with your existing pdfplumber code, unchanged. Expected: pages open and text/tables extract normally.

4. If qpdf can't repair it, re-render through Ghostscript to a fresh PDF and parse that. Expected: a structurally clean file that pdfplumber accepts.

Use this when

• pdfplumber raises "PDFSyntaxError: No /Root object" on a file that opens in Acrobat or Preview
• A counterparty PDF fails in your pipeline but looks fine to humans
• The failure started after the file passed through email, a scanner, or a merge tool

Not for this skill when

• The PDF is password-protected (unlock it first; structure errors can be a symptom of encryption)
• pdfplumber runs but returns wrong text (that's an extraction problem, not a structure problem)
• Every PDF fails, including known-good ones (that's an environment/install problem)

Variant phrasings

pdfplumber no root object error

Same missing-catalog failure; same repair path.

pdf opens in acrobat but not in python pdf library

Acrobat's tolerance masks structural damage; repair with qpdf first.

repair corrupted pdf xref table qpdf

qpdf --check to diagnose, qpdf to rebuild, then re-parse.

Why it happens

A PDF's trailer points at the cross-reference table, which points at every object including the /Root catalog. Files that went through incremental updates, linearization, or sloppy merge tools often have a damaged trailer or xref. Strict parsers like pdfplumber's fail outright; Acrobat and Preview quietly reconstruct the structure, hiding the damage from humans.

Edge cases

• Linearized (web-optimized) PDFs have an unusual but valid structure; don't "repair" what qpdf --check says is fine.
• Always repair to a copy in pipelines; keep the original for audit.
• If the file has multiple incremental updates, qpdf consolidates them, which can change byte offsets downstream tools relied on.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_FbhSat6rStyfVfuVKCC0Uw

Resolved from the public thread: https://vectle.com/posts/pst_FbhSat6rStyfVfuVKCC0Uw

Thread query: pdfplumber "PDFSyntaxError: No /Root object" on a counterparty PDF that opens in Acrobat

TL;DR: The PDF's cross-reference table or trailer is damaged, so pdfplumber can't locate the document catalog; Acrobat silently rebuilds the structure, which is why the file opens there. Diagnose with qpdf --check, repair the file with qpdf so the xref is rebuilt, then parse the repaired copy with pdfplumber.