Massive PDF exports shouldn't trigger a 413 Request Entity Too Large error.

Trying to push a 4GB production through a browser-based uploader is a recipe for a '413 Request Entity Too Large' error or a generic 'Connection Reset' message that forces you to restart from scratch at 9:00 PM. Most cloud-based discovery tools haven't solved the basic physics of moving massive legal datasets over residential or office Wi-Fi. Files time out, packets drop, and security filters often flag large outbound transfers as suspicious.

Omnibates handles this differently because your documents never leave your device. By performing automated bates numbering directly in your local browser environment, we bypass the need for an upload entirely. You aren't 'sending' a file to a server to be stamped; you're using your local processor to apply bates-sequential numbering to the source files living on your hard drive. It's faster, it doesn't crash, and it stays strictly within your firm's security perimeter.

The infrastructure limit of cloud-based discovery

Cloud infrastructure relies on middle-ware and load balancers that often have hard limits on the size of an incoming POST request. If your discovery set exceeds a few hundred megabytes, the server simply hangs up on you. In a 2026 litigation environment where high-resolution smartphone photos and dense PDF archives are the norm, these limits aren't just annoying—they're a systemic risk to fulfilling same-day productions.

Handling Method	Cloud-Based Upload	Local-First Processing (Omnibates)
Data Transfer	Full file must reach remote server	0MB transferred to external servers
Security Risk	Transit interception & server breach	Documents remain on your device
Speed Limit	Dictated by your ISP's upload speed	Dictated by your local CPU/RAM
File Size Cap	Usually capped at 100MB-2GB	No cap (limited only by disk space)

Why local processing is faster than the fastest fiber line

Even with a gigabit connection, the time spent encrypting, uploading, processing, and re-downloading a 10,000-page set is measurable in hours. Local processing happens in real-time. The moment you hit 'process,' the software begins bates labeling page zero. Since there's no round-trip to a data center in Virginia or Oregon, the latency is effectively zero.

We've seen legal teams lose entire billable afternoons just waiting for a progress bar to move from 98% to 99%, only for the browser to refresh and lose the entire batch. Using local-only execution means if your internet drops for five minutes, the production keeps running. The work happens in the browser's memory, not on a remote server that doesn't care about your deadline.

Ensuring audit-ready run logs without data exfiltration

One common misconception is that you need a cloud server to generate a defensible audit-ready run log. That's false. Omnibates generates these logs locally, mapping each source file to its stamped output. This provides a direct, verifiable chain of custody without needing to store a copy of the evidence in a third-party database. We provide the metadata—file names, MD5 hashes, and bates ranges—without ever touching the content of the files themselves.

• No 'File Too Large' errors.
• No security disclosures for third-party cloud storage.
• Absolute control over same-day productions regardless of bandwidth.

Frequently Asked Questions

Will my computer slow down during local processing?

Modern browsers are highly efficient at managing system resources. While a 50,000-page production will utilize your CPU, you'll generally be able to continue working in other applications. Because the processing is local, it's significantly more stable than relying on a fragile web socket connection to a remote server.

Do I need to install software for local processing to work?

No. Omnibates uses advanced browser-side scripts to perform court-approved formats and numbering. It works within your existing professional browser setup, but the code executes on your machine, not our servers. This is the 'zero-trust' standard for 2026 legal work.

How does Omnibates handle different page sizes locally?

Our software analyzes the pixel coordinates of each page in real-time. Whether it's a standard letter, a landscape spreadsheet, or a non-standard scan, the bates-sequential numbering is placed precisely according to your margin settings, ensuring no text is obscured regardless of the document's original dimensions.

Is there a limit to the number of files I can process at once?

Because we don't have to worry about server timeouts or upload buffers, your only real limit is your own computer's hardware. We’ve designed the engine for production-scale processing, meaning it can handle thousands of files without the 'Request Entity Too Large' errors that plague traditional web tools.

Sources / Further reading: For more information on local-first privacy architecture, see our technical breakdown of local-only browser execution.