“What format do you want the texts in?” is one of the first questions a client asks after you request their messages, and the honest answer depends on the phone, the app and what the office plans to do with them. A screenshot, a PDF and a CSV of the same conversation are not interchangeable. One keeps the look, one keeps some of the data, and one keeps most of it.
This guide compares the export formats clients can realistically produce, what each keeps and loses, which to ask for by device and app, and how to check a file when it arrives. App names and options change between versions, so confirm current behavior on the device in front of you.
What export formats can a client give the office?
Most text message exports fall into three families: structured data, readable renderings and images. The table compares the formats offices see most often.
| Format | Typical source | Keeps | Loses or risks |
|---|---|---|---|
| CSV or Excel | iPhone backup tools (for example, iMazing), some Android apps | One row per message with date, time, sender, number, text and attachment names | Layout; data altered if re-saved in a spreadsheet program |
| XML | Android backup apps (for example, SMS Backup & Restore) | SMS and MMS with raw timestamps, numbers, threads and embedded attachments | RCS chats in some versions; large file sizes |
| JSON | Facebook, Instagram and Google account downloads; some chat apps | Structured messages, often with UTC timestamps and identifiers | Needs a tool to read; some exports encode emoji oddly |
| TXT (zipped with media) | WhatsApp chat export | Dated lines per message; media as separate files if included | Date format follows phone region settings; one chat per export |
| HTML | Platform downloads, some export tools | Readable layout with dates and media | Harder to filter, merge or deduplicate |
| Export tools, printing | A readable rendering | Often omits numbers, years, reactions or attachments; not processable | |
| Full backup or database | Computer backups, forensic extraction | The most complete record, sometimes including deleted data | Needs a tool or examiner; collects far more than the request |
| Screenshots or screen recordings | The phone screen | What the user saw | Years, identifiers, full attachments, context and fidelity |
The practical rule: structured exports are for processing and production; renderings and screenshots are for reading and display. When a client can only produce screenshots, our guide to triaging a client screenshot dump covers how to work with them.
What should any text message export preserve?
Whatever the format, check that it carries the fields a log, an exhibit and a production will need:
- Both sides of every responsive conversation
- A full date with the year and a time, with the time zone or UTC basis known
- Sender and recipient identifiers, meaning phone numbers or account IDs, not only contact names
- Thread association, including group participants
- Attachments linked to the messages that carried them
- Reactions, edits and unsent or deleted markers where the platform records them
- Export details: the tool and version, the settings chosen, the date and the device or account
Which export should you ask the client for?
Ask for the structured export that fits the device and app, plus whatever readable rendering the same tool produces. That gives reviewers something to read and the office something to process.
| Device or app | Ask for | More detail |
|---|---|---|
| iPhone messages | A backup-based export to CSV or Excel, with attachments | iMessage export guide |
| Android messages | An XML backup of SMS and MMS, with MMS switched on | Android export guide |
| A chat export per conversation, with media included | WhatsApp evidence guide | |
| Facebook and Instagram messages | An account download covering messages, in JSON and HTML | Social media production guide |
| Google Voice | A Google Takeout download with Voice selected | Confirm texts appear in the archive |
| Co-parenting apps | The app’s own message report or record request | Co-parenting app records |
Screenshots still have a place: showing exactly what a message looked like, capturing something no export includes, or documenting a phone that has since been lost. They should not be the collection itself when a structured export is available.
How do you check an export when it arrives?
Check the file the day it lands, before anyone starts reviewing:
- Hash and store the original. Record a SHA-256 value and keep the file read-only. Every view, conversion or import uses a copy. See hash values in litigation.
- Confirm it opens and is complete. Zipped exports should unzip without errors; file sizes should be plausible for the number of attachments.
- Check dates. Confirm the year appears, identify the time basis (UTC or device local time), and record the phone’s region settings for text exports whose date order varies.
- Check characters. Emoji and accented letters should display correctly in a review copy. Garbled characters usually mean an encoding issue to fix in processing, not a change in the evidence.
- Spot-check against the phone. Compare the first and last message and the count for a key thread with what the client’s phone shows.
- Log it. Add the file, hash, source, tool and settings to the collection log that will support the chain of custody.
Template: “what to send us” instructions for clients
Please send your messages with [Name] from [date] to [date] using the steps for your phone below. Do not take screenshots unless we ask, and do not delete, edit or rename anything. iPhone: [backup tool] export of the conversation to [CSV/Excel], with attachments. Android: [backup app] backup of messages with MMS turned on and all conversations selected. WhatsApp: open the chat, choose Export chat, and include media. Upload the file to [secure link] the same day and reply to this message with the file name. If any step does not match what you see on your phone, stop and call us at [number].
The other half of getting good exports is telling clients what not to do. Our guide to getting clients to send organized evidence covers instructions, follow-ups and clients who cannot keep up with a system.
How do mixed formats become one record?
Real matters rarely arrive in one format. A client sends an iPhone CSV, a WhatsApp export, a Facebook download and forty screenshots of the same arguments. The work is to merge them into one set of threads, remove duplicates, normalize timestamps to a stated time zone and keep a manifest that ties every message back to its source file.
Message Extractor auto-detects iMazing CSV or Excel, SMS Backup & Restore XML, WhatsApp, Facebook, Instagram, Google Voice and email exports, merges duplicates into one thread model, and renders a paginated, Bates-stamped log with an index, attachment appendix and source manifest listing each file’s SHA-256 value.
Try it on one matterFree plan, no card
What goes wrong with client exports?
| Mistake | Consequence | Fix |
|---|---|---|
| Asking only for “the texts” | Screenshots with no years or numbers | Name the export and steps by device |
| Re-saving the original CSV | Altered dates and phone numbers | Hash first; work on copies |
| WhatsApp exported without media | Messages reference photos nobody has | Re-export with media included |
| Ambiguous date order | Messages placed on the wrong day | Record region settings; normalize |
| Contact nicknames left in the log | Distraction or embarrassment at the hearing | Review labels before production |
Which format to produce, whether to show contact names and how to describe collection in a written response are decisions for the supervising attorney. Courts and opposing counsel differ on what form they expect, so confirm local practice with counsel licensed where the matter is pending, and see producing text messages in discovery for the production steps.
