PDF Error: 'This File Cannot Be Opened Because It Has No Pages'

Error message: There was an error opening this document. This file cannot be opened because it has no pages.

Acrobat’s "This file cannot be opened because it has no pages" is one of the more honest error messages PDF readers produce. It means exactly what it says: the file’s internal page list is empty or unreachable, and there are no page objects for the reader to display. This is different from most PDF errors, where the content exists but the index is broken — here, the pages themselves are missing.

That distinction matters because it determines what’s actually possible. Repair tools can rebuild a damaged index when the underlying objects still exist. They cannot conjure pages that aren’t in the file.

Quick fix

1. Check whether you can re-create or re-obtain the file. Most files producing this error were created by scanner software that wrote an invalid PDF — particularly older HP and other consumer-scanner drivers. If you still have the source (paper documents, original Word file, web page), re-creating the PDF is far faster than trying to recover one that has no recoverable content. The Adobe community’s standard answer to this error, from experienced PDF developers, is: re-scan or re-export.
2. If the file came from someone else, ask them to resend it. A new export from the source application usually produces a clean file even when the original is unrecoverable.
3. Confirm the diagnosis before spending time on repair attempts. Open Terminal (macOS, Linux) or Command Prompt (Windows) and run pdfinfo input.pdf (install with brew install poppler on macOS, apt install poppler-utils on Linux, or use the Windows binaries from the poppler-windows project). If the output shows Pages: 0, the file genuinely has no pages — repair tools won’t help.

If that didn’t work

Some files report this error not because pages are missing, but because the /Pages tree in the PDF catalog is malformed and the reader can’t follow the references. This is rare but does happen, particularly with files that have been through aggressive “repair” attempts.

To check whether your file is in this category, run qpdf’s structural check:

qpdf --check input.pdf

If qpdf reports a damaged cross-reference table and successfully reconstructs it, then attempts to find the page tree, the output messages will tell you whether the page references are present-but-broken or genuinely absent. If qpdf reports objects exist but the catalog can’t reach them, try a structural rebuild:

qpdf --linearize input.pdf output.pdf

This forces qpdf to scan for objects and rebuild the catalog from scratch. If page objects exist somewhere in the file, this sometimes recovers them. If qpdf reports “no pages found” or the output file still produces the same error, the page data is not in the file.

If qpdf cannot help, try opening the file in Foxit Reader or Chrome. Both are occasionally more lenient than Acrobat on edge cases involving malformed page tree references. If neither displays anything, the file genuinely has no displayable content.

Advanced recovery

For files where you suspect content exists but is inaccessible, you can check whether any text is recoverable using poppler’s pdftotext:

pdftotext input.pdf -

The - directs output to the terminal. If text comes out, that text exists somewhere in the file even if page objects are broken. This is rare in this error class but worth a 10-second check before giving up.

You can also inspect the file directly. Open it in a hex editor or text editor and search for obj markers — patterns like 5 0 obj indicate object definitions. A PDF with no /Page objects (you’ll see /Type /Catalog, /Type /Pages, but no /Type /Page for individual pages) confirms the diagnosis: there is nothing to recover.

The DataNumen and similar commercial PDF repair tools sometimes produce a file with this error as their output — meaning the original file had problems that the tool tried to repair, but the result is a file that’s even less recoverable than what you started with. If a “repaired” file gives you this error, treat the original (even if it was broken) as more valuable than the repair output.

Why this happens

The most common causes, in order of frequency:

Scanner software that wrote an invalid PDF. Older HP all-in-one scanners are repeatedly cited in Adobe community threads as producing files with this error. Other consumer scanners with bundled “save as PDF” features have similar bugs. The scanner reports success, the file appears in the destination folder, but the PDF doesn’t contain valid page objects — only metadata and an empty page tree. Files in this category were never recoverable; they were broken at the moment of creation.

An interrupted save or write operation. If the PDF was being saved when the application crashed, the system shut down, or the disk filled up, the file may contain headers and structural metadata but no page content. The file size is usually noticeably smaller than expected.

Aggressive “repair” by another tool. Some commercial PDF repair tools, when given a severely damaged input, produce output that is technically a valid PDF (passes header checks) but contains no page objects. The tool reports success because it produced a parseable file; the user sees this error when they try to open it.

Corruption that affected the page tree specifically. Rare, but possible: storage media errors or specific byte-level damage that destroyed the /Pages object while leaving the rest of the structure intact. In these cases, page content may exist as orphaned objects in the file, and qpdf’s reconstruction can sometimes recover them. This is the only scenario where structural repair has any chance of success.

Preventing this in future

For documents you create from scans, prefer scanning software with a known-good PDF output engine — modern Adobe Scan, Microsoft Office Lens, ScanSnap Home, or NAPS2 (free, open source) all produce structurally valid PDFs. If you must use a manufacturer’s bundled scanner software, scan to image format (PNG or TIFF) first and convert to PDF separately using a reliable converter such as ImageMagick, the img2pdf Python tool, or LibreOffice Draw.

Verify newly-scanned PDFs immediately by opening them. The cost of catching a bad scan while the paper is still in front of you is essentially zero; the cost of finding it weeks later when the paper has been recycled is total.

For high-value documents, save in two formats — PDF for portability, plus the source format (Word, image archive, scan archive) for recoverability. PDF was designed as an end-format for distribution, not a master format.

Related issues

If your scanner produced the file but you can also see scanned content (it’s just not searchable), the problem isn’t this error — see scanned PDFs without searchable text. If Acrobat shows the broader "file is damaged and could not be repaired" error rather than the specific no-pages variant, see the guide to that error. For the underlying explanation of how PDF page structure works and where it can fail, the PDF repair pillar covers the format in depth.

Last verified: April 2026