§ Guide

Native Documents PDFs Or Images Which Production Format

This guide, 'Native Documents, PDFs or Images: Which Production Format?', addresses the critical decision of production format in e-discovery for UK litigators, in-house counsel, and investigators.

Ref · E-D · 2026 · §LIBClass · ConfidentialJuris · England & WalesStatus · Active

Guide · 17 pages · 21 min read · Published 2026-08-30

This guide, 'Native Documents, PDFs or Images: Which Production Format?', addresses the critical decision of production format in e-discovery for UK litigators, in-house counsel, and investigators. It covers what each format preserves and destroys, and how to choose in the Protocol. The guide details the three families of production formats - native, searchable PDF, and image-plus-load-file - and document classes that force the choice, such as spreadsheets, presentations, chat, and media. It also examines the rules layer, including PD 57AD and PD 31B, and what 'native' means in an order. Topics include redaction, confidential it y, the imaging exception, acceptance checks for receiving productions, and common mistakes. It provides questions to ask, suggested wording for disclosure protocols, and a checklist for when to involve a digital forensic expert.

Read this guide on your phone, browse guides by topic or go back to the full PDF library.

§ Credit and source

Published by Computer Forensics Lab on 2026-08-30. Original material of the practice, free to read, cite and download. The authority behind this subject is Practice Direction 57AD, Disclosure in the Business and Property Courts, which you should read alongside this guide. See every guide's author and source.

§ Full text of Native Documents PDFs Or Images Which Production Format

Download the PDF

Prefer a PDF that matches this page exactly? Download the current text as a PDF, generated from the wording shown here, including any later corrections.

Native Documents PDFs Or Images Which Production Format

PRODUCTION FORMAT S · A GUIDE FOR UK LAWYERS Native Documents, PDFs or Images: Which Production Format? What Each Format Preserves, What Each Destroys, and How to Choose in the Protocol COMPUTER FORENSICS LAB

§ ABOUT THE AUTHOR PREPARED BY COMPUTER FORENSICS LAB E-DISCOVERY TEAM

§ CONTENTS In this guide 01 Executive summary 02 The problem in plain English: the format is an evidence decision 03 The three families: native, searchable PDF and image-plus-load-file 04 Document classes that force the choice: spreadsheets, presentations, chat and media 05 The rules layer: PD 57AD, PD 31B and what "native" means in an order 06 Redaction, confidential it y and the imaging exception 07 Receiving productions: acceptance checks and challenge routes 08 Source architecture: where else the evidence lives 09 Worked examples 10 Common mistakes and technical limitations 11 Questions to ask · Suggested wording 12 Checklist and red flags · When to involve a digital forensic expert 13 Frequently asked questions 14 Glossary · References · Disclaimer · How a specialist laboratory can assist

§ 01 · ORIENTATION Executive summary THE HEADLINE POINT: PRODUCENATIVEBYDEFAULT, IMAGE ONLY FOR CA USE, AND PRESERVETHEROUTEBACKTOTHENATIVEFOREVERYDOCUMENTTHATMATTERS 87

§ 7's warning. Image-plus-load-file (TIFF/PDF images with extracted text and agreed metadata fields)

§ 02 · FIRST PRINCIPLES The problem in plain English: the format is an evidence decision

§ 03 · THEFAMILIES The three families: native, searchable PDF and image-plus-loadfile

§ 04 · THEFORCINGCLASSES Document classes that force the choice: spreadsheets, presentations, chat and media

§ 05 · THERULESLAYER The rules layer: PD 57AD, PD 31B and what "native" means in an order

§ 06 · THEIMAGINGEXCEPTION Redaction, confidential it y and the imaging exception

§ 07 · RECEIVINGEND Receiving productions: acceptance checks and challenge routes

§ 08 · THEWIDERMAP Source architecture: where else the evidence lives WHAT THE YOUR DMS / UPSTREAM PRODUCTION COUNTERPART CLOUD STRUCTURED STRIPPED COPIES PLATFORMS SOURCES PRODUCER'S TRANSMISSION DEVICE NATIVES RECORD LAYER

§ 09 · IN THE WILD Worked examples EXAMPLE1 · THE MODEL PRODUCED AS4, 100PAGES EXAMPLE2 · THE " NATIVE " ORDERANSWEREDWITHCONVERSIONS EXAMPLE3 · THEIMAGINGTHATWASEXACTLYRIGHT

§ 10 · WHEREITGOESWRONG Common mistakes and technical limitations Common mistakes Technical limitations

§ 11 · INTERROGATORIES & DRAFTING AIDS Questions to ask · Suggested wording Ask your client Ask your opponent Ask your e Discovery / forensic provider SUGGESTED WORDING · FORM AT PA R AG RAPHFORTHEDISCLOSUREPROTOCOL

§ 12 · QUICK CONTROL Checklist and red flags · When to involve a digital forensic expert The format checklist Red flags When to involve a digital forensic expert

§ 13 · COMMON QUESTIONS Frequently asked questions Is there a single best production format? The other side wants everything as PDFs "for convenience". Should we agree? How do we cite a native spreadsheet in a bundle or judgment? We received images and the text layer seems poor. Whose problem is that? Do we have to produce hidden sheets, tracked changes and speaker notes? The producing party says the native no longer exists. Now what?

§ 14 · REFERENCE Glossary Sources and authoritative references 35 reporting): cflab.uk/digital-forensics-services · guides library: cflab.uk/guides DISCLAIMER

§ HOW A SPECIALIST LABORATORY CAN ASSIST Working with Computer Forensics Lab Speak to a forensic examiner, not a salesperson. INSTRUCTTHELAB NEWENQUIRIESEMAILE - DISCOVERY

§ Common questions

Frequently asked questions

Is there a single best production format?
Per class, yes; universally, no: native where interiors may matter (which is more classes than intuition suggests), images where redaction or confidential it y forces fixity, fields and hashes travelling regardless: §3's hybrid is what competent protocols actually say. The one universally wrong answer is the undecided default.
The other side wants everything as PDFs "for convenience". Should we agree?
For correspondence-grade classes, often harmless; for interior-bearing classes, it is an evidence concession dressed as logistics: Example 1 is what "convenience" can cost. Agree a per-class table instead: PDFs where interiors cannot matter, natives where they can, and the route back for surprises: convenience and evidence both survive.
How do we cite a native spreadsheet in a bundle or judgment?
By identifier and internal reference: document ID plus sheet and cell: with key extracts rendered to fixed pages for the bundle while the native remains the evidence: §10's engineering point. Courts handle this daily; the failure mode is not c it at i on difficulty but nobody agreeing the convention until the bundle deadline.
We received images and the text layer seems poor. Whose problem is that?
Practically yours until challenged: your searches inherit their OCR: so the guide 86 response runs: score what arrived, re-OCR their images yourself where it pays, and put quality questions per §11 where the production falls short of the protocol. The protocol drafted with guide 86's paragraph makes this a compliance issue rather than a philosophical one.
Do we have to produce hidden sheets, tracked changes and speaker notes?
If the document is disclosable, its non-visible content is part of it: producing a version with the interior stripped is producing a different document: Example 2's principle. Privileged or irrelevant-and-confidential interior content is handled by redaction with the c on version flagged: not by silent flattening.
The producing party says the native no longer exists. Now what?
Test it, then route around it: preservation duties make "not retained" a serious statement (when did it exist, what happened, per the spoliation disciplines): while the §8 lattice rebuilds the interior from counterpart copies, platform versions, transmissions and upstream systems: Example 2's rebuild. The absence becomes its own chapter; the content usually turns up anyway. cflab. u k · e-disc ove r y. u k ©2026 Computer Forensics Lab Ltd ·cflab.uk ·e-discovery.uk ·info@cflab.uk ·+44 (0)20 7164 6915 Page 15 of 17
§ Related documents
Instruct the practice

Bring us in early. Defensibility is built, not retrofitted.

Whether you are responding to a regulator, preparing for disclosure, or scoping an internal investigation, start the chain of custody with a short, confidential conversation.

WhatsApp