PDF page count — the one number every PDF tool needs, and why word count + page size come free
Knowing how many pages are in a PDF is one of the most common things people ask about a file. Print quotes are per-page. Translation quotes are per-word. Invoicing is often per-page. Reading time is derived from word count. All of these answers come from a single parse of the document, which is why our page-count tool also surfaces word count, reading time, page dimensions, and mixed-orientation warnings at the same time. Here is how the count is computed, what "page" really means in PDF terms, and the four adjacent metrics that come along for free.
What "page count" actually means in PDF
A PDF's pages are organized in a tree structure called the /Pages dictionary. The top-level /Pages dictionary has a /Count field — the page count. PDF readers display this number in their status bar. The page-count tool parses the same /Pages dictionary and surfaces the same number.
The number is unambiguous: pages that are hidden in the reader's UI still count, pages with no visible content (blank pages) still count, pages at non-standard sizes still count. One physical page in the file = one count, regardless of what is on it. The PDF specification has been stable on this since version 1.0 (1993), so every PDF you have ever encountered reports its page count consistently.
Why word count comes free with the page count
Computing word count requires extracting every page's text — which the tool already does once for the page parse. We split the extracted text on whitespace and count the resulting tokens. The result is comparable to what Microsoft Word reports for the same document text. Two-page documents typically run 400-900 words; ten-page reports run 2,000-4,000 words; the variance comes from font size and layout density.
Scanned PDFs return 0 for word count because there is no extractable text — page count is correct, but word count cannot be computed from images. Run AI · OCR first to add a searchable text layer; the page-count tool will then surface the OCR'd word count too.
Four adjacent metrics that come along
Same single parse, four extra answers:
- Page dimensions per page. Each page's width × height in points (and inches). Useful when you suspect mixed page sizes — the tool flags this explicitly.
- Page size classification. Letter, A4, Legal, A3, A5, Tabloid, or Custom. Helps you know at a glance whether the document will print on standard paper without resizing.
- Orientation per page. Portrait or landscape. Mixed-orientation documents are flagged with a warning because they often need normalization before printing or distribution.
- Reading time at 250 WPM. Word count divided by 250 (average adult reading speed). Reading time is a much more useful summary than word count for non-technical audiences — "this report is 14 minutes of reading" lands faster than "this report is 3,500 words."
Five common situations where page count is the load-bearing number
Where this tool earns its place in workflows:
- Per-page billing. Bates stamping at $X per page. Translation at $Y per page. Print at $Z per page. Every per-page invoice starts with this number.
- Pre-allocating timesheets. If reviewing a 200-page document takes ~5 hours and reviewing a 50-page document takes ~75 minutes, knowing the page count lets you block calendar time correctly.
- Submission-portal validation. Many regulatory portals (USPTO, EU regulators, court e-filing systems) cap submission size in pages. Verify before upload.
- Splitting decisions. Should I send this as one PDF or split it into chapters? A 500-page single PDF is awkward; five 100-page splits are easier to consume. Page count is the signal that triggers this decision.
- Cost estimation. When asking for a print or translation quote, page count is the first thing you need. Sending a PDF and asking "how many pages?" wastes a back-and-forth — open the inspector, copy the number, paste it into your request.
Two patterns where the number deserves a second look
The cases where raw page count can mislead:
- Documents with mixed orientations. A 100-page document where 80 pages are portrait and 20 are landscape will print and bind awkwardly. The page-count tool flags this; resolve before sending or printing.
- Documents with mixed page sizes. A 50-page document where most pages are Letter and a few are A4 may render inconsistently across viewers. Pair with Resize Pages to normalize before distributing.
Limits and compatibility
On the free web tool, page count handles PDFs up to 100 MB with no page-count cap. Parsing runs in your browser via PDFium WebAssembly; nothing is uploaded. The tool surfaces page count, word count, reading time, per-page size/orientation, and a mixed-size warning in under a second for documents up to 100 pages and within 2-3 seconds for documents up to a few thousand pages.
For deeper introspection (font inventory, attachment list, JavaScript detection, encryption status, hyperlink count, embedded image inventory), use PDF Inspector — same single parse, much richer surface.