Apple makes it surprisingly hard to get your own messages out of Messages. There is no Export button and no easy way to export an iMessage conversation, and the workarounds run from tedious to technical. This guide covers every method that actually works in 2026: what each one is good for, and where each one falls down.
We will be honest about the trade-offs, including where our own tool fits and where it does not.
First, the short answer
- Just need a quick copy? Select messages in the Messages app and copy-paste. Fine for a handful of texts, painful for a long thread.
- Need a printout for legal or archival use? Print the conversation to PDF, or use a paid app like iMazing or Decipher TextMessage.
- Comfortable in the Terminal? The free, open-source
imessage-exportertool exports everything to text or HTML. - Want to ask ChatGPT or Claude about a conversation? You want a clean, token-efficient text export. That is exactly what we are building Lembic for.
Now the detail.
Method 1: Copy and paste from the Messages app
The simplest approach, and it needs no extra software.
- Open Messages on your Mac.
- Click the conversation in the sidebar.
- Scroll up to load older messages. Messages loads them lazily, so this can take a while on long threads.
- Click a message, then Edit → Select All (or
⌘A), and Copy (⌘C). - Paste into any text editor.
Good for: a few dozen messages.
Falls down because: you have to scroll by hand to load history, timestamps and sender names often do not come through cleanly, and reactions and attachments turn into noise. For a multi-year thread it is genuinely impractical.
Method 2: Print the conversation to PDF
macOS can “print” any conversation to a PDF file.
- Open the conversation in Messages on your Mac.
- File → Print (
⌘P). - In the print dialog, choose Save as PDF from the PDF dropdown.
Good for: a visual archive, or a record you need to hand to a lawyer.
Falls down because: PDFs are built for paper, not analysis. They are bloated, the layout wastes space, and if you paste one into an AI you will blow past its context limit almost immediately. A few hundred messages can balloon into a file no model can read in one pass.
Method 3: Paid desktop apps (iMazing, Decipher TextMessage)
Apps like iMazing and Decipher TextMessage read your iPhone backup and export conversations to PDF, CSV, or text.
Good for: bulk exports, attachments, and legal-grade records. These are mature, well-supported tools.
Falls down because: they cost money (subscription or a higher one-time price), the output is still designed for printing and archival rather than for AI, and some require a full device backup first.
If you landed here because a tool you used to rely on stopped working, we keep a current rundown of the options in the best PhoneView alternatives.
Method 4: The free command-line tool (imessage-exporter)
If you are comfortable in the Terminal, the open-source imessage-exporter (by ReagentX) is excellent. It reads your local Messages database directly and exports to clean text or HTML, including attachments and reactions.
# Homebrew
brew install imessage-exporter
# Export everything to TXT
imessage-exporter -f txtGood for: developers who want complete, scriptable exports for free.
Falls down because: it is a command-line tool. There is no contact picker, no preview, and no easy way to scope a single conversation or trim it to fit an AI’s context window. Most people are not going to install Homebrew to read their texts.
Method 5: The AI-ready way (what we are building)
Every method above was built for paper, backups, or programmers. None was built for the thing more and more people actually want to do: hand a conversation to ChatGPT, Claude, Gemini, and so on, and ask about it.
That is the gap Lembic fills:
- Pick a conversation by contact name. No chat IDs, no Terminal.
- Export a compact, token-efficient transcript an AI reads cleanly, so you fit far more of the conversation into one chat and get better answers.
- A token meter tells you whether the export fits your model’s context window before you paste it.
- One-click prompts like “summarize this relationship,” “extract every commitment we made,” or “make a timeline.”
- 100% on your Mac. No upload, no account, no server, and the export engine is open source so you can verify it.
It is a one-time purchase, not a subscription. Download Lembic for your Mac. The first 500 buyers get 50% off with code FOUNDING50.
A note on privacy
Whichever method you choose, remember that your messages are deeply personal. Be careful with any app that uploads your conversations to its own servers to “analyze” them. That is the opposite of private. The safest exports happen entirely on your own machine. (That is a hard requirement for us: Lembic has no backend to upload to.)
Frequently asked questions
Can I export an entire conversation, including old messages? Yes. Methods 3, 4, and 5 read your full local history. Copy-paste only captures what you have scrolled into view.
Do I need my iPhone plugged in to export iMessages? Not for the Mac-based methods. Your Mac already has a synced copy of your Messages history. If it does not yet, here is how to download your iMessages from iCloud first.
What is the best format to export iMessages for AI? Plain, compact text. PDFs and CSVs are bloated and blow past a model’s context limit quickly. A clean text transcript fits more of the conversation into one chat.
Can I export an iMessage conversation to PDF? Yes. Open the conversation in Messages on your Mac, use File → Print, then Save as PDF (Method 2 above). It is good for a printout or a legal record, but a poor fit for feeding to an AI.
How do I get the export into ChatGPT or Claude? Export to plain text, then paste it in (or upload the file). The cleaner and more compact the text, the better the AI handles it, which is the whole reason we built an AI-first exporter.
Is it safe to export my iMessages? It is safe as long as the export stays on your own machine. Avoid apps that upload your conversations to their servers to analyze them. The safest exports never leave your Mac.