WhatsApp Chat Export: Complete Guide (iPhone, Android, ZIP, PDF, 2026)

What WhatsApp Export Chat actually does (and what it doesn't)

I see this confused constantly in support tickets, Reddit threads, and WhatsApp help forums. People assume "export" means backup. It does not. WhatsApp's Export Chat feature produces a snapshot — a text file of the conversation as it exists right now, wrapped in a ZIP archive. It is not a sync, not a live connection to WhatsApp's servers, and not a way to restore the chat into a different WhatsApp account.

What it does: it reads your local chat history on the device, writes every message line-by-line into a plain text file called _chat.txt, and packages that file (plus any attached media, if you chose Including Media) into a ZIP. The process takes seconds for short chats and a couple of minutes for very long ones.

What it doesn't do: it does not export calls. It does not export disappearing messages that have already vanished. It does not give you chat history from a device you no longer own. And — this is the part that trips people up — it does not export all messages if your chat has more than 40,000. I explain that ceiling in detail in its own section below.

The output file is a standard ZIP archive. You can open it with any file manager, any decompression app, or any browser that handles ZIP files. The contents are plain text and media files — nothing proprietary, nothing encrypted.

Here is the practical upshot: if you want a portable, human-readable record of a WhatsApp conversation, the Export Chat menu is your starting point. What you do with the ZIP after that depends on what you actually need — a PDF, a spreadsheet, a backup, or just a local archive.

Without Media vs Including Media — when each one is the right call

WhatsApp offers two export modes. The choice you make here affects file size, export speed, and what you can do with the result.

Without Media exports _chat.txt only. Every message appears in plain text, with photo and video references shown as <Media omitted> placeholders. Voice notes, stickers, and documents are also replaced by placeholders. The resulting ZIP is tiny — usually under 1 MB even for thousands of messages. It exports quickly, emails easily, and uploads to any converter in seconds.

Including Media bundles _chat.txt with all attached files: images as .jpg or .webp, voice notes as .opus or .m4a, documents as their original format. For a media-heavy chat, this ZIP can easily be 100 MB or more. WhatsApp also applies a quiet constraint: media is only included for roughly the most-recent 10,000 messages. Messages beyond that cutoff appear as <Media omitted> in _chat.txt even though you chose Including Media. WhatsApp itself does not surface this limit in any dialog or warning — you only discover it if you check the dates of your media files against the full chat history.

Which should you choose? I use Without Media as my default when the goal is documentation, archiving, or legal evidence. The text record is what matters in those cases, and the smaller file is faster to handle. I switch to Including Media when photos and voice notes are part of what needs to be preserved — a family chat where images have sentimental value, a business conversation where a shared document is relevant to a dispute.

One practical note: if you are converting to PDF using ChatToPDF, Including Media means images appear inline in the PDF output rather than as <Media omitted> placeholders. The $14 Standard per chat conversion includes embedded photos. Voice notes are transcribed on the $29 Premium per chat tier and above — see my WhatsApp audio transcription guide for detail on how the voice pipeline handles different languages and audio quality.

The 40,000-message limit that nobody warns you about

Here's the part nobody tells you: WhatsApp caps every export at 40,000 messages. It does not warn you. It does not show a truncation notice. It just exports the most-recent 40,000 messages and stops. If your chat has 60,000 messages spanning five years, the exported _chat.txt covers only the most-recent 40,000. The older 20,000 are not in the file.

How do you know if you hit the ceiling? Open the exported _chat.txt and check the earliest timestamp. If it is more recent than you expect — if a chat you know started in 2019 only shows messages from 2022 — you hit the limit.

The bad news is that there is no simple way to export the older slice. WhatsApp's export function always takes the most-recent N messages up to 40,000. You cannot set a date range. You cannot say "give me messages from 2019 to 2020." The only clean workaround is to use Android tools like Android Backup Extractor to read the WhatsApp database directly — a process that requires root access or a full local backup, and is outside the scope of what most people want to attempt.

For most personal use cases — a chat you want to archive before switching phones, a conversation you want to share with a lawyer — 40,000 messages is more than enough. A 40,000-message chat covers roughly three to four years of moderate daily messaging. Only very active group chats or very long-running individual conversations bump into this ceiling.

If your chat exceeds 40,000 messages and you need the full history, I recommend exporting as early and as often as possible going forward, so the most-recent export always overlaps with your previous one. That is not a perfect solution, but it is the practical one given how WhatsApp's export works.

Inside the ZIP — what's in _chat.txt and how it's formatted

Unzip a WhatsApp export and you find two things: the _chat.txt file and, if you chose Including Media, a folder of attached files.

The _chat.txt file is plain UTF-8 text. Each message is one line. The format looks like this:

[2024-03-15, 14:32:18] John Doe: Hello there
[2024-03-15, 14:33:02] Jane Smith: Hey! How are you?
[2024-03-15, 14:33:45] John Doe: IMG-20240315-WA0001.jpg (file attached)

The brackets, the date format, the separator between date and time — all of these vary by locale. US-locale exports use M/D/YY, H:MM AM/PM format. ISO-locale exports use YYYY-MM-DD, HH:MM:SS. European exports often use DD/MM/YYYY, HH:MM. A parser that handles only one date format silently misreads every message in a differently-formatted file, which is how you end up with a PDF showing incorrect timestamps or merged messages.

Media file names follow WhatsApp's own naming convention: IMG-YYYYMMDD-WA####.jpg for images, PTT-YYYYMMDD-WA####.opus for voice notes (PTT stands for Push-to-Talk), VID-YYYYMMDD-WA####.mp4 for videos, and DOC-YYYYMMDD-WA####.pdf for documents. Each referenced file appears in both the _chat.txt line and as an actual file in the ZIP. If a media file is missing from the ZIP — because you chose Without Media, or because it fell outside the media window — the _chat.txt line shows <Media omitted> in place of the file reference.

System messages — events like "John added Jane to the group" or "The encryption key for this chat changed" — appear as lines with no sender name. They look like this:

[2024-03-15, 09:00:01] Messages and calls are end-to-end encrypted. No one outside of this chat, not even WhatsApp, can read or listen to them. Tap to learn more.

A well-built parser detects these and renders them differently from regular messages. ChatToPDF handles them as formatted system notices rather than treating them as messages from an unnamed sender.

Group chats: the export quirks (joined messages, anonymised contacts, system messages)

Group chat exports follow the same format as individual chats, but with a few quirks that consistently catch people off guard.

Anonymised contacts. If a participant has not saved their name in your contacts — or if their number is not in your phonebook — they appear as a phone number instead of a name. A line like [2024-03-15, 10:22:04] +27 82 555 1234: Hello everyone is normal in a group chat export with participants you do not have saved. The PDF output from ChatToPDF preserves this number as the sender attribution; it cannot invent a name that is not in the file.

System messages. Group chats generate more system messages than individual ones: additions, removals, subject changes, admin assignments. These clutter the export if left unhandled. In _chat.txt they are distinguishable from regular messages because they have no sender name — the line starts with the timestamp bracket and goes directly to the event text. Parsers that do not handle this end up attributing system events to the previous sender, producing confusing output.

Join-date cutoff. This is the one I see cause the most confusion. Your export only shows messages from the date you joined the group. If you joined a group in March 2023 and the group started in January 2020, your exported _chat.txt starts at March 2023. The history before your join date was never on your device and cannot be exported by you. If you need the full history, you need the export from someone who has been in the group since the beginning.

Forwarded messages. Forwarded messages appear in _chat.txt with a ‎Forwarded tag prepended to the content, sometimes followed by the original content. This is a special Unicode character (the left-to-right mark, U+200E), not a regular space. Parsers that do not strip it correctly render forwarded messages with a stray character artifact at the start.

For a full walk-through of how the parser handles these cases — and how they affect the PDF output — see my WhatsApp to PDF guide. If you are exporting a group chat that originally lived on Android and now need it on iPhone, my Android to iPhone transfer guide covers the full handoff.

Exporting on Android (every Android skin has a different menu)

The core path is the same across all Android versions: open the chat, find a menu with "Export Chat," tap it. The specific route to get there changes depending on your Android skin and WhatsApp version.

Stock Android and Pixel: Open the chat. Tap the three-dot menu icon (⋮) in the top-right corner. Tap More. Tap Export Chat. WhatsApp presents the Without Media / Including Media choice, then a share sheet. Tap Save to Files (or any cloud option you prefer).

Samsung One UI: The three-dot menu is present, but the label may say "Settings" on some One UI versions rather than going straight to "More." If you see Settings, tap it and look for Export Chat inside. Alternatively, long-press the chat title in the chat list — Samsung sometimes exposes Export Chat in the context menu at that level.

Xiaomi MIUI / HyperOS: The three-dot menu is present. The path is ⋮ → More → Export Chat. Some MIUI versions reorder the "More" submenu items; scroll down if Export Chat is not visible immediately.

OnePlus OxygenOS: Same as stock Android. ⋮ → More → Export Chat. No known deviations from the standard path as of OxygenOS 14.

Motorola and Nokia (close to stock): Follow the stock Android path. These manufacturers make minimal changes to the Android shell.

After tapping Export Chat and choosing your media option, WhatsApp shows a share sheet. The options visible depend on what apps you have installed. For moving the file off your Android without a cable, the most reliable options are:

• Save to Files (if you have a file manager installed) — saves to Internal storage/Downloads/ or equivalent
• Drive — saves to your Google Drive, where you can download it from any device
• Email to yourself — works, but be aware that large ZIPs may be blocked by email attachment limits

The exported file name follows the pattern WhatsApp Chat - [Contact Name].zip or WhatsApp Chat with [Contact Name].zip depending on your WhatsApp version.

Exporting on iPhone

On iPhone the menu path is slightly different from Android. You navigate to it through the contact sheet rather than a three-dot overflow menu.

Open the chat you want to export. Tap the contact name or group name at the very top of the screen — this opens the contact or group info sheet. Scroll down past participants, media gallery, links, and other settings. Near the bottom you will see Export Chat. Tap it.

WhatsApp for iOS then shows the same two choices: Without Media or Including Media. After you select one, WhatsApp prepares the ZIP and hands you an iOS share sheet. The share sheet options you see depend on your installed apps and iCloud configuration.

For keeping the file on your iPhone: tap Save to Files and choose a location you will remember. "On My iPhone → Downloads" is a good default. Avoid the Quick Look preview path — if you tap the ZIP attachment in Files without saving it first, you may see the contents but the file is only in a temporary location that the browser's file picker cannot reach.

For moving the ZIP to a Mac: AirDrop is the fastest option. Tap the share icon, tap AirDrop, select your Mac. The ZIP appears in your Mac's Downloads folder. Alternatively, saving to iCloud Drive syncs it to your Mac automatically if iCloud Drive is enabled.

For transferring to an Android or Windows device: save to iCloud Drive or email it to yourself. iCloud.com is accessible from any browser, so you can download from there.

One thing worth knowing about iPhone exports specifically: WhatsApp on iOS tends to include more complete media in the Including Media export than WhatsApp on Android, at least in my testing. The Android media window seems to cap earlier than iOS does on equivalent chats. If you have the option to export from either device, prefer iPhone for Including Media exports when full photo coverage matters.

Exporting to your computer — the three honest options

There is a persistent myth that WhatsApp Web or WhatsApp Desktop lets you export chats directly from your computer. It does not. WhatsApp Web is a mirror of your phone's connection — it displays your chats on a computer screen, but the data lives on your phone.

Here are the three options that actually work.

Option 1: Export on your phone, transfer the ZIP. This is the most reliable path. Export the chat on your phone using the steps above (Android or iPhone), then move the ZIP to your computer. On iPhone, AirDrop or iCloud Drive. On Android, USB cable drag-and-drop, Google Drive, or email. This approach works on every device, every OS version, and does not depend on any third-party software.

Option 2: WhatsApp Desktop's limited download feature. In 2024, WhatsApp added a chat history download option to WhatsApp Desktop on Windows and Mac for some accounts. It is not available to everyone — it appears to be a staged rollout — and it produces the same ZIP format as the phone export. If you see a "Download chat history" option in WhatsApp Desktop (typically under the three-dot menu in a chat), it works the same way. If you do not see it, you are not in the rollout and Option 1 is your path.

Option 3: Third-party backup tools. Tools like Backup Trans, iMazing (for iPhone), or Android Backup Extractor can access your WhatsApp database directly and offer more export flexibility — date-range filtering, full history regardless of the 40,000-message limit, and sometimes more media. These tools require a desktop app, a USB connection, and in some cases root access or a local encrypted backup. They are genuinely useful for power users who need full history exports. For everyone else, Option 1 is faster.

WhatsApp's own FAQ page covers the export feature in general terms, though it understates the 40,000-message ceiling and does not document the media-window limit on Including Media exports.

Excel and CSV exports (and why most people actually want a PDF)

WhatsApp does not natively export to Excel or CSV. When people ask for this, what they actually want is _chat.txt transformed into structured rows — sender in one column, timestamp in another, message text in a third. That transformation requires a parser. ChatToPDF supports both PDF and CSV output from the same ZIP upload.

Why you might want CSV/Excel: If your goal is analysis — counting messages per sender, calculating response times, doing sentiment scoring, building a frequency chart — structured rows are the right format. You can import CSV into Excel, Google Sheets, or any data tool. You can sort by sender, filter by date range, run formulas. The structure that makes PDFs readable (chronological flow, visual bubbles, timestamps as prose) makes them poor inputs for analysis.

Why most people actually want PDF: The PDF output from ChatToPDF reads like a document. Every message has a sender name, a timestamp, and the message content in order. You can scroll through it the way you would read a printed conversation. You can share it with someone who has never heard of WhatsApp and they will understand it immediately. You can attach it to an email, upload it to a legal case file, or print it. PDFs are universally readable; CSV files require a spreadsheet application to make sense.

I built ChatToPDF with PDF as the primary output because that is what the overwhelming majority of people want when they say "I need to save this conversation." If you need CSV, it is available — but I would ask yourself first: what are you actually going to do with that spreadsheet? If the answer is "read through the conversation" or "share it," you want PDF. If the answer is "count how many times this person said X" or "build a chart of message frequency by hour," you want CSV.

For the specific case of exporting WhatsApp to a format compatible with Excel, the CSV download button on ChatToPDF produces a three-column file: timestamp, sender, message. Import that into Excel and use Data → Text to Columns if any values contain commas.

Privacy-safe export workflow (what NOT to upload anywhere)

An exported WhatsApp chat contains private conversation data — often including names, phone numbers, locations, photos, and the full text of personal communications. The moment you upload that ZIP to a third-party service, you are trusting that service with all of it.

Here is what I look for before I upload any chat export anywhere, and what I recommend you check.

Do not upload to: Free unnamed converters with no privacy policy, services whose terms say "we may use uploaded content to improve our services" (a common clause that means your conversation data may feed a training set), or any tool hosted in a jurisdiction with weak data protection enforcement.

Before uploading anywhere, check: Does the service delete your file after conversion? Is there a stated retention period? Does the privacy policy explicitly say your content is not used for model training? Does the service process files on the server, or in your browser? Server-side processing is not inherently bad, but it means your file leaves your device.

ChatToPDF's approach: the ZIP is processed on the server, the resulting PDF is stored temporarily for download, and both are deleted after the delivery window closes. No training. No storage beyond conversion. The privacy policy is readable and specific on this point.

On the device side: after you have downloaded your converted PDF, you can safely delete the original ZIP from your phone and from any cloud location where you staged it. Keep the PDF; it is the durable version. The ZIP can be regenerated from WhatsApp at any time (up to the 40,000-message limit and however long WhatsApp retains the local chat).

Special consideration for group chats: you do not own the content in a group chat — each participant owns their own messages. Exporting a group chat and uploading it to a service means you are uploading other people's messages without their knowledge. For personal archiving this is generally fine. For business purposes, or for any situation where those other participants might have objections, it is worth a moment's thought.

For more on privacy-conscious handling of WhatsApp data, WhatsApp's privacy FAQ covers their data handling practices in reasonable detail.

Pricing and tier guidance

ChatToPDF uses per-conversion pricing. You pay for the specific chat you are converting today. There is no recurring fee attached to your account — each conversion stands alone.

Here is how I think about which tier fits which export scenario.

$7 Basic per chat conversion handles text-only exports up to 5,000 messages. Right for short conversations, quick records, and any chat where photos do not need to appear in the output. If you chose Without Media during the WhatsApp export and the chat is a few hundred messages, this is the tier you want.

$14 Standard per chat conversion handles exports up to 25,000 messages and includes embedded photos. This is the right tier for the majority of individual chat exports — it covers several years of normal messaging frequency and supports Including Media exports with inline images in the PDF.

$29 Premium per chat conversion removes the message-count ceiling and supports full media bundles. Voice notes appear as placeholder references in the PDF — transcription is not included at this tier. If your export has no voice notes (or you do not need them transcribed), this is the tier for very long chats.

$49 Premium+Voice per chat conversion adds Deepgram Nova-3 voice-note transcription with automatic language detection across 17 high-accuracy languages and 30+ more at a wider accuracy range. Up to 8 hours of audio per chat is included. If you have voice notes (.opus files) in your export and you want them transcribed inline in the PDF, this is the entry tier.

$99 Power User per chat conversion is for large exports: multi-year group chats, legal evidence compilations, business communication archives. No message ceiling, full media, Deepgram Nova-3 transcription with no audio cap, and priority queue processing. For HR, customer-service, and contract-trail archiving specifically, the WhatsApp Business PDF guide walks through the team workflows and retention patterns. For evidence preparation specifically, see the WhatsApp evidence court PDF guide for hash chains and admissibility considerations.

For a typical individual chat export — one conversation, a few thousand messages, maybe some photos — the $14 Standard per chat conversion covers almost every case. For group chats that have been active for years, step up to $29 Premium per chat or $99 Power User per chat depending on whether voice notes are present and how long the history runs.

If you are converting multiple individual chats — say, five conversations from a business dispute — each is a separate conversion at its applicable tier. There is no account-level access that bundles them.

Related guides — exporting WhatsApp chats deeper

I split the export-mechanics topic into 15 focused guides, each one solving a specific question. The vocabulary you searched for tells me what you actually need; pick the entry that matches the question in your head.

Start here if you are new to it:

• Export from WhatsApp — start here — entry-level overview that routes you to the right deeper guide

What "export chat" actually is:

• What "export chat" is at a feature level — what the menu produces, what it isn't, when to use it
• What it does for your data and privacy — what happens to the chat, the file, and the other person
• What "export chat" means as a phrase — why WhatsApp uses "export" rather than "download"
• The mechanics — menu, ZIP, what's inside — the menu, the ZIP, what's really inside

Step-by-step workflows:

• Export a single chat — one conversation focus — for when you only want to save one specific chat
• Export WhatsApp chat to PDF — the real path — ZIP to PDF in 30 seconds, with photos
• Download chat history — what users mean — three intents, three different answers
• Download chat history — step-by-step — three walkthroughs across iOS, Android, and Web
• WhatsApp Web export — yes, it exists — the desktop flow, hidden in the three-dot menu

Vocabulary variants:

• "Messages" vocabulary variant — when you only want some messages, not the whole chat
• "Conversation" vocabulary variant — when you think in conversations, not chats

Contacts (not chats):

• General contacts — four workarounds for the missing contacts-export feature
• Group contacts specifically — four workarounds for pulling a participant list

Analytical framing:

• Extract WhatsApp chat data — what fields you can pull, what to do with them

FAQ

Paul · ChatToPDF

I'm Paul. I built ChatToPDF after watching a friend try to print a 4-year-old WhatsApp chat across forty-something one-page PDFs. I write here about exporting WhatsApp chats, converting them to PDF, transcribing voice notes, and the messy edge cases nobody else writes about (40,000-message export limits, broken emojis, RTL Arabic, Samsung Secure Folder).

Published 2026-05-15