Document

File Formats for Legal Documents: Compliance and Best Practices

Published Mar 19, 2026 8 min read By ChangeThisFile Team

Quick Answer

Legal documents have strict format requirements: PDF/A for court filings and long-term archival, PAdES digital signatures for authenticated documents, proper redaction that removes data from all layers (not just visual masking), and metadata scrubbing before sharing to prevent inadvertent disclosure of hidden information.

Legal documents live under constraints that most other documents don't face. A filing deadline means the format must be exactly right — there's no "resubmit in the correct format" when the court's e-filing system rejects your PDF at 11:58 PM. A redaction failure means confidential information is exposed in public records. A missing digital signature means a contract isn't legally binding.

The legal profession has standardized on specific formats and practices not because lawyers love technology, but because courts, regulators, and opposing counsel enforce them. This guide covers the format requirements that matter: PDF/A for filings, digital signatures for authentication, redaction for confidentiality, metadata scrubbing for privacy, and document comparison for contract review.

Getting these right is not optional. Format non-compliance can result in rejected filings, sanctions, malpractice claims, and — in the case of failed redaction — ethical violations.

PDF/A: The Court Filing Standard

PDF/A (ISO 19005) is the archival subset of PDF required by most court e-filing systems. The U.S. federal courts (via CM/ECF), the European Patent Office, and numerous national court systems mandate PDF/A for electronic submissions.

PDF/A requirements:

All fonts embedded — the document must render identically without access to system fonts
No encryption — the document must be accessible without passwords
No external dependencies — no linked images, no JavaScript, no external stylesheets
Color space specification — either device-independent color or ICC color profiles
XMP metadata — machine-readable metadata in the file header

PDF/A conformance levels that matter for legal work:

PDF/A-1b — minimum compliance. Requires embedded fonts and device-independent color. Most court systems accept this level.
PDF/A-1a — adds tagged structure (headings, paragraphs, reading order) and Unicode character maps. Required for accessibility compliance.
PDF/A-2b — adds JPEG2000 compression and transparency support. Some modern court systems accept this.
PDF/A-3 — allows embedded files (e.g., XML data, spreadsheets) within the PDF. Used for e-invoicing and some regulatory filings.

To create PDF/A: Microsoft Word (Save as PDF > "ISO 19005-1 compliant" checkbox), LibreOffice (Export as PDF > "Archive (PDF/A-1a)" option), Adobe Acrobat (Save As Other > PDF/A), or Ghostscript command-line conversion. Always validate the result with a PDF/A validator (veraPDF is the open-source standard).

Digital Signatures: PAdES and Legal Validity

Digital signatures on PDFs use the PAdES (PDF Advanced Electronic Signatures) standard, which is a profile of the broader CAdES and XAdES frameworks. A PAdES signature embeds a cryptographic signature, a timestamp, and the signer's certificate chain directly in the PDF file.

PAdES levels:

PAdES-B (basic) — signature with certificate. Valid as long as the certificate is valid.
PAdES-T (timestamp) — adds a trusted timestamp. Proves the signature existed at a specific time.
PAdES-LT (long-term) — embeds validation data (CRLs, OCSP responses). Verifiable even after the certificate authority shuts down.
PAdES-LTA (long-term archival) — adds document timestamps for indefinite validity. The most durable option.

Under the EU's eIDAS regulation, a Qualified Electronic Signature (QES) has the same legal effect as a handwritten signature in all EU member states. QES requires a qualified certificate from a trust service provider. In the U.S., the ESIGN Act and UETA provide legal validity for electronic signatures broadly, without requiring a specific technology.

Practical implementation: Adobe Acrobat Pro, DocuSign, Adobe Sign, and SignNow all create PAdES-compliant signatures. For programmatic signing, libraries like iText (Java), PyKCS11 (Python), and OpenSSL handle the cryptographic operations.

Redaction: Proper vs. Cosmetic

Redaction in legal documents means permanently removing information from all layers of a PDF. It is not the same as drawing a black rectangle over text. This distinction has caused real-world failures:

In 2019, Paul Manafort's legal team filed a court document with "redacted" text that was simply covered by black rectangles. Copy-pasting revealed the hidden text, exposing their legal strategy to the public.
Multiple government agencies have released "redacted" documents where the underlying text was readable by removing the black overlay or copying the text.

Cosmetic redaction (wrong): Drawing a black rectangle, changing text color to black on black background, or layering an opaque shape over content. The original text remains in the PDF and is trivially extractable.

Proper redaction (right): Removes the content from the PDF's content stream, text layer, and metadata. The information is permanently destroyed. The redacted area is replaced with a redaction annotation (usually a black box) that confirms content was removed, not just hidden.

Tools that do proper redaction: Adobe Acrobat Pro (Edit > Redact), LibreOffice Draw (limited), and specialized legal tools (Relativity, Nuix). After redacting, always verify by selecting all text on the page and confirming that the redacted content is truly gone.

Metadata Scrubbing: Hidden Data Leaks

Document metadata is a confidentiality minefield. DOCX files can contain: author name, organization name, creation and modification dates, revision history, hidden text, tracked changes (including deleted text), comments, template paths, printer names, and embedded thumbnail images that may show previous versions of the content.

Real-world metadata exposure incidents are common. Lawyers have accidentally disclosed draft language by not scrubbing tracked changes. Author metadata has revealed ghostwriters. Template file paths have exposed internal network structures.

DOCX metadata scrubbing: Word's Document Inspector (File > Info > Check for Issues > Inspect Document) finds and removes hidden metadata, tracked changes, comments, and personal information. Run it on every document before sharing with opposing counsel.

PDF metadata scrubbing: Adobe Acrobat's "Remove Hidden Information" tool strips metadata, bookmarks, comments, hidden text, and embedded file attachments. The open-source tool exiftool can strip EXIF metadata from PDFs.

Best practice: Before sharing any legal document externally, run it through metadata inspection and removal. This should be a checklist item, not an afterthought. If sending as PDF, convert from the scrubbed DOCX — don't just strip PDF metadata, because the conversion process itself can create clean metadata.

Document Comparison and Blacklining

Contract negotiation involves comparing document versions to see what changed — a process called "blacklining" or "redlining." The format affects how well comparison works.

DOCX comparison: Word's Compare Documents feature (Review > Compare) produces a detailed diff showing insertions, deletions, and formatting changes. This works well with DOCX files because Word can access the document's paragraph structure. The result is a new document with tracked changes showing every difference.

PDF comparison: Comparing PDFs is harder because PDF doesn't store paragraph structure. Tools like Adobe Acrobat's Compare (Tools > Compare Files) and DiffPDF (open source) compare rendered pages visually, highlighting differences. This catches visual changes but may miss non-visual differences (metadata changes, hidden content, changed bookmarks).

Best practice for contract comparison: Compare in DOCX format, not PDF. If you receive a PDF revision, convert to DOCX first and compare against your DOCX version. The structural comparison is more reliable than visual comparison. Export the comparison result to PDF for the record.

Bates Numbering and Production Formats

Bates numbering assigns a unique sequential identifier to every page in a document production. In litigation discovery, each page is stamped with a Bates number (e.g., ACME-000001 through ACME-045678) that serves as a permanent reference. Bates stamps are typically placed in the footer or lower-right corner of each page.

Production formats vary by jurisdiction and agreement between parties:

Single-page TIFF + load file: The traditional production format. Each page is a separate TIFF image, with a load file (Concordance DAT, Relativity, or Summation) containing metadata and text extraction. This format is declining but still used in older proceedings.
PDF: Increasingly accepted for productions. Each document is a separate PDF with Bates numbering. Text-searchable PDFs are preferred. Some courts still require TIFF.
Native format: Producing files in their original format (DOCX, XLSX, emails as MSG/EML) with Bates-numbered slip sheets. Required for spreadsheets and databases where TIFF/PDF flattening destroys data structure.

Adobe Acrobat Pro and legal production tools (Relativity, Concordance, Nuix) handle Bates stamping. For basic needs, Acrobat's "Add Bates Numbering" feature (Edit > Header & Footer > Bates Numbering) works on individual PDFs or batches.

E-Filing: Format Checklist

Court e-filing systems (CM/ECF in the U.S. federal system, state equivalents, and international systems) impose specific format requirements. Common requirements:

Format: PDF (most systems), specifically PDF/A for some courts
File size: Typically 25-50MB maximum per filing. Large exhibits may need to be split.
Resolution: 300 DPI minimum for scanned documents
Color: Some courts require black-and-white or grayscale for cost reasons
Bookmarks: Required for exhibits and appendices in some jurisdictions (each exhibit bookmarked)
Text searchable: Required by most modern courts. Scanned documents must have OCR text layer.
Filename: Often specified (e.g., "Brief_in_Support.pdf" or case number format)
No security: No password protection, no permissions restrictions

Always check your specific court's local rules for electronic filing. Requirements vary by court, and non-compliance can result in rejected filings or orders to re-file. The consequences of a rejected filing at a deadline are severe.

Legal document formatting is a compliance issue, not an aesthetic one. The consequences of getting it wrong range from embarrassing (metadata exposure) to career-ending (failed redaction of client confidential information) to malpractice (missed filing due to format rejection). Treat document format preparation as a checklist process: validate PDF/A compliance, verify redaction completeness, scrub metadata, and confirm e-filing requirements before every submission.

The good news: these are mechanical processes. Once you establish a workflow — create in DOCX, review and redact, convert to PDF, validate PDF/A, scrub metadata, file — it becomes routine. The format doesn't need to be interesting. It needs to be correct.

Key Takeaways

PDF/A (ISO 19005) is the standard for court filings. It requires embedded fonts, no encryption, and no external dependencies. Validate with veraPDF.
Cosmetic redaction (black rectangles) does NOT remove text. Proper redaction permanently destroys content from all PDF layers. Verify by selecting text after redacting.
Document metadata (author, tracked changes, comments, revision history) is a confidentiality risk. Scrub it before every external sharing.
Digital signatures using PAdES have legal validity under eIDAS (EU) and ESIGN/UETA (US). PAdES-LTA provides indefinite verifiability.
Compare contracts in DOCX format for structural accuracy. PDF comparison is visual only and may miss non-visual changes.
E-filing requirements vary by court. Check local rules for format, size limits, searchability requirements, and filename conventions.

Frequently Asked Questions

What PDF format do courts require?

Most U.S. federal courts and many state courts require PDF for e-filing. Some specifically require PDF/A (ISO 19005) for archival compliance. The exact requirement varies by court and jurisdiction — always check the local rules for electronic filing. When in doubt, PDF/A-1b is the safest choice as it satisfies both standard PDF and archival requirements.

How do I properly redact a PDF?

Use a tool that performs actual content removal, not just visual masking. Adobe Acrobat Pro's Redact tool (Edit > Redact > Mark for Redaction, then Apply) permanently removes text from the PDF's content stream. After applying redaction, verify by selecting all text on the page — redacted content should not be selectable or copyable. Never use black rectangles, black highlight, or text color changes as redaction.

What metadata should I remove before sharing a legal document?

Remove: author name and organization, creation/modification dates (if sensitive), tracked changes and revision history, comments and annotations, hidden text, template file paths, and printer information. In Word, use File > Info > Inspect Document. In Acrobat, use File > Properties > Additional Metadata, and Tools > Remove Hidden Information.

Are electronic signatures legally binding?

Yes, in most jurisdictions. The U.S. ESIGN Act (2000) and state UETA laws give electronic signatures the same legal validity as handwritten signatures for most transactions. The EU eIDAS regulation provides a framework with three levels: simple, advanced, and qualified electronic signatures. Qualified signatures (using a certified provider) have the strongest legal standing in the EU.

How do I create a PDF/A document?

From Word: File > Save As > PDF > Options > check 'ISO 19005-1 compliant.' From LibreOffice: File > Export as PDF > check 'Archive PDF/A-1a.' From Adobe Acrobat: File > Save As Other > PDF/A. Always validate the result with a PDF/A validator like veraPDF to confirm compliance before filing.

Can I compare a PDF against a Word document?

Yes. Convert the PDF to DOCX first, then use Word's Compare Documents feature. The PDF-to-DOCX conversion may not be perfect (especially for complex layouts), but the structural comparison in Word is more reliable than visual PDF comparison for finding text changes. ChangeThisFile supports PDF-to-DOCX conversion at /pdf-to-docx.

What is Bates numbering?

Bates numbering assigns a unique sequential identifier to every page in a document production for litigation. Each page gets a stamp (e.g., ACME-000001) that serves as a permanent reference in court proceedings. Bates numbers are used in citations, indices, and privilege logs. Adobe Acrobat Pro and legal production software handle Bates stamping automatically.

Why was my e-filing rejected?

Common reasons: file exceeds size limit (typically 25-50MB), PDF is password-protected (courts require no security), document is not searchable (OCR required for scans), wrong PDF version (some courts require PDF/A), filename doesn't match required format, or the file is corrupted. Check the court's rejection notice for the specific reason and the local rules for requirements.

Ready to convert your files?

Use ChangeThisFile to convert between 600+ formats — free, fast, and private.

Start Converting