A spreadsheet that looks ordinary in a TIFF viewer can contain formulas, hidden columns, comments, pivot tables, and metadata that change the meaning of the evidence. A message shown only in its native email format may be difficult to redact or present consistently at trial. That is the practical issue behind native review vs image review: the format chosen for attorney review affects what reviewers can see, how quickly they can work, and whether the final production is defensible.
For high-stakes litigation, investigations, and regulatory matters, this is not an either-or decision made once at case intake. Most matters require a controlled combination of native files, rendered images, searchable text, and production-ready formats. The right approach depends on the document population, the protocol, the review objective, and the downstream demands of depositions and trial.
Native Review vs Image Review: The Core Difference
Native review displays a file in or close to its original application format. An Excel workbook is reviewed as an Excel workbook. A PowerPoint presentation retains its slides, notes, animations, and embedded elements where the review platform can render them. Email may be viewed with original message fields and attachments intact.
Image review presents a fixed visual rendering of a document, commonly as single-page TIFF or PDF images accompanied by extracted text and, where available, OCR text. The document is viewed as pages rather than as an editable file. This model closely resembles the way paper discovery has historically been reviewed, numbered, redacted, and produced.
Neither format is inherently superior. Native review preserves file behavior and content that may be lost in conversion. Image review provides stable pagination and more reliable visual control. Legal teams should decide which risks matter most for each document type and each stage of the matter.
When Native Review Is the Better Choice
Native review is particularly valuable when the substance of a document depends on functionality, structure, or embedded content. Financial models, data exports, CAD files, audio and video, complex presentations, and databases are common examples.
Spreadsheets and Structured Data
Excel files are the clearest case for native review. A static image can show cell values, but it may not reveal formulas, hidden worksheets, external links, filters, comments, or the relationship between tabs. A reviewer assessing a damages model, accounting schedule, or operational report often needs to test formulas and trace inputs. Reviewing only an image can conceal precisely the information that makes the file relevant.
That does not mean every spreadsheet should be produced natively without controls. Native spreadsheets can contain hidden information, tracked changes, personal data, or metadata outside the intended production scope. The legal team must evaluate the file, apply confidentiality designations, and confirm whether redactions or a slip-sheet process are required before production.
Files With Multimedia or Interactive Features
Video, audio, dynamic presentations, and certain proprietary files lose practical value when converted into page images. A call recording cannot be meaningfully reviewed as a TIFF. A presentation with speaker notes, linked media, or layered graphics may be incomplete when flattened.
Native handling also helps reviewers understand whether an item is usable evidence. A broken link, inaccessible attachment, or unsupported proprietary format may require special processing, conversion, or consultation with the producing party. Identifying those issues during review is better than discovering them in the week before a deposition.
Metadata-Driven Questions
Where creation dates, modification history, file paths, authorship, or other metadata are material, native files can provide essential context. Review platforms can expose much of this information in metadata fields, but a native file may still be necessary to investigate a dispute about provenance or authenticity.
The trade-off is consistency. Native files can render differently across applications, versions, and user environments. Review teams should establish a protocol for how to handle rendering exceptions, unsupported file types, and documents where the native and displayed content do not align.
When Image Review Provides Better Control
Image review remains the preferred workflow for many document populations because it creates a stable, page-level record. For correspondence, contracts, reports, PDFs, scanned documents, and ordinary business records, an image-based review set is often easier to manage from first-pass review through production.
Reliable Redactions and Bates Numbering
Redactions are a central reason to use images. Privilege, personally identifiable information, protected health information, trade secrets, and confidential business data require a format that supports visual verification before production. Image-based workflows allow the review team to place, quality-check, and burn in redactions on the exact pages that will be delivered.
Bates numbering is similarly straightforward. Each image page receives a unique identifier, making it easier to cite documents in motions, witness outlines, deposition exhibits, and trial binders. A native file can be associated with a Bates number, but it does not naturally provide the page-by-page reference attorneys often need in litigation.
Consistent Reviewer Experience
Fixed images reduce variation. Every reviewer sees the same page layout, text placement, stamps, and redactions. That consistency matters in large review teams, especially when attorneys are working remotely or when documents are being reviewed under tight court or regulatory deadlines.
Images are also useful when a document must be compared against a paper original, a scan, or a prior production. The visual record is predictable and easier to validate during quality control.
Trial and Deposition Readiness
Most courtroom and deposition workflows favor documents that can be identified and displayed as stable pages. An image-based production is generally easier to load into exhibit management systems, print into hearing binders, and display to a witness. It also allows counsel to direct the record to a precise Bates page without relying on a recipient’s ability to open a particular native application.
There are exceptions. A financial expert may need the native workbook to explain formulas, and a video may need to be presented in its original playable format. The practical answer is often to prepare the image rendition for reference while preserving an approved native version for substantive use.
The Best Practice Is Often a Hybrid Workflow
A defensible eDiscovery process does not force every file into the same review format. Instead, it uses a document-type and risk-based approach. Standard email and office documents may be rendered for image review, while spreadsheets and media are reviewed natively or with both native and image views available.
A hybrid workflow should be planned early, before attorneys have spent significant time coding documents. The case team should agree on whether native files will be produced, which file types require specialized handling, how confidential information will be redacted, and whether a placeholder or slip sheet will accompany native productions.
The production protocol matters. If parties agree to TIFF with extracted text and load files, the producing side should not assume that native production is acceptable for convenience. If native production is required for certain file types, the protocol should address naming conventions, Bates associations, confidentiality labels, metadata fields, and handling of redacted documents. Clear agreement reduces motion practice and rework.
Review Format Affects Cost, Speed, and Quality
Native review may reduce time spent waiting for large file populations to render, but it can introduce complexity when reviewers need to switch applications or inspect files that do not display cleanly. Image review requires processing and quality control, particularly for poor scans, oversized documents, and files with rendering errors. Yet it can make second-level review, redaction, and production more predictable.
The cost question is therefore not simply native versus TIFF. It is the cost of the full workflow. A fast native review that later requires manual redaction, reprocessing, and production correction is not efficient. Conversely, rendering every complex spreadsheet to images can waste time and make substantive review less accurate.
Quality control should test both legal and technical issues. Review managers should spot-check document families, compare native files to renderings where material, validate OCR quality, confirm Bates sequences, and inspect redactions in the final production format. For sensitive matters, chain-of-custody records and documented handling procedures are part of that same discipline.
A Practical Decision Framework for Legal Teams
Before selecting a default review format, ask what the reviewer must determine from the document. If the answer involves formulas, embedded content, playback, or underlying structure, native access should be considered. If the answer involves page-level privilege calls, visual redactions, consistent citations, or courtroom presentation, image review is usually the stronger foundation.
Then consider the production obligation. A document may be reviewed natively but produced as an image with extracted text. It may be reviewed as an image while its native file is preserved for experts or later disputes. The format used for review does not automatically dictate the format used for production.
For complex matters, the most reliable path is to make these decisions with litigation support and eDiscovery professionals before production deadlines narrow the available options. Concord Document Technologies supports native-file handling, image-based review, redaction, Bates labeling, RelativityOne review workflows, and production preparation for matters where precision cannot be left to a last-minute conversion. The right format is the one that lets your team see the evidence clearly, protect what must remain protected, and present the record with confidence when it matters most.
