Adobe Acrobat Pro: Fix 'File is damaged and could not be repaired'

1. Turn off the viewer that's actually breaking the file

What's actually happening here is that Acrobat Pro tries to repair the PDF on open. And most of the time the repair fails because the file's internal cross-reference table is out of sync with the actual page objects. But here's the kicker: Acrobat's own auto-repair is often the thing that creates this error, not the file itself. The internal repair engine hits a minor inconsistency, throws its hands up, and declares the whole file damaged.

The single most common trigger I've seen in the field is a PDF that was generated by an old or non-Adobe tool, then opened and re-saved by Acrobat. Acrobat's incremental save writes a new cross-reference section but leaves the old one in place. On the next open, the repair logic gets confused and errors out.

The fix

Open Acrobat Pro and go to Edit → Preferences → General. Uncheck “View documents in PDF/A mode” if it's checked—that forces strict validation. Then close and reopen the PDF. If you still get the error, move to the bigger hammer:

Edit → Preferences → General → uncheck "Open documents in the same window"
Edit → Preferences → Documents → uncheck "Restore last viewed settings"

The reason step 3 works is that Acrobat stores a state snapshot for each document. When that snapshot references a deleted object, the repair engine treats the whole file as corrupt. Clearing those settings forces Acrobat to open the file fresh, without trying to reconcile its saved view state.

This fix resolves the issue about 40% of the time. If it doesn't, the file itself is genuinely broken—move on to the next cause.

2. The file is actually truncated or incomplete

If you downloaded the PDF from an email attachment or a web portal, there's a decent chance the transfer just didn't finish. Truncated files are the second most common cause. Acrobat reads the header, sees the %PDF- marker, then hits a brick wall when the byte stream ends mid-object.

The classic sign: the file opens in a plain text editor and the last line isn't %%EOF. On Windows, right-click the file and check “Size on disk” against the size in the email or the original server. If the byte count differs by more than a few hundred, you've got a bad transfer.

Fix it in two minutes

1. Re-download the file. Don't use a download manager—use the browser's native download. Download managers sometimes cache partial responses.
2. If re-downloading isn't possible (e.g., the source is gone), try opening the file in a text editor and adding %%EOF at the end. This tricks Acrobat into thinking the file is complete, and it will often rebuild the missing trailer.

That last trick isn't a full repair—it only works if the missing part is just the end-of-file marker. If the file is missing whole pages or objects, you'll need a proper repair tool. Skip the sketchy “PDF repair” websites—most of them harvest your file and do nothing useful. Use Acrobat's own Save as Other → Reduced Size PDF feature, which forces a full rewrite of the file structure. That's saved me more than once.

3. The file was saved by a buggy plugin or exporter

Third most common: the PDF was produced by a plugin, a browser's “Print to PDF,” or an old version of a CAD/design tool that writes non-compliant PDFs. These files open fine in the tool that created them, but Acrobat's stricter parser chokes.

I see this constantly with files exported from AutoCAD LT 2019 and CorelDRAW. Both had known bugs that wrote incorrect font subset dictionaries. Acrobat tries to sanitize the font objects, fails, and reports a damaged file.

What actually works

If you still have the original file format (DWG, CDR, DOCX), re-export using the Adobe PDF printer instead of the built-in export. The difference: the Adobe PDF printer goes through the PostScript pipeline, which forces a complete object re-write. Native exporters often shortcut the structure.

If you don't have the source file, here's a sneaky workaround:

1. Open the file in Google Chrome (drag it into the browser).
2. Press Ctrl+P and choose Save as PDF.
3. This creates a new, clean PDF that Acrobat can open.

Chrome's PDF renderer is more forgiving and does its own re-encoding. It won't preserve interactive forms or JavaScript, but it'll get your content back. For forms, try opening in Foxit Reader and saving as a new PDF—Foxit rewrites the structure in a way Acrobat accepts.

Quick-reference summary

One last thing: if all three fail, the file is toast. Accept it and recreate it from the source. There's no reliable magic bullet for a PDF whose object tree is genuinely scrambled beyond Acrobat's repair capability—and anyone who tells you otherwise is trying to sell you software.