Free Tool Desk

Guide

How to Tell If a PDF Is Structurally Valid

Last updated October 5, 2026

"My PDF opens fine, so it must be fine" is a reasonable assumption, and often a wrong one. PDF viewers are lenient on purpose. Most will quietly work around a broken index or a bad reference and show the file anyway, with no sign that anything was wrong.

What "structurally valid" means

A PDF is more than a list of pages. Inside, a cross-reference table tells a reader where every object in the file lives, and the objects refer to each other. If that table is damaged, missing or points to the wrong places, the file is structurally broken even when enough of it still draws in a forgiving viewer. This is a different question from what PDF Information reports. Page count, version and size describe what is in the file; structure describes whether its internal bookkeeping is sound.

Why it matters when nothing looks wrong

The risk is the next program, not the one you use today. A stricter system, such as a print workflow, a document-management platform or another PDF library, may not recover as gracefully and can fail on a file that opened everywhere else. Damage that is invisible today can break the file later.

Common causes

  • An upload, download or transfer that was cut off partway through
  • A PDF-writing library with a bug in how it writes the cross-reference table
  • Low-level editing with a tool that does not rewrite the structure afterwards

How to check

Instead of guessing from whether the file opens, run it through the PDF Structure & Validity Checker. It inspects the cross-reference table and the object structure and reports a pass, a warning or an error, and whether the file is encrypted or linearised ("fast web view"). It is a diagnostic only: it finds problems but does not repair them. If a file fails, regenerating it from its source is usually more reliable than patching it.

What a pass does not tell you

A pass means the file's structure is sound. It does not mean the pages look right, that every font is embedded, that the text is real text rather than a scan, or that the content is what you expected. For those questions, open the file and look, and use the PDF Text Density Checker to see whether pages carry real text.

What the other PDF tools say about a bad file

Every PDF tool here reads the file's structure before it does anything. If the file cannot be read, you get the message "The file is not a valid PDF or is corrupted." The same message appears for a PDF that needs a password to open, because the tools cannot read inside it, so a password-protected file is not necessarily damaged. A PDF that has only an owner password (restrictions on printing or editing) can usually be read; the PDF Information page reports such a file as encrypted. In our tests such a file worked in Extract PDF Pages, Rotate PDF and Compress PDF but failed in Merge PDF with a general error. For a file that fails everywhere, check it with the structure checker first.

A practical order

  1. Try the file in a second viewer. If one of them struggles, the file may be damaged.
  2. Run the structure checker.
  3. If it reports errors, regenerate the file from the original source, or re-download it.
  4. If the file only needs pages from it, extracting them into a new PDF sometimes gives a clean file, though it cannot repair a badly damaged one.