July 6, 2026
Why sub-pixel bates labeling fails on variable-dpi discovery scans
Bates numbering isn't a simple text overlay. Trial-ready production requires a stamp to remain legible and correctly positioned regardless of whether the source file is a 72-DPI smartphone capture, a
Bates numbering isn't a simple text overlay. Trial-ready production requires a stamp to remain legible and correctly positioned regardless of whether the source file is a 72-DPI smartphone capture, a 300-DPI professional scan, or a high-resolution 1200-DPI architectural blueprint. If your software treats every page as a standard 8.5x11 canvas without account for underlying pixel density, your stamps will appear microscopic on high-res files or giant on low-res photos. This creates an immediate compliance risk for 2026 court filings.
Precise Bates numbering requires a coordination engine that translates physical page inches into pixel-relative offsets. When you handle production-scale batches, a single miscalculation in coordinate drift can push labels into the margin-bleed area, leading to rejection by electronic filing systems. Effective processing must happen locally on your hardware to maintain this precision without the latency or compression artifacts introduced by external server round-trips.
Does your discovery software handle DPI scaling automatically?
Most basic PDF editors apply a stamp to the "visual" layer without verifying the resolution of the physical page. In a mixed-media production set—containing both native exports and legacy scans—this leads to "floating" stamps. A floating stamp might look correct on your screen but becomes unreadable when printed to PDF/A for the court.
- Native PDFs: Often have high vector resolution; labels must be anchored to specific coordinates.
- Smartphone Photos (HEIC/JPG): These have massive pixel dimensions but low DPI metadata; software must normalize these for sequential numbering.
- Legacy Scans: Often crooked or off-center; labels need enough margin padding to ensure they don't overlap existing text.
The technical difference between pixel-relative and inch-relative stamping
| Stamping Method | Result on High-Res (1200 DPI) | Result on Low-Res (72 DPI) | Legibility Status |
|---|---|---|---|
| Fixed Pixel Offset | Stamp is tiny/invisible | Stamp covers half the page | Fail |
| DPI-Aware Scaling | Stamp maintains size | Stamp maintains size | Pass |
| Manual Text Box | Varying fonts/sizes | Inconsistent placement | Fail |
Why local processing is safer for high-resolution productions
Large, high-DPI files are heavy. A single 600-DPI color scan can exceed 50MB. If you have a production set of 1,000 such pages, you're looking at a 50GB upload. Not only is this a security risk — your client's data is now living on a third-party server — but it's physically slow.
OmniBates uses a local processing model where the heavy lifting happens within your browser's memory. The documents never leave your device. This allows for sub-second coordinate calculations across massive file sizes because there is no bandwidth bottleneck. You get same-day production speeds even when dealing with gigabytes of discovery data.
Maintaining a defensible audit trail across mixed formats
Court-approved formats aren't just about the number on the page; they're about the integrity of the sequence. If a 1200-DPI schematic causes your software to crash or skip a number, the entire Bates-sequential numbering is compromised.
We utilize audit-ready run logs that track the exact entry and exit of every file in the batch. If a file is skipped due to a corruption error, the log flags it immediately, preventing the nightmare of a 20,000-page sequence with a missing link discovered during trial.
"Accuracy in discovery isn't just a clerical goal; it's a forensic requirement. A single misaligned stamp on a crucial piece of evidence can be argued as an attempt to obscure data."
Precision stamping for same-day deadlines
When the deadline is 5:00 PM and you receive a discovery dump at 3:30 PM, you don't have time to manually check if the stamp size stayed consistent between the Word-to-PDF export and the grainy photo of a contract.
Automated systems must handle the math of page dimensions and pixel density in the background. By keeping the processing local, you ensure that the speed of your production is limited only by your computer’s processor, not a cloud server's queue or your office's upload speed. This is how we protect billable hours and firm reputation simultaneously.
Frequently Asked Questions
What happens if my discovery set has different page sizes?
OmniBates automatically calculates the corner coordinates for every unique page size in your set. Whether it's a legal-sized scan or a small receipt photo, the Bates label is placed with pixel-exact precision in the same relative location.
Why is local processing better for data privacy?
Since your documents never leave your device, there is zero risk of data exfiltration or third-party server breaches. Your firm maintains 100% custody of the evidence throughout the labeling process.
Can I use custom prefixes for different litigants in the same batch?
You can set specific prefixes and starting numbers for each production volume. The software ensures the sequence remains unbroken even if you add or remove files before the final export.
How does the software handle encrypted or password-protected PDFs?
Local processing allows you to provide the password to your own browser instance to decrypt the file for stamping. This information is never transmitted to our servers, keeping your credentials secure.
Sources / Further reading: See OmniBates Features for technical specs on local processing and run log generation.