Text messages are often the most useful documentation a co-parent already has, and the most commonly wasted. Almost every parent in a custody dispute has a few screenshots somewhere in their camera roll. Far fewer have those messages in a form an attorney can hand to a mediator without an argument about where they came from. This guide covers how to capture a thread so it keeps its value, how to keep what you capture findable months later, and what to avoid. It is general information, not legal advice: rules of evidence differ by state and by courtroom, and only a lawyer in your jurisdiction can tell you how a message will be treated in your case.
Why messages carry weight, and why most screenshots don’t
A message thread has two qualities a memory doesn’t. It was written by the other parent in their own words, and it carries its own date and time. When the dispute is about whether an exchange was cancelled at 4:12 PM or the next morning, a message settles it in a way that two conflicting recollections never will. Patterns show up too: fourteen last-minute cancellations across a spring read very differently from one.
The reason most screenshots fail isn’t that judges distrust technology. It’s that a single cropped bubble answers none of the questions a careful reader has. Who sent it? When? What came before and after? Was anything left out? An image showing one line of text, with no contact name, no timestamp and no surrounding conversation, asks the reader to take your word on all four, and gives the other side an easy objection. A screenshot that shows the exchange, the sender and the date is much harder to argue with, and it takes no more effort to capture.
Capture the thread, not the line
Take screenshots as though a stranger will read them without you in the room to explain. In practice that comes down to a short list of habits:
- Capture the full thread, not one bubble. Scroll back far enough to include what led up to the message and what followed it, and overlap your screenshots by a message or two so a reader can see the sequence joins up with nothing missing between images.
- Keep the sender visible. The contact name or number at the top of the screen should appear in at least one screenshot of every thread. If your co-parent is saved under a nickname, consider changing it to their full name so the header reads plainly to someone who has never met either of you.
- Get a date and time on screen. Most messaging apps show a date and time only at the top of a thread or where there is a gap in the conversation, not beside every message. Scroll so one of those dividers is visible and capture it, even if that means an extra screenshot at the start of the set. A thread with no date anywhere in it is the single easiest thing for the other side to question.
- Never crop to the damaging line. Cropping is the fastest way to make honest evidence look edited. If a message is bad on its own it is bad in context too, and it lands far harder in context.
- Include your own messages. A thread where only the other parent speaks invites the obvious question about what you said. Your half of the conversation is part of the record whether you capture it or not, so capture it.
- Keep the originals on the phone. A screenshot is a copy. If a message ever matters enough to be challenged, the thread on the device is what stands behind it. Don’t delete the conversation, and check any setting that auto-deletes old messages.
- Capture soon after it happens. Messages get deleted, phones get replaced, accounts get lost. Capturing the same evening also keeps the date you took the screenshot close to the date the message was sent, which is one less thing to explain.
A pile of screenshots is not a record
Capturing is the easy half. The half that decides whether the effort was worth anything is whether you can find one specific message in August that you screenshotted in March.
A camera roll fails at this for mundane reasons. It’s sorted by the day you took the picture, birthday photos sit in between, nothing tells you which exchange an image belongs to, and none of it says why you kept it. Ask that pile for “the messages about the cancelled Easter weekend” and you lose twenty minutes scrolling, usually the evening before you were meant to send something to your attorney.
What works is filing each capture against the event it documents: the incident, the date and time it happened, two or three factual sentences about what occurred, and the screenshots attached to that entry. Our guide on documenting custody violations covers the fields worth recording every time. Messages about money belong with the expense they concern, alongside the amount, who paid and how it was split. The test is simple: could someone else, handed your record, understand a given screenshot without asking you a single question?
Authentication and hearsay, in plain language
Two words come up whenever messages are offered as evidence, and both sound more intimidating than they are. Treat what follows as a rough map, not as the law where you live.
Authentication is showing that a message is what you say it is: that this person really sent it and that it hasn’t been altered. In many jurisdictions this is a relatively low bar, and it’s met in ordinary ways: the number or account the message came from, your own testimony about the exchange, the other parent acknowledging the conversation, or content that only they would know. It gets difficult when the only thing available is a cropped image with no header and no dates.
Hearsay is, very roughly, the rule against using someone’s out-of-court statement to prove what it asserts. It comes with a long list of exceptions, and statements by the opposing party are often handled differently from statements by a third person. Whether a particular message clears it depends on your jurisdiction and on what you’re offering the message to prove, which makes it a question for your attorney rather than for a website.
You can’t control how a judge rules on either point. You can make both easier to answer: keep the thread intact, keep the context, keep the sender and the dates visible, and be able to show which event each screenshot belongs to and when it was captured. Our guide on whether custody journals and text messages are admissible goes into what tends to strengthen or undermine records of this kind.
What not to do
- Don’t edit or annotate the images. No circles, no arrows, no highlighting, no cropping out the parts that don’t help you. Any mark on an image invites the question of what else was changed. Put your commentary in the entry text, where it is plainly yours, and leave the screenshot untouched.
- Don’t delete the other side of the conversation. Or your own. Selective preservation reads as manipulation even when it was innocent, and it moves the hearing’s attention onto your credibility instead of the events you were documenting.
- Don’t take selective screenshots. A thread trimmed to the other parent’s worst three lines is weaker evidence than the same thread in full, because the gaps are visible and the reader fills them in unfavorably.
- Don’t record calls without knowing your state’s rule. Recording audio is a different matter from screenshotting a message. Some states allow a participant to record their own conversation; others require every participant’s consent, and getting it wrong can carry criminal exposure as well as making the recording useless. Our state pages note which rule each state generally follows, and this is worth confirming with your attorney before you record anything.
- Don’t retype messages instead of capturing them. A transcript you typed is your account of what was said, not the message itself.
- Don’t send messages you wouldn’t want read aloud. Your words are as capturable as theirs. Assume everything you write will be printed one day and read in a calm room by someone with no stake in either of you.
Turning the screenshots into an organized record
Filing a backlog one screenshot at a time is the part people abandon, which is why Oya Shield can take them in bulk. From the “Import & Bulk Add” row in Settings, “Import Screenshots” lets you pick up to eight images of a conversation from your photo library, or paste the text of a thread instead. “Find Incidents & Expenses” reads them and proposes draft entries. The analysis happens on your iPhone, using Apple Intelligence and on-device text recognition, so it needs an iPhone with Apple Intelligence on iOS 26. There is no camera capture and no file or PDF import: it works from images already in your library, or from text you paste.
One import can propose incident drafts and expense drafts together, and there’s no cap on how many it produces, so a long backlog can yield twenty entries or more. Drafts stream in as they’re found, and stopping early keeps whatever has already arrived. Very long threads are truncated, and the app says so rather than quietly dropping the rest. Receipts, bills and statements follow a parallel path: “Import Receipts” takes up to twenty separate images. Repeat detections from the same conversation are merged so one incident doesn’t land twice; receipts are never merged, and merging never raises an entry’s severity.
Two guardrails matter more than the convenience. The first is that nothing is saved automatically. Every proposal arrives on a screen headed “Review before saving”, where you either confirm it with “Review & Save” or drop it with “Discard”. You decide what enters your record, so read each draft, correct anything the model got wrong, and discard what isn’t worth filing. Import and analysis are free to try; saving what it finds needs Premium or your account’s free first 7 days. Once you save, the entry and the screenshots attached to it sync to your private account, so the record survives a lost or replaced phone.
The second is provenance, and it’s the reason this kind of help can be safe around evidence at all. When a draft becomes an entry, the model’s proposed title, body, category and severity are stored permanently alongside it, together with up to three quotes checked as verbatim against your screenshots. Your later edits never overwrite that original proposal. The PDF export prints a provenance block for each entry, attributed either “as proposed by the assistant” or “rewritten by the account holder”, so a reader can see which wording came from the assistant and which is yours. Quotes are dropped rather than shown if the model paraphrased instead of quoting exactly. That distinction is what keeps an assisted record honest: the reader never has to guess who wrote what.
On an iPhone without Apple Intelligence the same flow still saves the typing. The button reads “Extract Text”, and the words in your screenshots are pulled into a prefilled editor so you can file the entries yourself.
The short version
Capture whole threads, with the sender and the dates showing, soon after they happen. Keep the originals on your phone. Don’t crop, don’t annotate, don’t delete, and don’t record audio without checking your state’s consent rule first. File every capture against the dated event it documents, so that months later the record answers questions instead of raising them. Then let your attorney decide what to use.
Reviewed August 2026. This guide is general information, not legal advice. Evidence rules and how they’re applied vary by state, county and case; for guidance on your situation, consult a family-law attorney in your jurisdiction.
Frequently asked questions
Are text messages admissible in custody court?
Often yes, but it depends on your jurisdiction and on how the messages were kept. Family courts see text messages routinely, and judges have wide discretion. What tends to cause problems isn’t the format but the handling: cropped images, missing timestamps, no visible sender, and threads where only one side of the conversation was preserved. Ask your attorney how messages are treated where your case is filed.
How do I prove who actually sent a message?
In many jurisdictions this is a lower bar than parents expect, and it’s usually met in ordinary ways: the phone number or account the message came from, your own testimony about the exchange, the other parent acknowledging the conversation, or content only that person would know. Keeping the thread intact on your phone, with the contact name and dates visible in your screenshots, makes the question much easier to answer. It becomes hard when all you have is one cropped image.
Should I ever delete the original messages?
As a rule, no. Screenshots are copies, and the thread on your device is what stands behind them. Deleting conversations that relate to your case can look like you removed something inconvenient, even when you didn’t, and in some situations there may be a duty to preserve records once a case is anticipated. Check auto-delete settings on your phone, and ask your attorney before deleting anything connected to the dispute.
How many screenshots are enough?
Enough to show the whole exchange in context rather than the one line that helps you. For a single incident that usually means a few overlapping screenshots covering what led up to it, the message itself, and what followed, with the contact name and date visible somewhere in the set. Quality of context beats volume: 400 loose screenshots nobody can navigate are worth less than 12 filed against the events they document.