What other tools can export iMessages besides TextKeep?

Several commercial and open-source tools provide iMessage export functionality by accessing the local chat.db database. Each offers different features, formats, and pricing models.

Commercial Tools

iMazing ($45-70): A comprehensive iOS device management tool that includes message export. iMazing exports to PDF, CSV, Excel, or HTML formats, includes attachments when available locally, provides conversation filtering and selective export, and works with both live devices and iTunes/iMazing backups. The main limitation is that iCloud-offloaded attachments show as placeholders. iMazing is one of the most polished commercial options with a long track record.

PhoneView (~$30): A Mac-only message export utility that exports to PDF and text formats and includes media extraction capabilities. PhoneView is simpler and less expensive than iMazing but offers fewer export format options.

TouchCopy (~$30): Similar functionality to PhoneView but cross-platform, supporting both Mac and Windows. TouchCopy provides basic export capabilities at an affordable price point.

AnyTrans (pricing varies): A comprehensive iOS data management tool where messages export is one of many features. AnyTrans is suited for users who need broader iOS data management beyond just messages.

Open-Source Solutions

imessage-exporter: A Rust-based command-line tool that exports conversations to HTML or other formats. It handles the complex relational database schema automatically, names output files by phone number for easy identification, and is completely free and open-source. However, it requires Rust toolchain installation and command-line comfort. Installation is done via cargo install imessage-exporter, and usage is typically imessage-exporter -f html -c compatible.

Direct Database Access

Advanced users can query chat.db directly using SQL tools like TablePlus, SQLite Browser, or command-line sqlite3. This approach requires understanding the database schema and constructing appropriate JOIN queries across multiple tables. Recent macOS versions complicate this by storing message text as hex-encoded blobs rather than plaintext, requiring additional decoding steps. Direct database access offers maximum flexibility but demands technical expertise.

Common Limitations

All export tools share common limitations. Attachments stored only in iCloud appear as placeholders rather than actual files. Once messages are deleted and sync completes, they're permanently removed—no tool can recover them. All tools depend on local device access where private keys reside; remote export from iCloud alone is impossible due to encryption architecture. iMessage-specific features like reactions and message effects often don't translate perfectly to export formats.