Binary Documentation

The imessage-exporter binary exports iMessage data to txt or html formats. It can also run diagnostics to find problems with the iMessage database.

Installation

There are several ways to install this software.

Cargo (recommended)

This binary is available on crates.io.

cargo install imessage-exporter is the best way to install the app for normal use.

Installing manually

• clone the repository
• cd to the repository
• cargo run --release to compile

How To Use

```txt -d, --diagnostics Print diagnostic information and exit

-f, --format Specify a single file format to export messages into

-h, --help Print help information

-n, --no-copy Do not copy attachments, instead reference them in-place

-o, --export-path Specify a custom directory for outputting exported data If omitted, the default directory is ~/imessage_export

-p, --db-path Specify a custom path for the iMessage database file If omitted, the default directory is ~/Library/Messages/chat.db

-V, --version Print version information ```

Examples

Export as html and copy attachments from the default iMessage Database location to your home directory:

zsh % imessage-exporter -f html

Export as txt from the default iMessage Database location to a new folder in the current working directory called output:

zsh % imessage-exporter -f txt -o output

Export as html from /Volumes/external/chat.db to /Volumes/external/export without copying attachments:

zsh % imessage-exporter -f html --no-copy -p /Volumes/external/chat.db -o /Volumes/external/export

Features

Click here for a full list of features.

Caveats

HTML Exports

In HTML exports in Safari, when referencing files in-place, you must permit Safari to read from the local file system in the Develop menu:

Further, since the files are stored in ~/Library, you will need to grant your browser Full Disk Access in System Settings.

PDF Exports

I could not get PDF export to work in a reasonable way. The best way for a user to do this is to follow the steps above for Safari and print to PDF.

wkhtmltopdf

wkhtmltopdf refuses to render local images, even with the flag enabled like so:

rust let mut process = Command::new("wkhtmltopdf") .args(&vec![ "--enable-local-file-access".to_string(), html_path, pdf_path.to_string_lossy().to_string(), ]) .spawn() .unwrap();

This persisted after granting cargo, imessage-exporter, and wkhtmltopdf Full Disk Access permissions as well as after copying files to the same directory as the HTML file.

Browser Automation

There are several chomedriver wrappers for Rust. The ones that use async make this binary too large (over 10mb) and have too many dependencies. The sync implementation in the headless-chrome crate works, but times out when generating large PDFs, even with an extreme timeout.