BatesKit

BatesKit stamps continuous Bates numbers across a folder of litigation PDFs — ABC-000001 onward, no gaps — plus confidentiality legends and exhibit labels. Then, before the set ships, five read-only checks run on the same documents, all on your device: metadata (author, custom keys, dates, XMP, embedded files), redaction (renders every page and asks whether text sits under a dark region, a white/light cover, or invisible ink), privileged or sensitive content (privilege markers, SSNs, emails, phone numbers; a local OCR reads scan bodies when you ask), production QA (numbering gaps, duplicates, mixed page geometry), and your index or privilege log reconciled against the assigned ranges.

Everything runs in the browser tab. pdf-lib parses and rewrites each PDF locally and writes finished files into a folder you pick; originals are never touched. Files never leave the device, which is what makes it usable for documents under a protective order. The only requests the page ever makes are six ~30-byte anonymous counters — no cookie, no identifier, no filename.

A manifest CSV records relative path, filename, page count, BegBates, EndBates and the output SHA-256 per file; a Summation-style load.dat accompanies it.

No account, no subscription. Free for one file up to 25 pages with every feature enabled; unlimited is $19 once, a licence verified offline against a public key compiled into the page.