How to Export iMessage History

There is no export button. Apple has never shipped one, on iPhone or on Mac, and after two decades of the Messages app that is clearly a decision rather than an omission.

What you have instead are four realistic routes, in rough order from free to paid:

• Run imessage-exporter, a free, open-source tool that writes your whole history to HTML or TXT with attachments, reading either the Messages database on a Mac or a local iPhone backup. This is the best answer for most people and the one the affiliate listicles never mention.
• Print a single conversation to PDF from Messages on a Mac. Native, built in, one thread at a time — the way to export imessage to pdf without any tool.
• Copy text out by hand into a document for a tiny job, and save attachments individually.
• Buy a paid utility only for a format the free tool does not produce — PDF across many threads at once, CSV, a spreadsheet, or a purpose-built legal-discovery package.

And one route that people expect to work and does not: requesting your data from Apple. More on that below, because it is the single most common wasted afternoon in this whole topic. And if what you actually want is for the history to stay current rather than freeze into a file, skip to the ongoing alternative at the end.

For most people asking how to download imessage history, the honest best answer is a free, open-source command-line tool: imessage-exporter by ReagentX (github.com/ReagentX/imessage-exporter), released under the GPL-3.0 license. It is the thing the affiliate roundups leave out, because there is no referral fee on free software.

On a Mac, install it with Homebrew — brew install imessage-exporter — or with Cargo if you already use Rust. It reads the live Messages database at ~/Library/Messages/chat.db, the ordinary SQLite file Messages already keeps on disk, and writes a full export to HTML or TXT with attachments saved alongside. It preserves the things a naive copy-paste loses: attachments, tapbacks and reactions, replies, edited-message history, and stickers, across SMS, MMS, RCS, and group chats. One run saves every conversation, so to save an imessage conversation — or all of them at once — is a single command, not four hundred manual operations.

No Mac? It also reads a local iPhone backup, which is how a Windows or Linux user can extract imessages from iphone: make an unencrypted backup of the phone to the computer, point the tool at that backup, and you get the same readable HTML or TXT out the other side.

The one thing it does not do is PDF. It exports HTML and TXT only. If you need a PDF, open the exported HTML in a browser and print it to PDF — the tool gives you the readable, attachment-complete export, and the browser handles the format conversion. For a single thread you can skip the tool entirely and print straight from Messages, covered next.

This is the only genuinely native option — no tool to install — and for a single important thread it is often enough.

Open Messages on a Mac, select the conversation, and use File → Print. In the print dialog, choose Save as PDF instead of a printer. You get the conversation laid out the way it appears on screen, with sender names and timestamps preserved.

The limits are real. It works one conversation at a time, so an archive of 400 threads is 400 manual operations — which is exactly why imessage-exporter exists for the bulk case. Long conversations may need scrolling to load older messages before they will print. Attachments come through as inline previews rather than original files. And it only covers what is actually present on that Mac — if a thread predates the machine, or never synced to it, it is not there to print.

For "I need a clean PDF of this one conversation, today," it is the right tool. For anything archival, reach for the exporter above.

You can select messages inside a thread, copy, and paste into a text editor or document. Attachments can be saved out of the thread individually.

This is the lowest-tech option and it has exactly the properties you would expect: perfect for pulling three messages into an email, useless for anything larger. Formatting, sender attribution, and timestamps degrade depending on where you paste, and there is no reliable way to keep the text and its attachments associated with each other afterwards.

On an iPhone there is even less available — you can forward selected messages to yourself or take screenshots, and that is broadly it. There is no built-in path from an iPhone directly to a readable file on a computer; that path runs through a Mac or a local backup, as above.

Worth stating clearly, because a lot of people go down this road first: requesting a copy of your data from Apple’s Data and Privacy portal does not give you your iMessage conversations.

iMessage is end-to-end encrypted, and Apple cannot read the contents, so there is nothing for it to hand back. The archive you receive contains things like sign-in records, purchase and app usage history, marketing and support history, and various account metadata — useful for a subject-access request, useless as a message archive. You may see capability-query logs, which record whether a number could receive an iMessage; those are not conversations and contain no message text.

The same logic applies to a warrant or a legal-hold request aimed at Apple. The content is not Apple’s to produce. If you need iMessage history for a dispute or a compliance matter, it has to come off the device — via the exporter or a paid utility, not from Apple.

A device backup — to iCloud, or a local backup made on a Mac or PC — will normally carry your messages forward to a new phone. That is a genuinely important thing to have, and if you have not checked recently, check.

A raw backup, on its own, is not an export. It is an opaque restore artifact, designed to be read by another Apple device, not by you. You cannot open it and read a conversation, search it, hand it to a colleague, or feed it into anything by itself. It answers "will I lose my messages," not "can I read my messages somewhere other than this phone."

But here is the nuance that matters: a local, unencrypted backup is exactly what imessage-exporter reads to produce a readable export — it is the no-Mac path from the free-route section above. So a backup is not an export, yet the right backup is the raw material an export tool turns into one. What still does not work is expecting the backup file itself to be human-readable, or expecting Apple’s data download to stand in for it.

One related trap: Messages in iCloud changes where the authoritative copy lives, so what is present on any given Mac depends on your sync settings and how long that machine has been signed in. Before assuming a thread is exportable, confirm it is actually visible in Messages on the machine you plan to export from.

The best-known iMessage export tool is free and open-source, so the paid desktop applications are a tier, not the whole category. You reach for one when you need something imessage-exporter does not do:

• PDF or CSV across many threads at once. The free tool leaves PDF to a browser print and does not emit CSV; a paid tool can produce both directly.
• A spreadsheet or database-ready format for loading messages into another system.
• Legal discovery. For a matter handed to a lawyer or an auditor, purpose-built discovery formats and chain-of-custody features are their own market.
• A graphical interface. If a command line is a non-starter, a GUI app that reads a Mac or a local backup and clicks through to an export can be worth paying for.

They all work either from a Mac where your messages are present, or from a local device backup you have made. Points to weigh before buying one:

• What it reads from. Working from a local backup and working from a live Mac are different products with different completeness.
• Attachment handling. Whether photos and files are exported as real files, correctly associated with the message they arrived on, or flattened into an image of the conversation.
• How participants are labeled. Threads carry phone numbers and email addresses; whether the tool resolves those to names varies, and it is the difference between a readable archive and a wall of digits.
• Trust. You are pointing a third-party application at the most personal data you own. Buy from someone who says clearly whether anything leaves your machine.
• Format fit. A folder of PDFs is an archive, not a record system. Nothing searches it, nothing links it to a customer, nothing tells you it exists in six months.

Step back and the shape of the problem is clear. Every route above — free tool included — produces the same thing: a snapshot, of some threads, in a format nothing else uses.

• It is frozen at the moment you ran it, so effort scales with how often you need it current.
• It is stale immediately — the export you made this morning is missing this afternoon’s messages.
• Text and attachments live as separate files, and unless the tool keeps them linked they often never find each other again.
• The output is a document, so it cannot be searched across, linked to a customer, or joined up with anything you said to the same person by email or on another messenger.
• Group threads have no clean representation across most formats.

Which means most people asking "how do I export my iMessage history" do not actually want a file. They want the history to be somewhere useful — attached to the person it belongs to, searchable, and still true next week. An export cannot be that, structurally.

Exporting a message history means making a durable copy of a conversation that other people were also part of, and they were not asked.

Sometimes that is entirely proper — your own business records, a matter under legal hold, a handover you are obliged to make. Sometimes it is not, and the difference is worth thirty seconds of thought before you run the command or click the button. A personal Messages archive contains far more than work: family, health, and years of private conversation with people who assumed it stayed on your phone. Export the threads you need, not the whole archive out of convenience. Be careful where the output goes, because a folder of HTML files or PDFs has none of the encryption the original conversation had. And if this is an employee’s account rather than your own, the decision belongs to them, with their knowledge — not to whoever administers the laptop.

If the need is one-time — a legal matter, closing an account, handing over a thread — take the export and be done. Run imessage-exporter, print a thread to PDF, or buy a utility for the format you need.

If the need is ongoing, an export is the wrong shape, because every export above is a snapshot that is stale the next morning. What you want instead is for the history to keep arriving somewhere that treats it as a record rather than a document. That is what the Pantheon desktop app does: it reads local iMessage on your Mac and keeps it as a searchable record, per contact — and it does the same for Telegram and WhatsApp, so the same person is one profile no matter which app or which handle a message came from. Your iMessage history stops being a folder of files and becomes part of one searchable relationship record that does not go stale, because it does not stop.

Stage honesty: Pantheon is in alpha. Telegram is live today; WhatsApp and iMessage run through the desktop app on your Mac; mobile is incoming.