How to Add Page Numbers & Bates Stamps to PDFs
Why merged PDFs need unified post-merge pagination
Every file format and statutory compliance rule has a deterministic structure underneath the user interface. When teams rely on manual spreadsheet edits or generic cloud converters, subtle structural details get lost: page coordinate boxes reset, check digits go unverified, or rounding rules drift by several hundred rupees across a financial year. Understanding the exact specification behind PDF Page Numbers lets you verify every output before it enters an audit file or government portal.
The reference table below summarizes the core technical and statutory parameters enforced by the local engine:
| Parameter / Rule | Specification / Formula | Practical Audit Impact |
|---|---|---|
| Format Templates | "Page X of Y", "X / Y", "Page X", or custom prefix (Bates style) | Supports court exhibit and audit workpaper conventions |
| Anchor Positions | Bottom-Left, Bottom-Center, Bottom-Right, Top-Left, Top-Center, Top-Right | Calculated relative to each page visible /CropBox |
| Start Offset | Custom start page & starting number (e.g. start at p.2 as #1) | Leaves cover sheets unnumbered when required |
| Font & Legibility | Clean monospace/sans vector stamp at 9 to 12 pt | Zero rasterization of underlying page content |
Because each rule above is evaluated directly in your browser tab using typed JavaScript arrays and WebAssembly workers, there is no server queue, no file-count cap, and zero external data retention. Every byte of the source document or ledger table is parsed inside volatile browser memory and released as soon as the tab closes.
Step-by-step: stamping Page X of Y in ShiftTools
Running this workflow in Add PDF Page Numbers takes four deterministic steps from raw input to verified output:
- Open Add PDF Page Numbers and drop your compiled PDF into the workspace.
- Select your anchor position (such as Bottom-Right or Bottom-Center) and numbering pattern (such as Page X of Y).
- Set the starting page and margin offset so the stamp sits cleanly in the footer whitespace.
- Click Stamp Page Numbers to write the pagination layer and download the numbered PDF.
When you process recurring monthly batches, keeping the input schema consistent across runs ensures that downstream checks in related guides such as merge pdf files offline browser, stamp diagonal text watermarks on pdf pages, trim pdf margins and adjust cropbox coordinates match to the exact rupee or byte. Before starting a large batch, verify that your source file is not locked by an unknown password and that column headers or page indices match the expected range.
Worked example: numbering a 45-page compilation while skipping the cover
Numbering a 45-Page Audit Binder Starting After the Title Sheet
An audit team compiles a 45-page workpaper PDF where page 1 is a title sheet and pages 2 to 45 hold schedules from six different sources. Configuring Add PDF Page Numbers with pattern "Page {n} of {total}", position Bottom-Right (28 pt from right edge, 24 pt from bottom edge), sets every sheet from page 1 to 45 with a consistent 10-point reference ("Page 1 of 45" through "Page 45 of 45"). During review calls, citing "Page 31 of 45" jumps every participant to the exact same schedule.
Page Box: A4 [0, 0, 595.28, 841.89]
Anchor: Bottom-Right (x = width - 28pt, y = 24pt)
Stamped Label: "Page 31 of 45" (10pt, #16181A ink)
File Overhead: +4.8 KB across 45 pages
You can reproduce this exact calculation at any time by pasting the sample values above into PDF Page Numbers and comparing the generated summary row against your internal workpaper. Recording the input parameters alongside the output file creates a self-contained audit trail for statutory or peer review.
Coordinate positioning across bottom-right, bottom-center, and top headers
In production accounting and document engineering workflows, edge cases appear when inputs combine multiple conventions in a single batch. For example, a merged PDF bundle may mix portrait A4 text pages (/MediaBox 595.28 × 841.89 pt) with wide environment annexures, or a quarterly ledger export may combine April-to-September transactions with October-to-March entries after a mid-year threshold revision.
To prevent silent errors across those boundaries, always inspect the per-item diagnostic status before exporting the final file:
- Verify unit consistency: Confirm whether input figures represent monthly vs annual amounts, GST-exclusive vs GST-inclusive values, or 1-based physical page indices vs printed document numbers.
- Check boundary conditions: Pay close attention to exact threshold cutoffs, leap-year day counts, and page rotation multiples (0, 90, 180, 270 degrees) where off-by-one errors commonly occur in manual spreadsheets.
- Preserve audit trails: Save the exported summary CSV or processed PDF alongside the raw source file so any reviewer can trace the transformation step by step without re-keying data.
- Cross-check neighbour utilities: Pair PDF Page Numbers with companion tools in the PDF Suite suite (merge pdf files offline browser, stamp diagonal text watermarks on pdf pages, trim pdf margins and adjust cropbox coordinates) when a task spans multiple stages.
Handling existing conflicting page numbers in source scans
Stamping new page numbers draws on top of the existing page canvas; it does not automatically erase an old printed number that was already sitting in the exact same corner. If an underlying document already has conflicting footer numbers in the bottom-right corner, either trim the bottom 25 pt margin first using PDF Crop or place your new unified stamp in the Top-Right or Bottom-Center slot.
By separating deterministic local computation from external portal lookups, your team eliminates manual formatting and calculation errors while keeping sensitive client files off third-party cloud servers.