A request for photographs and videos lands, and the evidence lives in a camera roll with years of family pictures, screenshots, bursts and edited versions of the same moment. Producing photos in discovery looks easier than producing text messages, but it has its own traps: compressed copies that lost their dates, edits that replaced originals, location data that reveals an address, and video files that cannot carry a Bates stamp.
This guide covers the production side, from reading the request to serving the response. Collection and metadata get a short treatment here; our guide to photo metadata in litigation covers both in depth. Rule references are to the Federal Rules of Civil Procedure; state rules often track the same concepts with different numbering and deadlines.
What should you check in the request before collecting anything?
Start with the definitions, the date range, the subjects and any instruction on form. Under Rule 34(b)(1)(C) the requesting party may specify a form for electronically stored information, and many requests for images ask for native files with metadata intact. If the request is silent, Rule 34(b)(2)(E) points you to a form in which the files are ordinarily maintained or one that is reasonably usable, and Rule 34(b)(2)(D) requires you to state the form you intend to use.
- Whether “documents” is defined to include photographs, videos, screenshots and audio
- The date range, and whether it is measured by capture date or by date received
- Subjects, people or places that make an image responsive
- The requested form: natives, metadata fields, a load file or printed copies
- Any ESI protocol or protective order that already sets the rules
If the requested form is a problem, for example printed color copies of several hundred videos, raise it at the meet-and-confer rather than in a deficiency letter later. Our comparison of PDF, native and load file production formats explains the trade-offs.
Where do the original photos and videos come from?
From the source library, copied in a way that keeps the original file. The usual sources are the phone’s camera roll, a cloud photo library, a camera’s memory card and shared albums. A few device behaviors cause most of the trouble:
- HEIC and HEVC. Recent iPhones save photos as HEIC and videos as HEVC by default. Keep the originals; make JPEG or MP4 copies for review only.
- Automatic conversion. An iPhone set to transfer to a computer automatically may convert files on the way. The Keep Originals transfer setting, or a desktop export of unmodified originals, avoids that. Settings vary by version, so check the device in front of you.
- Optimized storage. When a cloud library keeps full-size originals and the phone holds smaller versions, collect from the cloud or download originals first.
- Live Photos. These are a still image paired with a short video. Decide whether the motion portion is responsive and keep the pair together.
- Edited versions. Phone editors often keep the original and the edit together. Export both when the edit could matter, and record which is which.
- Shared albums and cloud exports. Shared albums may hold reduced-resolution copies, and some cloud exports place dates and locations in separate sidecar files that must stay with their images.
Record the source, tool, settings, date and operator for each collection, and hash every original on arrival. Evidence Helper bulk-ingests photos and documents, keeps each original untouched with a SHA-256 hash recorded on arrival and normalizes HEIC images for review, so reviewers never work on the only copy.
How do you remove duplicates without losing evidence?
Remove exact duplicates by hash value and treat near-duplicates as separate items. Two files with the same SHA-256 value are byte-for-byte identical, so producing one and logging the other is safe. Our guide to hash values in litigation explains why.
Near-duplicates are different. Burst frames, an original and its edit, a photo and a screenshot of that photo, or the same image saved at two resolutions all have different hashes and may tell different stories. A screenshot of a photo has its own capture date, and an edit may crop out something the other side wants to see. Group near-duplicates for the reviewer, but let the reviewer decide what to produce, and write down the deduplication method so it can go in the written response.
How do you scope and review a photo set?
Filter first, then review what remains. Capture dates, people and places usually do the filtering:
- Apply the date range. Use the capture date from the metadata, not the file system date, which changes when files are copied. Note any images with no capture date.
- Apply the subject. Tag images by issue, person or location. Albums and captions help, but confirm by looking.
- Review for privilege. Photos the client took at counsel’s request, or annotated for counsel, can raise work-product questions for the attorney to decide.
- Review for privacy. Children, unrelated third parties, medical information, intimate images and location data all need a decision before anything leaves the office.
- Record every decision. Produced, withheld, redacted or designated, with the reason.
How do you redact a photo or its metadata?
On a copy, visibly, and with disclosure. To redact an image, burn the redaction into a copy, label it with the reason and produce that copy as an image; the native is then withheld for that item and listed in the redaction log. To remove a metadata field such as GPS, produce a copy with the field removed, keep the untouched original preserved, and say in the written response which field was removed and why. Blurring a child’s face or a third party’s identifying details is a redaction too, and so is cropping. For sensitive images, a confidentiality or attorneys’-eyes-only designation under a protective order may be the better tool. Our guide to redacting exhibits covers labeling and logs.
How do you Bates number photos and videos?
Through the file name or a slip sheet, never by altering the original. The two common methods:
| Method | How it works | Best for |
|---|---|---|
| Bates file names | Each produced native is renamed with its number, such as PREFIX-000412.HEIC, and the original file name is kept in the metadata spreadsheet | Native-only productions of photos and videos |
| Slip sheets | A one-page placeholder in the imaged or PDF set carries the Bates number, original file name, hash and a note that the item is produced natively | Mixed productions, videos and load file productions |
| Stamped review copies | A JPEG or PDF rendering of each photo carries a visible Bates stamp, alongside the unaltered native | Photos that will be cited at deposition or a hearing |
Videos are produced natively, with a slip sheet giving the Bates number, file name, duration and hash. If a video uses a format the other side may not play, say so in the cover letter and offer a converted review copy without replacing the native. Use one consistent prefix, never reuse a number, and keep the Bates sequence aligned with any message or document production in the same matter; the Bates numbering guide covers prefixes and ranges. A slip sheet in the production is not the same as an exhibit slip sheet in a hearing binder, though the idea is similar; see exhibit stickers and cover sheets.
What goes with the files?
A metadata spreadsheet or load file, a hash list and a written response. A typical metadata spreadsheet has one row per produced item with the Bates number, original file name, capture date and time with a stated time zone, device make and model, location fields if produced, file type, duration for videos, any redaction or designation, and the SHA-256 value. If the parties agreed on a load file, follow the agreed field list.
Sample written response
Response to Request No. [number]: [Party] will produce responsive photographs and videos dated [date] through [date] in native format, as collected from [device or account] on [date], with Bates numbers applied as file names ([PREFIX]-[number] through [PREFIX]-[number]). A metadata spreadsheet listing each item’s original file name, capture date in [time zone], device and SHA-256 value is included. Exact duplicates were removed by hash value. Location data has been removed from [number] items identified in the redaction log for the reason stated there; the originals are preserved. [No other responsive items are being withheld.]
A production cover letter ties the delivery to the response, and the production log records the Bates range, date served and delivery method.
What goes wrong in photo and video productions?
| Mistake | Consequence | Fix |
|---|---|---|
| Producing texted or emailed copies | Missing or rewritten dates and locations | Collect originals from the source library |
| Stamping Bates numbers on originals | The produced file no longer matches its hash | Bates file names or slip sheets; stamp review copies only |
| Deduplicating near-duplicates | An edit or burst frame silently disappears | Exact duplicates only; review near-duplicates |
| Silently stripping GPS data | Accusations of altered evidence | Treat as a redaction and disclose it |
| Converting videos and discarding natives | Lost quality and lost metadata | Produce the native; offer a review copy |
| Filtering by file system date | Wrong items in or out of the date range | Filter by capture date and state the zone |
If a photo or video may be authenticated at a hearing, the collection record you made now becomes the foundation later; our guide to authenticating video evidence covers what that testimony usually needs. For message attachments, the same principles apply inside a message production; see producing text messages in discovery.
Decisions about privilege, privacy redactions, protective-order designations and objections to the scope of a request belong to the supervising attorney. Paralegals and staff should flag them rather than resolve them, and when a matter sits in a family, housing or state trial court with its own forms and deadlines, confirm local practice with counsel licensed there.
