How to Bates stamp PDF documents for legal discovery
Legal discovery productions under U.S. Courts Federal Rules of Civil Procedure Rule 34 depend on unambiguous page-level tracking across hundreds of exhibits. Rather than numbering each PDF from 1, a continuous counter increments across every file in your queue so opposing counsel can cite any single leaf without ambiguity.
Configuring prefix, suffix, start number, and zero-padded digits
The options panel exposes Prefix and Suffix fields capped at 20 characters each, alongside Start at for any integer from 0 upward. Selecting between 3 and 8 Digits controls leading zeros, and a live range bar previews the exact first and last labels before you click Add Bates numbers.
For continuing Bates numbers across subsequent productions, note the final number from your earlier batch and enter the next integer in Start at. Keeping a brief log of prefixes and ending counters ensures supplemental productions never collide with prior exhibits.
When you need to unify separate exhibits into a single numbered binder after stamping, you can combine production files into one binder in the next step. Keeping the queue order accurate before export guarantees the counter never skips or duplicates a page.
Keeping discovery exhibits inside your browser tab
Privileged contracts, medical records, and internal emails never leave your device because all PDF parsing and content-stream drawing run inside a local Web Worker. Network traffic stays at 0 bytes of file data during both preview and export, eliminating third-party cloud retention risks.
What is the difference between Bates numbering and page numbers?
Bates numbering assigns a globally unique alphanumeric identifier across an entire multi-document production set, whereas standard page numbers reset at 1 for each file. Legal teams rely on Bates prefixes and fixed-width digits to cite individual pages across thousands of exhibits regardless of how files are split or bundled.
As documented in the EDRM Electronic Discovery Reference Model, unique production identifiers remain stable even when exhibits are exchanged across different review platforms. Standard pagination works well for standalone reports, so choose Add page numbers to PDF when you only need local “Page X of Y” labels inside a single manual.
When comparing native ESI production versus Bates-stamped PDFs, native spreadsheets preserve formulas but cannot carry visible corner stamps. Converting records to PDF first lets paralegals apply uniform Bates identifiers across emails, memos, and scanned receipts in one pass.
| Attribute | Bates numbering | Standard page numbers |
|---|---|---|
| Counter scope | Continues across all queued PDFs | Resets to 1 per document |
| Label format | Prefix + zero-padded digits + suffix | Integer or “Page X of Y” |
| Typical digit width | 6 to 8 fixed digits (e.g. 000123) | Variable 1 to 4 digits |
| Sorting behavior | Lexicographically safe in file explorers | Intended for human reading only |
| Primary use case | Litigation discovery, exhibits, audits | Reports, manuals, slide decks |
Zero-padding math, WinAnsi encoding, and content-stream baking
Fixed-width padding and clean character encoding prevent subtle production failures when opposing teams ingest PDFs into e-discovery review databases. Two technical safeguards run automatically during stamping.
Preventing alphanumeric sorting mistakes with 6-to-8 digits
Without leading zeros, file systems and spreadsheet tables sort ABC10 before ABC2 because character comparison evaluates 1 before 2. Padding every counter value to 6 digits (such as ABC000001 through ABC999999) or 8 digits keeps alphabetical and numerical order identical across all operating systems.
If you are numbering a small internal binder under 999 pages, 3 or 4 digits keep labels compact on narrow margins. For formal litigation discovery, sticking with 6 or 8 digits leaves ample room for supplemental productions months later.
Normalizing Unicode hyphens and spaces for Helvetica embedding
Copy-pasted case captions often include non-breaking spaces, figure dashes, or fi and fl ligatures that fail WinAnsi encoding in Standard Type 1 fonts defined by the PDF Association ISO 32000-2 Specification. The normalizer converts those code points into standard ASCII spaces, hyphens, and letter pairs before embedding 9 pt Helvetica directly into the page content stream.
If a production also requires visible privilege markers across the page center, pair your stamped exhibits with confidentiality watermark stamps before distributing the final set.
Placement, confidentiality legends, and ZIP archive output
Choosing a consistent corner and packaging format keeps stamped exhibits readable across court filings and review software. Every page is stamped at 9 pt inside standard corner margins without altering underlying page dimensions.
Choosing corner positions that avoid existing footers
The Position selector offers Bottom right, Bottom centre, Bottom left, Top right, and Top left. Bottom right is the standard discovery convention because it avoids left-hand binding margins and top letterheads, though Top right works better when scanned invoices carry dense payment tables along the bottom edge.
Under the Library of Congress PDF Format Description, writing operators straight into the page content stream ensures stamps stay visible across archival viewers. When you also need opposing-corner privilege banners or dates, use a dedicated tool to place running confidentiality legends opposite page numbers.
Exporting single PDFs versus multi-file ZIP bundles
Single-file runs download immediately as a suffixed PDF, while batches of two or more documents package into a ZIP archive named with the exact start and end labels. Keeping every original filename intact inside the ZIP lets litigation teams cross-reference Bates ranges against existing exhibit logs directly.
Tip: Verify the live range preview at the bottom of the options panel before exporting a multi-file batch. Checking the final number confirms your total page count matches the production index log.