How to Open a Corrupt PDF on Mac

A corrupt PDF on a Mac shows up in a few painful ways: Preview displays a blank page, Acrobat warns of damage, a third-party reader refuses to open, or specific pages render as garbage. The file is sometimes salvageable, sometimes not. This guide walks through the practical recovery options on macOS.

What "corrupt" means

A PDF can be corrupt in several ways:

Truncated, file was cut off during download or save
Header missing, file does not start with %PDF-
Xref damaged, cross-reference table at end is broken
Object corruption, specific objects malformed
Encrypted with lost password, technically not corrupt, but unreadable
Wrong format, file with .pdf extension is actually something else
Hardware-level corruption, bits flipped on storage

The fix depends on which kind.

First check: is it really corrupt?

Quick checks:

Try a different reader. Preview, Acrobat Reader, Foxit, Chrome's built-in viewer. If one opens it, the file is fine.
Try downloading again if it came from the web.
Check the file extension, .pdf should be a PDF. If the file is much smaller than expected (e.g., 8 KB), it may be HTML, an error message, or truncated.

Often the file is fine; the reader has issues.

Tool 1: Preview

Preview is built into macOS. To try:

Right-click the PDF → Open With → Preview
If Preview opens it, you're done

Preview is more forgiving than Acrobat for some kinds of damage.

Tool 2: Adobe Acrobat Reader

If Preview fails:

Install Acrobat Reader (free)
Open the file
Acrobat may show "repair" prompt, accept

Acrobat has stronger repair capabilities for damaged files.

Tool 3: Browser

Drag the PDF into Chrome, Safari, or Firefox. The built-in PDF viewers sometimes open files that dedicated readers refuse.

Tool 4: qpdf

For deeper repair, install qpdf via Homebrew:

brew install qpdf

Then try:

qpdf input.pdf repaired.pdf

qpdf's default behavior includes attempting to rebuild the xref table, this fixes many corruption issues silently. See qpdf introduction.

For stubborn cases:

qpdf --suppress-recovery=false damaged.pdf fixed.pdf

Tool 5: Ghostscript

If qpdf fails:

brew install ghostscript
gs -o repaired.pdf -sDEVICE=pdfwrite damaged.pdf

Ghostscript re-renders the PDF, which can recover from issues qpdf cannot. The downside: it is slower and re-renders rather than truly repairs (so the result may be slightly different from the original).

See Ghostscript introduction.

Tool 6: mutool clean

MuPDF's mutool can clean PDFs:

brew install mupdf-tools
mutool clean -ggg damaged.pdf cleaned.pdf

The -ggg flag enables aggressive cleanup. Often handles cases other tools miss. See MuPDF introduction.

Tool 7: pdftk

pdftk via Homebrew:

brew install pdftk-java
pdftk damaged.pdf output repaired.pdf

Often the simple repair works for moderate corruption. See pdftk introduction.

Tool 8: Online tools

Several web services offer PDF repair:

PDF2Go, has repair tool
iLovePDF, repair option
Smallpdf, repair feature
DocFly, repair

These often help but require uploading the file. For sensitive content, prefer offline tools. See are online PDF editors safe.

Tool 9: PDF specialists

If standard tools fail:

PDF Studio by Qoppa has a repair feature
Adobe Acrobat Pro has more sophisticated repair than Reader
iSkysoft PDF Repair, Stellar Repair for PDF, dedicated repair tools (paid)

For business-critical documents, these may be worth the cost.

Recovery for specific scenarios

Truncated file. If the file is shorter than it should be, the end (xref table) is missing. qpdf can often rebuild. If the truncation is severe (only the first few KB of a large file), recovery may be impossible.

Header missing. Open the file in a text editor. If it does not start with %PDF-1.something, the header is corrupt. Some text editors show it; replace if you can.

Encrypted with lost password. Not actually corrupt. You need the password. There is no decryption shortcut for AES-256. For files you own with permissions but no user password, qpdf may help.

Wrong format. Open in a text editor. If it looks like HTML or an error page, it is not actually a PDF. Re-download.

Specific page rendering wrong. The file is mostly fine, one page bad. Try opening in different readers; some are more forgiving. Or extract good pages with qpdf and skip the broken one.

A practical sequence

For a corrupt PDF on Mac:

Try Preview, sometimes works
Try Acrobat Reader, auto-repair attempts
Try a browser, alternative renderer
qpdf input.pdf output.pdf, silent rebuild
mutool clean -ggg input.pdf output.pdf, aggressive cleanup
gs -o output.pdf -sDEVICE=pdfwrite input.pdf, re-render
Try an online repair service
Try dedicated repair software

If none work, the file may be unrecoverable. Restore from backup.

Salvaging readable content

If the PDF cannot be fully repaired:

Extract text: pdftotext damaged.pdf - may work even if the PDF won't fully render
Extract images: pdfimages damaged.pdf images may recover embedded images
Render pages individually: mutool draw -F png damaged.pdf may render some pages even if others fail

For pdftotext and pdfimages, see poppler-utils introduction.

Prevention

Reduce future PDF corruption:

Reliable downloads, verify hash if available
Reliable storage, RAID, cloud sync with versioning
Backups, see how to archive PDFs long-term
Avoid edits in unreliable tools that corrupt PDFs on save
Validate important PDFs after generation

Common gotchas

File partially downloaded. Check size against expected.

Encryption confused for corruption. Try the password if available.

Reader-specific issue. Open in three different readers; if all fail, it's the file.

Backup file is also corrupted. If primary and backup both fail, the corruption may predate the backup. Restore from older backup.

Recovery makes things worse. Always work on a copy; do not overwrite the original until recovery succeeds.

Recovered file has different content. Ghostscript re-renders, which can introduce subtle differences. Compare to original visually.

Encrypted PDFs may need decryption first. If qpdf or other tools fail on an encrypted file, decrypt first.

Cloud-side recovery

If the PDF lives in iCloud Drive, Google Drive, OneDrive, or Dropbox:

Check version history in the cloud service. You may be able to restore an earlier version.
Trash / Bin, recently deleted versions may be recoverable.
Some services have specific document recovery tools.

For these scenarios, the corruption may have happened during sync. Cloud version history is your friend.

Hardware-level corruption

If the storage media itself is failing:

Time Machine restore if you have it
Cloud backup restore
Disk recovery services for severe failures (expensive)

A corrupt PDF on a failing drive is a symptom of bigger problems. Address the drive, not just the file.

Practical recipe

For a corrupt PDF found on your Mac:

Make a backup copy of the corrupt file
Try qpdf input.pdf output.pdf first
If that fails, try Ghostscript and mutool
If those fail, try dedicated repair software
If all fail, restore from backup
If no backup, salvage whatever content is recoverable (text, images)

For high-stakes content where no backup exists, professional recovery services exist for paid recovery.

Takeaway

Corrupt PDFs on Mac are often recoverable with the right tools: qpdf, mutool, Ghostscript, and Adobe Acrobat each have different strengths. For minor corruption, the basic qpdf repair handles 80% of cases. For severe corruption, professional tools may help. The strongest defense is prevention: reliable storage, regular backups, and not editing important PDFs in unreliable tools. For browser-based PDF operations on Mac alongside recovery, Docento.app handles common tasks. For related topics, see how to recover a corrupted PDF, qpdf introduction, and Ghostscript introduction.