Screenshots vs. full message exports

Choose the record that preserves the question you need to answer

Screenshots show appearance. Full exports show sequence. A specialist acquisition may preserve device-level records and document a controlled technical process. These are not interchangeable, and using more than one can be sensible.

Feature	Screenshots	Full platform export	Specialist phone acquisition
Visual appearance	Strong	Usually reformatted	Depends on deliverable
Long-thread continuity	Weak unless carefully overlapped	Strong	Strong when within scope
Dates and times	Only what the screen displays	Often present, with platform limits	May include underlying stored values
Sender identity	Header and bubbles only	Names, numbers, or IDs vary	May correlate account and device records
Search and sorting	Poor	Good in TXT, CSV, or JSON	Usually good in produced data
Attachments	Visible previews	May include separate files	May recover available files within scope
Cost and effort	Low	Low to moderate	High
Main weakness	Cropped context	Export omissions and ambiguous zones	Cost, scope, and need for interpretation

Screenshots preserve the visible screen, not the whole thread

A screenshot can accurately capture one screen and still omit essential information. Many chat views do not print a date or exact time beside every message. The sender may appear only as a saved contact name. Earlier messages, later qualifications, replies, reactions, and attachments can sit just outside the frame.

Common challenges are practical: Who took it? From which phone and account? When? Was the contact label edited? What appears immediately before and after it? Is a date separator missing? Has the image been cropped, marked up, or passed through an app that recompressed it?

Those questions do not mean a screenshot is false. They identify the foundation a witness should explain under the authentication principles in FRE 901. Preserve the original image and the native thread so another person can check it.

Take better screenshots when that is the available method

Start with an orientation image showing the app and contact header. Capture date separators and any visible number, username, or group name. Then scroll in small steps, leaving at least one complete message visible in both consecutive images. The overlap demonstrates sequence and makes accidental gaps easier to spot.

Do not crop, draw on, filter, or paste screenshots together in the originals. If you need a focused illustration, duplicate the file and label the derivative. Keep original filenames and metadata. Record the date, phone, app, conversation, operator, and start and end points in a brief capture note.

For long conversations, add a screen recording of the careful scroll if lawful and appropriate, but do not use it as the only copy. Video is harder to cite page by page. A set of original screenshots plus a complete export is generally easier to review.

Use a repeatable capture sequence:

1. Preserve the phone before changing contact names, time settings, or app settings.
2. Photograph or capture the conversation list and open the relevant thread.
3. Show the contact or group header. Where the app permits, open contact details so the number, username, or account identifier is visible.
4. Return to the thread and show the first relevant date separator.
5. Capture one screen at a time. Leave one or two complete messages overlapping between consecutive images.
6. Open important attachments and capture identifying details without replacing the original attachment file.
7. Continue past the disputed passage far enough to show replies, corrections, and the next date marker.
8. Stop and record the final filename, capture time, device, app, account, and known gaps.

Disable avoidable notification previews before capture if doing so will not alter the source. Do not hide relevant content by placing banners over it. If exact message times appear only after a swipe or tap, capture that state as an additional image and explain it. Do not claim that the interaction exposed a stored timestamp unless the platform documentation or underlying data supports that conclusion.

Contact names and crops create predictable disputes

A saved contact name is an address-book label controlled by the phone owner. It is useful orientation, but it is not the same as a phone number or platform account identifier. Capture both when the app allows it, and document any display-name overlay separately.

A crop can remove the status bar, app identity, header, date separator, or neighboring reply. Keep the uncropped original even if a court form needs a focused image. Make the crop from a copy, use a new filename, and list the relationship between source and derivative. The same rule applies to arrows, highlights, and captions.

Edited image files deserve a plain explanation. Normal phone processing and file transfer can alter metadata without changing visible pixels. Conversely, intact metadata does not prove that the conversation itself is genuine. Preserve the earliest file and transfer it without sending it through social media or a messaging service that may resize it.

Screen recordings add continuity but need an index

A screen recording can show a continuous path from the conversation header through a long exchange. Scroll slowly, pause at date changes, and avoid rapid jumps. Keep the original video file and record the device’s time-zone setting at capture.

Create an index with elapsed times, such as “00:42 contact details,” “02:16 March 4 exchange,” and “05:03 final date separator.” Extracting still images for a filing creates derivatives; retain the video and map each still to its video time. Recordings may capture incoming notifications or third-party information, so review privacy and recording rules before sharing.

Video has limits. Compression can make text unreadable. A recording may not show hidden timestamps or attachment metadata. It is also cumbersome to search and print. Use it to demonstrate navigation and continuity, not as a substitute for a complete export where one is available.

Full exports preserve more context

A platform export can capture hundreds or thousands of messages in source order. Text or structured data is searchable and can be rendered with repeated dates, sender labels, page numbers, and a stated time zone. It also lets you retain surrounding messages while presenting a focused excerpt.

Exports have limits. WhatsApp text exports do not carry a time-zone identifier. Some platform downloads include only the requesting user’s data. Reactions, edits, read receipts, deleted items, or offloaded attachments may be absent. Document those limits rather than filling the gaps.

For a WhatsApp .txt or .zip, the free WhatsApp-to-PDF tool parses locally in the browser and does not upload chat contents. Keep the original package alongside the PDF; the PDF is a readable rendition, not a replacement source.

Compare the records before choosing one

The right method follows the disputed fact. If appearance, reaction icons, or a message marked “edited” matters, screenshots may preserve the clearest display. If sequence, searching, or a multi-month date range matters, a full export is usually more manageable. If device ownership, database fields, or account compromise is disputed, specialist help may be proportionate.

Run a spot check whenever you have two methods. Select messages at the beginning, middle, and end. Compare sender, exact text, visible time, order, edits, replies, reactions, and attachment names. List differences. Do not force one source to look like the other. A platform export and interface can legitimately expose different fields.

Use stable names such as 01-original-screenshots, 02-platform-export, and 03-readable-pdf. Keep a small inventory with file count, byte size, date received, and SHA-256 value. Hashes help detect later file changes; they do not prove the source conversation was genuine.

Specialist acquisition is for consequential or disputed matters

A qualified technical examiner may be worth considering when authenticity is sharply contested, the device itself must be examined, underlying databases or status records matter, or a court order defines a technical collection. Counsel can help set a proportionate scope.

Ask what devices and accounts will be collected, whether work occurs on a copy, which date ranges and apps are included, how unavailable data is reported, what hash and activity records are supplied, and whether the examiner can explain the process. No method guarantees that deleted material exists or can be obtained.

Also ask what the quoted fee includes rather than comparing one headline number. Relevant scope questions include device intake, passcode handling, expedited work, cloud collection, additional apps, deleted-data analysis, report writing, declarations, travel, testimony, and a second production after redaction. Ask how the provider protects private content, how long copies are retained, and how they are destroyed at the end of the engagement.

Do not install unfamiliar recovery software on the only phone to “see what is there.” Installation and testing can change the device. Preserve it, document its condition, and get advice before intrusive work when the stakes justify it.

Make a presentation copy without weakening the source

Keep preservation files read-only where practical. Create a separate working folder for pagination, captions, redaction, and exhibit stamps. Every derivative should have a distinct filename and, for important versions, its own hash and creation note.

For a screenshot exhibit, use one image per page or a consistent grid large enough to read at 100 percent. Add a caption outside the image area with the source filename and sequence. Do not place text over message bubbles. If an image is scaled, preserve its aspect ratio and do not sharpen it in a way that changes characters.

For an export, state the source format, date range, time-zone convention, and known omissions on a cover page. Add page numbers and stable message numbers. If only an excerpt is presented, mark gaps and retain the complete relevant export. The context guide explains a reviewable method.

Preserve first, present second

FRE 1001(d) recognizes an accurate readable output of electronically stored information as an original under the federal best-evidence definitions. Accuracy still needs support. Keep the source from which the output was made and a record of conversion.

Presentation should be separate from preservation. Preserve the full source set. Then create a numbered, readable exhibit with disclosed redactions or omitted ranges. This protects context while keeping a hearing or filing manageable.

The strongest practical package often includes the original phone, original screenshots, a platform export, a readable PDF, and a short process note. Each answers a different question, and none replaces witness knowledge.