Skip to main content
Export guide

How to export an iMessage conversation

Here is the honest version up front: iMessage has no export button. Apple provides no official way to download a conversation. But there are three real paths to a usable file — and knowing what each one preserves (and loses) saves you from doing it twice.

Last updated: July 15, 2026

Option 1: How do I copy a conversation from Messages on a Mac?

If your iPhone conversations sync to a Mac, this is the fastest free route and handles long histories far better than anything on the phone itself.

  1. 1Open the Messages app on your Mac and select the conversation.
  2. 2Scroll up to load as much history as you want included — Messages only copies what has been loaded.
  3. 3Click inside the conversation, then press Command + A to select all visible messages.
  4. 4Press Command + C to copy.
  5. 5Open TextEdit, create a new document, and choose Format → Make Plain Text (Command + Shift + T).
  6. 6Paste with Command + V, then save the document as a .txt file.

Option 2: Can I export from just an iPhone?

There is no bulk option on iOS, but for a shorter stretch — one argument, one week, one thread of decisions — forwarding works:

  1. 1Open Messages on your iPhone and long-press any message in the conversation.
  2. 2Tap More… — selection circles appear next to every message.
  3. 3Tap each message you want to include (there is no select-all, so this suits shorter stretches).
  4. 4Tap the forward arrow in the bottom-right corner.
  5. 5Address it to yourself via email, send, then copy the text into a plain .txt file.

The catch: forwarded messages arrive as a block of text without the original timestamps, and hand-selecting hundreds of messages gets old fast. For anything beyond a focused excerpt, use a Mac or an export tool.

Option 3: What about third-party export tools?

Several desktop utilities (iMazing is a well-known example) read the Messages database from your Mac or from an iPhone backup and export whole conversations at once. For analysis purposes, what matters is the output format, not the brand:

  • .txt or .csv with one message per line — including a timestamp and the sender’s name — is ideal.
  • JSON works when each message is an object with sender, text, and timestamp fields (most tools’ default JSON layout fits).
  • PDF exports are made for printing, not parsing — if the tool offers .txt, .csv, or JSON, pick one of those instead.

What format should the final file be in?

ReadBeneath reads plain text, CSV, JSON, and .zip archives that contain them. For text files, these line shapes parse with full fidelity — timestamps, senders, and all:

Mar 15, 2026 at 2:30 PM - Jordan: running late, sorry
Mar 15, 2026 at 2:31 PM - Alex: all good, see you soon
2026-03-15 14:30 - Jordan: running late, sorry

If your file is just bare lines of text with no names or times, it will still upload and get a descriptive read — but the timing and per-person analysis that makes a report genuinely useful needs to know who sent what, and when. When you have a choice, keep the metadata.

Quick answers

Why does iMessage have no export feature?

Apple has never shipped one. Messages stores your history in a local database on your devices, and the only built-in ways out are copy-paste on a Mac or forwarding individual messages. Everything else goes through third-party tools that read the Messages database from your Mac or an iPhone backup.

What file formats can I upload from an iMessage export?

Plain text (.txt), CSV, or JSON. The analysis reads best when each message carries a timestamp and a sender name — for example 'Mar 15, 2026 at 2:30 PM - Jordan: running late'. JSON exports work when each entry has sender, text, and timestamp fields.

Do timestamps and names really matter that much?

Yes. Who said what, and when, is most of the signal: response gaps, late-night spirals, who initiates, who withdraws. A transcript without senders or timestamps still gets a basic read, but the timing and per-person patterns — often the most useful part — cannot be recovered from bare lines of text.

What happens to Tapback reactions like Loved or Liked?

If they appear in your export, ReadBeneath folds each Tapback onto the message it reacted to instead of treating it as its own message — so reactions enrich the picture without inflating your message count.

Are third-party export tools safe to use?

Treat them with the same care as anything that touches your message history: prefer tools that run locally on your own Mac rather than uploading your database to someone's server, and check what they claim to do with your data. ReadBeneath has no affiliation with any of them — we just read the file they produce.

File in hand? See what is underneath.

Upload your .txt, .csv, or JSON export, pick a focus, and get a free descriptive analysis — cited evidence for every observation, a fair alternative reading, and honesty about what a small sample can and cannot show.

Start a free analysisSee what each plan includes