A reader that keeps complaining
Give a PDF that opens but carries many structural warnings a qpdf rewrite and see whether a cleaner copy comes out.
Guide
PDF Repair deals with files that have broken structures, that make readers complain, or whose pages will not all open. The flow is not “turn the whole file into images”: qpdf inspects the file and collects warnings, then rewrites it by regenerating the object and compressed streams. Only when qpdf cannot produce a result does the tool try a PDF render engine, rasterising the pages that still display and rebuilding them as a fresh image PDF.
Updated 2026-09-104 min read
PDF Repair deals with files that have broken structures, that make readers complain, or whose pages will not all open. The flow is not “turn the whole file into images”: qpdf inspects the file and collects warnings, then rewrites it by regenerating the object and compressed streams. Only when qpdf cannot produce a result does the tool try a PDF render engine, rasterising the pages that still display and rebuilding them as a fresh image PDF.
Even when the structure is healthy, a rewritten version is produced. If the tool enters rescue mode, the diagnostic card shows the total page count, the pages rescued and the numbers of the pages that failed to render, so you can judge what is missing.
<original-name>_rescued.pdf, and when nothing can be read the tool reports failure plainly rather than inventing a success file.| Input | Output | Notes |
|---|---|---|
a PDF that barely opens with a reader warning about a broken cross-reference table |
qpdf collects warnings and rewrites it; the status reads "repaired" and the output is written as <original-name>_repaired.pdf |
the PDF page structure is kept where possible |
serious structural damage that qpdf cannot rewrite, but 27 of 30 pages still render |
the 27 renderable pages are rebuilt at the chosen DPI, and the failed page numbers are listed in the report |
rescue mode may lose pages |
an encrypted PDF with no password entered |
a message that the file is encrypted and an open password is needed under the repair options |
a password problem is not mistaken for structural damage |
Give a PDF that opens but carries many structural warnings a qpdf rewrite and see whether a cleaner copy comes out.
When the structural repair fails, save as many renderable pages as possible into a new image PDF.
When the open password is known but the structure is abnormal, supply the password during repair and output an unencrypted repaired copy.
Even when the qpdf check finds a healthy structure, the flow still performs one structural rewrite, so you get “structure healthy, optimised rewrite output”.
Rescue mode saves each successfully rendered page as a JPEG image and repacks it into a PDF, so the original text layer and interactive objects are not kept.
No. The code adds only pages that render successfully to the new document and lists the failed page numbers in the report, so check the page count against the original file.
The qpdf check, the structural rewrite and the rasterised rescue all run locally in the browser; the PDF and its open password are never uploaded to a server.
Updated 2026-09-10
Diagnose a damaged file and rewrite it; when badly broken, rasterize whatever pages still render
Everything runs locally in your browser; files are never uploaded to a server