Varying PDF page sizes often break court-mandated discovery seqences

A 50,000-page production is rarely uniform. You're dealing with a chaotic mix of standard letter-sized memos, legal-sized contracts, and high-resolution smartphone photos of handwritten notes. When you apply a static Bates stamp across a set with varying aspect ratios, the numbers frequently 'drift' off the page or overlap critical text. In 2026, courts are increasingly rejecting productions where the Bates label is cut off by the printer's non-printable area or obscured by a document header. Use toolsets that anchor stamps based on relative pixel coordinates rather than fixed margins to ensure every page—regardless of size—remains compliant.

The geometry of a failed production

Most software treats every page as an 8.5 x 11 canvas. This is a mistake. When your discovery set includes landscape-oriented spreadsheets or oversized architectural scans, a standard 'bottom right' stamp often lands in a void or gets sliced in half during the conversion process. If the stamp isn't visible, the document isn't legally identifiable in a deposition.

We see high failure rates when firms try to 'force' uniform margins on a disparate set of files. Not only does this risk stretching the evidentiary image, but it also creates a massive amount of manual QC work. A single misplaced stamp in a 10,000-page run can trigger a motion to compel, forcing your team to redo the entire production from scratch.

Comparing production methods for mixed file sizes

Feature	Manual Stamping	Browser-Based Local Processing	Cloud-SaaS Discovery
Page Size Flexibility	Poor; requires manual adjustment	Automatic relative positioning	Variable; often requires 'standardizing'
Data Privacy	High (local)	Absolute (Local-only architecture)	Low (files leave your device)
Processing Speed	Extremely slow	Thousands of pages per minute	Limited by upload bandwidth
Audit Integrity	None	Full Run Logs	Partial

Why local processing handles scaling better than the cloud

Reliability in 2026 discovery isn't just about speed; it's about security and sovereignty. When you're managing a production-scale job, uploading 20GB of sensitive legal documents to a third-party server just to add a footer is a massive security liability.

Local-first software like OmniBates processes the files entirely within your browser's memory. This means the documents never leave your device. Because the heavy lifting is done by your local hardware rather than a shared cloud server, you aren't fighting for bandwidth or waiting in a rendering queue during peak filing hours. You get same-day productions with the peace of mind that your data remains behind your firm's firewall.

Checklist for final production verification

Before you hit 'send' on a production volume, verify these technical markers:

• Sequence Continuity: Are there any gaps in the Bates-sequential numbering between volumes?
• Margin Clearance: Does the stamp remain at least 0.5 inches from the edge on both 8.5x11 and 8.5x14 pages?
• Legibility: Is the prefix and number distinct from the document's native footer text?
• Run Logs: Do you have an audit-ready log that matches the final page count for the court?

How do I handle landscape orientations without manual rotation?

Advanced discovery tools detect the metadata of the PDF page rotation and adjust the stamp's X/Y coordinates automatically. This ensures the Bates number appears in the same relative position (usually the bottom right) whether the page is portrait or landscape. This eliminates the need for manual pre-sorting before the production run.

Can I process password-protected files with OmniBates?

No. For security and integrity reasons, documents must be decrypted before they are stamped. This ensures that the Bates label is permanently 'burned' into the document layer and cannot be stripped away or altered after service. This immutability is a core requirement for court-approved formats.

What happens if I make a mistake in the matter prefix?

With local processing, you can simply clear the queue and rerun the production. Since there is no per-page 'upload fee' or cloud processing cost, you can iterate on your production formatting until the coordinates are pixel-perfect. We recommend running a 5-page sample of mixed sizes before committing to a 5,000-page run.

Why are run logs required for 2026 productions?

A run log serves as your firm's technical affidavit. It proves exactly which files were processed, their original filenames, and their assigned Bates ranges. If the opposing counsel claims a document is missing or was altered, your audit-ready run log is your primary defense to prove the chain of custody remained intact from the moment of discovery export to the final production.

Sources / Further reading: Consult the 2026 Federal Rules of Civil Procedure (FRCP) regarding the technical standards for 'Electronically Stored Information' (ESI) productions.