PDF 복구

이 도구가 하는 일

This rebuilds a damaged PDF from whatever is still readable inside it. The cross-reference table - the index that tells a reader where every object lives - is reconstructed by scanning the file, and the result is written out as a clean document. Before you are offered anything, the repaired file is opened again to check it really works, and the report tells you how many pages it had before and how many it has now.

Use it when a reader refuses the file: a download that stopped part way, a file recovered from a failing drive or a memory card, one that came out of a crashed export, or one that opens in a browser but not in Acrobat.

작동 방식

1. Drop the damaged PDF onto this page. This is the one tool that accepts a file whose header looks wrong, because that is exactly the file it exists for.
2. Leave Rebuild the cross-reference table on. It is the fix for the large majority of PDFs that will not open.
3. Leave Recover pages on so that, if the ordinary repair fails, the document can be rebuilt from its pages alone.
4. Turn on Drop unreadable objects only if the first attempt fails. It sacrifices whatever those objects held in exchange for getting a file at all.
5. Press Repair, then read the report: it says how many pages were readable before and how many the repaired file contains.

Most files that will not open are not badly damaged. A PDF ends with a table of byte offsets pointing at every object in it, and if that table is wrong - because bytes were added, a transfer truncated, or an editor wrote it incorrectly - a strict reader gives up even though the content is all present. The repair scans the whole file for objects, rebuilds the table from what it finds, and writes a fresh document around it.

There is a second, stronger attempt behind the first. If the ordinary repair cannot complete, the document is rebuilt from its page tree into an empty file, which recovers documents whose catalogue is gone but whose pages survived - the usual shape of an interrupted download. That path copies page content and leaves document-level structures behind, so a file recovered this way may lose its outline, its interactive form and its attachments while keeping every page.

The result is verified before it is offered to you. A repair that produces a file nothing can open has not repaired anything, so the output is read back and its pages counted. The counts before and after are both reported, and a repair that recovered 4 pages of 40 is a very different outcome from one that recovered all 40.

Nothing can be recovered that is not in the file. If a transfer stopped at 60 per cent, the missing 40 per cent is gone and no tool will invent it. Keep the damaged original until you have checked the result, because a second attempt with different options sometimes does better.

The repair runs on your device using qpdf compiled to WebAssembly. That matters more here than elsewhere: a file you cannot open is a file you cannot check, and uploading an unknown document to a stranger's server to find out what is in it is a poor trade.