NearPDF

2026-08-06

Why court e-filing rules require PDF page numbers at the bottom — and how to add them without uploading anywhere

Most people who search for "add page numbers to a PDF" want exactly what it sounds like: a small gray number at the bottom of every page, done in a minute. For a specific and fairly large category of PDFs, though, that plain request isn't cosmetic at all — it's a written formatting rule, with a stated, functional reason behind it, and getting it wrong can mean a document literally doesn't match what a reader typing a page number into their PDF viewer expects to see. Court e-filings are the clearest example, and they're a useful way to understand what "add page numbers" should actually mean before you do it to any document.

The rule behind the request: your page number has to match the reader's "Go to page"

California's Rules of Court are explicit about this, in Rule 2.109: "Each page must be numbered consecutively at the bottom unless a rule provides otherwise for a particular type of document. The page numbering must begin with the first page and use only Arabic numerals (e.g., 1, 2, 3)." That's not a style preference — it's a functional requirement, and the U.S. Court of Appeals for the Second Circuit's own instructions for paginating a PDF spell out exactly why: "Any person viewing a PDF filed in CM/ECF must be able to enter a page number in the page search field on the tool bar or 'Go To Page' field under 'View' and have that number match the page number displayed in the filer's PDF." A PDF viewer's built-in page counter has no idea what a document's cover page, table of contents, or exhibit labels say — it just counts physical pages from the first one, starting at 1. If the printed number on page 12 doesn't agree with what a reader's "Go to page 12" jump actually lands on, a judge or opposing counsel citing "page 12" of your filing ends up looking at the wrong page, and it's the filer's formatting that caused the mismatch, not the reader's mistake.

What that requirement boils down to: plain, consecutive Arabic numerals, starting at 1

Strip away the legal language and the requirement is genuinely simple: one continuous run of Arabic numerals, in order, with no gaps and no restarts, printed where a reader will actually see it — which both of the rules above put at the bottom of the page. That's also, without any configuration needed, exactly what NearPDF's page-number tool does. Click "Add page numbers" and it stamps every page currently in the workspace with a plain number at the bottom center, starting at 1 and counting up by one per page, in whatever order the pages are in right now — respecting each page's own rotation, so a page you turned sideways still gets its number sitting right-side-up from the reader's point of view instead of printed sideways along with the content. There's no dialog to misconfigure and no setting to get wrong, because there's only one behavior on offer: the plain, consecutive numbering that rules like California's actually call for.

The workspace order is the numbering order — fix the pages first, then number them

Because NearPDF numbers pages in whatever order the workspace currently holds them, the sequence you get out is only as clean as the sequence you go in with. If a scan came out of order, drag the pages into the right sequence in the workspace grid before you click Add page numbers — that's the same organize/reorder mechanic the workspace uses everywhere else. If a duplex scanner left blank pages behind single-sided originals, delete those first; a NearPDF post on exactly that problem covers why scanned PDFs end up with blank pages and how to actually remove them one by one, and doing that cleanup before you number is what keeps the final count matching the actual page count — nobody wants a filing where page "14" is a blank sheet a scanner added by accident. Numbering is deliberately the last step in the workspace, not the first, for exactly this reason.

"Add page numbers" means different things depending on the document ✓ Plain sequential — 1, 2, 3… Page 1 → "1" Page 2 → "2" Page 3 → "3" → what NearPDF's page-number tool does, and what CA Rule 2.109 requires ✕ Thesis/dissertation front matter split Title page → (none) Abstract → "ii" Chapter 1 → "1" (restarts) → two numbering systems in one document; NearPDF only produces one run ✕ Bates numbering (legal discovery) Exhibit A p.1 → "ABC_0001" Exhibit B p.1 → "ABC_0501" (continues) → prefixed ID that carries a running count across separate files; not plain digits Same phrase, three genuinely different jobs — worth knowing which one you actually need.
Three things "add page numbers to my PDF" can mean — and which one NearPDF's plain, one-behavior tool actually produces.

Where NearPDF's plain numbering is the wrong tool — restated honestly

Two common cases need something NearPDF's page-number tool doesn't do, and it's worth naming both so you don't waste time discovering it by trial and error. The first is academic front matter. The University of Michigan's Rackham Graduate School dissertation formatting guide is typical of how research universities handle this: front-matter pages — the abstract, table of contents, acknowledgments — carry lowercase Roman numerals starting at "ii," and "at that point, the numbering should restart in Arabic ('1, 2, 3…')" once Chapter 1 begins, with every page number "placed at the bottom center." That's two separate numbering systems living in one document, with a defined restart point in the middle. NearPDF's tool produces exactly one continuous Arabic run starting at page 1 of whatever order the workspace holds — it has no concept of "switch numeral systems here" or "restart the count at this page," so it structurally cannot produce a thesis's front-matter-plus-body scheme after the fact. That numbering has to be built into the document before it's exported to PDF, in whatever word processor produced it, not stamped on afterward by a generic page-numbering tool — generic or paid.

The second case is Bates numbering, the identifier scheme used across legal discovery and litigation. As Everlaw's guide to the practice explains, a Bates number is a prefix plus a sequential count — something like "ABC_0001," "ABC_0002" — and critically, "when documents are processed in multiple batches, numbering continues from where the previous set ended... so if one batch ends at 'ABC_0500,' the next batch begins at 'ABC_0501.'" The whole point is a unique, gap-free identifier across an entire document set, not just within one file. NearPDF's page-number tool stamps bare digits with no prefix option and no way to tell it "start counting at 501 because this is the second file in a set" — every run starts fresh at 1. That's a genuinely different job, built for a different purpose, and it needs dedicated Bates-numbering or e-discovery software, not a plain per-file page-numberer.

A practical workflow

For the case NearPDF's page-number tool is actually built for — a report, contract, brief, or any other document that just needs one clean run of numbers a reader can navigate by — the sequence is short: add the file (or use NearPDF's merge tool first if you're assembling several documents or exhibits into a single filing), drag any out-of-order pages into place, delete anything that doesn't belong — a blank scanned page, a duplicate, a divider sheet — then click Add page numbers and save. Worth a quick check before you send the result anywhere that a rule like California's applies: open the downloaded file and confirm the number on the last page matches the total page count, and that the number on any page you cite elsewhere in the document (a cross-reference, a table of contents entry) actually lands you on that page when you jump to it. One nuance worth knowing about Rule 2.109 itself: it says a filing's page number "may be suppressed and need not appear on the first page" — suppressing it is optional, not required, so a document with a number stamped on page 1 too, which is exactly what NearPDF always produces, is still fully compliant either way.

The honest limits, restated

NearPDF's page-number tool does one job, and does it without any configuration to get wrong: plain, consecutive Arabic numerals at the bottom center of every page, starting at 1, in whatever order the workspace currently holds — which happens to be exactly the format that rules like California's Rule 2.109 and the federal courts' CM/ECF pagination guidance actually require, for a concrete, stated reason rather than tradition. It doesn't do prefix-plus-sequential Bates numbering that continues across separate files, and it doesn't switch numbering systems partway through a document the way a thesis's front matter requires — both are real, well-documented, but genuinely different jobs that call for purpose-built software, not a generic page-numberer bolted on after the fact. For the much larger set of everyday PDFs that just need one clean, consecutive count a reader can navigate by, that's the entire job, done entirely on your device with nothing uploaded anywhere to find out whether it worked.