How to authenticate text messages for court

Authentication asks a narrow question

Authentication asks whether there is enough support to treat the offered record as what you say it is. FRE 901(a) uses the short formulation “sufficient to support a finding that the item is what the proponent claims it is.” That threshold is separate from whether a statement is hearsay, relevant, complete, or persuasive.

A useful description is specific. Instead of saying “these are the defendant’s texts,” say what the exhibit is: an export made on a stated date from a named conversation displayed on a particular phone, covering a defined period. That gives the witness and court a claim that can actually be tested.

A witness can explain what they know

The most direct foundation often comes from someone who participated in or observed the conversation. FRE 901(b)(1) identifies testimony that an item is what it is claimed to be as an example. The witness should distinguish personal knowledge from assumptions.

Typical questions include:

1. Is this your phone or account?
2. Whose number or account appears on the other side?
3. How do you know that number or account belongs to that person?
4. Had you communicated through it before?
5. What details in the messages do you recognize?
6. How was this export or set of screenshots made?
7. Does it fairly show the conversation as you saw it?
8. Is the relevant exchange complete, and were anything or any periods omitted?
9. Were names corrected, messages redacted, or pages changed?
10. Where are the original phone and source files now?

Answers should be factual. “I saved the number after they gave it to me in person” is more useful than “I know it was them.” If the witness cannot explain a step, they should not guess.

Distinctive characteristics can connect messages to a person

FRE 901(b)(4) permits authentication through an item’s “appearance, contents, substance, internal patterns, or other distinctive characteristics,” considered with the circumstances. For a chat, those characteristics may include a phone number, username, nickname, writing pattern, shared plans, references to events, or knowledge unlikely to be held by a stranger.

No single feature is automatically decisive. A saved contact label can be edited. Numbers can be reassigned, accounts compromised, and phones shared. A collection of consistent details is generally more informative than one label at the top of a screenshot.

The advisory material to Rule 901 also describes reply evidence: content and circumstances can indicate that a communication was sent in reply to an authenticated one. In a text thread, a responsive answer may therefore add context. It is not a magic rule. The surrounding facts still matter.

Explain the export, not just the conversation

The readable document has its own history. Record the phone, operating system, app, source conversation, export method, date, and person performing the steps. Preserve the native thread and the first exported files. If software converted a source file to PDF, keep both.

State what the method could not capture. A screenshot may omit exact times. A platform text export may omit reactions, delivery status, or a time-zone identifier. An OCR result can contain recognition errors. Honest limits make the process easier to evaluate.

Completeness also needs a direct answer. Define the date range. Identify omitted attachments, unavailable media, removed duplicates, redactions, and gaps. Never silently repair text. Put corrections and display-name changes in a separate log.

Treat the questions as illustrations, not a script

Foundation questions should draw out facts the witness actually knows. They should not supply an answer. The earlier list is an illustration of common topics, not testimony to memorize or a script that fits every court.

A participant might explain that the other person gave them a number face to face, that they saved it under a contact name, and that they had used it for months. They might recognize a private nickname, a reference to an appointment both attended, or a reply to a question asked seconds earlier. They can explain whether the conversation on the phone looked the same when captured. Each fact adds support; none should be invented to fill a gap.

The process questions matter too. A witness may be asked whether airplane mode was used, whether notifications obscured text, whether the conversation was searched or scrolled, and whether screenshots overlap. For an export, useful facts include the command or built-in feature used, the selected date range, whether media was included, and where the first output was stored. Keep a contemporaneous capture note so the explanation does not depend on memory months later.

Group chats require extra care. Identify the group, the account or number attached to each displayed sender, and membership changes known from the source. Do not assume that a group display name proves who controlled an account at a particular moment.

Hearsay is a different question

Authenticating a message does not establish that its words may be used for every purpose. Hearsay rules ask why a statement is being offered and whether a rule or exception applies. The same message might be offered to prove that words were communicated, to show their effect on the recipient, or to prove that the assertion in the words was true. Those are different uses.

Under FRE 801(d)(2), a statement offered against an opposing party can be treated as not hearsay when one of the rule’s stated conditions applies. Authentication still comes first: the proponent needs support for connecting the statement to that person or to another category in the rule. Messages from friends, children, unidentified group members, or forwarded content do not become an opposing party’s statements merely because they appear in the same thread.

Do not label an entire conversation “not hearsay.” A thread can contain several speakers and several purposes. A lawyer can identify which rule applies to each disputed passage.

Printouts can qualify as originals under the federal definitions

The federal “best evidence” rules do not automatically require handing the phone to the court. FRE 1001(d) says that for electronically stored information, an “original” includes any printout or other output readable by sight if it accurately reflects the information. The important word is accurately. The person offering the printout should be able to explain its source and conversion.

FRE 1003 generally allows a duplicate to the same extent as the original unless a genuine question is raised about authenticity or admitting the duplicate would be unfair. FRE 1004 identifies circumstances in which other evidence of content may be admitted when originals are lost, destroyed without bad faith, unobtainable, controlled by the opponent after notice, or not closely related to a controlling issue. These rules do not excuse avoidable deletion. Preserve the device and source files whenever possible.

A PDF may accurately render a raw export while omitting interface features the raw format never contained. State that boundary. Keep the raw export, conversion settings, final PDF, and a comparison sample showing that sender, text, timestamps, and order carried through.

Rules 902(13) and 902(14) require more than a label

FRE 902 provides routes for certain evidence to be self-authenticating, but the electronic-data provisions have formal conditions. Rule 902(13) addresses a record generated by an electronic process or system that produces an accurate result, shown by a certification of a qualified person. Rule 902(14) addresses data copied from an electronic device, storage medium, or file and authenticated by a process of digital identification, also shown by a qualified person’s certification. Both invoke Rule 902(11)’s certification and notice requirements.

A person does not satisfy those provisions merely by adding an official-looking label to an export. A lay user normally cannot assume that they are the qualified person for a technical certification. A SHA-256 manifest can give an examiner a useful reference and can support ordinary witness testimony about unchanged files, but it is not automatically a Rule 902 certification. If self-authentication matters, ask counsel what declaration, notice, technical work, and qualification evidence the court requires.

A denial of authorship changes what matters

When the other side says “that was not me,” collect facts that test alternative explanations. A phone may be shared. An account can be compromised. A contact name can be changed. Caller ID and SMS sender information can be spoofed. A number can later be reassigned. These possibilities do not decide the issue, but they explain why the name shown at the top of one screenshot is weak by itself.

Useful corroboration may include earlier undisputed exchanges, contemporaneous conduct, replies from another known channel, photographs or attachments known to the sender, and testimony about possession of the phone. Carrier billing or connection records may help establish communications between numbers, but ordinary carrier records may not contain message content. Platform records may be limited, encrypted, unavailable, or require valid legal process. A subpoena is a legal demand, not a consumer export feature; counsel should assess scope, timing, jurisdiction, and notice.

Where device databases, deleted records, account compromise, or disputed metadata are central, a qualified examiner may be appropriate. Ask the examiner to define the question, collection method, preserved source, validation checks, limitations, and deliverables. Technical collection still does not decide who physically typed a particular sentence.

Hashes answer only the later-change question

A cryptographic hash is a repeatable digital fingerprint of a file. If one byte changes, the calculated value will almost certainly differ. A manifest can list filenames, byte sizes, SHA-256 values, the export identifier, creation details, and the method used. The free export verifier checks matching files in the browser without uploading their contents.

That comparison supports a limited statement: the checked file matches the file represented by the recorded hash. It does not establish that a WhatsApp text file was accurate before hashing, that the account holder typed a message, or that nothing was omitted before export. The reference hash also needs a credible history. A newly created hash cannot establish what an older file looked like.

FRE 902(14) is more formal. It covers data copied from an electronic device, storage medium, or file when a process of digital identification is shown through a certification by a qualified person that meets specified certification and notice requirements. A consumer manifest may help document the process, but it is not automatically that certification and does not make its creator a qualified person.

England and Wales uses a procedural notice rule

In civil proceedings, CPR 32.19 says a party is deemed to admit the authenticity of a document disclosed under Part 31 unless that party serves notice requiring proof. The notice ordinarily must be served by the latest date for witness statements or within seven days after disclosure, whichever is later. Read the actual rule and any case directions.

This does not mean every message is accepted as true. It addresses authenticity of the document. Civil Evidence Act 1995 section 8 separately allows authenticity of a copy to be proved in the manner the court approves. Preserve the source and be ready to explain the copy even where no notice is served.

Hearsay procedure is separate here too. Civil Evidence Act 1995 section 2 provides for notice where a party proposes to rely on hearsay evidence in civil proceedings, subject to the rules and exceptions stated there. A failure to give notice does not automatically make the evidence inadmissible under the Act, but it can affect costs and weight. Check the Civil Procedure Rules, the case directions, and the type of proceeding rather than carrying a US label into an England and Wales case.

Family proceedings have their own rules and practice directions. This guide does not state that the CPR notice timetable applies unchanged in family court. Follow the order and current Family Procedure Rules for the case.

Build a small authentication packet

A compact packet makes the process easier to explain. Keep these items together without modifying the preserved originals:

1. the original phone and native conversation, if available;
2. the first screenshot files or raw platform export;
3. a readable PDF made from that source;
4. a capture note naming the operator, device, app, date, zone, method, and range;
5. a list of omissions, redactions, corrections, and unavailable attachments;
6. a manifest with filenames, sizes, and hashes; and
7. a simple map from exhibit pages back to source message or file identifiers.

Test the map before relying on it. Pick several messages from the beginning, middle, and end. Compare text, sender, timestamp, attachment reference, and sequence against the native thread or raw export. Record discrepancies rather than silently fixing them.

Keep the packet’s versions distinct. An unstamped source PDF, a redacted filing copy, and a numbered exhibit are three different files. Record which one a witness reviewed. If a later correction is necessary, preserve the earlier version and describe the change so old citations still make sense.

Build a foundation that another person can follow

The best record is not the most decorated PDF. It is a traceable set: the original device, native conversation, raw export, readable rendition, manifest, and a short contemporaneous note of what happened. Use stable filenames and make working copies rather than editing the originals.

Before filing, check the relevant court’s directions. A judge may require an exhibit declaration, exchange by a deadline, a particular PDF format, or live testimony. Authentication is fact-specific, and state evidence rules may differ from the federal rule summarized here.