PDF HERE.
Your file never leaves this tab.
Everything runs in JavaScript (and WebAssembly) on your device. We can't see your PDF, and neither can our servers — because your file never touches them.
HOW PAGE COUNTER WORKS.
01. Drop
Drag your file onto the box, or click to pick one from your device.
02. Tweak
Set the options in the sidebar. Defaults work for most.
03. Download
Hit the big button. Your file is ready in seconds — never leaves your browser.
ABOUT PAGE COUNTER.
Counting pages sounds trivial until you need an exact number across a whole batch of files — confirming a scanned document has all its expected pages, checking page counts before a per-page printing cost estimate, or verifying a batch of reports all match an expected length before submission. minipdftoosz's Page Counter tool reads a PDF's internal page tree (via pdf-lib) and reports the exact page count instantly, and — because it supports multiple files at once — can process an entire batch in one pass rather than one file at a time.
Reading the page count is a lightweight operation compared to most other tools on this site: it doesn't need to render any page content, extract images, or modify anything — it just reads the document's structural metadata to determine how many page objects exist, which is why this tool tends to feel closer to instant even on fairly large files, compared to tools that need to process every page's visual content.
Batch mode matters more than it might first appear: if you've received twenty scanned documents and need to know each one's page count for a filing or billing purpose, doing that one file at a time in a regular PDF viewer (open, check the page indicator, close, repeat) is meaningfully slower than dropping all twenty in here and getting every count back at once.
A frequent practical use: confirming a scan came out complete before relying on it — a 42-page contract that should have exactly 42 pages, verified as a quick sanity check before archiving or forwarding it, catching a scanner misfeed or a skipped page early rather than discovering it later when it actually matters.
If exact page counts matter for a billing or compliance reason — per-page pricing, a regulatory page-limit requirement — running this as a final verification step right before submission, rather than trusting a count from earlier in your process, catches any last-minute change (an added cover page, for instance) before it becomes someone else's problem to notice.
People handling batches of scanned documents for filing, billing, or compliance purposes are the typical users of Page Counter, valuing the ability to check many files' page counts in one pass rather than one at a time.
The same batch capability also helps when auditing a folder of files you didn't create yourself — quickly confirming, for instance, that a vendor's delivered batch of scanned invoices actually matches the page counts stated in an accompanying manifest, before you file everything away as complete.
- Drop multiple files at once to get every page count back in a single batch rather than checking files one at a time.
- Useful as a fast sanity check that a scan or export came out complete before you rely on it further.
- This reads structural metadata only — it doesn't open or render page content, which is why it's typically very fast even on large files.
FAQ.
Common questions about page counter. Something else on your mind? Ask us.
Yes. Free forever. No sign-up. No credit card. No trial.
Never. Everything runs locally in your browser using JavaScript and WebAssembly.
Only limited by your browser’s memory. Most laptops handle 100MB+ with ease; very large files may be slower.
Once the page and its tool script have loaded, yes — processing runs entirely client-side.