PDF

PDF Won't Open: How to Fix a PDF That Refuses to Load

A PDF that won’t open is stressful, particularly on deadline. The good news is that most of these files are recoverable with minimal effort — a re-download or a different reader resolves the majority of cases before any repair tool becomes necessary. This guide walks the fixes in order from zero-effort diagnostic through command-line repair, and flags honestly when a file is unlikely to be saved.

Quick fix

The first three steps below resolve most “won’t open” cases. Do them in order before reaching for a repair tool.

  1. Re-download or re-request the file. Interrupted downloads are the single most common cause of broken PDFs. If the file came from a website or email attachment, download it again. In many cases the new copy opens without issue.
  2. Open the file in a different reader. Try Chrome, Firefox, or Edge by dragging the PDF onto the browser window. On macOS, open with Preview. Different engines tolerate different structural oddities, and a file Acrobat rejects often opens elsewhere.
  3. Check the file is actually a PDF. Every valid PDF starts with the bytes %PDF- followed by a version number. Open the file in a plain text editor and check the first line. If it starts with <!DOCTYPE html> or is empty, the file isn’t a PDF at all — it’s likely a saved error page or a failed download stub. Request a fresh copy.

If the file still won’t open after those three steps, move to the repair strategies below.

If that didn’t work

Diagnose the file with qpdf

Before running repair, check what qpdf reports:

qpdf --check input.pdf

Exit code 0 means qpdf found no structural problems — the issue is likely in rendering, not structure, and repair tools won’t help. Exit code 2 means the file is damaged beyond qpdf’s ability to process it. Exit code 3 means damage was found but qpdf could recover from it, which is the case where repair is likely to succeed.

Run a structural repair with qpdf

The default repair command reads the file, rebuilds the cross-reference table, and writes a clean output:

qpdf --linearize input.pdf output.pdf

If qpdf reports warnings but produces an output file, inspect it before discarding the original. A repaired file is usually readable, but the warnings sometimes indicate content-level issues that a structural fix can’t address.

If --linearize isn’t enough, try a more aggressive rebuild:

qpdf --object-streams=generate input.pdf output.pdf

This rewrites object stream structure from scratch, which fixes a wider range of problems than --linearize alone. It changes the byte-level structure of the file, so avoid it for workflows that require preserving the original structure — digital signature verification, forensic analysis, anything where the file’s exact bytes matter.

See the complete guide to qpdf for the full set of repair and transformation recipes.

If qpdf reports the file as unrecoverable but a browser can still render it, the browser’s print pipeline can produce a fresh structurally-valid PDF from what it renders:

  1. Open the file in Chrome, Firefox, or Edge by dragging it onto the browser window.
  2. Open the browser’s print dialog (Ctrl+P or Cmd+P).
  3. Choose “Save as PDF” or “Microsoft Print to PDF” as the destination.
  4. Save to a new filename.

This is not a repair in any structural sense — the output file is a rendered copy of what the browser showed. Form fields, annotations, embedded attachments, and accessibility tagging are all lost. It works when the structure is broken but the content streams are intact enough for the browser to draw them.

Advanced recovery

If the strategies above have failed and the file still won’t open, Ghostscript’s re-rendering approach sometimes salvages files that structural tools cannot. Ghostscript re-interprets the PDF and emits a new one from scratch:

gs -o recovered.pdf -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress input.pdf

Ghostscript succeeds on some files qpdf cannot because it doesn’t depend on the original structure being parseable. The cost is significant. Form fields, annotations, digital signatures, bookmarks, and tagged accessibility structure are commonly lost in the re-render. The result is a file that looks right on screen but has been stripped of anything that isn’t visual content. Use it only when the alternatives have failed and the visual pages are what you need to preserve. See the complete guide to Ghostscript for PDF recovery for the caveats in full.

If Ghostscript also fails, the file is likely unrecoverable with general-purpose tools. Commercial recovery tools like Stellar Repair for PDF and Wondershare Repairit use the same underlying techniques with a GUI wrapper; they may produce a result but will not exceed what the free tools can do on a genuinely damaged file.

Why this happens

A PDF that won’t open has usually lost the structural integrity a reader depends on to navigate the file. PDFs are built as a collection of numbered objects — pages, fonts, images, metadata — stitched together by a cross-reference table (the xref) that records where each object begins. Readers open the xref first, then follow its pointers to build the document. When the xref is wrong, even by a single byte, the reader can’t find anything, and the file appears completely broken even when most of the content is still intact.

Specific causes, in rough order of frequency:

Interrupted download. The last few kilobytes never arrived, taking the trailing xref with them. This is by far the most common cause, which is why re-downloading resolves so many cases before repair tools come out.

Transfer corruption. An intermediate step — a flaky connection, an email gateway that mangled encoding, a USB stick that lost bytes on copy — altered the file. Even a single byte change can invalidate the xref.

Improper generation. The tool that created the PDF produced a technically-invalid file. Scanners, OCR tools, and casual PDF libraries written without rigorous adherence to the PDF specification sometimes emit files that Acrobat’s lenient repair engine will open but stricter readers reject.

Storage errors. The file is intact on the server but the local copy was corrupted by a failing drive or bad flash memory. Re-obtaining the file from the source resolves this.

Reader-side issues. The file is fine; the reader has a problem. Updating Acrobat, using the Help menu’s Repair Installation option, or trying a different reader distinguishes this from genuine file corruption.

For a deeper explanation of PDF structure and what repair tools actually do to the bytes, see the PDF repair complete guide.

Preventing this in future

Most “won’t open” problems trace back to transfer and generation issues, both of which have straightforward prevention.

Verify file integrity on important downloads. If a source provides a checksum (SHA-256 or MD5), compare it against your downloaded copy. A mismatch means the download was corrupted and you need a fresh one before you even open the file.

Avoid editing PDFs with multiple different tools in sequence. Each editor may add its own incremental update, and conflicting update chains produce files that no single reader can resolve correctly. If a PDF will pass through several stages of editing, flatten it to a clean single xref between stages — opening and saving through qpdf does this.

Keep backups of PDFs that matter. Cloud sync services with version history (OneDrive, Google Drive, Dropbox) let you roll back to a working version if the current file corrupts. For business-critical documents, a versioned backup is cheaper than any repair attempt.

If the PDF opens but the pages are blank or black, the problem is in rendering rather than structure — see the guide to PDFs that open blank or black for the fix path. If the PDF came from an email attachment, transfer corruption is almost certainly the cause; the email-specific guide covers that diagnostic sequence in full. If the reader displays a specific error message — “file is damaged and cannot be repaired” or similar — the error-specific guides give targeted fixes based on the exact wording.

Last verified: April 2026