Discovery is never a clean, uniform pile of PDFs unless you happen to be litigating in a vacuum.

Discovery is never a clean, uniform pile of PDFs unless you happen to be litigating in a vacuum. In the real world of 2026, you get a USB drive or a Dropbox link filled with a chaotic mix of high-res smartphone photos, grainy office scans, and screenshots that vary wildly in DPI and orientation. Trying to apply a standard Bates stamp to this mess is usually where the wheels come off.

Most Bates numbering tools are designed for "clean" documents. The moment you throw a 4000-pixel vertical photograph into the mix, the software either crashes or places the Bates label in a microscopic font somewhere in the middle of the image. Or worse, it scales the file so aggressively that the metadata becomes unreadable. This forces paralegals to manually convert images to PDFs one by one, adding hours of unbillable prep time to a production that was supposed to be out the door by 5:00 PM.

Document production scale shouldn't be held hostage by file extensions.

When we built OmniBates, we spent a significant amount of time focusing on the "non-standard" files that make up the bulk of modern discovery. We wanted a system that could handle discovery format acceptance across the board—PDFs, scans, and photos—without requiring a dozen third-party converters. The goal was to ensure that a custom prefix or a matter number looks identical on page 1 of a clean memo and page 500 of a low-light cell phone photo.

This is particularly tricky when you consider firm-standard compliance. If your firm requires a specific margin offset for court-approved formats, that offset has to stay consistent regardless of the source file's resolution. Many online platforms struggle with this because they process files on a remote server that prioritizes speed over precision.

We took a different route by utilizing local processing. Instead of forcing you to upload sensitive discovery files to a cloud server—which is a data security nightmare—OmniBates uses your browser to process the files locally on your own machine. This doesn't just protect the data; it allows the software to calculate the exact pixel coordinates for the Bates label based on the specific geometry of every individual scan or photo in the set.

Beyond just getting the numbers on the page, there is the issue of the sequence itself. If you are processing three thousand files and one image fails to convert, your entire Bates-sequential numbering is now incorrect. You either spend the night re-running the entire production or you risk a motion to compel by serving a production with gaps.

To solve this, we integrated audit-ready run logs into the local workflow. The moment a production is finalized, you get a log that verifies every file, every page count, and every prefix. If a scan is wonky or a photo is corrupt, you know exactly where it happened before you hit send. It’s an insurance policy against those tiny clerical errors that judges in 2026 have zero patience for.

Efficiency in a law firm isn’t about how fast you can type; it’s about how many manual, repetitive steps you can eliminate from the critical path. If you are still dragging JPEGs into a Word doc just so you can print them to PDF and then stamp them, you’re losing money. By the time you get to the production phase, the hard work of discovery is supposed to be over. The labeling should be the easiest part.

Whether you are dealing with a same-day production or a multi-year litigation, the software should adapt to the files you have, not the files it wishes you had. Local processing for mixed-media discovery is the only way to maintain firm standards without sacrificing security or your entire evening.