10 Common PDF Problems and How to Fix Them
After enough years working with PDFs, you stop seeing weird new problems and start recognising the same ten or so coming back in different costumes. Here are the recurring ones, ordered roughly by how often they hit, with the most reliable fix for each. None of these require advanced tools.

1. The PDF will not open at all
Symptoms: a "file is damaged or could not be opened" error, or the reader simply hangs on a blank page. Causes, in rough order of likelihood: the download was interrupted; the file was renamed without keeping the .pdf extension; the file is actually an HTML error page that was saved with a PDF name; or the file was generated by software that produced invalid PDF structure.
Fix: first, redownload the file from the source. About half of "broken PDF" cases are partial downloads. Second, open the file in a different reader — Adobe Acrobat, Foxit, your browser's built-in viewer (Chrome and Firefox both have one) and Preview on macOS implement the spec slightly differently, and one of them will often open what the others reject. Third, check the file size: if it is suspiciously small (under 1 KB), it is almost certainly an error page rather than a real PDF.
2. The PDF opens but pages are blank or garbled
Symptoms: the file opens, page count is correct, but the content is missing, blocks of text are replaced by squares, or graphics look corrupted. Cause: a font referenced in the PDF was not embedded, and your reader is substituting an incompatible fallback. Less commonly, an image stream is genuinely corrupted.
Fix: open the file in a different reader (the substitution behaviour varies). If the issue is consistent, contact the document's author and ask for a version with embedded fonts. If you produced the file yourself, re-export and check the "embed all fonts" option. For corrupted images, you usually need the source.
3. The PDF prints differently from how it looks on screen
Symptoms: text is cropped at the edges, colours look wrong, fonts shift, or page elements move. The most frequent cause is that the document was designed for one paper size (US Letter, for example) and is being printed on another (A4), and the printer driver is silently scaling.
Fix: in the print dialog, find the page size or scaling option and set it explicitly to "Actual size" or "100%" rather than "Fit to page". If colours are wrong, check whether your printer is in colour mode and whether the driver is using the correct ICC profile. If text is cropped, the document may have content outside the printable area, which most home printers cannot reach — adjust the source margins, not the print scaling.
4. "This PDF is password-protected" — but you do not know the password
Symptoms: opening the file prompts for a password you were never given. There are two cases here, and they are very different. Case A: the PDF requires a password to open at all (a "user password"). Without it the content is encrypted and inaccessible — there is no legitimate way to bypass this, and any tool offering to do so is either ineffective or relies on guessing weak passwords. Case B: the PDF opens, but printing, copying or editing is restricted (an "owner password"). This is much weaker and most readers will let you remove it if you have the legal right.
Fix: for case A, the only reliable path is to contact whoever sent you the file and ask. For case B, opening and re-printing-to-PDF in your operating system's print dialog typically produces an unrestricted copy — but only do this if you have a legitimate right to use the document.
5. Pages are out of order or upside down
Symptoms: the document opens but the page sequence is wrong, or scanned pages are rotated 90° or 180°. This usually means the document was assembled from multiple sources, or scanned with mixed page orientation.
Fix: nearly every PDF reader exposes a "rotate page" command (or right-click on the page thumbnail in the sidebar). For reordering, our merge tool lets you load a single PDF, drag pages into the order you want, and save the result. Some readers also let you drag thumbnails directly to reorder.
6. The file is huge for the amount of content
Symptoms: a 10-page document is 80 MB. Cause: oversized embedded images, unsubsetted fonts, or accumulated revision history. We covered the diagnosis in detail in our compression article.
Fix: downsample images to 150–200 DPI for screen reading, ensure fonts are subsetted, and run a "save as optimized" pass. For scans, dropping to grayscale or B&W can shrink the file dramatically.
7. You cannot copy text from the PDF
Symptoms: selecting text either grabs nothing, grabs gibberish, or grabs the right shape but the wrong characters. Two causes are common. The PDF may be a scan — the "text" is really pixels of text and there is nothing to copy. Or the PDF was produced by older software that mapped fonts non-standardly, so the underlying character codes do not match the visible glyphs.
Fix: for scanned PDFs, run OCR — Adobe Acrobat, ABBYY FineReader and many free tools can produce a "searchable PDF" with an invisible text layer over the scan. For the bad-mapping case, recent versions of Acrobat and Foxit have improved heuristics; if those still fail, OCR-ing the file as if it were a scan is sometimes the cleanest workaround.
8. The file shows up as 0 KB or "missing" after download
Symptoms: the download seemed to complete but the file is empty, or the OS reports it as missing. Cause: nearly always an antivirus or browser security feature deleted the file mid-stream because it was misidentified as a threat, or the disk filled up.
Fix: check your antivirus quarantine and your browser's downloads page for a blocked-download notice. Confirm the disk has free space. Try downloading again — temporary network errors can also produce empty files, especially over flaky mobile connections.
9. Hyperlinks in the PDF do not work
Symptoms: clicking a link in the PDF does nothing, or opens the wrong destination. Causes: the source document had Word-style cross-references that did not export as live links; the PDF was generated by a "print to PDF" path that flattens hyperlinks; or the reader is in a security mode that blocks external URLs.
Fix: on the production side, export rather than print to PDF, and verify "create hyperlinks" or equivalent is enabled in the export options. On the consumption side, check your reader's preferences for a "trusted hyperlinks" or "allow external content" setting and enable it if appropriate.
10. The form fields will not save
Symptoms: you fill in a fillable PDF, save it, reopen it, and all the fields are blank again. The form was saved as a "static" form rather than a fillable one, or the reader is missing the right permissions to save form data.
Fix: first, confirm the form is genuinely fillable by trying it in a different reader (Adobe Reader supports form-data persistence everywhere; some lighter readers do not). If the source document is yours, ensure you exported as a "PDF Form" rather than a flat document. If you are filling someone else's form, an alternative is to print the form to a fresh PDF — the printed copy bakes your entries into the page content permanently.
Bonus: a couple of "fixes" you should be sceptical of
Two patterns float around online forums that we recommend treating with caution.
- "Online PDF repair tools." Some legitimately reconstruct broken PDFs; many are simply uploading your file to a server you know nothing about and either succeeding by accident or charging a fee for a no-op. If you must use one, do not feed it sensitive content.
- "Password remover" tools that work on user-passworded PDFs. If a tool claims to instantly remove the open-password from any PDF, it is either guessing very weak passwords from a dictionary, or lying about what it does. Real PDF user-password encryption with a strong password is not bypassable in practice.
The general principle
Most PDF problems fall into one of three buckets: the file itself is broken (corruption, partial download), the file is fine but your reader can't render it the way the author intended (font substitution, scaling, security restrictions), or the file is fine but the workflow is wrong (asking for editable text from a scan, expecting form data to persist in the wrong reader). Diagnosing which bucket you are in is half the fix. The other half is usually a different reader, a fresh download, or going back to the source.