How to Export WhatsApp Chat History in 2026: Every Method, and What You Lose

The short answer

WhatsApp lets you export one chat at a time to a text file. You open the conversation, tap the contact name or the three dots, tap Export Chat, and pick whether to include media. You cannot select all chats and export your entire account at once. Cloud backups on Google Drive or iCloud are restore files for a phone, not readable documents. If you need clean records for legal review or a staff handover, you must run the manual export for each customer conversation.

Method 1: export a single chat from inside the app

WhatsApp puts its export tool inside the settings page of each individual conversation. There is no batch export option anywhere in the interface. If an account has two hundred open conversations, someone has to repeat the steps two hundred times.

Exporting on iPhone

1. Open WhatsApp on the iPhone and tap the chat you need to save.
2. Tap the contact name or the group subject at the top of the screen to open Chat Info.
3. Scroll to the bottom of the list and tap Export Chat.
4. Choose Attach Media or Without Media.
5. The iOS share sheet will appear on screen. Tap Save to Files, AirDrop the zip file to a Mac, or send it to an internal email address.

Exporting on Android

1. Open WhatsApp on the Android device and enter the target conversation.
2. Tap the three vertical dots in the top right corner.
3. Tap More, then tap Export chat.
4. Select Without media or Include media on the prompt.
5. Select a destination from the Android system share sheet, such as Google Drive, Gmail, or local storage.

When you finish the export, WhatsApp hands you a single .zip file if you selected media, or a raw .txt file if you skipped media.

Inside the text file, WhatsApp formats every line with a timestamp, the sender name, and the message content. On iOS, timestamps look like [14/03/2024, 09:15:22] Alice: Morning, sending the invoice now. On Android, the default format is slightly different: 14/03/2024, 09:15 - Alice: Morning, sending the invoice now.

Because there is no global export button, archiving an entire phone by hand requires opening every thread, checking if it holds business details, running the export, and saving the resulting file into a structured folder. If you are preparing to wipe a handset or hand it to a replacement hire, take a look at our companion guide on moving a number to a new handset before you erase the local database.

The message ceiling nobody tells you about

WhatsApp applies a hard limit to the number of messages included in a single export file. When a chat exceeds this limit, the app silently cuts off the oldest messages. You will not see an error message or a warning dialog telling you that the export is incomplete.

If you choose the Without Media option, the export file cuts off at 40,000 messages.

If you choose the Attach Media option, the ceiling drops hard. Widely reported figures put it near 10,000 messages. The real number moves with how heavy the attachments are, because WhatsApp is trying to keep the resulting zip small enough to hand to a share sheet.

This design causes serious problems during operational audits or legal disputes. You might open the generated .txt file expecting five years of negotiations with a supplier, only to find the file begins mid-sentence in November 2024. The first three years of messages, price agreements, and delivery confirmations are simply absent from the file. The data still sits inside the WhatsApp SQLite database on that specific phone, but the built-in export mechanism refuses to write it to disk.

Method 2: Google Drive and iCloud backups, and why they are not an export

Many business owners believe their nightly Google Drive or iCloud backup acts as a company archive. It does not.

A mobile cloud backup is an encrypted restore package designed to rebuild an app state on a replacement handset. The files are stored in proprietary, chunked formats. You cannot open Google Drive in a web browser and read messages sent by a customer. You cannot search the text, copy an individual quote out of a thread, or pipe the data into an eDiscovery tool.

To read anything from a Google Drive or iCloud backup, you must have:

1. A physical phone or a configured mobile emulator.
2. The exact SIM card or eSIM matching the original phone number to receive a verification SMS.
3. The Apple ID or Google account that created the backup.
4. A fresh installation of WhatsApp that has not yet registered an account.

Restoring that backup overwrites whatever messages currently exist on the target phone. You cannot merge two backups together. If an employee spent six months using a temporary phone number, restoring their old backup wipes those six months of newer conversations.

Google account storage policies also affect these backups. Since 2024, WhatsApp backups on Android count against the shared 15 GB quota on personal Google accounts. They used to sit outside it. If an employee fills their Drive with photos, the nightly WhatsApp backup stops running and nobody is told.

If you activate end-to-end encrypted backups, WhatsApp requires a custom password or a 64-digit encryption key. If the employee who set that key leaves the company without recording it in your password manager, the entire backup blob on iCloud or Google Drive becomes useless noise. Apple and Google cannot reset this key, and Meta cannot decrypt the file for you.

Method 3: the Business API, and the backfill that does not exist

When companies outgrow physical phones, they often sign up for the WhatsApp Business API or the WhatsApp Cloud API through Meta. Operations teams frequently assume that connecting their business phone number to an API platform will pull in the historical messages sitting on the office smartphone.

The WhatsApp Business API has zero backfill capability.

Meta's Cloud API functions as a message gateway, not an archive. It sends inbound messages to your server webhook in real time. It sends delivery receipts as they occur. When you register a phone number on the Business API, Meta severs the number from the standard mobile app interface. The message history that lived on the phone stays trapped on that local hardware.

If your webhook server goes down for maintenance, or if an endpoint throws HTTP 500 errors during an outage, Meta retries delivery with a backoff for up to seven days. If your endpoint does not recover within that retry window, those messages disappear permanently from your downstream software. The API does not provide a query endpoint to ask for missed messages from last Tuesday.

You can inspect the technical capabilities of modern message ingest on our WhatsApp integration page to see how structured archiving differs from standard gateway webhooks.

What you cannot get back

When you run a standard WhatsApp export or extract data after the fact, specific metadata and message states vanish.

Media: the part that breaks

If you run an export with media included, you will quickly find that the output is difficult to navigate.

Voice notes export as raw .opus audio files. Standard Windows and macOS business utilities cannot play these files without third-party audio software like VLC. More importantly, audio files are unsearchable. If a client confirmed a 50,000 euro order via a thirty-second voice note, searching for the word "approved" inside the exported folder returns zero matches.

Images and documents lose their original contextual filenames. WhatsApp renames incoming images according to its internal convention, producing files like IMG-20240314-WA0002.jpg.

The generated .txt transcript references these files with inline markers such as image omitted or <attached: IMG-20240314-WA0002.jpg>. If someone moves the text file to a different folder without the accompanying media files, the links break immediately. You are left with a text file describing attachments you cannot view, and a separate pile of thousands of loose images with no visible indication of who sent them or why.

A working procedure for a business

If an operations manager needs to offboard a salesperson, preserve evidence for a commercial claim, or archive an account, this process captures the maximum possible data within WhatsApp's technical constraints.

1. Inventory the hardware. Collect the physical phone, confirm the screen lock PIN, and verify that the SIM card is present and receiving SMS messages.
2. Disable auto-deletion. Open WhatsApp, go to Privacy in Settings, and check Default message timer. Turn it off. Open key customer threads and confirm that Disappearing Messages is toggled off for each individual thread.
3. Run the text-only export first. For each high-priority client thread, follow the export steps and select Without Media. Save this .txt file with a clear name: YYYYMMDD_ClientName_TextOnly.txt. This step reaches back up to 40,000 messages, capturing the deepest possible text history.
4. Run the media export second. Open the same thread, run the export again, and select Attach Media. Save this .zip archive as YYYYMMDD_ClientName_WithMedia.zip. This ensures you have the voice notes, contracts, and photos from recent months, even though the text history in this file will be truncated earlier than the text-only version.
5. Pair and hash the files. Move both files into a dedicated client folder on your company storage. Generate a SHA-256 hash of the files if the export relates to a legal dispute or formal compliance audit.
6. Log the extraction date and SIM status. Record the date of export, the WhatsApp application version, the phone OS build, and whether the SIM card remains active.

When managing multiple accounts across growing teams, review our data export options and our account pricing tiers to understand how centralised capture avoids manual extraction checklists entirely.

Keeping the archive instead of exporting it

Manual file exports are an emergency fallback for conversations that were never tracked systematically. They require physical access to handsets, take hours of repetitive tapping, and leave you with split folders of Opus audio and truncated text files that cannot be searched together.

CommunicationOS takes the other route. It indexes every conversation across WhatsApp and eighteen other networks from the moment an account connects, and a connected personal number brings the history already sitting on the handset along with it. Voice notes are transcribed on the way in, so searching for the word "approved" finds the thirty second clip where somebody said it.