PDF Page Counter

Counting locally

Page count lives in the PDF's internal page tree, on the root pages node. Reading it requires parsing the document structure but not rendering anything, so it is fast even for large files and works entirely in the browser. The file is read from your device and never transmitted, which matters because the documents people most often need to count are contracts, medical records, statements and submissions.

Why counts sometimes disagree

A viewer's page count and a print dialog's page count can differ. A PDF may contain page-level scaling, booklet imposition, or a print setting that places multiple logical pages on one sheet. Some documents also carry an optional page-label structure so displayed numbers run i, ii, iii before 1, 2, 3, meaning the label on the page does not match its index in the file.

Encrypted and damaged files

A PDF encrypted with an owner password can usually still be parsed for structure, since the restriction is on permissions rather than reading. One encrypted with a user password cannot be opened at all without it, and no page count is available. Linearised or incrementally updated PDFs contain multiple cross-reference sections, and a truncated download often keeps the earlier ones, so a damaged file may parse successfully and report a stale count from an earlier revision.

Page count as a document signal

Where page count matters it usually matters precisely: court filings, academic submissions and printing quotes all have hard limits. Verify against the specific requirement rather than assuming, since some rules count only the body and exclude appendices, exhibits or the bibliography.

Counting pages is not reading them

A page count says nothing about whether the pages contain extractable text. A scanned document is a sequence of images and reports its page count perfectly while containing no machine-readable text at all. If you need the words rather than the count, the file needs OCR first.

Related tools

• User Agent Parser — Parse a User-Agent string into browser, engine, operating system and device. Explains why UA strings are unreliable and what to use instead.
• QR Code Generator — Generate QR codes for URLs, text, Wi-Fi and contact details. Adjustable error correction and size, produced entirely in your browser.
• Credit Card Validator — Validate a card number with the Luhn algorithm and identify the issuing network from its prefix. Runs locally, nothing is transmitted.
• Text Case Converter — Convert text between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case and sentence case. Runs entirely in your browser.