Convert CRYPT12 to TEXT

A .crypt12 backup must be decrypted before its messages can be read or archived as a plain .txt file. This is useful when a chat needs to be searched, edited, indexed, or opened without WhatsApp.

What the CRYPT12 format is

msgstore.db.crypt12 is an encrypted SQLite database used for local WhatsApp chat backups on Android. Dated variants such as msgstore-2020-01-01.1.db.crypt12 may also be present in the WhatsApp databases folder. Message records and metadata are stored in the database; photos, videos, documents, and voice notes are normally stored separately.

The file is encrypted with a key associated with the WhatsApp installation. A .crypt12 file alone is usually insufficient: the correct key, an intact backup, and compatible WhatsApp data are required. Access to the key may require the original device, root access, or a device-specific extraction method, especially on recent Android versions.

What the TXT format is

A .txt file contains unformatted character data and can be opened by Notepad, TextEdit, code editors, search tools, and document-import software. It is smaller and easier to index than a formatted chat export, but it cannot retain WhatsApp layouts, media previews, stickers, reactions, reply links, or other interactive features.

Use UTF-8 when opening or resaving the export so that emoji, accented names, and non-Latin alphabets remain intact. A normal WhatsApp text export includes dates, times, sender names, and message content, but its exact formatting varies by device and WhatsApp version.

How to convert CRYPT12 to TXT

Do not rename the extension. Renaming .crypt12 to .txt does not decrypt or convert the database, and ordinary document converters cannot read it.

Restore and export with WhatsApp

1. Make a read-only copy of the original .crypt12 file and work only with the copy.
2. On Android, place the copy in the WhatsApp databases directory. Depending on the Android release, this is commonly /Android/media/com.whatsapp/WhatsApp/Databases/ or the older /WhatsApp/Databases/ path. Preserve the original filename pattern.
3. Install WhatsApp on a compatible Android device, verify the phone number associated with the backup, and select Restore when the local backup is detected. A local .crypt12 backup is different from an encrypted Google Drive backup; a Drive backup may also require its associated Google account or backup password.
4. Open the required conversation and select More options → More → Export chat. Choose Without media for a compact text export, or Include media if attachments are needed.
5. Extract the resulting ZIP archive if necessary. WhatsApp normally supplies a chat.txt file. Open it as UTF-8 and save it under a descriptive name.

WhatsApp's export function is preferable when restoration works because it performs the decryption without handing the key or database to third-party software. Export limits can apply; large chats may be truncated, particularly when media is included.

Decrypt and export with desktop software

If WhatsApp cannot restore the backup, obtain the matching key from the original Android installation using a lawful, device-compatible method. Modern Android security may prevent key extraction without root access. The key and backup must match; a key from another installation normally will not decrypt the file.

Use a maintained local utility that explicitly supports crypt12, such as a current build of wa-crypt-tools, and verify its documentation before processing the file. Support for crypt14 or crypt15 does not automatically mean support for crypt12. After decryption, the output should be an SQLite database, commonly msgstore.db.

Open the decrypted database with an SQLite viewer or a compatible WhatsApp database viewer, select the required conversation, and export the records to CSV or TXT. If only CSV is available, convert it locally while selecting UTF-8 and preserving the timestamp, sender, and message columns. Database schemas differ between WhatsApp releases, so inspect the schema before using SQL:

Do not assume that a fixed query such as SELECT * FROM messages; will work: table names, columns, and message storage structures can change between releases. A viewer is usually safer for reconstructing readable conversations than exporting raw database rows.

Security and compatibility limits

There is no reputable online converter that can safely turn an encrypted WhatsApp .crypt12 file into readable TXT without the decryption key. Avoid uploading the backup, key, or decrypted database to a website; they may contain private messages, contacts, and media references. A local desktop workflow is the appropriate alternative to an online converter.

Decryption can fail because of a wrong key, a damaged or incomplete file, an altered filename, an incompatible backup version, or a database that was copied while incomplete. Keep the original unchanged and retain multiple working copies.

Messages deleted before the backup was created cannot normally be recovered from it. A TXT export does not embed attachments unless a separate media export is made, and third-party tools may omit or reconstruct differently reactions, quoted messages, disappearing messages, system events, and message formatting.