Convert CRYPT12 to TXT

People convert an older WhatsApp backup to TXT when they need searchable, editable chat text that can be shared or archived without a database viewer. The process requires decrypting the backup first; changing the filename or opening it in a text editor does not convert it.

What the CRYPT12 format is

.crypt12 is an encrypted local WhatsApp database format used mainly by older Android releases. Files commonly have names such as msgstore.db.crypt12 or msgstore-YYYY-MM-DD.1.db.crypt12 and were stored in the phone's WhatsApp/Databases folder.

The encrypted database contains messages and metadata in an SQLite-based structure, but it cannot be read by a normal SQLite viewer, file manager, or text editor. Decryption requires the WhatsApp key belonging to the installation that created that specific backup. On older rooted Android devices, the key was commonly found at /data/data/com.whatsapp/files/key; modern Android security and newer WhatsApp versions can make direct extraction unavailable.

CRYPT12 is not a universal archive format. Recent local backups may use .crypt14, .crypt15, or another version, and WhatsApp's end-to-end encrypted cloud-backup password or 64-digit recovery key is different from the local database key.

What the TXT format is

.txt is plain text without HTML styling, database structure, images, or other presentation data. A chat exported as UTF-8 TXT can be searched in ordinary editors, processed by scripts, copied into another system, and retained as a relatively small archive.

A typical export contains dated lines such as 12/08/2020, 14:32 - Name: Message. It normally cannot preserve message formatting, reactions, reply links, contact photos, or the original WhatsApp database fields. Attachments are usually represented by filenames or placeholders; the media files themselves are not embedded in the text.

How to convert the backup

1. Make a working copy of the CRYPT12 file and keep the original unchanged. Preserve its complete filename and extension.
2. Obtain the matching WhatsApp key through an authorized extraction from the original Android installation or an existing, legitimate backup of that installation. A key from another phone, WhatsApp account, or database will not work. Do not bypass a device lock or access data that is not yours.
3. Use WhatsApp Viewer, a third-party desktop utility that can decrypt and inspect several WhatsApp database versions. Download it only from its identifiable project repository or another verifiable source; it is not an official WhatsApp product, and support for newer formats may be incomplete.
4. In WhatsApp Viewer, choose the decryption command, which may appear as File → Decrypt or Decrypt .crypt12. Select the copied database, provide the key, and save the decrypted file as msgstore.db.
5. Open the decrypted database in WhatsApp Viewer, select the required conversation, and use its export command. Choose TXT or plain text if the installed version provides that option. Some releases export HTML instead; open that HTML locally and convert it to text with an offline HTML-to-text utility, or copy the rendered conversation into a plain-text editor.
6. Open the result in Notepad, Notepad++, or Visual Studio Code and save it as UTF-8. Avoid ANSI encoding, which can corrupt non-Latin names, emoji, and other Unicode characters.

If WhatsApp can still restore the local backup, its built-in Chat info → Export chat function is usually safer than manually querying the database. Restore the backup on a test device or after preserving the current chats, then export the selected conversation and choose whether to include media. This produces a TXT file and, when media is included, separate attachment files; it does not export the entire database as one text document.

Fallback for database tools

If WhatsApp Viewer decrypts the file but cannot export the conversation, DB Browser for SQLite can inspect the resulting msgstore.db. WhatsApp schemas and column names vary by release, so identify the message and chat tables before exporting rows. A raw table export is not necessarily a readable conversation: it may contain internal IDs, timestamps, encoded media references, and separate sender fields that require sorting and formatting with a script.

Do not upload the CRYPT12 file, decrypted database, or WhatsApp key to a web converter. No reputable online service can turn an arbitrary CRYPT12 file into TXT without the matching key, and sending the files to a third party exposes private conversations. Online file converters are suitable only for non-sensitive, already-decrypted text or HTML, not for the encrypted WhatsApp backup itself. Tools marketed as automatic CRYPT12 converters, including unverified “WhatCrypt” downloads or websites, should not be treated as official WhatsApp software.

Quality and compatibility limits

A successful decryption does not guarantee a complete chat. The backup contains only messages present when it was created; deleted messages, newer messages, damaged database pages, or unavailable contact records may be missing. Group participants can appear as phone numbers rather than names.

TXT removes formatting and database metadata, and its timestamp layout may depend on the exporter and locale. Long messages, line breaks, emoji, right-to-left text, and unusual characters should be checked after export. Media, reactions, quoted-message relationships, and attachment content generally require the original WhatsApp export or separate media files.