Apply Bates numbering

This calculator produces the complete label plan before any PDF is stamped: enter the PDF page count, the prefix your matter or workflow requires, the number assigned to page one, and the desired digit width. The result pairs each physical page position with its numeric value and finished label. It also checks the end of the sequence in advance, preventing a too-narrow padding choice from creating inconsistent identifiers halfway through a file.

Define a numbering plan before altering the PDF

A reliable Bates workflow starts with a numbering plan, not with drawing text onto pages. First obtain the PDF page count from a trusted reader or document-processing step. Then choose a prefix that identifies the case, production, client, exhibit, or batch without relying on the filename. The starting number is the numeric value for the first physical page, while the padding width determines how many digit positions appear after the prefix. For example, a start of 17 with a width of five becomes 00017. This capability calculates the entire sequence and returns a record for every page, including its one-based page position, raw number, and finished label. Because it does not modify or upload PDF bytes, you can review the numbering plan, store it in an audit record, or feed it into a separate stamping process. This separation is useful when approval is required before permanent page marks are applied or when several tools must agree on the exact identifier assigned to each page.

Prevent padding changes inside a document

Padding is more than a visual preference. Fixed-width numbers sort correctly as text, align cleanly on a page, and remain easy to compare across document productions. The important check is not whether the starting number fits; it is whether the final number fits after every page has been counted. A 20-page PDF beginning at 990 ends at 1009, so a width of three would be invalid even though 990 initially appears to fit. This calculator determines that final value before producing any labels and returns an input error when its digit count exceeds the requested width. It never silently expands the later labels, because doing so would make the series internally inconsistent. Choose a width that can accommodate anticipated growth if subsequent files will continue the same sequence. The returned last number can become the reference point for the next batch: begin the following PDF at last number plus one, keep the same prefix and width, and preserve a continuous production range without overlaps or accidental gaps.

Use the labels safely in legal and records workflows

The result is deterministic: identical inputs always produce identical page mappings, with no network lookup, current time, or random component involved. That makes it suitable for repeatable evidence preparation, public-record releases, contract exhibits, internal investigations, and archival indexing. Keep the generated mapping beside the source document checksum and the final stamped-file checksum if chain-of-custody or reproducibility matters. Before stamping, confirm that the supplied page count includes every page the stamping tool will process, including covers, separator sheets, appendices, and intentionally blank pages. Also confirm whether an existing production requires a particular prefix spelling, punctuation pattern, starting value, and fixed width. This capability computes labels only; it does not edit a PDF, inspect page content, detect previously applied numbers, or decide where a mark belongs. Those boundaries are deliberate. They let a caller validate the sequence independently and then use a PDF stamping tool with explicit placement, font, color, and margin controls while retaining a clear record of exactly which label belongs to each page.