Opposing counsel has called the client’s screenshots fabricated, and the client has an idea: “I’ll just take a video of my phone scrolling through the whole conversation.” It is not a bad idea. A continuous recording answers some of the questions screenshots raise. Done carelessly, though, it creates new problems and still leaves the court with something nobody can read from the bench.
This guide covers when a screen recording of a text thread helps, where it falls short, how to make one that holds up, how to pair it with an export and a message log and how opposing counsel may challenge it. References are to the Federal Rules of Evidence; many state rules follow the same structure, so check the rules and standing orders that govern your matter.
Is a screen recording of text messages admissible?
It can be, once a witness authenticates it. Under Federal Rule of Evidence 901(a), the proponent needs evidence sufficient to support a finding that the item is what it is claimed to be. For a screen recording, that usually means a participant in the conversation, or the person who made the recording, testifying that it fairly and accurately shows the thread as it appears on the phone. The full authentication toolkit, including proof of authorship, is in our guide to authenticating text messages under Rule 901.
The original-writing rules rarely stand in the way. Rule 1001(d) defines an original of electronically stored information as any printout or other output readable by sight, if it accurately reflects the information. Admissibility of the content is a separate question: hearsay, relevance and completeness apply to messages shown on video exactly as they apply to a printout.
What does a screen recording show that screenshots don’t?
Continuity, context and the phone itself. A scroll from one end of the relevant range to the other answers the argument that screenshots were stitched together or that messages in between were left out. It can show the contact card with the actual phone number or email address behind a saved name, the messaging app’s interface and attachments being opened in place. Our article on screenshot evidence admissibility lists the gaps a recording can help close.
There are two kinds of recording, and they prove slightly different things:
| Method | Shows | Weakness |
|---|---|---|
| Built-in screen recording | Sharp, readable capture of exactly what the screen displayed | Does not show the physical device or whose hands it is in |
| Second camera filming the phone | The physical device, its lock screen and a person operating it | Glare, focus and readability problems; harder to read on a courtroom screen |
Some teams combine them: a short filmed segment showing the device and its settings, followed by a built-in recording of the thread.
What are the limits of a screen recording?
It is a picture of the screen, not the data behind it. Expect these limits:
- Hard to read and cite. A judge cannot flip to page 14 of a video. Without an index of timecodes, the record of what was shown is vague.
- Still needs a witness. The recording does not authenticate itself, and authorship still has to be proved.
- Shows only what is on the phone now. Deleted messages, edits and the underlying database are invisible. Saved contact names can be changed by the phone’s owner.
- Not a substitute for an export or extraction. When authenticity is seriously disputed, an export from the device or a forensic extraction carries far more weight. See iMessage export options for litigation.
- Long threads make long videos. A year of messages can run for hours, which is impractical to play and review.
When is a screen recording worth making?
When it answers a specific question an export or screenshots cannot. Common triggers:
- The other side has already called screenshots fabricated or incomplete.
- Authorship turns on what the contact card shows behind a saved name.
- The hearing is days away and a backup-based export can’t be completed in time, so the recording preserves what the phone shows today.
- The app displays something an export may not capture, such as an “edited” label, a reaction or a message that disappears on a timer.
When a clean export already exists and nobody disputes authenticity, a recording usually adds little but another file to produce and log.
How do you make a screen recording of a text thread that holds up?
Plan it, record it once, slowly, and never edit the result. Both major platforms have built-in recorders: Apple explains how to record the screen on an iPhone from Control Center, including how to set the microphone, and Google explains how to record the screen on an Android device from Quick Settings, where steps vary by device and Android version.
- Prepare the phone. Turn on Do Not Disturb so unrelated notifications don’t appear on screen, charge the battery and clear enough storage for a long file.
- Turn off the microphone. Record the screen only. No narration and no background conversation.
- Show who. Open the conversation, then open the contact details so the phone number or email address is visible, not just the saved name.
- Show when. Bring timestamps into view where the app allows it. On an iPhone, swiping left in a conversation reveals each message’s time; many Android apps show the time when a message is tapped.
- Scroll slowly. Start before the relevant range and finish after it, pausing on each screen long enough to read it. Don’t skip ahead. For long threads, record in segments that overlap by a few messages, and log each segment as its own file.
- Open the attachments that matter. Photos, voice notes and links shown in place tie them to the message that carried them.
- Keep the original file. No trimming, filters or captions. Transfer it by cable or file transfer, not a messaging app that may compress video.
- Hash it and log it. Record a SHA-256 value when the firm receives the file, along with who recorded it, on what device and when. Hash values in litigation explains what that does and does not prove.
How should a screen recording fit with an export and a message log?
The export is the data, the log is what everyone reads and cites, and the recording corroborates both. Export the thread from the device or a backup, render it as a paginated, Bates-numbered log using the conventions in our text message exhibit format guide, and then build a short index that maps the recording’s timecodes to Bates pages. When a witness is asked whether a message on page 14 is real, the answer can point to the exact second it appears on the phone.
Example (fictional)
In a commercial lease dispute, the tenant’s property manager, Priya Castellano, has a thread with the landlord’s agent spanning February through May. The paralegal exports the thread, produces it as a 26-page log, Bates TEN-000201 through TEN-000226, and records the thread on Castellano’s phone in two overlapping segments, 6 minutes 12 seconds and 4 minutes 50 seconds long. The index reads, in part: “Segment 1, 00:00–00:41: contact details showing (555) 555-0187. Segment 1, 00:42–03:10: TEN-000201 to TEN-000209. Segment 2, 00:00–02:15: TEN-000208 to TEN-000217.” Both video files, their hashes and the index are produced with the log.
How might opposing counsel challenge a screen recording?
Usually by attacking the file, the phone or the gaps. Prepare the answers before the hearing:
| Challenge | Where the answer comes from |
|---|---|
| “The video was edited.” | Original file, hash recorded at collection, unbroken scroll, matching export |
| “That contact name could be anyone.” | Contact details segment showing the number; subscriber records if authorship is disputed |
| “Messages are missing.” | Full-range recording plus an export; segment overlaps that show nothing was skipped |
| “Nobody can read this.” | The Bates-numbered log and the timecode index |
| “We never received it.” | Production log entry for the native video file with its hash |
| “Someone else was using the phone.” | The same authorship evidence any text exhibit needs: replies, content, conduct |
Whether to offer the recording, and as what, is a decision for the supervising attorney under the court’s rules and standing orders. This article is general information, not legal advice.
How CourtBriefly helps
A screen recording corroborates; the exhibit people actually read is the log. Message Extractor ingests the client’s exports, merges duplicates into one thread model and produces a paginated, Bates-stamped, fingerprinted PDF log with an index and a source manifest, including a SHA-256 digest and a 902(13)–(14) declaration template. Map the recording’s timecodes to those Bates pages, and the video and the log support each other.
Start freeFree plan, no card
