You double-click a PDF and instead of a document you get a wall of red text. Maybe it's 'damaged and could not be repaired'. Maybe it 'requires a password you don't have'. Here's what those messages actually mean and the next step that usually fixes them.
'The file is damaged or corrupted'
This usually means the download didn't finish, an email gateway truncated the file, or a sync conflict scrambled it. First step: re-download from the original source. If that fails, ask the sender to re-share — preferably via a link rather than an attachment. If you have a half-working copy, open it in Flint and try saving a copy; the cleanup step often rescues partially-readable files. Truly corrupted PDFs aren't always recoverable, but most aren't truly corrupted.
'Password required to open'
Someone encrypted the file. If you set the password yourself, type it in. If a sender did, ask them — never guess random passwords. There are two layers: open passwords stop you opening the file at all, and permissions passwords restrict editing/printing. If you have the right and need to lift it, use unlock PDF. If you're locking your own file, password-protect PDF is the matching tool.
'Cannot extract embedded font' or 'font missing'
Whoever made the PDF didn't bundle a font with it, so your viewer is improvising. The document still opens but might look slightly off. It's a cosmetic issue, not a corruption issue. Workarounds: open in a different viewer, or re-export from the source app with 'embed all fonts' ticked. If the PDF prints fine, you can usually ignore this one entirely.
FAQ
Why does the same PDF open on my phone but not laptop?
Different viewers handle damaged files differently. Mobile viewers are often more forgiving. If your laptop reader refuses, try a browser (drag the PDF into Chrome) before assuming the file is broken.
The error mentions a missing plugin — what now?
Older PDFs sometimes need legacy plugins for forms or 3D content. Modern viewers usually offer to skip the unsupported parts. Click through; the rest of the document should still display.
Should I trust a PDF that throws errors?
Errors don't mean malware, but unexpected PDFs from unknown senders deserve caution. If you didn't expect it, verify the sender before opening, and never enable scripts the file requests.
Most PDF errors are boring once translated. Try opening the file in Flint — if it loads, the original viewer was the problem, not the document.