How to read a WhatsApp backup on a computer

Reading your WhatsApp history on a computer sounds like it should be simple. There is a backup, there is a computer, the two ought to meet. In practice most of the obvious routes are dead ends, and the ones that work each demand something specific.

Here is the whole landscape, including the parts that do not work.

The five routes, side by side

Now the detail.

1. WhatsApp Web or Desktop

The first thing most people try, and the source of most of the confusion. Linking a browser or the desktop app to your phone gives you your conversations on a big screen, which feels like it solves the problem.

It does not, for archiving purposes. Linked devices show a mirror of what is on your account, synced over the network. There is no way to point it at a backup file, no way to export everything, and no offline copy that survives you unlinking the device. It is a better keyboard for WhatsApp, not a reader for your history.

2. Export the chat and open the text file

Genuinely useful, and it works from any phone including an iPhone. Export a chat from inside WhatsApp, move the file to the computer, and open it.

The catch is what the export contains. WhatsApp includes only the most recent 10,000 messages if you attach media, or 40,000 without, with no warning when it truncates. And a .txt in a text editor is hard going for anything long: no bubbles, no dates that stand out, and every photo sitting in a separate pile of files named IMG-20240312-WA0007.jpg with nothing tying them to the messages they came from.

You can improve the reading experience without giving up the simplicity: dropping the ZIP into WaChat Web rebuilds the conversation with bubbles, dates, playable voice notes and search, entirely in the browser. It does not remove the export cap — nothing can, the messages are simply not in the file — but it makes what you have readable.

3. The encrypted backup plus your 64-digit key

This is the route that actually gets you everything, and it is Android only.

WhatsApp writes a local encrypted backup to the phone:

Android/media/com.whatsapp/WhatsApp/Databases/msgstore.db.crypt15

That file contains every message in every chat, with no cap, because it was built for restoring a phone rather than for sharing a conversation. It is encrypted with a key that only you hold — the 64-digit key from Settings → Chats → Chat backup → End-to-end encrypted backup.

What you need:

1. The key. If WhatsApp is showing you a passkey instead of digits, turn the encrypted backup off and on again and choose the 64-digit key option. A passkey lives in your phone's secure hardware and cannot be exported, so nothing outside WhatsApp can use it.
2. A fresh backup. Generating a key does not re-encrypt yesterday's file. Run Back up in WhatsApp afterwards, or the key and the file will not match.
3. The file on the computer — over a USB cable in file transfer mode, or via Quick Share. Or skip the computer entirely and open the browser on the phone itself, picking the file with the system file dialog.
4. The media folder, optionally. The backup holds messages and thumbnails; the actual photos and voice notes are in WhatsApp/Media next to it. Add that folder and attachments reattach to their messages.

In WaChat Web the decryption runs in a background worker in the browser using the WebCrypto API. The file is not uploaded, the key is not sent anywhere, and a wrong key is detected within the first second rather than after processing the whole file.

4. The same file, with command-line tools

There are open-source scripts that decrypt a crypt15 file given the same 64-digit key. They work. It is worth being clear about what you end up with.

The output is msgstore.db, a SQLite database. Open it in a database browser and you get tables — message, chat, jid, message_media — where a conversation is a join across several of them, senders are phone-number identifiers rather than names, timestamps are numbers, and media is a set of file paths pointing at a folder the database does not contain. Getting from there to something you would actually read means writing queries.

If you are comfortable with that, it is a perfectly good route and it keeps everything in your hands. If you were hoping to double-click a file and see your chats, it is not that.

5. Restore onto a second Android phone

Install WhatsApp on a spare phone, sign in with the same number, and restore from the backup during setup.

This works, and it gives you WhatsApp itself rather than a viewer. The cost is high: your number can only be active on one phone, so doing this signs WhatsApp out on your main phone, and the spare phone needs to be wiped first. It is a reasonable move if you are retiring a device anyway, and a bad one otherwise.

What does not work, no matter what you read

• Downloading the Google Drive backup. It lives in Drive's hidden app-data area. There is no download, only deletion. More on that here.
• Opening msgstore.db.crypt15 in a SQLite browser. It is ciphertext until it is decrypted. A database tool will just report a corrupt file.
• Reading .crypt14 or .crypt12 files. These predate end-to-end encrypted backup, and their key sits in WhatsApp's private app storage, which no other app can read without rooting the phone. The fix is to turn on encrypted backup with a 64-digit key and run a fresh backup, which produces a .crypt15.
• Reading a passkey-protected backup outside WhatsApp. The passkey cannot leave your device's secure hardware.
• Reading an iPhone's local backup. There is no equivalent accessible file on iOS. Export is the route there.

Practical notes for the working routes

Storage. Decrypting happens on your machine, so it needs room: roughly one and a half times the size of the backup file, plus space for a search index. Check you have it before you start on a nearly-full laptop.

Browsers. Chrome and Edge give the full experience including a proper folder picker for your media. Firefox and Safari 17 and later handle exports and single backup files but use folder upload instead. Android Chrome works with single files but cannot pick a folder. The full matrix is in supported browsers and storage.

Your key is a secret. No legitimate tool, service or support desk ever needs you to send it. Your backup file is useless to someone without the key, and the key is useless without the file — which is exactly why the two should never travel together.

Where to go from here

If you want one conversation and it is not enormous, export it and open the file — no key, no cable, five minutes. If you want your whole history on a computer and you are on Android, the encrypted backup with your 64-digit key is the only complete route, and it stays complete: every chat, every message, media reattached.

• Getting the key: getting your 64-digit encryption key.
• Getting the file across: transferring the backup to a computer.
• The whole sequence in one page: the import guide.