July 1, 2026
Why sub-second batch processing is the only way to meet a 2026 court deadline
Large-scale litigation doesn't follow a 9-to-5 schedule. When 15,000 pages of discovery drop at 4:30 PM for a midnight filing, the technical efficiency of your document processing determines whether y
Large-scale litigation doesn't follow a 9-to-5 schedule. When 15,000 pages of discovery drop at 4:30 PM for a midnight filing, the technical efficiency of your document processing determines whether you go home or pull an all-nighter. The delay isn't just in the stamping; it's in the upload time, the server-side rendering, and the eventual download of massive files. Standardizing on local browser-based execution eliminates the data transfer bottleneck entirely, allowing for production-scale numbering at speeds that cloud-based services can't match.
The velocity of local-first processing
Cloud-based legal tools operate on a 'hop' model. You upload, the server processes, and you download. For a 500MB production set, that's often 20 to 30 minutes of just waiting for progress bars—assuming your office internet doesn't flicker. Local processing turns your browser into the engine. Because the data never leaves your device, the 'upload' time is zero.
In 2026, the bottleneck for document production isn't processor power anymore; it's bandwidth. By keeping the files in your local memory, you bypass the external server queues that typically slow down large productions during peak filing hours. This is how we move from 'processing documents' to 'producing sets' in the time it takes to grab a coffee.
Why batch size shouldn't break your workflow
Most legacy systems struggle when a production set contains a mix of standard PDFs and high-resolution JPEG evidence. A single 12-megapixel photo of a contract on a whiteboard can have a file size ten times larger than a standard text-based PDF page. When a software tries to process these in a single linear sequence, it often hangs.
| Feature | Local Browser Processing | Standard Cloud Upload |
|---|---|---|
| Data Residency | Stays on your device | Transferred to external servers |
| Processing Speed | Sub-second per page | Dependent on upload/download speed |
| Security Risk | Zero cloud exposure | Potential server-side data breach |
| Stability | Works offline | Requires constant high-speed connection |
| Scalability | Limited only by local RAM | Limited by server bandwidth and timeouts |
Maintaining sequence integrity under pressure
Speed is a liability if it leads to numbering drift. If your system skips a page or miscalculates a prefix because of a memory leak, the entire production is tainted. You need a system that generates an audit-ready run log simultaneously with the stamping process.
We focus on three technical pillars for high-speed productions:
- Predictive Indexing: Ensuring the next number in the sequence is reserved before the stamp hits the pixel.
- Coordinate Persistence: Locking the Bates stamp location across thousands of pages regardless of varying aspect ratios.
- Zero-Trust Architecture: Ensuring that even at high speeds, no data is cached on a third-party server.
FAQ
How does local processing handle 10,000+ pages without crashing the browser?
Modern browsers can access significant system memory. By using efficient scripts that process pages in rapid bursts rather than loading the entire 10,000-page file into active view at once, we maintain stability while numbering at production scale.
Do I need an internet connection to run the Bates numbering?
Only to load the initial application interface. Once the tool is active in your browser, the actual document processing, stamping, and log generation happen locally. This means you can finish a production on a plane or in a courthouse with no Wi-Fi.
How are the run logs formatted for court compliance?
Our logs provide a direct mapping of original filenames to their new Bates-stamped counterparts. This creates a transparent audit trail that is critical during the discovery phase to prove that no documents were altered or omitted during the production process.
What happens if my production includes mixed file types like PNGs and PDFs?
OmniBates handles mixed-media inputs by converting them into a standardized format for stamping. This ensures that the Bates-sequential numbering remains perfectly consistent whether the source was a scanned document or a smartphone photo of an exhibit.
Sources / Further reading: Check the OmniBates technical overview for details on our local processing architecture.