Native Production Isn't the Risk the Playbook Says It Is

Native files or page images: the format choice sets the bill and the fights that follow.

Native production means you hand over files the way they were kept, metadata and all, instead of flattening them into pictures. So the question I'd put to you is plain: who on your matter checks the files before they leave?

The playbook says otherwise. It says natives leak and invite fights, so you pay to convert, and the conversion is the thing being sold. Back in 2022, practitioners recalled that imaging was once billed at 2 to 3 cents per image and had since become just part of processing. The fee faded. The fear stayed.

And the data moved on without it. A 2023 eDiscovery Assistant piece on collaboration platforms found that internal talk has shifted to chat, that Slack exports arrive as .JSON, and that search terms and TAR (technology-assisted review) "work best with native data." Teams scatters private chats, group chats and files in separate places. You don't image your way through that.

So the question isn't whether native is risky. It's what makes it safe. A protective order, a tool that opens natives cheaply for both sides, and a Rule 502(d) order covering the slip you can't foresee. Then the fight moves to how files get handled once they land, and that is where I'd look first.

What does TIFF conversion actually cost you?

TIFF conversion costs you volume, metadata and hours. One email with a Word attachment came out 41.74 times larger as TIFF than as native, and hosting bills follow volume.

Before you agree to image everything, I'd run three checks on your own matter:

1. Ask what your review platform charges per gigabyte hosted each month. A format that multiplies file size multiplies that bill.
2. List the file types that lose meaning as pictures: spreadsheets, documents with tracked changes, audio and video.
3. Count the documents that truly need redaction. Only those need to become images.

A sworn declaration filed in a federal ESI protocol fight in 2020 put hard numbers on the first check. An email between counsel with a Word file attached was 41.74 times larger as TIFF than as native. A second set, 24 public plaintiff publications and five sets of procedural rules, came out 12.59 times larger. Cloud review platforms charge by the volume they host. So the bigger file is the bigger bill, and it comes every month, and the requesting party pays it.

Then there is the metadata. Anith Mathai, writing on LinkedIn in 2021, said it flat: metadata such as creation date and author "is usually altered or destroyed when a file's format is changed." Mathai also notes TIFF was built by Aldus in 1986 and has not been updated since 1992. That is the format the careful lawyers want.

The EDRM Production Standards say the same thing in a chart. For image productions they flag higher costs for image conversion and longer turnaround on most of the data set. Their Category A, the native and near-native option, images only the files that need redaction.

The common assumption is that imaging is the conservative choice. It is not conservative. It is bigger, slower, and it throws away the dates.

And somebody has to read what comes out. A paralegal in 2024 got a standard TIFF production, thought it was scrambled, and faced about 20,000 .txt and .tiff files by hand. If you are on that end, it helps to know how to go about making an unsearchable image production usable under Rule 34, because nobody else will do it for you.

An analysis of 5 sources shows one pattern: conversion adds volume, adds time, and strips the facts that date a document. In practice, the format choice sets your budget for the life of the case. So before you agree to TIFF, ask who pays for the conversion and what it buys your client.

Our own economics point the same way. At Relevant e-Discovery, AI-assisted review runs cents per document, against dollars per document and roughly $19K/GB for manual review, and you can see that delta on your own matter. The production side runs on immutable originals with content hashing, append-only audit trails and documented chain of custody, so the native you hand over is the native you collected.

Which leaves the one fear that still has teeth, and that is what rides along inside the native file.

What are the real risks of native production, and do the safeguards cover them?

The real risks are hidden fields, embedded attachments, encryption and rendering fights. Most are process failures, and a privilege gate, a clawback order and controlled processing cover them.

The playbook is not lying about failure modes. Practitioners on the r/ediscovery forum laid them out plainly in 2022, and I take each one seriously. So I put one question to each. Is this a problem with the format, or a problem with how somebody handled it?

Four of the five are process failures. One is partly about format, and it touches only the handful of documents that end up in front of a witness.

Here is the part the risk talk leaves out. Hicks Johnson PLLC wrote in 2019 that courts accepting an ordinary-course production look for unaltered metadata, likely including at least the original file name and file path. A bare statement that files were produced as kept "routinely are held insufficient," the firm noted. Conventional wisdom treats every metadata field as exposure. Some of it is simply what the rule asks for.

A Rule 502(d) order is the backstop. Under one, producing a privileged document does not by itself waive privilege, and you can claw it back. I'd like to tell you how often metadata slips out with an order and without one. The sources I have never counted it, and I won't guess.

The clawback has its own weak spot, and it sits on the other side of the table. A receiving vendor that reprocesses your production instead of loading it with your load file rewrites the metadata. Practitioners call that spoliation. It also makes the clawed-back document harder to find later.

Our answer at Relevant e-Discovery is to keep privileged material in your hands from the start. Processing runs single-tenant, or inside your own AWS account under your own keys, with no vendor retention and no model training, so nothing you feed it trains anyone's model or waives privilege.

And the gate has to run every time you produce, which matters when you are deciding between rolling productions or one final set. So the question stops being whether to go native. It becomes how you write native into the protocol, and that fight starts at the meet and confer.

How can a small firm Bates-number and produce natives defensibly without an expensive vendor?

Name the production category at the meet and confer, number each native at the file level, image only what needs it, and check every cited fact against its source exhibit before filing.

The rule gives you more room than most lawyers use. Under Rule 34(b)(2)(E), the requesting party may name a form. If it does not, you may produce in the form the ESI is "ordinarily maintained" or in a "reasonably usable form." And a party "need not produce the same electronically stored information in more than one form." So the first agreement is the one you live with. Get it right at the start.

Here is how I'd run it, in four moves:

1. Propose a category by name. The EDRM Production Standards built their categories to be "easily communicated by attorneys at a meet and confer by referring to the category of production." Say Category A, native and near-native, and put it in writing.
2. Trade review tools. EDRM tells the requesting party to say which review tool it will use, so the producer can build a production that loads. Ask the same question back.
3. Number the file, not the page. Under Category A each file name matches its DocID, as in ABC0000123.doc. That is your Bates number. Image only the redacted documents, plus the few exhibits you will put in front of a witness, and page-number those.
4. Verify before you file. Every fact you cite in a response or a brief should trace to the exhibit it came from. Check it there, not from memory.

None of this needs a litigation support vendor on retainer. It needs a protocol with a category in it and a platform that reads natives. The hard part is discipline, not money.

The fourth step is where small firms get hurt. A wrong cite costs more than a wrong format. At Relevant e-Discovery our outputs link back to the exact exhibit they came from, so an attorney can one-click verify before filing, which is the structural answer to the Mata v. Avianca sanctions risk. I'd rather a lawyer check one link than explain one mistake.

A named category also makes the production harder to attack. When opposing counsel says the format was inadequate, you point to the category they agreed to and the file names that match it. That argument is short, and short arguments tend to win.

If cost is what has kept you off a real platform so far, it is worth reading what a small firm should pay in per-matter versus annual platform pricing before the next meet and confer. Because the protocol is only half of it. The other half is what you do when the documents are not files at all, but a year of chat.

How can I reduce the cost of document review in litigation?

Stop paying to turn files into pictures. Produce native under a 502(d) order, ask for native back, and load what arrives as produced, so review runs on searchable data.

That is the whole bet. When one email weighs 41.74 times more as an image, the image is a bill, not a safeguard.

The next fights won't be about TIFF. They'll be about chat and links. A 2023 eDiscovery Assistant analysis found that Slack, Teams and Gmail now send links instead of attachments, and in Nichols v. Noom the court held hyperlinks are not attachments and would not order discovery redone for a party that hadn't asked up front. So the native terms go in the protocol on day one, or they don't go in.

I'd rather lose an argument at the first meet and confer than a motion later. The first costs a phone call. The motion costs what's left of the budget.

And when the other side's vendor reprocesses what you sent instead of loading it, the metadata that changes is theirs to explain.