How Opposing Counsel Uses Your PDF Metadata Against You

Every document you produce contains a hidden record of everything you thought, changed, and deleted. Here's how it gets used — and how to stop it.

The Metadata You Don't See

When you create a Word document or PDF, the file doesn't just contain what you see on screen. Embedded in the binary structure of the file is a complete record of your document's history:

• Author name — the Windows/Mac account name that created the file, which may differ from what you intend to show
• Revision history — every "accept changes" operation, showing how the document evolved
• Tracked changes — deletions and insertions that appear removed but are still in the file
• Comments — internal notes between attorneys that survive "accepted" reviews
• GPS coordinates — location data embedded in any photo placed in the document
• Edit timestamps — exact dates and times of every modification
• Hidden text — text formatted as white-on-white or hidden that still exists in the file
• Prior document versions — embedded snapshots from "Fast Save" operations

How Opposing Counsel Reads It

Any competent opposing counsel — or their paralegal — can extract this metadata in under two minutes using free tools. On a Mac, mdls filename.pdf dumps dozens of metadata fields instantly. On Windows, right-clicking and selecting Properties → Details reveals author, company, and revision count. More sophisticated analysts use tools like ExifTool, PDF Inspector, or commercial eDiscovery software.

In federal court, metadata is discoverable. Rule 34 of the Federal Rules of Civil Procedure requires production of electronically stored information "in a form or forms in which it is ordinarily maintained" — which includes metadata. Many state courts have adopted equivalent rules.

Real Scenarios Where This Goes Wrong

The Demand Letter That Showed Its Own Negotiation

A plaintiff's attorney sends a $2.1 million demand letter. The PDF's metadata shows 14 revisions. Opposing counsel extracts the revision history and reconstructs that the original draft demanded $4.8 million — then $3.2 million — then $2.1 million over three weeks. That negotiation roadmap now belongs to the defense.

The Settlement Agreement With The Wrong Author

A firm produces a "clean" settlement agreement. The metadata author field reads "Janet Morrison" — a paralegal. Opposing counsel uses this to argue the document wasn't reviewed and signed by a licensed attorney as required, attempting to void the agreement.

The Photo That Placed the Client at the Scene

An attorney includes a client photo in a civil filing. The JPEG contains GPS EXIF data placing the photo at a specific address — an address the client had denied visiting. The metadata became evidence.

The Deleted Paragraph That Survived

An attorney drafts a contract, deletes an indemnification clause, and saves the final version. In Microsoft Word's "Fast Save" format, the deleted clause remains in the binary file. Years later in litigation, the deleted clause is extracted and used to argue about the parties' original intent.

What The ABA Says About Your Obligation

ABA Formal Opinion 477R (2017) updated the standard for competence regarding electronically stored information. The opinion makes clear that attorneys must understand the technology their clients use, including the metadata implications of electronic document production.

Model Rule 1.6 requires attorneys to make reasonable efforts to prevent unauthorized disclosure of client information. Sending documents with embedded metadata to opposing counsel is increasingly being viewed as a failure of that duty.

Several state bars — including New York, Florida, and California — have issued specific guidance on metadata, noting that inadvertently sending privileged metadata may waive the privilege and constitute an ethical violation.

How to Strip Metadata Before Production

The most reliable method is to use a dedicated metadata stripping tool that processes the file structure itself — not just the visible content. "Print to PDF" removes some metadata but misses embedded objects, XMP packets, and document properties.

ShieldDrop processes 200+ file types, rebuilds PDFs from scratch to eliminate incremental update history, and strips EXIF, XMP, IPTC, document properties, and revision data — all in your browser without uploading files to any server.