Where iMessages are actually stored on a Mac

Messages does not store your conversations in the cloud, in the app bundle, or in a document you can drag somewhere. It keeps them in a database in your home folder, and once you know where it is, a lot of confusing behaviour starts making sense.

This page covers the exact locations, what each file is for, how to look at them without damaging anything, and the specific reasons a straight copy of the folder often does not work.

The location

Everything lives under your own home folder, in a hidden Library directory:

• ~/Library/Messages/chat.db is the main database. Every message, every conversation, every timestamp.
• ~/Library/Messages/chat.db-wal is the write ahead log. Recent messages can live here and not yet be in chat.db.
• ~/Library/Messages/chat.db-shm is shared memory used to coordinate access to the database.
• ~/Library/Messages/Attachments holds photos, videos, and files, in nested folders with generated names.
• ~/Library/Messages/StickerCache holds sticker and reaction art.

The tilde is your home folder, so for a user named alex the full path is /Users/alex/Library/Messages. This is the per user Library inside your home folder, not the /Library folder at the top of the disk. They are different directories and only the one in your home folder holds messages.

How to open the folder

The Library folder is hidden by default. In Finder, choose Go from the menu bar, then hold the Option key and Library will appear in the menu. Or choose Go, then Go to Folder, and enter the path directly.

What chat.db actually is

It is a standard SQLite database. That is good news, because SQLite is an open, well documented, extremely stable format, and it means your history is not locked inside a proprietary file that only Apple can read.

The structure that matters is small. Four tables carry almost everything:

• message holds the individual messages, their text, timestamps, and whether they were sent or received.
• handle holds the phone numbers and email addresses of the people you talk to.
• chat holds the conversations, including group threads.
• attachment holds pointers to the files in the Attachments folder, not the files themselves.

Because the attachment table only stores paths, a copy of chat.db on its own gives you every word and no pictures. The database and the Attachments folder have to travel together or the media is lost.

Timestamps are not normal timestamps

Dates in chat.db are stored as nanoseconds since 1 January 2001, which is Apple’s reference date rather than the Unix epoch of 1970. A tool that reads them as ordinary Unix time will place your entire history about 31 years in the past.

This is the single most common bug in home made export scripts, and it is worth knowing about, because a set of exported messages with visibly wrong dates is worse than no export at all if you ever need someone to trust it.

Why copying the folder often fails

Dragging ~/Library/Messages to an external drive feels like it should work. Sometimes it does. Often it produces an archive that is missing recent conversations or will not open at all, for three reasons.

The write ahead log

SQLite writes new data to chat.db-wal first and folds it into chat.db later. Copy chat.db alone while Messages is running and the most recent messages, sometimes weeks of them, are still sitting in the log file you did not copy.

Copying a live database

A file being written to while it is copied can produce a corrupt result. The copy looks like it worked, the file size looks right, and it fails to open later when you actually need it. Quitting Messages before copying avoids this.

Full Disk Access

macOS protects ~/Library/Messages specifically. Finder can see it because you granted Finder access long ago, but any app that wants to read it must be given Full Disk Access in System Settings, under Privacy and Security. An app without that permission sees an empty folder rather than an error, which is why some tools report finding no messages on a Mac that clearly has thousands.

Local iPhone backups are a second copy

If you have ever backed up an iPhone to this Mac, there is another copy of a message database on the disk, from whenever that backup was made. Those live under ~/Library/Application Support/MobileSync/Backup, in folders with long hexadecimal names.

Inside a backup the files are renamed to hashes, so the message database is not called chat.db there and cannot be found by browsing. It has to be located through the backup’s own manifest.

These backups are frequently the only surviving copy of conversations that were later pruned from the Mac, which is a good reason not to delete old ones to reclaim space. An encrypted backup needs its password before anything can be read out of it.

Reading it yourself

If you are comfortable in Terminal, you can copy the database to your Desktop and open it read only without touching the original. Quit Messages first.

1. Quit Messages completely.
2. Copy all three database files together, not just chat.db, so the write ahead log comes with it.
3. Open the copy with sqlite3 and query the message table.
4. Convert the date column from Apple reference time before trusting any timestamp you see.

This is genuinely useful for a one off look. It is a poor long term plan, because you have to remember to do it, the export has no attachments unless you handle those separately, and a folder of text you produced yourself carries no evidence that it was not edited afterwards.

Where Message Archive fits

Message Archive handles the awkward parts of the above. It reads chat.db together with its write ahead log so recent messages are not missed, keeps attachments with the messages they belong to, converts Apple reference timestamps correctly, and finds local iPhone backups and merges their conversations in alongside the ones on the Mac.

It reads the Messages database read only and never writes to it. The archive lives wherever you choose, outside ~/Library/Messages, which means it is not affected by the Keep Messages setting, by iCloud sync, or by macOS clearing attachments when storage runs low.

It can also produce a sealed export, which is a copy carrying a cryptographic seal and an independent RFC 3161 timestamp from a third party. Anyone can check that seal at our verify page without buying anything, and it establishes that the file has not been altered since the timestamp. It is a tamper evident, independently timestamped record. Whether any particular person or process accepts it is their decision, not something software can promise.

$47 per year, per Mac. 14-day free trial, no account needed to try it.

The short version

• Messages live in ~/Library/Messages/chat.db, a normal SQLite database.
• chat.db-wal holds recent messages that are not in chat.db yet, so copy all three files together.
• Attachments are separate files, and the database only stores paths to them.
• Timestamps use Apple reference time, not Unix time, and are off by 31 years if read wrong.
• Any app reading this folder needs Full Disk Access, or it will see nothing at all.
• Old iPhone backups on the same Mac often hold conversations the Mac itself has already lost.