Screenshots vs. printing vs. a database export
Screenshots are quick but incomplete: times go missing, messages get cropped, and there's no record of where they came from. Printing from Messages is tidier but records little more than what's on screen. Exporting from the message database gets you every message with its exact timestamp, plus a record of the source. For anything longer than a few messages, the export is the better record.
At a glance
| Screenshots | Print from Messages | Database export | |
|---|---|---|---|
| Time on every message | Rarely | No, occasional headers | Yes |
| Complete for a date range | Hard to show | What's loaded on screen | Yes |
| Page identifiers (Bates) | No | No | Yes |
| Record of the source | No | No | Path and SHA-256 hash |
| Photos inline | If captured | Usually | Yes |
| Effort for 500 messages | Hours | Minutes, lots of scrolling | Minutes |
| Cost | Free | Free | Varies by tool |
Screenshots
Screenshots are what most people bring to their first meeting with a lawyer, and for three or four messages they can be fine. The trouble starts at scale.
- Times are missing. On iPhone, the exact time of each message is hidden until you swipe left, so most screenshots show only an occasional date header.
- Gaps are invisible. A stack of screenshots can't show that nothing was left out between them, and the other side may argue that something was.
- They're hard to cite. Forty images with no page numbers make it hard for anyone to say "see page 12."
- They're easy to question. An image of a chat bubble says nothing about where it came from or whether it's been changed.
Printing from Messages on a Mac
Messages on the Mac has File → Print, and the print dialog can save to PDF. It captures roughly what the conversation window shows: chat bubbles, with dates as occasional headers rather than a timestamp on every message. For a long conversation you have to scroll back far enough for everything to load first. There are no page identifiers and no record of the source.
It's better than screenshots, and it costs nothing. For a short exchange where exact times don't matter, it may be all you need.
Exporting from the message database
Behind the Messages app is a database, chat.db, holding every message
with its sender and its exact timestamp. A database export reads that directly,
so the output doesn't depend on what happened to be on screen.
Several tools do this. Well-known ones include iMazing and Decipher TextMessage, which can work from an iPhone backup (Decipher can also read a Mac's Messages), and they're good options, especially on Windows. Legal Message Export reads the database already on your Mac and is built specifically for the legal case. How the three compare. What it adds:
- A timestamp and sender on every message
- A Bates number on every page, with your prefix and starting number
- A cover page with the source path, the SHA-256 hash, and the import and export dates
- An optional declaration of authenticity in US, Canadian, UK, or generic wording
- Local only: the database is copied and read on your Mac, and nothing is uploaded
What Bates numbers and the SHA-256 hash add →
When you need more than any of these
If the authenticity of the messages is seriously disputed, for example if someone claims they were fabricated or edited, a forensic examiner who extracts data directly from the phone is the right tool. None of the options on this page, including ours, replaces an expert witness. Your lawyer will know when that's worth the cost.
See what a database export looks like
The sample PDF is a fabricated five-page conversation exported with Legal Message Export: cover, declaration, transcript.
Legal Message Export produces a documented record. It doesn't guarantee that a court will admit it; that's the judge's decision. iMazing and Decipher TextMessage are trademarks of their respective owners and are named here for comparison only.