Skip to main content
Records Authority
Category: E-Discovery and Legal Holds

Native Format Production

Also known as: Native Production, Native File Production, Native File Format Production
Simply put

Native format production is the practice of providing electronic documents in the same file format used by the application that originally created them, such as a word processing file kept in its authoring format rather than converted to an image. In this approach, files are typically supplied as copies of the originals with their embedded information intact, rather than being flattened into a static format. It is commonly encountered in the context of litigation and eDiscovery, where parties exchange documents.

Formal definition

Native format production refers to the exchange of electronic files in the format generated by their originating (authoring) application, preserving the file in a state that ideally reflects the original as created, with associated metadata typically intact. True native files are described in the evidence as copies of the original documents in the authoring application's format, existing in the same state as when captured or uploaded and not modified thereafter. This contrasts with converted or imaged production formats (such as rendered page images), where the document is transformed for review or redaction purposes; the practice is most often discussed within eDiscovery workflows covering the review and production of file types from their source. Note that the scope of what constitutes a 'native' file, and the extent to which metadata and integrity are preserved, may depend on collection and processing practices; the evidence provided does not address jurisdiction-specific procedural requirements governing when native production is required or permitted.

Why it matters

Native format production matters because the format in which electronic documents are exchanged can affect what information is preserved and available to the receiving party. When a file is supplied in the format created by its authoring application, embedded information and associated metadata typically remain intact, whereas converting a document into a static image can flatten or strip away that content. In litigation and eDiscovery contexts, where parties exchange documents as evidence, these differences can be significant for assessing the completeness and integrity of what is produced.

The practice also bears directly on the properties that distinguish an authoritative record from a mere copy or rendering. A true native file is described as a copy of the original that has not been modified since it was captured or uploaded, existing in the same state as when it entered the collection. Preserving files in this state supports the authenticity, integrity, and usability of the material, which can matter when the reliability of a document is contested. Because native files retain their original structure, spreadsheets, embedded formulas, and other application-specific features remain accessible rather than being reduced to a fixed page image.

At the same time, native production involves practical trade-offs that professionals should weigh. Native files can be more difficult to redact or annotate than imaged formats, which are often used precisely because they can be marked up or partially withheld. The extent to which metadata and integrity are genuinely preserved may depend on how files are collected and processed, so native production is not automatically a guarantee of fidelity. Whether native production is required, permitted, or preferred generally depends on jurisdiction, applicable procedural rules, and the agreement of the parties, matters that fall outside the scope of the evidence here.

Who it's relevant to

Litigation Support and eDiscovery Professionals
Those managing document review and production in litigation rely on an understanding of native format production to determine how file types are collected, processed, and exchanged. They must weigh the preservation of original format and metadata against the practical challenges of reviewing and redacting native files.
Records Managers and Information Governance Officers
Professionals responsible for maintaining records as evidence of activity have an interest in how formats affect authenticity, integrity, and usability. Native production intersects with their concern for keeping authoritative copies in a state that reflects the original as created, rather than as a modified or flattened rendering.
Legal and Compliance Teams
Lawyers and compliance leads involved in disclosure or discovery need to understand what native production preserves and what it does not, since the choice of production format can affect the completeness of what is exchanged. Because requirements depend on jurisdiction and the agreement of the parties, these teams typically address format questions as part of case-specific planning.
IT and Data Processing Staff
Technical staff supporting collection and processing determine, in practice, the extent to which files retain their native characteristics and metadata. Their handling of files during capture and upload directly influences whether a produced file can be described as a true, unmodified native copy.

Inside Native Format Production

Native Format
The file format in which a record or document was originally created and is ordinarily maintained by its authoring application, such as a word processing file, spreadsheet, email store, or database export, as distinct from formats to which the material has been converted for review or delivery.
Metadata Preservation
The retention of embedded and associated metadata that typically accompanies a file in its native state, which may include authorship, creation and modification information, and application-specific properties. Native production is often sought precisely because it can preserve metadata that may be lost or altered when a file is converted to another format.
Production in Litigation or Disclosure Context
The act of delivering electronically stored information to another party, typically during discovery or a comparable disclosure process. The scope, form, and obligations attached to production depend on the applicable jurisdiction, procedural rules, and any agreement or order between the parties.
Alternative Production Forms
Other forms in which material may be produced, such as static image formats (for example, page-rendered images) or extracted text, often accompanied by separate load files carrying metadata. Native production is one option among these and is generally distinguished by delivering the original file rather than a rendered or converted representation.
Integrity and Authenticity Considerations
The properties, such as authenticity, reliability, integrity, and usability, that determine whether produced material can be relied upon as evidence. Producing in native format can support these properties, but it may also raise handling concerns because native files can be more readily altered than fixed representations.

Common questions

Answers to the questions practitioners most commonly ask about Native Format Production.

Does producing records in native format mean the files are handed over exactly as originally created, with nothing changed?
Not necessarily. Native format production refers to providing records in the file format of the application that created or maintains them, rather than converting them to an image or paper equivalent. However, the term describes the format of the produced item, not a guarantee that the file is pristine or unaltered. In practice, steps such as extraction from a source system, copying, or the application of identifiers can occur. Whether the produced file preserves the properties that make it an authoritative record, such as integrity and authenticity, depends on how the production is handled and documented, and often on the requirements of the relevant jurisdiction or matter.
Is native format production the same thing as producing metadata along with the file?
These are related but distinct. Native format production concerns the format in which a record is delivered, whereas metadata refers to the contextual information about the record, such as authorship, dates, or system properties. Native files often carry embedded or associated metadata, and one reason parties may request native production is to retain that metadata. However, producing in native format does not by itself define which metadata is included, preserved, or excluded. Metadata scope is typically addressed separately and may depend on organizational policy, technical constraints, and applicable requirements.
When is native format production typically preferred over an image-based or converted format?
Native format is often preferred when the usability, functionality, or embedded metadata of the original file matters, for example where formulas, tracked changes, or system-generated fields are relevant. It can also reduce conversion effort. The suitability of native versus converted formats generally depends on the purpose of the production, the requirements of the matter or jurisdiction, and any agreement between the parties involved. There is no single format that is appropriate in all circumstances.
What practical steps help preserve the integrity of records produced in native format?
Common measures include documenting the extraction and handling process, maintaining a defensible chain of custody, and recording any changes made during production. Some organizations use verification techniques to confirm that produced files match their source. The specific steps that are appropriate depend on organizational policy, the sensitivity of the records, and any applicable requirements. The goal is generally to be able to demonstrate that authenticity, reliability, integrity, and usability have been maintained through the production process.
How should embedded or associated metadata be handled during native format production?
Because native files can carry embedded and system metadata, organizations typically decide in advance which metadata should be preserved, produced, or excluded, and document that decision. Considerations often include whether the metadata is relevant, whether it contains sensitive or privileged content, and whether producing it is consistent with applicable obligations, which vary by jurisdiction and sector. Handling metadata deliberately, rather than by default, helps avoid inadvertently disclosing or losing significant contextual information.
What challenges commonly arise when producing records in native format?
Practical challenges can include managing files that require specific software to open or interpret, handling large or complex file types, applying identifiers without altering the underlying record, and reconciling native production with any need to redact sensitive content, which can be more difficult in native form than in an image format. Interpretation of the file may also depend on the availability of compatible applications. How these challenges are addressed generally depends on organizational policy, technical capability, and the requirements of the specific matter.

Common misconceptions

Native format production is always the required or default form of production.
The required form of production depends on jurisdiction, applicable procedural rules, and any agreement or order between the parties. In many jurisdictions parties may agree to, or a tribunal may order, image-based or other forms of production instead of, or alongside, native files.
Producing a file in native format automatically preserves all of its metadata and guarantees its integrity.
While native production can retain metadata that conversion might strip away, native files can also be more susceptible to inadvertent alteration during handling. Preserving integrity typically depends on appropriate handling controls and documentation rather than the native format alone.
A native file produced in discovery is necessarily the authoritative record.
A produced file may be an authoritative record, a copy, a draft, or transitory information. Whether a given native file constitutes an authoritative record depends on its characteristics and the recordkeeping context, not on the fact that it was produced natively.

Best practices

Clarify and, where possible, agree the required form of production with the receiving party or as directed by the tribunal early in the process, recognizing that expectations differ by jurisdiction and procedural regime.
Identify which metadata should accompany native files and confirm whether that metadata is preserved or altered by the collection and production workflow before delivery.
Apply and document handling controls that protect the integrity of native files, since native formats can be more readily altered than fixed representations.
Maintain clear documentation of how files were collected, handled, and produced to support later demonstration of authenticity and reliability.
Distinguish authoritative records from copies, drafts, and transitory information within a production set so that the evidential status of each item is understood.
Consider whether native, image-based, or hybrid production forms best meet the applicable obligations and the needs of the matter, rather than assuming a single default form applies.