Authenticating Text Messages Under Rule 901: Foundation That Holds Up

You have a text thread that could shape the outcome of a hearing: an admission, a threat, a promise to pay, an agreement about a schedule. Opposing counsel has already signaled an authenticity objection. Rule 901 does not demand certainty that the messages are genuine; it demands enough evidence that a reasonable factfinder could conclude they are what you say they are. Building that showing deliberately, before the hearing, is the difference between a two-minute foundation and a contested sidebar.

This guide breaks text-message authentication into the two questions courts usually care about, maps the Rule 901(b) methods to each, offers a sample foundation examination, and covers the pretrial tools that can take authenticity off the table entirely. It is written against the Federal Rules of Evidence. Many states model their evidence codes on the federal rules, but wording and case law differ, so verify the rule that governs your matter.

What does Rule 901 actually require for text messages?

Rule 901(a) requires evidence “sufficient to support a finding” that the item is what the proponent claims it is. The court screens whether that threshold is met; once it is, remaining doubts about genuineness generally go to weight, for the factfinder to resolve.

For text messages, the claim being authenticated usually has two parts, and it helps to prepare them separately:

1. Accuracy. The exhibit (screenshot, printout or export) accurately reproduces messages that were actually sent and received, with nothing added, altered or silently removed.
2. Authorship. The messages attributed to a particular person were in fact written or sent by that person.

Accuracy is rarely the hard part, because a participant in the conversation can usually testify to it. Authorship is where most objections focus: phones are shared, numbers change hands, contact names are typed by the phone’s owner, and screenshots are easy to edit. Keep in mind that authentication is a separate question from hearsay; the guide to hearsay and text messages covers the next hurdle.

Which Rule 901(b) methods work for text messages?

The examples in Rule 901(b) are illustrative, not exclusive, and text messages are usually authenticated with a combination of them.

The certification route is a different mechanism (self-authentication rather than testimony) and has its own notice requirement. The guide to Rules 902(13) and 902(14) explains when it is worth the effort.

How do you prove who sent a text message?

Connect the number to the person and the content to the person, using as many independent strands as the stakes justify. One strand alone, especially a contact name, invites a challenge; three or four strands that point the same way are much harder to dispute.

• The number has been used for prior communications between the witness and the person, over a period of time
• The person has given out the number: on an intake form, an email signature, a lease, prior filings or discovery responses
• Carrier subscriber or account records tie the number to the person (see subpoenaing phone records for what carriers keep)
• The messages contain details few other people would know
• Messages are replies that fit the conversation, sent in response to messages addressed to that number
• The person’s later conduct matches the messages (arriving at the agreed time, paying the amount discussed)
• Characteristic nicknames, spelling, phrasing or sign-offs that match the person’s other writing
• The person produced the same messages in discovery, or admitted them in a deposition or pleading

What does a foundation examination for text messages sound like?

A participant-witness foundation usually covers identification of the exhibit, how it was made, its accuracy and completeness, and the link between the number and the author. The structure below is a starting point; every question has to fit what the witness actually knows.

If the witness is not a participant, such as a paralegal who prepared an export from the client’s phone, the foundation shifts toward process: what device, what tool, what steps, and how the output was checked against the source.

How can you resolve authenticity before the hearing?

The cheapest foundation is the one the other side concedes. Several procedural tools can narrow or eliminate the authenticity fight before anyone takes the stand.

1. Requests for admission. Federal Rule of Civil Procedure 36(a)(1)(B) allows requests to admit the genuineness of described documents. Attach the thread. Untimely responses can result in the matter being deemed admitted, and Rule 37(c)(2) allows expense-shifting when a denied matter is later proved.
2. Deposition questions. Show the opposing party the messages and ask whether the number is theirs, whether they sent them, and whether anything is missing.
3. Stipulations. Propose a stipulation on authenticity that expressly reserves other objections such as hearsay and relevance. Opposing counsel is often more willing to concede genuineness than admissibility.
4. Pretrial disclosure objections. In federal court, Rule 26(a)(3)(B) generally treats objections to disclosed exhibits as waived, other than objections under Rules 402 and 403, unless made within the time allowed or excused for good cause. Check the scheduling order and local practice.
5. Matching copies. Request the other party’s copy of the same thread. Matching content from both devices is strong corroboration.

State and family courts handle these tools differently, and many hearings move faster and less formally than federal trials, so confirm what is available and on what timeline in your forum.

What authenticity challenges should you anticipate?

Expect the objection to target authorship or completeness, and prepare a specific answer for each before the hearing.

“Someone else had my phone”

Shared devices and family plans are real. The answer is usually content and context: messages that refer to things only that person knew, replies consistent with that person’s schedule, and conduct afterward that matches the messages.

“That screenshot was edited or fabricated”

Fake chat generators and image editors exist, and courts are aware of them. The stronger response is a source that is harder to fake: an export from the device, original files hashed when received, the other party’s own copy, or forensic examination when the stakes justify the cost.

“Messages are missing”

Selective excerpts invite a completeness argument under Rule 106. Produce the full thread in discovery, mark any omissions in the exhibit, and be ready to explain why the excerpt is fair.

“My number was spoofed”

Spoofing a sender number is possible for some message types, but a two-way conversation in which the person responded to messages sent to that number is difficult to explain that way. Carrier records can add support.

How should the exhibit itself support authentication?

A well-built exhibit answers foundation questions before they are asked. It shows phone numbers or handles rather than only contact names, full dates and times with the time zone, a complete sequence with omissions marked, and a short source note stating where and how the messages were captured. The guide to text message exhibit formatting covers layout in detail.

When a thread runs to hundreds or thousands of messages, a tool like Message Extractor can produce a chronological, paginated log from the phone or app export, with a SHA-256 digest and a declaration template modeled on FRE 902(13)–(14) that counsel completes. See what the message log contains. Whether a given foundation is sufficient remains a judgment for the responsible attorney, licensed where the matter is pending, working from the governing evidence code and local case law.