PDF Won't Open or Looks Corrupted? Here's How to Fix It

You double-click a PDF and get "There was an error opening this document." Or the file opens but every page is blank, or half the text is gibberish squares, or the reader spins forever. Frustrating, but almost never fatal — the PDF is usually recoverable, and often the fix takes under a minute once you know which of the five common problems you're actually looking at.

This guide is organized in order of frequency: check the first thing first, then the second, and so on. By the time you get to the bottom you've either fixed it or you're looking at one of the rare cases where the file is genuinely gone.

1. The file finished downloading, but not really

This is by far the most common cause and the easiest to miss. The download completed as far as your browser is concerned, but a hiccup on the server side sent you a partial file. Some PDF readers refuse partial files outright; others open them and just show blank pages after the truncation point.

Check the file size against whatever the sender told you it should be. A 12 MB report that lands at 4 MB is truncated. If you can, re-download it — over a different network if you're on flaky wifi. Cloud storage links (Drive, Dropbox, WeTransfer) sometimes serve a corrupted preview file; downloading the raw file explicitly (right-click → Download) usually fixes it.

2. The PDF is password-protected

A reader that supports password prompts (Acrobat, Preview, Chrome's built-in) will ask for the password. Lightweight readers and some browser preview widgets just fail silently and show "cannot open." If you have any reason to think the file is protected — it came from a bank, a lawyer, an HR portal, a government form — try opening it in a different reader that will actually surface the prompt.

Once you have the password, you can remove protection so it opens cleanly everywhere by running the file through Protect / Unlock PDF in unlock mode. The unlocked copy opens in every reader on Earth.

3. Your reader can't handle the PDF's features

PDF is a big, sprawling standard. Not every reader supports every feature. Common examples: PDFs with embedded 3D models (common in CAD exports), interactive forms built with newer XFA syntax, or PDFs generated with unusual color profiles that older readers can't render.

Symptoms include: pages open but appear blank, text renders as random squares (a font-embedding issue), or the reader complains about an unsupported version. The fix is almost always the same — open the PDF in a modern browser (Chrome, Edge, Firefox) which uses its own permissive rendering engine, then print-to-PDF to produce a clean, universally-compatible copy. It's a five-second operation and the resulting file works everywhere.

4. Weird text encoding or missing fonts

You open the file and the text is there, but instead of letters you see rectangles or random glyphs. The PDF was generated with fonts that were referenced but not embedded, and your reader doesn't have those fonts installed. Older Word-to-PDF workflows on Windows are notorious for this.

The fix: ask the sender to re-export with "embed all fonts" enabled. If that's not possible, running the file through OCR extracts the text as plain characters — you lose formatting but you can at least read and copy the content. Then rebuild a proper PDF from the extracted text via Text / Markdown to PDF.

5. The PDF is actually damaged

This is the rare case, and it usually happens for a specific reason: the file was cut off during upload to a broken form, a crashed application saved a half-written PDF, or someone opened and saved it in a program that mangled the internal object table.

Signs it's real corruption: the file is roughly the right size, no password prompt appears, multiple readers all fail. In that case:

1. Try opening it in a browser. Chrome and Firefox both have permissive rendering engines that tolerate a lot of broken PDFs and will happily render what they can.
2. If the browser opens it, use its "Print → Save as PDF" to produce a fresh, clean copy. This regenerates the file structure from scratch and drops whatever was broken.
3. If the browser also fails, try opening it in an image viewer that supports PDF (Preview on macOS, or a PDF-aware viewer on Windows). Sometimes one specific page is broken and the rest render fine, in which case you can export the working pages as images and rebuild a partial PDF.
4. If nothing works, ask the sender to regenerate the file from the source (Word, InDesign, whatever it was exported from). Truly-corrupt PDFs generally aren't repairable — the internal structure is a graph of objects, and once the offsets are wrong there's no way to reconstruct them without the original.

How to stop this happening to files you send

Two habits eliminate most of these problems on your end. First, always embed fonts on export — every modern PDF export has this option and it costs almost nothing in file size. Second, if a file is large, compress it before sending: a smaller file completes downloads reliably, and shorter transfers reduce the chance of network truncation.

Both are one-tool jobs. Compress PDF handles the size problem locally in your browser, and re-exporting with fonts embedded is a checkbox in every serious authoring tool.