Workflow 9 min read 18 October 2026

PDF in Legal Practice: Court Filings, Discovery, Bates Numbering, and Privilege Logs

Legal professionals rely on PDF for court filings, e-discovery production, contract execution, and document management. This guide covers court-specific PDF filing requirements (PACER, CM/ECF), Bates numbering, redaction for privilege and confidentiality, e-discovery formats (TIFF vs native vs PDF), and PDF/A for long-term case file archiving.

Legal professionals interact with PDFs more intensively than almost any other profession. Court filings require strict PDF format compliance. Electronic discovery involves processing thousands of PDFs under tight deadlines. Contracts must be executed with verifiable electronic signatures. Privileged documents must be redacted before production. And case files must be preserved reliably over decades. This guide covers the PDF-specific requirements and best practices across the legal document lifecycle: court filing formats, e-discovery, Bates numbering, privilege redaction, and long-term archiving for litigation hold purposes.

Court filing requirements: PACER and CM/ECF

In the United States federal court system, electronic filings are submitted through CM/ECF (Case Management/Electronic Case Files) and accessed via PACER (Public Access to Court Electronic Records). PDF format requirements for federal court filings are specified in local court rules and the PACER/CM/ECF system requirements. Common PDF filing requirements: - Format: PDF version 1.4 or later. Text-based (searchable) PDFs required — scanned-image-only PDFs are not acceptable for most filing types. - No encryption or passwords: Filing PDFs must not have security restrictions that prevent access. - File size limits: Most federal courts have a 10 MB per-document limit (some courts 15 MB). Exhibits must be filed as separate attachments. - Fonts: Fonts should be embedded (reduces rendering variance across court computers). Non-embedded standard fonts (Times New Roman, Arial/Helvetica) are typically acceptable but embedding is best practice. - Bookmarks: Longer documents (over 50 pages) often require bookmarks/outlines for each major section. - Hyperlinks: Internal hyperlinks to exhibits are permitted and expected in jurisdictions with CM/ECF 6.x. - Page orientation: Portrait for pleadings; landscape acceptable for exhibits with wide tables or drawings. - No JavaScript: PDFs with JavaScript may be rejected by the filing system. State court systems — State courts have their own e-filing systems (Odyssey, Tyler Technologies, JusticeConnect) with varying PDF requirements. Always check the specific court's local rules before filing.

Bates numbering

Bates numbering is the systematic page-by-page labelling of documents in legal proceedings to enable unambiguous reference. Each page receives a unique sequential identifier — typically a prefix identifying the producing party plus a zero-padded number (e.g., PLAINTIFF00001, DEF-000001). Bates numbers are used in deposition transcripts, discovery productions, trial exhibits, and briefs. Bates stamp placement — Bates numbers are typically stamped in the footer of each page (bottom-right or bottom-centre). They must be visible but should not obscure the document's content. The stamp is added as a content stream overlay — a Form XObject stamped onto each page. This is a permanent modification to the PDF; the Bates number becomes part of the page content. Bates numbering in Acrobat Pro: 1. Tools > Organize Pages > More > Add Headers & Footers. 2. Alternatively: Tools > Edit PDF > Header & Footer > Add. 3. Add a Bates number using the Bates Numbering option (available in the multi-file Bates numbering dialog: Tools > Edit PDF > More > Bates Numbering > Add). Acrobat's Bates numbering dialog allows setting prefix, suffix, starting number, and number of digits. It processes multiple PDFs in sequence, applying continuous numbering across the entire production set. Third-party tools — Litera, Xerox LitigationReady, and Nuance tools provide Bates numbering as part of broader legal document processing suites. Python with PyMuPDF can implement Bates numbering programmatically for automated production pipelines. Bates ranges in briefs — Court briefs cite documents by Bates range (PLAINTIFF00001–PLAINTIFF00025 for a 25-page document). The relationship between Bates numbers and PDF page labels is important: a document may have its own internal page numbering (i, ii, 1, 2, ...) that differs from its Bates numbers. Maintaining both is standard practice.

Redaction for privilege and confidentiality

Legal document redaction removes privileged, confidential, or irrelevant content from documents before production. This is distinct from cosmetic blackout — the content must be permanently removed from the file, not just visually hidden. Why visual-only redaction fails — Placing a black rectangle over text using an annotation or a content stream shape does not remove the underlying text. The text remains in the PDF content stream and can be extracted by selecting it, using Ctrl+F, or running a text extraction tool. This has caused significant privilege breaches in high-profile cases (the infamous "NSA PDF" case and various corporate litigation examples). Only proper redaction — where the content stream data is removed — is compliant. Correct redaction in Acrobat Pro: 1. Tools > Redact. 2. Use "Mark for Redaction" to select text, images, or areas. 3. Use "Find & Redact" to locate and mark all occurrences of specific text strings. 4. Click "Apply Redactions" — this removes the marked content from the content stream and replaces it with a solid redaction mark. 5. After applying, use Sanitize Document to remove hidden data (metadata, annotations, embedded content, JavaScript) that might reveal redacted information. Privilege log redaction — Privilege logs list documents withheld from production with descriptions that do not reveal privileged content. Redacted documents that are produced (rather than withheld) need the redaction marks to clearly indicate the type of withheld information (e.g., "ATTORNEY-CLIENT PRIVILEGE", "WORK PRODUCT") as a visible watermark on the redaction box. Redaction verification — After redaction, verify by: (1) opening the file in a text editor (the redacted text should not appear); (2) running pdftotext (the text should not be extractable); (3) having a second reviewer confirm the applied redactions are complete.

E-discovery and litigation hold PDF formats

E-discovery (electronic discovery) involves identifying, preserving, collecting, processing, reviewing, and producing electronically stored information (ESI) in response to litigation or regulatory investigation. PDFs are involved at multiple points. Native vs TIFF vs PDF production — Electronic documents are traditionally produced in three formats: native (original file format — Word, Excel, email), TIFF (image-only with OCR), or PDF. TIFF was the e-discovery standard for decades because it was reproducible and verifiable. PDF has largely displaced TIFF for most modern e-discovery productions because: searchable PDF is more useful than TIFF for review teams, PDF preserves formatting better than flat TIFF, and PDF file sizes are generally smaller. EDRM standards — The Electronic Discovery Reference Model (EDRM) provides guidelines for e-discovery practices. The EDRM model covers information governance, identification, preservation, collection, processing, review, analysis, production, and presentation. PDF is a specified production format in most EDRM-compliant production specifications. Litigation hold and PDF/A — Litigation hold requires preserving documents in a manner that prevents modification. For PDFs subject to litigation hold: use PDF/A format (self-contained, no external dependencies), store on WORM or write-protected storage, and apply RFC 3161 trusted timestamps to establish the document's existence at a specific date. Hash values (SHA-256) of each preserved PDF should be recorded in a manifest for integrity verification. Metadata in e-discovery PDFs — Document metadata is discoverable in litigation. PDF metadata (XMP and DocInfo) fields including Author, Creator, modification history, and embedded file properties may need to be preserved (for production) or scrubbed (for confidentiality protection). Production specifications typically specify whether metadata should be stripped or included.

Frequently asked questions

What PDF format do federal courts require for CM/ECF filings?

Federal courts using CM/ECF (Case Management/Electronic Case Files) generally require: PDF version 1.4 or later, searchable text (not scanned image-only), no password protection or encryption, fonts embedded or using standard fonts, file size under 10 MB per document (varies by court). Many courts also require bookmarks in longer documents. The specific requirements vary by district court — always check the local rules of the court you are filing in. The PACER website (pacer.gov) publishes technical specifications for PDF filing. Some courts have moved to PDF/A requirements for long-term archiving. JavaScript, multimedia, and non-standard features should be avoided. State court e-filing systems (Odyssey, Tyler Technologies) have their own requirements, often similar to federal CM/ECF.

How do I add Bates numbers to a PDF without Adobe Acrobat?

With Python and PyMuPDF: import fitz; doc = fitz.open("input.pdf"); for i, page in enumerate(doc): bates = f"PLAINTIFF{i+1:05d}"; page.insert_text((page.rect.width - 100, page.rect.height - 20), bates, fontsize=9, color=(0,0,0)); doc.save("bates_numbered.pdf"). This inserts a text Bates number at the bottom-right of each page. For a multi-file production set with continuous numbering, add a start_bates parameter and accumulate across files. For production-quality Bates stamping (consistent positioning, font, formatting), consider Litera or similar legal document processing tools. Note that Bates numbers added to PDFs this way are content stream text — they are permanent and part of the page content, which is the correct approach for legal productions.

What is the difference between redaction and sanitisation in PDF?

Redaction removes specific visible content (text, images, areas) from the PDF page — replacing it with a solid mark or blank area. Sanitisation removes hidden data from the PDF that the redaction process itself may not address: metadata (author, revision history), annotations (which may contain privileged text in comments), embedded files, hidden layers, JavaScript, form field values, cached versions of the document, and digital signature information. Acrobat Pro's "Sanitize Document" function (available in the Redact toolbar after applying redactions) performs sanitisation. For legally compliant privilege redaction, both redaction (content removal) and sanitisation (hidden data removal) are necessary — redaction alone is not sufficient because metadata and annotations may reveal privileged information that does not appear visually on the redacted page.

Try it yourself

Everything in this article can be done directly in the free PDFTheGuide editor — no account required.

Redact PDF Sign PDF Protect PDF Open editor