Counting pages in multiple PDFs at once means producing a structural page count for each file in a folder without uploading any of them, and the PDF Page Counter delivers exactly that workflow: one file at a time, locally in the browser tab, with no server round-trip and no signup. The tool reads the PDF's internal page tree directly from the file you select, so the page total it reports is the structural count defined by the document itself, not an estimate from file size, thumbnail count, or visible page-number labels. The page total comes directly from the PDF document structure exposed by the existing PDF library, and rotation metadata can change how a viewer shows a page without changing the structural total. For each selected file, the report also groups identical page-box dimensions in PDF points, which turns a folder of mixed reports, scans, and inserts into a clean inventory you can compare at a glance. Because processing stays on the current tab, you can run the tool repeatedly across a folder and build a multi-file page-count sheet without any of the source documents leaving your device.
What "Multiple Files at Once" Actually Means Here
The phrase "multiple files at once" can mean two very different things. The first is a true batch operation, where a single click takes a folder of PDFs and returns one combined report. The second is a repeatable per-file inspection, where each document is processed locally and the results are recorded by the reader. PDF Page Counter is built for the second approach: one file per selection, one read of the page tree per selection, one report per selection. That design is intentional, because it keeps every document strictly local and avoids the server-side aggregation step that comes with batch tools. A practical consequence is that "at once" really means almost no extra work per file, which is fast enough to step through a folder in a few minutes while every document remains private.
For most readers, the practical question is whether the per-file approach scales. It does, because the page tree of a normal document reads almost instantly, the displayed counts and dimensions appear once the read finishes, and selecting another file clears the old result before a new read begins. The tool also guards against stale asynchronous reads, so a slow previous selection cannot overwrite a newer result. A separate run per file also gives you the freedom to reorder, rename, or skip documents mid-folder, which batch tools rarely support.
Run the Counter Across a Folder of Files
Each file in a folder takes the same three actions. The exact operating sequence for PDF Page Counter is:
- Choose a non-empty PDF no larger than 25 MiB from your local drive.
- Wait for the browser to read the document page tree; the total page count appears once that read completes.
- Review the total page count and each grouped page-box dimension listed for that file.
- Note the result, then select the next PDF in your folder to repeat the process for the next document.
Between files, the previous result clears before processing begins, so the displayed count always belongs to the named current file. If you keep the tool open in a single tab, a job identifier makes sure a slow read from an earlier selection never overwrites the most recent one. Selecting another file replaces, rather than appends to, the previous result.
Why Page-Box Dimensions Matter Across a Folder
A page count answers "how many" but rarely "what shape." The grouped page-box report answers both at the same time. For a folder of mixed PDFs, you will often see one or more of these patterns:
- A standard 612 × 792 point group representing US Letter pages.
- A 595 × 842 point group representing A4 portrait pages.
- A smaller group, frequently a cover page, a foldout, or an inserted scan that arrived at a different size.
- A landscape group, where width is greater than height.
The counter groups equal displayed sizes in first-seen order, so a single document with two 612 × 792 pages and one 400 × 500 page reports both sizes and their counts in the order they appear in the page tree. Mixed-size PDFs are handled without assuming the first page represents all later pages, which is exactly the behaviour you want when a cover or foldout shifts the page geometry mid-document. Rotation metadata can affect how a viewer presents a page, but the reported width and height stay as the page-box values returned by the underlying PDF page size access.
The tool does not label those boxes as A4, Letter, or another paper standard, because that decision would require orientation and tolerance rules. It simply reports the dimensions present in the file. The displayed dimensions are PDF points, the geometry defined by the file rather than the monitor or printer, and they are not pixels, so they do not reveal scan resolution or image quality. Treat the size inventory as document geometry, not as a quality score.
What the Per-File Report Looks Like
Below is a representative layout for a folder where three different documents were inspected back to back. The table describes the relationship between a file's contents and what the tool reports; the actual totals come from running PDF Page Counter on each file.
| File in folder | What the dimension grouping reveals |
|---|---|
| Standard report | Single 612 × 792 group covers every page |
| Manual with a foldout | Main body at one size plus a wider foldout at a second size |
| Mixed original and scanned inserts | Several groups at once: cover, text pages, and raster scans at different sizes |
Once you have a row like the third, you immediately know which pages need different handling at print or merge time.
Limits That Affect Every File
Several limits apply per file, and each one can stop a run before a count appears:
- File size cap. Any document above 25 MiB returns a visible error instead of a count.
- Empty or non-PDF selections. A zero-byte file or a non-PDF selection produces an error rather than a fake zero.
- Encrypted and password-protected files. Password protection is not bypassed; the read fails visibly.
- Damaged cross-reference data. A PDF with broken xref tables errors rather than returning a guessed count.
- Unsupported PDFs. Files the underlying PDF library cannot parse surface as an error rather than a fallback estimate.
Errors are useful signals, not roadblocks. A file that errors out is one that needs to be opened in a viewer, repaired, or converted before any downstream count can be trusted. None of the listed failures alter the source file, because the operation is strictly read-only and creates no modified document.
When the Count Points to Another Tool
PDF Page Counter is an inspection step, not a transformation. Once a multi-file inventory is in hand, the next decision often belongs to a different tool. The table below pairs common findings with the tool that actually does the work.
| Finding from the count | Best follow-up tool | What it does |
|---|---|---|
| One file is too long for upload | Split PDF | Splits one local PDF into smaller files by page count or ranges |
| Several small files belong together | Merge PDF | Combines several local PDFs into a single file in your chosen order |
| Two files share their dimensions perfectly | Alternate Mix PDF | Interleaves two local PDFs in A1, B1, A2, B2 order locally |
| A page-size mismatch needs normalizing | Resize PDF | Resizes every page to A4, Letter, Legal, or a percentage scale |
| The count includes pages you do not want | Delete PDF Pages | Removes selected pages and produces a trimmed download |
| The count is right but layout needs N-up | PDF N-Up | Places two or four source pages on each output sheet |
The follow-up tools create new files, while the counter stays a private inspection step that does not touch the original bytes. For readers who arrived from a search for a similar batch workflow, this pattern also matches the privacy-first approach described in the guide on counting pages in multiple PDFs without uploading files.
Putting It Together for a Folder of PDFs
A typical run goes like this: open PDF Page Counter, select the first file, note the page count and grouped dimensions, then select the second file. After the third or fifth file, the per-file rhythm becomes predictable enough that the whole folder can be walked in a few minutes. The resulting record, page count plus dimension grouping per file, is enough to size an upload, plan a print job, drive a split, or feed a merge.
Two practical habits help when the folder has surprises. First, watch for a second dimension group inside a single document; that is often the signal of a foldout or cover. Second, treat the per-file count as the structural truth: a PDF can show page numbers starting at 5, repeating, or using Roman numerals, and those visible labels do not change the structural total reported by the counter. That distinction is the reason the count is reliable for upload checks, print estimates, splitting plans, and document QA in every workflow, whether you need it for one file or several.
Related reading: Convert a PDF to Multiple PNG Files at Once.