When this tool is useful
Creating a visible sequential identifier on an unsigned review, production, discovery, or archive copy under a controlled numbering plan.
How local processing works
The browser generates one label per physical page, checks numeric overflow and built-in-font support, draws the label at the selected corner or center position, then reopens the output and verifies the page count.
How to use it
- Prepare a safe working copy: Keep every source unchanged and review the supported input, controls, and limits before processing. Creating a visible sequential identifier on an unsigned review, production, discovery, or archive copy under a controlled numbering plan.
- Process locally: Run the documented operation in this browser and stop if an unsupported structure is reported. The browser generates one label per physical page, checks numeric overflow and built-in-font support, draws the label at the selected corner or center position, then reopens the output and verifies the page count.
- Download and verify: Check the first, last, and several middle labels, confirm sequence, prefix, padding, placement, and legibility, and record the numbering plan outside the PDF when evidence handling requires it.
Important limitations
Bates text is visible page content, not a cryptographic signature, chain-of-custody record, legal certification, database index, or tamper-proof audit log. It can overlap existing artwork, and signed PDFs are refused.
Verify the downloaded result
Check the first, last, and several middle labels, confirm sequence, prefix, padding, placement, and legibility, and record the numbering plan outside the PDF when evidence handling requires it.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
When is this tool useful?
Creating a visible sequential identifier on an unsigned review, production, discovery, or archive copy under a controlled numbering plan.
What does the browser actually do?
The browser generates one label per physical page, checks numeric overflow and built-in-font support, draws the label at the selected corner or center position, then reopens the output and verifies the page count.
Which limits must I understand?
Bates text is visible page content, not a cryptographic signature, chain-of-custody record, legal certification, database index, or tamper-proof audit log. It can overlap existing artwork, and signed PDFs are refused.
How should I verify the result?
Check the first, last, and several middle labels, confirm sequence, prefix, padding, placement, and legibility, and record the numbering plan outside the PDF when evidence handling requires it.