Metadata in e-discovery is the hidden information inside electronic files — timestamps, authorship, routing, GPS coordinates, tracked changes — that federal litigants must preserve, produce, and sometimes fight over under Rules 26, 34, and 37(e) of the Federal Rules of Civil Procedure. The visible text of a document rarely proves when it was written, who touched it, or whether it was altered. Metadata does. That is why courts treat it as discoverable evidence and why mishandling it carries real consequences, from cost-shifting to case-ending sanctions.
If you are a party, counsel, or in-house decision-maker facing a dispute that involves electronic records, the work breaks into a few concrete steps: figure out what metadata matters, preserve it in time, agree on how it will be produced, and protect privilege along the way.
What Metadata Actually Matters in a Case
Not every field is worth fighting for. Asking for everything inflates costs; asking for too little leaves gaps you cannot fix later. The categories most litigants care about fall into a few groups.
System metadata is what the operating system tracks about a file: name, location, size, and the created, modified, and last-accessed timestamps. Those timestamps are often the backbone of a timeline — they can show when a file moved between devices or when someone opened a document they later denied seeing.
Application metadata lives inside the file. Word processors retain tracked changes and earlier drafts. Spreadsheets carry formulas that show how a number was built, not just the number itself. Emails contain header fields with blind-copy recipients and the servers a message passed through.
Embedded metadata in photos is especially powerful. EXIF data from a smartphone records GPS coordinates, timestamps accurate to the second, and device information. A photo whose embedded timestamp lines up with an independent record becomes verified evidence rather than a loose image, and forensic examiners can test whether that data has been altered.
Social media records add their own layer: login times, IP addresses, geolocation tags, and interaction histories. Printing a page or taking a screenshot strips all of this away, which is why social media collection requires specialized tools.
When the Duty to Preserve Begins
The obligation to preserve metadata starts the moment a party reasonably anticipates litigation. Zubulake v. UBS Warburg established that once litigation is foreseeable, a company must suspend routine document destruction and issue a litigation hold so relevant files stay intact. No formal lawsuit is required to trigger this. A demand letter, an internal complaint hinting at legal action, or a supervisor acknowledging privately that a suit seems likely can all start the clock. The hold covers metadata alongside the documents themselves.
Miss this step and the rest of the e-discovery process gets much harder, because the fight shifts from what to produce to what was lost and why.
Scope, Proportionality, and Production Format
Rule 26(b)(1) lets parties discover any nonprivileged matter relevant to a claim or defense, filtered through proportionality. Courts weigh six factors before compelling broad metadata production: the importance of the issues, the amount in controversy, each party’s relative access to the information, the parties’ resources, the importance of the discovery for resolving the dispute, and whether the burden or cost outweighs the likely benefit.1Legal Information Institute. Federal Rules of Civil Procedure Rule 26
A party can also resist producing data from sources it identifies as not reasonably accessible because of undue burden or cost. Archived backup tapes and legacy systems often fit that description. A court can still order production if the requesting side shows good cause.1Legal Information Institute. Federal Rules of Civil Procedure Rule 26
Rule 34 governs format. When a request does not specify one, the producing party must hand the information over either in the form it is ordinarily maintained or in a reasonably usable form.2Legal Information Institute. Federal Rules of Civil Procedure Rule 34 Courts tend to favor formats that preserve searchability and sorting, which is why stripping metadata on the way out the door usually invites a dispute.
Negotiating the ESI Protocol
Rule 26(f) requires the parties to confer early and build a discovery plan addressing the form of ESI production, preservation, and privilege.1Legal Information Institute. Federal Rules of Civil Procedure Rule 26 The metadata details are nailed down in an ESI protocol — effectively the technical contract between the parties. This is where most practical disputes get prevented or baked in.
Two decisions dominate the protocol.
Which Fields You Need
Date Sent, Author, File Extension, and Last Modified Date are standard starting points. A case involving spreadsheet manipulation might also call for formula data and cell edit history. A case built on photos might require EXIF. Requesting fields you do not need drives up processing costs; omitting fields you do need forces a second trip to the well, often with less leverage.
Native Format or Static Images
Native files preserve all metadata and allow full interaction with the document, but they are harder to redact. Spreadsheets are the hardest case: merged cells, embedded charts, and formula dependencies can turn a simple redaction into a cascading problem across the workbook.
Static images like TIFF or PDF are easier to review and redact, but they strip metadata unless it rides along separately. That is the job of load files — typically .DAT files holding the metadata field values and .OPT files linking each image to its Bates number. Confirming these specifications early prevents technical disputes that can delay production for weeks.
Sanctions When Metadata Is Lost
Rule 37(e) controls what happens when electronically stored information that should have been preserved is gone. It applies when three conditions line up: the information should have been preserved in anticipation of litigation, the party failed to take reasonable steps to preserve it, and it cannot be restored or replaced through additional discovery.3Federal Judicial Center. Amendments to the Federal Rules of Practice and Procedure: Civil Rules 2015 – Failure to Preserve Electronically Stored Information
The consequences split into two tiers. Under Rule 37(e)(1), if the loss causes prejudice, a court can order curative measures “no greater than necessary” to remedy that prejudice. Under Rule 37(e)(2), the heavier sanctions require a finding that the party acted with intent to deprive the other side of the information. Only then may a court presume the lost information was unfavorable, instruct the jury to draw that same presumption, or dismiss the case.4Legal Information Institute. Federal Rules of Civil Procedure Rule 37
That intent threshold is where spoliation cases are won and lost. Negligent destruction, even grossly negligent destruction, does not unlock the harshest sanctions under the federal rule. Proving someone deliberately wiped files is a different battle than showing someone forgot to issue a hold.
Protecting Privilege With a 502(d) Order
Metadata creates a privilege problem that visible text usually does not. Tracked changes can expose attorney comments. An Author field can reveal that in-house counsel drafted what looks like a business memo. Hidden speaker notes in a presentation can contain legal strategy. Reviewing every field across thousands of documents for privilege is expensive, and mistakes happen.
Federal Rule of Evidence 502 is the safety net. Rule 502(b) says an inadvertent disclosure does not waive privilege if the holder took reasonable steps to prevent it and promptly tried to fix the error after discovery. The stronger protection is Rule 502(d), which lets a federal court order that any disclosure connected to the litigation — inadvertent or otherwise — does not constitute waiver. That order binds not just the parties in the case but anyone in any other federal or state proceeding.5Legal Information Institute. Federal Rules of Evidence Rule 502
A 502(d) order is the most cost-effective tool in metadata-heavy litigation. It lets parties narrow their pre-production privilege review because the worst consequence, permanent waiver, is off the table. Some parties use these orders to skip detailed privilege review in favor of a clawback arrangement: produce everything, and if privileged material surfaces, the producing party claws it back without penalty. The Rule 26(f) conference is the right time to raise it, since the discovery plan explicitly contemplates whether parties want to ask the court for a 502(d) order.1Legal Information Institute. Federal Rules of Civil Procedure Rule 26
Ethical Duties Around Metadata
Technology Competence
Comment 8 to ABA Model Rule 1.1 states that lawyers must keep abreast of changes in the law and its practice, “including the benefits and risks associated with relevant technology.”6American Bar Association. Model Rules of Professional Conduct Rule 1.1 Competence – Comment A majority of states have adopted that language. In practice, an attorney who does not understand what metadata is, how it can be preserved or destroyed, and how format choices affect the evidence is falling short of the competence standard. You do not need to be a forensic examiner. You need to know enough to spot the problems and ask the right questions.
Reviewing Metadata in Documents You Receive
What happens when a document from opposing counsel contains metadata exposing privileged information — an attorney’s name in the Author field, tracked changes showing legal advice, comments meant for internal eyes only? What you can do with that depends on where you practice.
The ABA’s position in Formal Opinion 06-442 is that the Model Rules do not specifically prohibit reviewing metadata embedded in documents received from another party. The only affirmative duty under Model Rule 4.4(b) is that a lawyer who receives information and knows or reasonably should know it was inadvertently sent must promptly notify the sender.7American Bar Association. Model Rules of Professional Conduct Rule 4.4 Respect for Rights of Third Persons The rule requires notification but does not explicitly require you to stop reading or return the document.
Several states disagree. New York, Alabama, and Maine, among others, have concluded that deliberately mining metadata from opposing counsel’s documents is ethically impermissible and may constitute dishonesty or deceit. Other jurisdictions permit it only in certain circumstances or leave the response to the receiving attorney’s discretion. Check your jurisdiction’s ethics opinions before opening a file’s properties panel, and scrub your own documents of privileged metadata before sending anything out.
Budgeting for Metadata Work
Metadata-related costs stack up across processing, hosting, forensic extraction, and review, and attorney review of documents and their associated metadata typically accounts for 70% or more of total e-discovery spend. Volume drives that number, which is why narrowing metadata fields in the ESI protocol pays off directly.
Those costs are also substantive, not just operational. When a metadata request would generate hundreds of gigabytes of processing against a modest amount in controversy, courts have discretion to limit scope under Rule 26’s proportionality factors. A realistic cost estimate built before the Rule 26(f) conference strengthens your position whether you are requesting broad production or resisting it.