Fix a Damaged PDF File
Your PDF says "damaged" or "cannot be opened"? Find out why, then repair it — without uploading it anywhere.
Reading the file…
How to use this tool
- Select the damaged PDF, or drag it onto the box above.
- It is checked first — header, end-of-file marker, cross-reference pointer, encryption and object count — and the findings are shown before anything is altered.
- Repair runs automatically: a lossless structural rebuild first, page-by-page recovery only if that fails.
- Download the repaired file. The panel tells you which method was used.
"Damaged file" from a PDF reader is a symptom, not a diagnosis. It can mean a broken cross-reference table (very repairable), a truncated download (partly recoverable), encryption (not a fault at all), or a file that was never a PDF. This tells you which before doing anything.
The specification
| First step | Diagnosis — header, EOF marker, xref, encryption, object count |
|---|---|
| Then | Lossless structural rebuild |
| Fallback | Page-by-page recovery |
| Honest limit | Missing bytes cannot be recreated |
| Limit | 100 MB |
Why uploads get rejected
Meeting the size is only part of it. These are the failures that actually come up:
- Acrobat says damaged but the file opens in Chrome — that is a broken cross-reference table, and it is the most repairable case.
- The file will not open anywhere and is much smaller than expected — that is truncation.
- It asks for a password. Not damage; remove the password in your reader first.
How it works
The file is diagnosed before anything is changed. The raw bytes are checked
for the %PDF- header at the start, the %%EOF marker at
the end, a startxref pointer, an /Encrypt dictionary,
and how many PDF objects are actually present. Those five checks distinguish the
common failures from each other, and you see the findings before repair runs.
Repair then makes two attempts, in order. The first is a structural rebuild: the document is parsed with lenient settings, its objects are copied into a fresh document, and a clean cross-reference table is written. This is lossless — text stays selectable, images keep their quality — and it fixes the most common cause of a PDF that will not open, which is a broken index rather than missing content.
If the structure is too damaged for that, the fallback renders each page it can reach and assembles those images into a new PDF. This recovers pages that would otherwise be lost, but it flattens them: text becomes part of an image. The result panel tells you plainly which method was used, because the difference matters to what you can do with the file afterwards.
One thing repair cannot do is invent data. If a download was interrupted, the missing bytes are not anywhere in the file and no tool can reconstruct them.
Who uses this
Anyone facing "There was an error opening this document", a blank PDF, or a file recovered from a failing disk or a failed transfer.
Other names for this tool
People look for this under several different names. If you arrived searching for any of the following, this is the right page — they all describe the same thing:
- pdf file damaged fix
- pdf will not open
- there was an error opening this document
- pdf says damaged
- cannot open pdf file fix
- broken pdf file repair
- pdf file is corrupted how to fix
- blank pdf fix
Frequently asked questions
What does "damaged file" actually mean?
Usually that the reader cannot find the cross-reference table telling it where each object sits. The pages are still in the file; the index is broken. That is exactly what a structural rebuild fixes.
It opens in Chrome but not Acrobat — why?
Chrome uses pdf.js, which rebuilds a broken index on the fly. Acrobat is stricter. Repairing writes a clean index so both accept it.
How long does repair take?
A structural rebuild is near-instant. Page-by-page recovery takes a few seconds per page, since each one is re-rendered.
Is this really free?
Yes — no account, no trial, no watermark and no cap on usage. It runs on your own device rather than our servers, so there is no cost for us to pass on.
Does it work on a phone?
Yes. The interface adapts to phone and tablet screens and everything runs in the browser, so there is no app to install.
Related tools
From other categories
Your files stay on your device. This tool runs entirely in your browser. No file is uploaded, transmitted, or stored. You can verify this by opening your browser's Network tab while using the tool.
Disclaimer. Specifications published by exam boards, governments and platforms change without notice. We verify and date every specification on this site, but you should always confirm against the official source before submitting an application. See our full disclaimer.