How to Export WhatsApp Chat History in 2026, and What the Export Leaves Out

The short answer

WhatsApp exports one chat at a time to a text file. Open the conversation, tap the contact name or the three dots, tap Export Chat, and pick whether to include media. The app has no option to select all chats and export a whole account in one go. Cloud backups on Google Drive and iCloud are restore files for a phone rather than readable documents. Clean records for legal review or a staff handover therefore mean running the manual export once per conversation.

Method 1: export a single chat from inside the app

The export tool sits inside the settings page of each conversation. The interface has no batch export option. An account with two hundred open conversations needs the steps below repeated 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 appears. 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.

The export produces a single .zip file when you include media, and a raw .txt file when you skip it.

Inside the text file, each line carries a timestamp, the sender name, and the message content. iOS timestamps look like [14/05/2025, 09:06:22] Maya Chen: Legal needs another week. Please move the launch to 12 June. The Android format differs slightly: 14/05/2025, 09:06 - Maya Chen: Legal needs another week. Please move the launch to 12 June.

Archiving a whole phone by hand means opening each thread, checking whether it holds business detail, running the export, and filing the result. Before you wipe a handset or pass it to a replacement hire, read the companion guide on moving a number to a new handset.

The message cap on a single export

WhatsApp truncates long exports. When a chat holds more messages than the export file can carry, the app drops the oldest ones.

WhatsApp does not publish the cap, and the export finishes without a dialog telling you it was applied. Read the first line of every file you generate and compare it against the thread it came from. Where the file starts later than the conversation does, the export truncated.

The truncation matters during an audit or a commercial dispute. You open the generated .txt file expecting five years of supplier correspondence, and a truncated file can begin mid-sentence part way through. The earlier messages, price agreements, and delivery confirmations are absent from the file. Those messages still sit inside the WhatsApp database on that phone. The built-in export refuses to write them to disk.

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

A nightly Google Drive or iCloud backup is not a company archive.

A mobile cloud backup is an encrypted restore package for rebuilding an app on a replacement handset. The files use proprietary chunked formats. You cannot open Google Drive in a browser and read a customer's messages. You cannot search the text, copy a quote out of a thread, or feed the data into an eDiscovery tool.

Reading anything out of a Google Drive or iCloud backup requires four things:

1. A physical phone or a configured mobile emulator.
2. The 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 with no account registered yet.

Restoring the backup overwrites the messages on the target phone. Two backups cannot be merged. If an employee spent six months on a temporary number, restoring their older backup removes those six months.

Google's own storage policy governs Android backups. A WhatsApp backup counts against the shared 15 GB quota on a personal Google account. An employee who fills their Drive with photos stops the nightly WhatsApp backup, and nobody is told.

WhatsApp's end-to-end encrypted backup needs a custom password or the 64-digit encryption key it generates. When the employee who set that key leaves without recording it in your password manager, the backup on iCloud or Google Drive becomes unreadable. Apple and Google cannot reset the key, and Meta cannot decrypt the file for you.

Method 3: the Business API and the history it does not hold

Companies that outgrow physical phones sign up for the WhatsApp Business API or the WhatsApp Cloud API through Meta. Operations teams then expect the connection to pull in the messages sitting on the office smartphone.

The Business API has no backfill.

Meta documents the Cloud API as a message gateway rather than an archive. It posts inbound messages to your server webhook as they arrive and posts delivery receipts as they occur. Registering a phone number on the Business API detaches that number from the standard mobile app, and the message history on the phone stays on that hardware.

Meta documents retries of a failed webhook delivery at increasing intervals for up to seven days. If your endpoint returns HTTP 500 through an outage and does not recover inside that window, the messages are gone from your downstream software. The API has no query endpoint for asking what you missed last Tuesday.

The WhatsApp integration page covers how structured archiving differs from gateway webhooks.

What you cannot get back

A standard export, or an extraction after the fact, loses specific metadata and message states.

Media, and where it becomes hard to use

An export with media included is difficult to navigate.

Voice notes export as raw .opus files. Standard Windows and macOS business software cannot play them without a third-party player such as VLC. Audio is also unsearchable. When Maya at Northstar confirms a new launch date in a thirty-second voice note, searching the exported folder for "12 June" returns nothing.

Images and documents lose their original filenames. WhatsApp renames incoming images to its own convention, producing files such as IMG-20250514-WA0002.jpg.

The .txt transcript refers to those files with inline markers such as image omitted or <attached: IMG-20250514-WA0002.jpg>. Moving the text file to another folder without the media alongside it breaks every reference. You are left with a transcript describing attachments you cannot open, and a separate pile of loose images with no sender and no reason attached to them.

A working procedure for a business

For offboarding a salesperson, preserving evidence for a commercial claim, or archiving an account, this procedure captures as much as WhatsApp's own tools allow.

1. Inventory the hardware. Collect the phone, confirm the screen lock PIN, and check that the SIM card is present and receiving SMS.
2. Disable auto-deletion. In Settings, open Privacy and check Default message timer. Turn it off. Open the important threads and confirm Disappearing Messages is off for each one.
3. Run the text-only export first. For each priority thread, export with Without Media selected. Save the file with a clear name: YYYYMMDD_ClientName_TextOnly.txt.
4. Run the media export second. Export the same thread again with Attach Media selected. Save as YYYYMMDD_ClientName_WithMedia.zip. This file holds the recent voice notes, contracts, and photos. Compare the first line of each file, because the two do not always reach the same point in the thread.
5. Pair and hash the files. Move both files into a client folder on company storage. Generate a SHA-256 hash of each file when the export relates to a dispute or a formal audit.
6. Log the extraction. Record the export date, the WhatsApp version, the phone OS build, and whether the SIM card is still active.

For teams running several accounts, the data export options and the plan tiers describe how central capture removes the checklist above.

Keeping the archive instead of exporting it

A manual export is a fallback for conversations nobody tracked. It needs physical access to the handset and one pass per conversation, and on its own it leaves you with split folders of Opus audio and transcripts that cannot be searched together.

CommunicationOS indexes conversations across 19 messaging networks from the moment an account connects. Voice notes are transcribed on the way in, so a search for "12 June" reaches the clip where Maya said it.

The export files described above are also an input. Upload the .txt or the .zip from a chat export and those messages join the same index, searchable beside everything that arrives after them. The truncation still applies to the file WhatsApp writes, so run the text-only export as well as the media one and upload both.