Understanding WhatsApp Export Files Explained

Most people who export a WhatsApp chat do so in a hurry - they need it as evidence, want to archive it before changing phones, or are handing it to a solicitor. What they receive is a .zip file, and what they find inside it is often confusing. A plain text file, a collection of cryptically named image and audio files, and no obvious way to read everything together. This guide explains exactly what a WhatsApp export contains, how the files are structured, what differs between iOS and Android exports, and what the limitations are if you intend to use the export in a legal context.

What Is a WhatsApp Export File?

When you trigger an export from within a WhatsApp conversation - by tapping the three-dot menu, selecting 'More', then 'Export chat' - WhatsApp bundles the conversation into a compressed archive. The result is a .zip file that you can share via email, cloud storage, or any standard file-sharing method. The zip file contains at minimum the text log of the conversation and, if you selected 'Include media', all the media attachments that are still stored on your device at the time of export. Once you have this file, it represents a complete snapshot of the conversation as it existed on that device at that moment.

Inside the .zip: What You Will Find

Extracting the zip file reveals a predictable set of contents. The central file is always named '_chat.txt' (on Android) or 'WhatsApp Chat with [Name].txt' (on iOS for individual chats). Alongside it, each media attachment that was present on the device appears as a separately named file. There is no folder structure inside the zip - all files sit at the root level. The total number of files depends entirely on how many media items the conversation contains and how many have already been deleted from the device or were never downloaded.

• _chat.txt - the complete text log of every message, in chronological order
• IMG-YYYYMMDD-WAnnnn.jpg - photographs sent or received in the conversation
• VID-YYYYMMDD-WAnnnn.mp4 - videos sent or received
• AUD-YYYYMMDD-WAnnnn.opus or .m4a - voice messages and audio files
• DOC-YYYYMMDD-WAnnnn.pdf (or other extension) - documents shared in the chat
• STK-YYYYMMDD-WAnnnn.webp - stickers

The _chat.txt Format: How Messages Are Recorded

The _chat.txt file records every message on a single line using a consistent pattern: a timestamp in square brackets, followed by a dash, followed by the sender's name (as it appears in your contacts or as the phone number if not saved), a colon, and the message body. The standard Android timestamp format is [DD/MM/YYYY, HH:MM:SS]. On iOS the separator and order may differ slightly depending on the device's regional date format settings. Understanding this structure is essential if you need to parse or convert the file.

• [14/03/2025, 09:42:07] Sarah Jones: Morning, can we talk about the contract?
• [14/03/2025, 09:44:31] You: Yes, give me ten minutes.
• [14/03/2025, 09:51:18] Sarah Jones: <attached: 00000023-IMG-20250314-WA0002.jpg>
• [14/03/2025, 10:02:45] You: \u200eMessages and calls are end-to-end encrypted. No one outside of this chat, not even WhatsApp, can read or listen to them.
• [14/03/2025, 10:15:00] Sarah Jones: This message was deleted.

Media File Naming Conventions

WhatsApp's naming convention for media files follows a predictable pattern that encodes the file type, the date, and a sequential number. The prefix identifies the media type: IMG for images, VID for videos, AUD for audio, DOC for documents, and STK for stickers. The date segment (YYYYMMDD) records when the file was sent or received. The four-digit sequence number (WA0001, WA0002, and so on) distinguishes files sent on the same day. This naming system is generated by WhatsApp itself and does not depend on the original filename that the sender used - a photograph taken on the sender's device as 'DSC_4821.jpg' will appear in your export as 'IMG-20250314-WA0003.jpg'.

What 'Media Omitted' Means in the Text Log

When you export a chat without media - either because you chose 'Without media' during export, or because certain files were no longer on your device - the _chat.txt file records a placeholder instead of a filename. The placeholder text is '<Media omitted>' on Android or '<attached: (file name)>' where the file is absent. This indicates that a media item existed in the conversation at that point but is not included in the export. For legal purposes, this is significant: the presence of '<Media omitted>' entries proves that media was exchanged but does not preserve the content of those items. Courts may note the gap and ask for an explanation.

System Messages in the Export

WhatsApp inserts system messages into the text log to record events that are not standard messages from a participant. These appear without a sender name or with WhatsApp's own attribution. Common system messages include the end-to-end encryption notice (inserted at the start of every conversation), notifications that a participant joined or left a group, group name changes, and the 'This message was deleted' marker that appears when a sender deletes a message after it has been delivered. The deleted message marker confirms that a message existed and was subsequently deleted - it does not reveal the original content.

iOS vs Android Export Differences

While the overall structure of a WhatsApp export is consistent across platforms, there are meaningful differences between iOS and Android exports that can cause confusion when converting or parsing the files. These differences are worth understanding before you attempt to use the export for any formal purpose.

• Timestamp format: Android defaults to [DD/MM/YYYY, HH:MM:SS], while iOS can produce [MM/DD/YYYY, HH:MM:SS] or [DD/MM/YYYY at HH:MM:SS] depending on the device locale
• Audio format: Android voice messages are saved as .opus files; iOS voice messages are saved as .m4a files
• File naming: the core naming convention is the same, but iOS may include the contact name in the zip filename itself
• System message wording: minor phrasing differences between iOS and Android versions of WhatsApp for the same event
• Emoji rendering: emoji are stored as Unicode code points in both, but some parser libraries render them differently depending on platform
• Very large exports: iOS exports may be split differently by the system share sheet; Android uses a consistent zip compression method

What Is Not in the Export

Understanding the limitations of a WhatsApp export is as important as understanding what it contains. Several categories of information that users might expect to find are simply not present in the export file, and this absence can be legally significant in proceedings where that information is contested.

• Deleted message content - the export records that a message was deleted, but not what it said
• Read receipts - the export does not record when or whether your messages were read by the recipient
• Message reactions - older WhatsApp versions and some export scenarios do not include emoji reactions to messages
• Edit history - when a sender edits a message, only the final version appears in the export; the original text is not preserved
• Forwarding metadata - the export does not indicate when a message was forwarded from another conversation
• Link preview thumbnails - web preview images generated by WhatsApp are not included as separate media files

Why the Raw .txt Is Difficult to Use in Legal Contexts

The _chat.txt file is a machine-readable log, not a court-ready document. It contains no page numbers, no way to cite a specific message by reference, no formatting that conveys the conversational flow, and no embedded media. If you submit the raw .txt to a solicitor, they face the task of manually formatting it into something usable - a time-consuming process that introduces risk. The file also provides no integrity verification: without a hash, there is no way to prove that the .txt has not been edited after the export. For any formal legal use, the raw text file must be processed into a structured, authenticated document.

The Role of a Converter Like WaChat to PDF

A converter takes the raw export zip - _chat.txt and all associated media files - and transforms it into a structured, readable PDF. This involves parsing the timestamp and sender format from the text log, matching each '<attached:>' reference to the corresponding media file in the zip, rendering the conversation in the original WhatsApp bubble layout, embedding images and audio references inline, and generating a cover page with export metadata. A legal-grade converter also computes a SHA-256 hash of the final PDF and applies Bates numbering to every page, producing a document that satisfies court authentication requirements. The result is an exhibit that accurately represents the original conversation and can be cited precisely in legal filings.

Group Chat Exports vs Individual Chat Exports

Group chat exports follow the same format as individual chat exports, with some additional elements. Each message in a group chat is attributed to a specific participant by name, so the _chat.txt includes a different name prefix on each line depending on who sent the message. System messages record when participants joined, left, were added by an admin, or were removed. The group name and any changes to it are also logged. For legal purposes, group chats present additional complexity: you must be able to identify each participant by name or phone number, and the export only includes messages from the period before any participant was removed.

Using Exported Data in Legal Proceedings

Authentication is the central challenge when using a WhatsApp export in court. You must be able to demonstrate that the export came from your device, that it was made at the time you claim, and that it has not been altered since. The most effective approach combines a witness statement from the device owner explaining the export process, a PDF generated from the original zip file (not from screenshots), and a SHA-256 hash that allows independent verification of the PDF's integrity. Courts in the UK, US, and Australia have all accepted WhatsApp exports as evidence when these requirements are met. The export process itself - built into WhatsApp and documented by Meta - provides additional credibility compared to screenshots.

Data Privacy Considerations

A WhatsApp export contains the private messages of every participant in the conversation, not just your own messages. Before sharing the export with anyone - a solicitor, a court, or a third party - you should consider your obligations under data protection law. In the UK, the Data Protection Act 2018 and the UK GDPR require that you handle other people's personal data carefully and do not disclose it further than is necessary for your legitimate purpose. If the export contains phone numbers, addresses, or other personal information about third parties who are not involved in your dispute, you may need to redact those details before disclosure. Using a tool with built-in PII redaction addresses this obligation automatically.