How to Export iMessage History

Apple Messages on Mac can print an individual conversation to PDF, but it has no bulk export button for all your threads. Choose a route based on the output you need:

• One conversation as a PDF: select it in Messages on a Mac and use File → Print → Save as PDF.
• Many conversations as readable files: use the free, open-source imessage-exporter to produce HTML or TXT from a Mac database or local iPhone backup.
• A few lines: copy selected messages or take screenshots, checking timestamps and participant names.
• A specialized handoff: evaluate a paid utility if you specifically need bulk PDF, CSV, or a managed discovery workflow.

Every route reads the messages available in its source. Before installing or buying anything, check whether the conversation is present on the Mac or in the backup you plan to use.

imessage-exporter is a free, open-source command-line tool. On a Mac, its installation guide covers Homebrew and Cargo. It can read the local ~/Library/Messages/chat.db or an encrypted or unencrypted local iPhone backup on macOS, Windows, or Linux. It outputs HTML or TXT and supports group chats, replies, tapbacks, and available media.

Two details matter for a usable archive. First, grant your terminal Full Disk Access on macOS if the database cannot be opened. Second, the default attachment mode references files at their current paths; choose --copy-method clone or another copy mode if you need self-contained files that survive a move to another computer. Open several exported conversations and attachments before deleting the source.

The tool does not emit PDF directly. Export HTML and print it from a browser; its FAQ recommends --no-lazy when preparing HTML for PDF so images load for printing. For one thread, the native Mac print route is simpler.

After installing the tool using its current instructions, this exports the messages present in the Mac database as HTML and copies attachments in their original formats into the output folder:

imessage-exporter -f html -c clone -o ~/imessage-archive

For only conversations involving a particular number or email address, add a participant filter, for example:

imessage-exporter -f html -c clone -t "name@example.com" -o ~/imessage-contact-archive

The filter can include group conversations with that participant, so inspect the output rather than assuming it contains one private thread. If you want a PDF, add --no-lazy, open the resulting HTML in a browser, and print it. On macOS, grant the terminal Full Disk Access if the tool cannot read chat.db. Keep enough free space for copied media and open several files before treating the archive as complete. For an encrypted iPhone backup, point -p at the backup directory and let the tool prompt for its password; putting a password directly in a command can expose it in shell history.

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.

Do not treat a request at Apple’s Data and Privacy portal as your Messages export plan. Apple’s data file guides describe account and service files, while Messages and iCloud use their own sync and backup paths. If you need a readable conversation, check a device or a local backup that actually contains it.

Encryption claims need care: iMessage is end-to-end encrypted in transit, but iCloud backup and Messages in iCloud have their own key and recovery rules. Apple’s privacy explanation is the place to check those rules. Do not infer from end-to-end encryption alone what Apple can or cannot supply under every account configuration.

A device backup is designed for restoration, not for reading individual conversations. A local backup can be a source for imessage-exporter; the tool’s FAQ says it accepts encrypted or unencrypted local iPhone backups. It cannot read messages that exist only in iCloud and are absent from the Mac database or local backup you supplied.

Apple distinguishes Messages in iCloud from iCloud Backup: when Messages in iCloud is on, messages sync separately and are not included in the daily iCloud device backup. When it is off, messages can be included in that device backup. Check your settings and the actual contents of the source rather than assuming every backup includes every message.

Check Recently Deleted in Messages before trying an exporter. On an iPhone, open Messages → Filters → Recently Deleted; on a Mac, choose View → Recently Deleted. Apple says you can recover messages for up to about 30 days, then export them after they reappear. Apple’s Mac instructions and iPhone instructions give the current steps.

Messages in iCloud is sync, not an independent archive: deleting a message on one connected device removes it from the others. An exporter can only read messages still present in the Mac database or backup you give it. Do not buy an export utility on the assumption it can reverse a permanent deletion; ask what source it would recover from first.

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.

An HTML or TXT export is useful: you can read it later and search the files. Its limit is that it only reflects the source at the time you ran it. New messages require another export; a file does not set follow-up dates or connect the same person’s conversation on another app.

If preservation is the job, keep a verified export and a separate device recovery plan. If daily relationship work is the job, use a contact record for the conversations it captures. You may need both.

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, every export above is a snapshot that goes stale as new messages arrive. A searchable relationship record solves a different job: keeping the conversations it captures attached to the right person across apps. Pantheon’s iMessage CRM does that through its Mac desktop app, alongside Telegram, WhatsApp, and supported X DMs. It does not turn a past export into a restorable Apple backup.

Pantheon is in alpha. Test a real thread on the Mac you plan to connect, including an older message and an attachment, before depending on captured history.