Skip to content
BatesKit

Inspect a real BatesKit export

Three fictional PDFs. Six numbered pages. Download the actual output, inspect its CSV, DAT and OPT files, then reproduce it in your browser before using your own documents.

Verified on September 14, 2026 with the public sample in the free workspace. These files contain fictional material only.

Run the sampleDownload processed ZIPDownload original PDFs

What is inside the output?

Three stamped PDFs
Two pages each, numbered continuously from ABC-000001 to ABC-000006. The schedule uses landscape pages. Numbers are searchable PDF text; the originals remain unchanged.
manifest.csv
One row per document: source and output filenames, page count, beginning and ending Bates numbers, exhibit label, and SHA-256 of the exact output bytes. The sample ZIP includes this file. For your own documents, use Download manifest CSV after stamping.
load.dat
A Summation-style, pipe-delimited file with BEGBATES|ENDBATES|FILEPATH|PAGECOUNT|SOURCE. It is a minimal document inventory, not a complete metadata export for every review platform.
load.opt
Six page-level rows. Each document starts with a Y marker and its page count. Rows for the same document reference the same multi-page PDF. Check your receiving system: an importer requiring one single-page TIFF per row will not accept this PDF layout. BatesKit does not create TIFF images for this export.

Reproduce this export

  1. Open the sample workspace in a fresh tab. Confirm three files and six pages. If your own files are already loaded, clear them first; samples never replace an existing queue.
  2. In Stamp, set prefix ABC-, six digits, start at 1, step 1, Continuous across files, and All pages. Leave the confidentiality and exhibit layers off. Use the filename template {name}_{beg}-{end}.
  3. Under Output, keep Re-open and verify each stamped file before writing and the Summation-style load file enabled. Enable Write an Opticon image load file; OPT is off by default.
  4. Choose Stamp and write. The fictional sample downloads as a ZIP. Unzip it and check the PDF pages, manifest ranges and load files before trying an import.

The checked-in sample has fixed bytes. A new run may produce different PDF hashes because document timestamps can change. Each run’s manifest should match that run’s own PDFs.

Run checks on the files you intend to send

Switching to Check checks the files currently in the queue. After stamping, those are still the original input files. To inspect delivered output, clear the queue and choose the extracted, stamped PDFs.

Choose Run checks, review Metadata, Redaction, Content and Production findings, and use the CSV or JSON report download. Index reconciliation compares an imported index or privilege-log CSV with the ranges assigned by the current queue and numbering settings; keep those settings aligned with the set.

Stamp verification searches for expected labels in the generated PDF text. Read-only checks flag potential issues for human review. They do not certify safe redaction, identify every sensitive passage, or approve a production for delivery. Scans can require the optional local English OCR model and manual review.

Read about production QA

Limits and processing location

Free batches include up to 20 files and 60 total pages with every feature enabled. The $19 one-time licence removes those quantity limits. Browser memory, supported PDF structures and output mode still constrain large jobs; try a representative batch first.

PDF parsing, stamping and checks run on your device. Site assets and the optional OCR model must load before offline use. Checkout, support messages and anonymous usage counters use the network; your PDF contents are not sent to the processing service. See the privacy details.

For OPT, every page needs a Bates number. If numbering covers only some pages, BatesKit reports the problem and omits the OPT file. Confirm your recipient’s delimiter, encoding, path and image requirements with this sample before relying on a load file.