How to export an iMessage conversation
Clark Reads reads an iMessage conversation from a plain text file. This page covers what that file has to contain, which layouts we can read, and what happens when the format is unclear.
Start from the device that holds the conversation
iMessage history lives on the iPhone, iPad or Mac that received it. Open Messages on that device and open the thread you want read — everything below works from that one conversation.
Get the conversation into a text file
This is the step we cannot do for you: iMessage has no built-in plain-text export, so the file has to be prepared on your side. What we need in the end is simple — one message per line, in the order it was sent, with the sender in front of every line.
Check the shape of the file
Open the file in any text editor. Each message should start with the sender name followed by a colon, for example Alex: are you around? A line that does not start with a name is read as part of the message above it, so a message may run across several lines.
Keep the dates and times if you have them
A full date with a 24-hour clock and a month name with a 12-hour clock are both read. If your file has no dates at all, the conversation is still read in order — the timeline in the report is simply thinner.
Upload the file on the setup page
Choose iMessage as the source, then drag the text file in. We count the messages and show what we found — the senders, how many messages each one sent, and the span of the conversation — before you go on.
What the file has to look like
One message per line: the sender, a colon, then the message itself. Continued lines that do not start with a sender name belong to the message above them, and nothing inside a message is dropped — the whole text is read.
Dates and times are welcome but not required. When they are present, we read the stamp in front of the sender name; when they are missing, the report leans on the order of the conversation instead of exact dates.
One conversation per file. A file that mixes several threads produces senders who never spoke to each other, and we will say so rather than quietly analyze the mixture.
What happens when the file is unclear
When we cannot read the file at all, we stop and tell you — we do not guess and we do not hand you a report built on nothing. The message you get says we could not recognise the format and gives you one thing to try: open the file in a text editor and check that every message starts on its own line with the sender name followed by a colon.
When we can read the file but the senders look unreliable — only one sender found, far more names than one conversation should have, or most lines without a sender in front of them — we ask you to confirm who is who before the report is written.
Long conversations
Nothing is sampled away. The conversation is followed from the first message to the last, so the parts that changed over time — a week where the tone shifted, a question that was never answered — stay in the reading.
Ready with a file? Read your iMessage conversation with Clark.
Want to see the shape of the result first? Open the sample report.
To be honest about the current state: this is a manual step. iMessage does not give you a plain-text export and we do not offer an export tool, so you prepare the text file yourself and Clark Reads reads it.