What is the difference between native, near-native, and TIFF-plus-load-file production formats, and how do I decide which to use?

In e-discovery, “production format” describes how electronically stored information (ESI) is delivered to another party after collection and review. The three most common approaches are native, near-native, and TIFF (or image) plus a load file. Each balances fidelity, usability, redaction, and cost differently. For broader context, see e-discovery.

The Three Formats

Native means files are produced in the same format the application created — a spreadsheet stays a spreadsheet, an email keeps its original structure. Native files preserve metadata and dynamic content (formulas, hidden columns, tracked changes) and are generally the lowest-cost option because no conversion is needed. The trade-offs: they are harder to redact, can be altered, and need Bates-style identifiers tracked outside the file.

Near-native keeps data in a usable, application-like form but standardizes or normalizes it for processing — for example, exporting mailboxes into a common email format. It retains much of the native experience and metadata while making large, complex sources easier to review and produce consistently.

TIFF (or image) plus load file converts each document into static page images accompanied by a load file — a structured text file listing document boundaries, Bates numbers, and selected metadata fields, often with extracted searchable text. This format makes redaction and endorsement straightforward and produces a fixed, tamper-evident record, but it strips dynamic content and increases volume and cost.

How to Decide

There is no single correct answer; the right format depends on the data and the matter. Useful questions include:

• Does the content depend on metadata or dynamic features? Spreadsheets and databases often demand native or near-native production.
• Is redaction needed? Privileged or sensitive material is frequently easier to redact in an imaged format.
• What do the rules and the parties require? US federal civil practice emphasizes form-of-production planning and meet-and-confer discussion; many parties adopt hybrid productions (native for some file types, images for others). State courts and other countries impose different requirements.

Agreeing on format early — and documenting it in a stipulation or ESI protocol — reduces disputes, rework, and cost later.