Count Pages in a PDF

What PDF Page Counter does

PDF Page Counter reads the selected document's page tree and reports the total number of PDF pages. It also displays the source filename and file size. The result can be downloaded as a compact JSON report when the count needs to be recorded or passed to another workflow.

The count refers to actual page objects, starting with the first page shown by an ordinary reader. Printed labels can differ: front matter may use roman numerals, an appendix may restart numbering, or a scan may have no visible numbers at all.

When to use this tool

A quick count is useful before printing, estimating review effort, entering split ranges, checking a submission limit, or confirming that a scan includes the expected number of sheets. It avoids waiting for every page thumbnail to render.

Use Metadata Viewer when you also need title, author, producer, or date fields. Use Password Status Checker when the document will not open through the standard parser.

• Confirm a scan includes every page from a paper packet.
• Check a page-limit requirement before submission.
• Plan custom ranges for splitting or extraction.
• Record document length in an inventory.

How to count PDF pages

1. Select the PDF you want to inspect.
2. Choose Count pages; no range or output settings are needed.
3. Read the page total, filename, and source size in the result panel.
4. Download the JSON report if the values need to be retained.
5. Compare the total with expected content and inspect the PDF when it differs.

Practical examples

A scanner operator expects a 52-page output from 26 duplex sheets. The counter reports 51, indicating that at least one side may be missing or that the expectation was wrong. The count identifies a discrepancy but cannot identify which page is absent, so visual comparison is still required.

An application portal accepts no more than 20 pages. A draft reports 23. The author can use Delete Pages for unneeded complete pages or revise the source, then count the new result again. Compression changes file size but does not make a 23-page document comply with a 20-page rule.

Tips for better results

• Compare the result with the expected physical sheet count for scans.
• Remember that one duplex sheet normally creates two PDF pages.
• Use the reported total when validating page-range inputs.
• Do not confuse file size limits with page count limits.
• Inspect content whenever the total is unexpected.

Planning and quality checks

Define the expected count independently before treating the tool result as confirmation. For scans, record the number of physical sheets, whether both sides were captured, and whether separator or blank pages were intentionally included. For a report, compare the total with its table of contents and final printed label. Differences can be legitimate, but they deserve explanation before distribution.

When the number feeds another process, keep the source version stable. A later merge, cover replacement, or blank-page deletion changes the total and can make an earlier JSON report obsolete. Record a meaningful filename, date, and preferably a file hash in systems that require traceability. The counter's JSON includes only filename, byte size, and page total; it does not uniquely identify a document or certify its completeness.

Quality control still requires visual sampling. Open the first and last page, inspect section boundaries, and check areas where a scanner may have double-fed sheets. A page count can confirm quantity but not sequence, legibility, orientation, or meaning. Treat it as one fast check within a document-control process, not a substitute for reviewing important content.

Repeat the count after any page-level edit and associate the new result with the edited version, not with the original filename alone.

Limitations and important details

The counter does not detect blank, duplicate, missing, or unreadable page content. A blank page object still counts as one page. It also does not explain printed page labels or identify nested attachments that contain their own PDFs.

A password-protected or damaged PDF may not be readable. The JSON report records only the basic values displayed and is not a certified inventory, hash, signature, or evidence of document completeness.

Frequently asked questions