DEV Community: ChatToPDF

Why WhatsApp Export Parsers Break: 14 Formats Tested

ChatToPDF — Tue, 14 Jul 2026 08:04:27 +0000

Disclosure: I am the founder of ChatToPDF and maintain the open-source parser used in the linked benchmark. Every published fixture is synthetic; no customer conversation appears in the test data.

A WhatsApp export parser usually breaks because the timestamp at the start of each message is not one universal format. Brackets, separators, date order, seconds, AM/PM position, numeral script and invisible direction marks can all change with the phone and locale. A parser that recognizes only DD/MM/YY, HH:MM - Name: text may appear correct in development and then merge an entire German, US, Dutch or Arabic export into one message.

TL;DR: Do not build a WhatsApp export parser around one regular expression. Normalize Unicode digits and spacing first, try an ordered set of explicit timestamp families, keep ambiguous numeric dates visible as a limitation, and parse the file as a stateful stream so multiline messages are joined instead of discarded. Our public 2026.07 benchmark contains 24 synthetic cases: 14 timestamp layouts, four numeral-normalization cases and six behavior cases. The published Node.js and Python packages passed those 24 cases. That result describes this fixture set only; it is not a claim that every WhatsApp export ever produced is supported.

Why one WhatsApp timestamp regex fails

The first parser I wrote had the usual shape: split the file into lines, run one regex against each line, and treat anything that matched as a new message. It worked against the sample in front of me. That was the problem. The sample came from one phone with one regional setting.

This pattern is a reasonable first experiment for an Android export using a slash date and an English AM/PM marker:

const header = /^(\d{1,2}\/\d{1,2}\/\d{2,4}),\s+(\d{1,2}:\d{2})\s+(AM|PM)\s+-\s+([^:]+):\s+(.*)$/i;

It matches:

3/15/24, 2:30 PM - Researcher: Hello

It does not match any of these valid shapes from the public fixture set:

[2024/07/09, 08:01:49] Researcher: Morning
15.03.2024, 14:30 - Researcher: Guten Tag
[15-03-2024, 14:30:01] Researcher: Hoi
[15/3/24 下午 2:30:45] Researcher: 你好
2026-01-13, 12:22 PM - Researcher: Hello

When a header fails to match, the common continuation-line rule appends it to the preceding message. That makes the bug quiet. Instead of throwing an error, the parser can report one enormous message with thousands of lines. A count check is therefore as important as the regex itself.

The exported file is plain text, but its structure depends on the exporting environment. The academic ChatDashboard parsing description reports the same underlying issue: operating system, language, date settings and time settings affect the exported log structure. WhatsApp's official export instructions explain how to create the file; they do not promise one developer-facing timestamp schema.

The timestamp families a parser meets

The 2026.07 benchmark groups 14 layouts by structural family. The point is not that 14 is a permanent total. It is that a production parser needs explicit coverage and fixtures rather than an assumption that one example represents the format.

Family	Example	Structural difference
iOS year-first slash	[2024/07/09, 08:01:49] Name: text	Brackets, seconds, year first, no dash
iOS slash + AM/PM	[3/15/24, 2:30:45 PM] Name: text	Month/day ambiguity and optional seconds
Android slash	3/15/24, 2:30 PM - Name: text	No brackets and a dash before sender
European dotted	15.03.2024, 14:30 - Name: text	Dots, day first and 24-hour time
Dutch dashed	15-03-2024 14:30 - Name: text	Dash date and no comma
ISO year-first	2026-01-13, 12:22 PM - Name: text	Year first with dash separators
CJK marker	[15/3/24 下午 2:30:45] Name: text	Day-period marker appears before time

Some families differ only in punctuation. Others change the meaning of the numeric fields. Bracket detection alone is not enough: iOS can emit bracketed slash, dotted and dash-date forms, while non-bracketed Android-style forms can use slash, dash or year-first dates.

This is also why a permissive expression such as ^(.+?), (.+?) - (.+?): (.*)$ is not a dependable fix. It accepts more lines, but it pushes all the difficult work into later guesses and can mistake message text for a header. A parser should be tolerant about known equivalent syntax and strict about the boundary that declares a new message.

Normalize before matching

Regular expressions are easier to reason about after equivalent characters have one representation. The input can contain characters that look familiar on screen but are not the ASCII characters in your pattern.

The published parser performs a normalization pass before trying timestamp families:

Remove carriage returns and selected directional control marks around headers.
Convert narrow no-break and non-breaking spaces to ordinary spaces.
Map localized AM/PM markers to AM or PM.
Translate Arabic-Indic, Persian, Devanagari and Thai numerals to ASCII digits.
Normalize punctuation such as the Arabic comma where it appears in the header.

Here is a reduced JavaScript version of the digit step:

function translateDigits(text) {
  return [...text].map((char) => {
    const point = char.codePointAt(0);
    if (point >= 0x0660 && point <= 0x0669) return String(point - 0x0660); // Arabic-Indic
    if (point >= 0x06f0 && point <= 0x06f9) return String(point - 0x06f0); // Persian
    if (point >= 0x0966 && point <= 0x096f) return String(point - 0x0966); // Devanagari
    if (point >= 0x0e50 && point <= 0x0e59) return String(point - 0x0e50); // Thai
    return char;
  }).join('');
}

For example, the Arabic-Indic header ١٥/٠٣/٢٤, ١٤:٣٠ becomes 15/03/24, 14:30 before structural matching. The message body remains unchanged. Normalization should be scoped: rewriting the entire message body can damage the content you were asked to preserve.

Normalization reduces the number of patterns, but it does not remove date-order ambiguity. It makes symbols comparable; it does not tell you whether 03/04/24 means 3 April or March 4.

Use ordered format families

The parser uses an ordered list of sender and system-message patterns. More specific shapes are tested before more general shapes. A match returns the date string, time string, optional day-period marker, sender and body, plus a pattern type that controls date construction.

Conceptually, the loop looks like this:

for (const pattern of timestampPatterns) {
  const senderMatch = line.match(pattern.senderRegex);
  if (senderMatch) return parseSenderMessage(senderMatch, pattern.type);

  const systemMatch = line.match(pattern.systemRegex);
  if (systemMatch) return parseSystemMessage(systemMatch, pattern.type);
}
return null; // continuation text, preamble or unsupported header

Pattern order matters. A broad slash-date expression placed first can consume a more specific four-digit Brazilian form and apply the wrong month/day rule. A sender pattern should also run before a corresponding system pattern so the colon in Name: message is not swallowed as generic system text.

Keep timestamp recognition separate from message classification. Once the header boundary is known, the body can be classified as text, media, call, deleted or system using its own localized markers. Combining every possible body type into the timestamp regex makes the structural expression difficult to test and easy to break.

Treat ambiguous numeric dates honestly

15/03/24 is not ambiguous because 15 cannot be a month. 03/15/24 is equally clear. 03/04/24 is not. Without context, both 3 April and March 4 are valid interpretations.

The published parser uses structural context and a limited heuristic:

If the first number is above 12, treat it as the day.
If the second number is above 12, treat it as the day.
If both are 12 or below and an English AM/PM marker is present, prefer the US month-first interpretation.
Otherwise prefer day-first for the generic slash family.

This is useful, not infallible. The right production behavior is to retain the raw line, record the detected pattern and make ambiguous dates auditable. For evidence, research or compliance work, compare the result with the source device and surrounding messages. The parser should not turn a heuristic into a certainty claim.

A stronger application can detect locale from a sample of unambiguous dates across the file, then apply the inferred order to ambiguous dates. Even then, keep a warning when the sample provides no decisive values.

Parse messages as state, not isolated lines

A WhatsApp message can contain line breaks. Only its first line has a timestamp header. The following lines must be appended to the current message until another recognized header begins.

3/15/24, 2:30 PM - Alice: first line
second line
third line
3/15/24, 2:31 PM - Bob: next message

A minimal state machine is clearer than splitting on a regex:

const messages = [];
let current = null;

for (const line of normalizedText.split('\n')) {
  const header = recognizeHeader(line);
  if (header) {
    if (current) messages.push(current);
    current = header;
  } else if (current) {
    current.text += `\n${line}`;
  }
}
if (current) messages.push(current);

This state also gives you a place to handle preamble text, blank lines and unsupported headers deliberately. The first unmatched line should not create a phantom message. An unmatched line after a valid message is continuation text. A run of thousands of unmatched lines is a diagnostic signal that header recognition probably failed.

System messages need a separate path because they have a timestamp but no sender/body colon. Participant joins, group changes and encryption notices are not sender-attributed chat messages, yet dropping them changes message counts and chronology. The benchmark includes one system case, one multiline case and participant extraction across two senders for that reason.

How the 24-case benchmark works

The WhatsApp Export Parser Benchmark 2026 is intentionally small enough to inspect. It contains no customer messages and no private chats. Every fixture is synthetic and declares its input plus expected structured fields.

The suite currently contains:

14 timestamp cases covering bracketed and non-bracketed layouts, slash/dot/dash separators, year-first dates, seconds, and day-period placement.
4 normalization cases using Arabic-Indic, Persian, Devanagari and Thai numerals.
6 behavior cases for multiline messages, system messages, media markers, deleted messages, call markers and participant extraction.

Both runners read the same fixture JSON. They assert message count and, when applicable, participants, sender, text, type, year, month, day, hour and minute. A failure produces a non-zero exit status, which makes the benchmark usable in CI.

{
  "id": "timestamp-android-slash",
  "input": "3/15/24, 2:30 PM - Researcher: Hello",
  "expected": {
    "messageCount": 1,
    "sender": "Researcher",
    "year": 2024,
    "month": 3,
    "day": 15,
    "hour": 14,
    "type": "text"
  }
}

Node.js 0.1.1 and Python 0.1.1 each passed 24 of 24 published cases. Read that result narrowly. It does not prove support for every device, app version, locale, malformed ZIP or future WhatsApp change. It proves that the two published implementations satisfy the explicit expectations in this public fixture set. You can download the fixture JSON, case results CSV and full summary.

A safer implementation shape

If you need a parser rather than a finished PDF, the open-source package exposes the same approach in Node and Python. The source, runners and release artifacts are available in the whatsapp-chat-to-pdf GitHub repository.

Node.js:

npm install whatsapp-chat-to-pdf

import fs from 'node:fs';
import { parseText } from 'whatsapp-chat-to-pdf';

const input = fs.readFileSync('_chat.txt', 'utf8');
const chat = parseText(input);

console.log(chat.messageCount);
console.log(chat.participants);
console.log(chat.messages[0]);

Python:

pip install whatsapp-chat-to-pdf

from whatsapp_chat_to_pdf import parse_file

chat = parse_file("WhatsApp Chat with Alice.zip")
print(chat.message_count)
print(chat.participants)
print(chat.messages[0])

The implementation sequence is the transferable part:

Find the real chat text inside a TXT or ZIP, ignoring macOS __MACOSX and ._ resource-fork entries.
Normalize structural Unicode variants without rewriting the message body unnecessarily.
Recognize an ordered timestamp family and retain the raw input line.
Build the timestamp with an explicit rule for that family.
Stitch continuation lines into the current message.
Classify the message body separately.
Extract participants from non-system senders.
Assert fields against synthetic fixtures in every supported runtime.

If you are inspecting the export before writing code, the extract WhatsApp chat data guide explains the fields inside _chat.txt. The export chat meaning guide explains what the ZIP is and is not. For a formatted media-rich result rather than a parser library, the WhatsApp to PDF guide covers the hosted workflow.

Production checklist and limitations

Before trusting a WhatsApp export parser, check these properties:

Format coverage is named. “Supports WhatsApp” is too broad. Publish the layouts or fixtures you actually test.
Normalization is tested independently. A format test written only with ASCII digits will not catch localized-numeral failures.
Raw input is retained. When a timestamp is ambiguous or classification looks wrong, the original line is needed for review.
Counts are plausible. Zero, one or an unexpectedly small number of messages should trigger a diagnostic rather than a confident empty output.
Multiline content survives. A continuation line should stay with its message and preserve its newline.
System messages are explicit. Do not attribute group events to the previous participant.
ZIP selection is defensive. Ignore resource forks and prefer the recognized chat filename over the first .txt entry.
Failures are visible. Record unsupported header samples using synthetic or safely redacted examples; never upload a private conversation to a public issue.
Claims stay bounded. Passing a fixture suite is not proof of export completeness, authorship, authenticity or legal admissibility.

The current benchmark does not measure speed, memory consumption, PDF fidelity, attachment matching or voice transcription. It does not statistically sample all WhatsApp versions. Those are separate tests. A useful next contribution is a new synthetic fixture representing a genuinely different header shape, accompanied by the expected parsed fields and a source description that does not expose private chat content.

Reproduce before you trust

Download the fixtures, run both public benchmark commands, then add a synthetic case shaped like the export you expect to receive. A parser is reliable to the extent that its assumptions are visible and repeatedly tested.

FAQ

What format is a WhatsApp exported chat?

WhatsApp exports one conversation as a plain-text chat file, optionally inside a ZIP with media. Message headers commonly contain a localized timestamp followed by a sender and message body, but punctuation, ordering and day-period markers differ across device and locale. Use WhatsApp's official Export Chat flow to create the file; treat the parser schema as something your own fixtures must verify.

Can one regex parse every WhatsApp export?

Not safely. One broad regex can accept many header shapes, but it cannot by itself resolve date order, localized digits, day-period markers, system events and multiline continuation. Use normalization plus ordered structural families, then construct dates according to the matched family and validate the result with field-level fixtures.

How do I parse multiline WhatsApp messages?

Read the export as a stateful stream. A line with a recognized timestamp header starts a new message. A non-header line after a message is appended to that current message with its newline preserved. Flush the current message when the next header appears and again at end of file.

Why does a parser swap the day and month?

Purely numeric slash dates are ambiguous when both values are 12 or below. Use unambiguous dates elsewhere in the file, structural markers and device context to infer the order, but retain the raw line and surface the assumption. For sensitive work, verify the interpreted date against the source device and surrounding conversation.

Is the 24 out of 24 benchmark result universal?

No. It means Node.js 0.1.1 and Python 0.1.1 passed the 24 synthetic fixtures published in benchmark version 2026.07. It does not cover every WhatsApp release, locale or damaged export and it makes no claim about authorship, authenticity, completeness or admissibility.

Key takeaways

A WhatsApp export parser needs multiple explicit timestamp families because brackets, separators, date order, seconds and day-period position vary.
Normalize structural Unicode variants and four tested numeral scripts before matching; do not rewrite the preserved message body unnecessarily.
Treat numeric day/month ambiguity as a visible assumption, not a fact inferred from one line.
Parse with state so multiline messages and system events remain separate and message counts stay meaningful.
The public benchmark reports 24 of 24 for two runtimes only against its 24 synthetic cases; fixtures and limitations are downloadable.
Production reliability comes from named assumptions, raw-line retention, diagnostics and regression fixtures rather than one permissive regex.

Test a WhatsApp export in the free preview

Originally published at ChatToPDF. This Dev.to copy declares that page as its canonical URL.

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

ChatToPDF — Mon, 15 Jun 2026 09:16:19 +0000

TL;DR: A WhatsApp chat export is a ZIP file containing _chat.txt plus any attached media. WhatsApp silently caps the export at 40,000 messages — older history is cut off. Group chats add their own quirks: anonymised contacts, system messages, and a join-date cutoff. The fastest path from that WhatsApp chat export ZIP to a readable, sender-attributed document is a $14 Standard per chat conversion on ChatToPDF — about 30 seconds from upload to PDF.

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.

One situation where Including Media is always the right call: preserving a conversation with someone who has died, where the voice notes are usually what matters most. That situation has its own gentle guide.

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. Given that WhatsApp users collectively send over 100 billion messages a day, though, those very active chats are more common than you'd expect.

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.

Convert your WhatsApp export to PDF — from $7 Basic per chat

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

When the export itself goes wrong — troubleshooting

The Export Chat menu is reliable, but a few things still trip people up. Here's the fix for each:

Export ZIP too big, or only some messages came through — media bloat and the 40,000-message cap
Exporting without media — what you actually get — the text-only export, and when it's the right call
Export stuck on "Preparing file…" — large chats, storage, background limits
The exported ZIP won't open / is "damaged" — interrupted transfers and how to avoid them
Arabic / Hebrew text reversed in the export — bidi rendering, and how the ChatToPDF output handles RTL

Key takeaways

A WhatsApp export produces a ZIP file containing _chat.txt (every message, line by line) and, for Including Media exports, all attached photos, voice notes, and documents
Without Media exports are typically under 1 MB even for thousands of messages; Including Media exports can reach 100 MB or more, with media only included for roughly the most-recent 10,000 messages
WhatsApp caps all exports at 40,000 messages — the most-recent 40,000 — with no warning or truncation notice in the app
The _chat.txt date format varies by locale: US exports use M/D/YY, H:MM AM/PM, ISO exports use YYYY-MM-DD, HH:MM:SS, and European exports often use DD/MM/YYYY, HH:MM; a parser must handle all three
Group chat exports include system messages with no sender name, phone-number-only contacts for anyone not in your phonebook, and history only from your personal join date — not from the group's founding date
The $14 Standard per chat conversion handles exports up to 25,000 messages with inline photos; the $29 Premium per chat conversion adds voice-note transcription for chats containing .opus audio files
Before uploading any chat export to a third-party service, verify their deletion policy, data-use terms, and whether they exclude user content from model training

FAQ

What does an exported WhatsApp chat actually contain?

The export produces a ZIP file with a _chat.txt plain-text file inside. Each message is one line, formatted as [date, time] Sender Name: message text. If you chose Including Media during export, the ZIP also contains the attached files — images, voice notes, documents — named with WhatsApp's own convention (IMG-YYYYMMDD-WA####.jpg, PTT-YYYYMMDD-WA####.opus, etc.). Calls and disappearing messages that have already expired are not included.

How do I export a WhatsApp chat on iPhone?

Open the chat on iPhone, tap the contact or group name at the top to open the info screen, scroll to the bottom, and tap Export Chat. Choose Without Media for a text-only ZIP or Including Media to bundle photos and voice notes. iOS shows a share sheet — tap Save to Files and choose a folder you will remember. To convert the ZIP to a PDF, upload it to chattopdf.app; the $14 Standard per chat conversion handles most individual chats including photos.

What is the 40,000-message limit and how do I work around it?

WhatsApp exports a maximum of 40,000 messages per export, always taking the most-recent 40,000. There is no date-range filter and no warning when the limit is hit. To check whether you hit it, open _chat.txt in a text editor and look at the first timestamp — if it is later than expected, the export was truncated. The only workaround for accessing older messages is a third-party tool that reads the WhatsApp database directly (Android Backup Extractor, iMazing on iPhone), which requires a local backup or device root access.

Why do some contacts appear as phone numbers in my group chat export?

WhatsApp uses the contact name from your phonebook as the sender name in _chat.txt. If a group participant's number is not saved in your contacts, their messages appear with the raw phone number as the sender — something like +27 82 555 1234: Hello everyone. ChatToPDF preserves this phone number as the sender attribution in the PDF output; it cannot infer a name that is not in the source file. If you want names, save the number in your phone contacts and re-export.

Can I export a WhatsApp chat directly from a computer?

Not reliably. WhatsApp Web and WhatsApp Desktop mirror your phone's connection but do not offer a native export on most accounts. The only direct path is to export on your phone (Android: ⋮ → More → Export Chat; iPhone: tap the contact name → scroll down → Export Chat), then transfer the ZIP to your computer via AirDrop, USB, Google Drive, or iCloud Drive. A limited chat history download was added to WhatsApp Desktop for some accounts in 2024, but it is not available universally.

Is it safe to upload my WhatsApp export to ChatToPDF?

ChatToPDF processes the ZIP on the server, generates the PDF, and then deletes both files after the download window closes. Content is not used for model training, and there is no long-term storage of your messages. For group chats where other participants' messages are included, consider whether the export contains sensitive information before uploading to any service — including this one. WhatsApp's own end-to-end encryption protects messages in transit; it does not apply to files you export and upload elsewhere.

Which ChatToPDF tier do I need for a group chat export?

It depends on message count and whether voice notes are present. The $14 Standard per chat conversion covers up to 25,000 messages with photos, which handles most group chats under two to three years old. For longer group chats, the $29 Premium per chat conversion removes the message ceiling and adds voice transcription. For very large, multi-year group archives, the $99 Power User per chat conversion adds priority processing and handles the largest exports. Check the first and last timestamp in your _chat.txt to estimate message volume before choosing.

WhatsApp Evidence Court PDF: Format, Authenticity, Hash Chains (2026)

ChatToPDF — Mon, 15 Jun 2026 09:16:10 +0000

TL;DR: A WhatsApp evidence court PDF needs three things: sender attribution on every line, immutable timestamps, and a SHA-256 hash that proves the chat was not edited. ChatToPDF produces that PDF from your WhatsApp export — clean, formatted, hash-stamped on the cover page. Admissibility itself is the court's decision and your lawyer's job. For most evidence-prep workflows, the $14 Standard per chat conversion covers text and photos; the $49 Premium+Voice per chat conversion adds transcribed voice notes.

I am not a lawyer. This is not legal advice.

Whether your WhatsApp evidence is admitted depends on the court, the jurisdiction, and the argument your lawyer constructs. ChatToPDF produces a clean, formatted PDF — that's it. Everything after the download is on you and your counsel. Nothing in this guide substitutes for legal advice on your specific matter. Please talk to a lawyer before relying on any WhatsApp conversation as evidence in any proceeding.

Why courts accept WhatsApp chats as evidence — and what makes them refuse

I built ChatToPDF because I needed a WhatsApp conversation as a legal document. Not a stack of screenshots. Not a forwarded message thread. A proper, readable, attributed record that a solicitor could open on their desktop and work with directly. That original need is why the legal-evidence use case is baked into the tool's design at every level — the hash generation, the ISO timestamps, the formal PDF style.

Courts in most jurisdictions are willing to consider WhatsApp conversations as evidence when the communication is relevant and its authenticity can be reasonably established. The legal principle is straightforward: a relevant communication is admissible if you can show it is what you claim it is. WhatsApp messages satisfy that bar more often than people expect, because the export format preserves verifiable metadata that a screenshot simply does not have.

The cases where WhatsApp evidence has been accepted are wide-ranging. Contract disputes hinge on informal messages that amount to acceptance — a "yes, deal" in a WhatsApp thread can be a binding agreement in many jurisdictions. Employment disputes turn on harassment threads where the pattern of communication, not just individual messages, makes the case. Family law matters involve custody-related conversations where the tone and frequency of contact are directly relevant. Commercial disputes rely on deal terms agreed informally before formal contracts were drafted.

Courts refuse WhatsApp evidence for five main reasons:

Authenticity not established. If the other side can credibly argue the messages were fabricated or edited, and you have no integrity proof, the evidence weakens or fails. A manipulated screenshot is easy to produce; a verified export with a hash is much harder to dispute.

Chain of custody broken. If the chat was extracted using an unverified method, has no metadata, and cannot be tied back to a specific phone or account, the chain of custody argument collapses.

Hearsay problems. In jurisdictions with strict hearsay rules, a WhatsApp message may be excluded as an out-of-court statement offered for its truth, unless it falls within an exception such as a party admission or a business record.

Privacy and consent violations. A chat obtained by accessing someone's phone without permission, or by intercepting a private conversation you were not a party to, raises serious admissibility problems — and potentially criminal liability. I am not going to help you do that. If you were a participant in the conversation, you're on much firmer ground.

Group-chat third-party complications. Messages from participants who are not part of the dispute can introduce consent and data protection considerations that some courts find problematic. The solution is usually targeted redaction, not wholesale exclusion — but this is a question for your lawyer.

The bottom line: a clean, authenticated PDF made from WhatsApp's own export mechanism gives you a strong foundation. What you build on top of that foundation is legal work, not formatting work. If you are new to the export process itself, start with the WhatsApp to PDF overview before returning here for the evidence-specific requirements.

The format checklist — what a usable evidence PDF must show

Not every PDF is equally useful in a legal context. A conversation pasted into a Word document and saved as PDF is not the same as a structured export from WhatsApp's own mechanism. Here is what a properly formatted evidence PDF should contain, and what ChatToPDF generates automatically.

Cover page. A dedicated first page that shows the chat title (the group name or the contact's name and phone number), the date range of the exported conversation, the total message count, and — critically — the SHA-256 hash of the source ZIP file. The hash is what ties the PDF to the original export and makes integrity verification possible.

Page numbers with total count. Every page should carry a "Page X of Y" footer. This prevents anyone from claiming pages were removed or reordered after the fact.

Sender attribution on every message. Each message in the PDF should show the sender's display name and phone number. Display names alone are not sufficient — names can be changed or spoofed. Phone numbers are tied to registered accounts and are harder to fabricate.

ISO 8601 timestamps. WhatsApp exports use locale-specific date formats like [15/03/2024, 14:32:18]. ChatToPDF converts these to ISO 8601 format — 2024-03-15T14:32:18 — which is internationally unambiguous. A timestamp that reads 01/03/2024 is ambiguous between January 3 and March 1 depending on locale; the ISO version is not.

Per-message anchors. Each message in the PDF should be referenceable. ChatToPDF assigns a page-and-line anchor to each message — so your lawyer can cite "page 4, message 7" in a submission without ambiguity.

Footer on every page. A persistent footer reading something like "Generated by ChatToPDF · Export date: 2024-03-20 · SHA-256: [first 16 chars]" creates a clear chain of custody marker across the full document.

No editorial commentary. The PDF should be a faithful rendering of the export, nothing more. Annotations, highlighted sections, or added commentary on the chat content itself should be handled separately by your lawyer, not baked into the evidence document.

The Formal PDF style in ChatToPDF was designed specifically for this use case. It uses a letterhead-style cover page, small-caps sender attribution, right-margin timestamps, and indented message bodies — the format that reads most like a deposition transcript and least like an app screenshot.

Authenticity: how to prove the chat was not edited

The most common objection to WhatsApp evidence is that messages were fabricated or altered. It is a reasonable objection — any text file can be edited. The way to rebut it is a hash chain: a cryptographic fingerprint computed at the moment of export that changes if even a single character in the source file changes.

Here's how it works in practice. WhatsApp's Export Chat feature packages your messages into a _chat.txt file and, if you chose Including Media, wraps it in a ZIP alongside any photos, voice notes, and documents. ChatToPDF computes the SHA-256 hash of that ZIP file the moment you upload it. SHA-256 produces a 64-character hexadecimal string that is unique to that exact file content — change one character anywhere in the file and the hash changes completely.

That hash is printed on the cover page of the PDF. It is also embedded in the PDF's document metadata (the Producer and Keywords fields), so it travels with the file even if the cover page is somehow separated.

The verification step works in reverse. If a court or opposing counsel wants to verify the PDF against the original export, they take the original ZIP file — which you should preserve alongside the PDF as part of your chain of custody — compute its SHA-256, and compare it to the hash on the cover page. If they match, the source file was not modified after the PDF was generated. If they do not match, something changed.

This is not an exotic or complex process. SHA-256 is a standard cryptographic algorithm supported by every operating system and built into tools like OpenSSL and macOS's built-in shasum utility. It is the same algorithm used to verify software downloads and file integrity across the internet.

One important caveat: the hash proves the source ZIP was not modified after you uploaded it. It does not prove the chat was not edited before you exported it. WhatsApp's own "Edit message" and "Delete for everyone" features can alter message content before you export. I cover what those features do to the export in the section on edited and deleted messages below. This is a distinction your lawyer needs to be aware of and prepared to address.

Metadata you must preserve — timestamps, sender phone numbers, chat title

The metadata in a WhatsApp export is what separates it from a screenshot in terms of evidentiary value. Here is a precise breakdown of what ChatToPDF extracts and preserves, and why each field matters.

Timestamps. WhatsApp's _chat.txt stores each message with a timestamp that reflects the local time on the exporting device, in the format [DD/MM/YYYY, HH:MM:SS]. ChatToPDF converts these to ISO 8601 with timezone offset where inferable. If you are dealing with a cross-border dispute or a conversation where participants are in different time zones, raise this with your lawyer — the timezone attached to each timestamp matters for establishing the sequence of events.

Sender phone numbers. For contacts not saved in your address book, WhatsApp uses the phone number directly in the _chat.txt. For saved contacts, it uses the display name you assigned. ChatToPDF renders both — display name plus the underlying phone number where present. Phone numbers are registered to specific accounts at specific times through WhatsApp's own verification process, which makes them more reliable identifiers than display names.

Chat title. For group chats, the group name as it existed at export time is preserved. For individual chats, the contact name or number is the title. This appears on the cover page and in the PDF header of every page.

Message sequence. The order of messages in the export is the order they appear in the _chat.txt — which is chronological. ChatToPDF preserves this order and assigns sequential anchors so the complete record is navigable.

Media references. Even in a text-only export (Without Media), the _chat.txt contains references to attached files: <attached: 00000012-AUDIO-2024-03-15-09-22-31.opus>. ChatToPDF renders these as clearly labelled placeholders in the PDF. If you later need the actual media, you can re-export with Including Media — but the text record already shows that a file was sent at that time.

One thing I want to be direct about: preserving this metadata is a technical task, but deciding which metadata is legally relevant in your specific case is your lawyer's job. The phone number of the sender matters enormously in a fraud case; it may be less significant in a contract dispute where the identity of both parties is already established. Do not assume that preserving everything is the same as knowing which parts matter.

Screenshots vs exports — why screenshots get rejected

I get asked this question constantly: "Can't I just take screenshots?" The honest answer is: sometimes screenshots are the only option, and courts do occasionally admit them as supplementary evidence. But as a primary evidence format, screenshots have problems that an authenticated export does not.

Here's the core issue. A screenshot is a photograph of your phone's screen at a specific moment. It contains whatever was visible on that screen, no more. There is no machine-readable content. There is no metadata beyond the screenshot's own file timestamp (which reflects when you took the photo, not when the messages were sent). And critically, a screenshot is trivially editable in any image editor — change the text, adjust the timestamp, alter the sender name — and a visual inspection cannot detect the manipulation.

Courts are aware of this. In multiple jurisdictions, judges and magistrates have explicitly noted that screenshots alone are insufficient to authenticate digital communications, particularly where the other side contests the messages. The UK Ministry of Justice guidance on digital evidence and the US Federal Rules of Evidence (Rule 901, authentication requirements) both point toward requiring more than a visual image for digital communications.

A WhatsApp export is different in every one of these dimensions. It is machine-readable text with embedded metadata. It was produced by WhatsApp's own export mechanism, not by a third-party tool or a screen capture. It contains timestamps recorded at the moment of transmission, not the moment of capture. And it can be hashed at export time to detect any subsequent modification.

If screenshots are all you have — because the conversation was deleted before you thought to export it, or because you were viewing someone else's device at the time — then screenshots with corroborating evidence (other communications, witness statements, phone records) are better than nothing. But wherever you can get a clean export, get the export.

For a detailed walk-through of the export process on both iPhone and Android, the WhatsApp chat export guide covers every step including the common points where exports go wrong.

The hash-chain workflow — from export to filed PDF

This is the canonical workflow I recommend for anyone preparing WhatsApp evidence for any kind of legal proceeding. It is not complicated — most of it is handled automatically by ChatToPDF — but the steps matter.

Step 1: Export the chat from WhatsApp with Including Media.

Open WhatsApp, navigate to the chat, tap the contact or group name at the top (iPhone) or the three-dot menu (Android), and choose Export Chat. Select Including Media even if you think the images are not relevant — having the complete ZIP with media preserves more options and supports a stronger integrity argument. Save the ZIP to a location you can access from a browser.

Step 2: Note the file details immediately.

Before uploading anything, note the file name, file size, and — if you are technically comfortable — compute the SHA-256 yourself using shasum -a 256 yourfile.zip on macOS or certutil -hashfile yourfile.zip SHA256 on Windows. ChatToPDF will also compute this and display it to you during upload. Comparing the two confirms nothing changed in transit.

Step 3: Upload to ChatToPDF and select the appropriate tier.

The $14 Standard per chat conversion covers text and inline images, which handles the majority of evidence-prep use cases. If the chat includes voice notes that are relevant — instructions given verbally, verbal agreements, threatening messages — the $49 Premium+Voice per chat conversion adds Deepgram Nova-3 transcription, and the transcripts appear inline in the PDF at the correct chronological positions.

Step 4: Review the hash on the cover page of the generated PDF.

When your PDF is ready, open it and confirm that the SHA-256 hash on the cover page matches the hash you computed in Step 2 (or the one displayed during upload). This is your moment to catch any discrepancy before the document enters a legal workflow.

Step 5: Store the original ZIP and the PDF together, unchanged.

This is the part people skip. The original ZIP is the anchor of your chain of custody. If you delete it, you lose the ability to verify the hash later. Store both files in a secure location — an encrypted cloud folder, an external drive, or wherever your lawyer instructs you to keep evidence materials. Do not re-export, do not rename the ZIP, and do not open it in any application that might modify it.

Step 6: Give the PDF (and the ZIP on request) to your lawyer.

The PDF is the working document. The ZIP is the proof. Your lawyer may not need the ZIP immediately, but they should know where it is. Some proceedings may require you to produce the original export as part of discovery; having it intact and unmodified is the only way to satisfy that requirement.

Group-chat evidence — the consent and admissibility issues

Group chats add complexity that individual chat evidence does not have. I want to be specific about what that complexity looks like, because it affects both how you prepare the evidence and how your lawyer will need to argue for its admission.

When you export a group chat, the export contains every message sent by every participant during the exported period. That includes participants who are not parties to your legal matter. Their messages appear in the _chat.txt alongside the messages you actually need. This creates several potential issues.

Third-party content. The messages of uninvolved participants are personal data under most data protection laws. Presenting those messages in a legal proceeding may require that you have a lawful basis for processing that data. In most jurisdictions, legal proceedings provide that basis — but the specifics depend on the jurisdiction and the nature of the proceeding. Your lawyer needs to be aware of which participants' data appears in the export.

Redaction of non-evidentiary content. In some matters, courts will accept a redacted version of the group export — one where uninvolved participants' messages are blacked out, leaving only the participants and content relevant to the claim. This is often cleaner and more persuasive than submitting an unredacted 300-person group chat where 280 people are irrelevant. ChatToPDF generates the structured PDF; targeted redaction is a step your lawyer's office typically handles using standard PDF tools.

Consent and privacy expectations in group chats. Many jurisdictions treat group chats differently from private one-to-one messages. The general principle is that when you participate in a group conversation, you have reduced privacy expectations relative to a private direct message — all participants know the conversation is shared across the group. But this is not a universal rule, and it varies by jurisdiction and context.

System messages. WhatsApp exports include system-generated messages — things like "[Contact] joined using an invite link" or "[Contact] changed the group description." These appear in the _chat.txt and in the PDF. They can be useful for establishing when someone joined the group, or when group settings were changed, which is sometimes directly relevant to the dispute.

The bottom line with group chats: the export is technically straightforward. The legal considerations around third-party participants are not simple. Do not assume a group-chat export is ready to file just because you've turned it into a clean PDF. Talk to your lawyer about which participants' content you need and what, if anything, needs to be redacted before the document enters a legal proceeding.

Edited and deleted messages — what shows up, what does not

This is the part that most guides skip, and it is the part most likely to create problems if you do not understand it before you submit your evidence.

Deleted messages — messages where the sender tapped "Delete for everyone" — appear in the export as a placeholder: This message was deleted. That is all. The original message content is gone. The export reflects what is currently visible in the chat, not what was ever sent. If a critical message was deleted before you exported, it is not in your export. Period.

Edited messages — WhatsApp introduced a message-editing feature in 2023 — appear in the export only as their final edited form. The original version of an edited message is not preserved in the export. There is no [edited] marker in the _chat.txt; the message appears exactly as it currently reads. If someone edited "Yes, I agree to those terms" to "No, I never agreed to anything" before you exported, your export will show the edited version.

This is not a flaw in ChatToPDF. This is a fundamental characteristic of WhatsApp's export mechanism. The _chat.txt reflects the current state of the conversation on the exporting device, not a complete immutable history of every message ever sent.

Here's the part nobody tells you: this limitation cuts both ways. If the other side claims a message was edited or deleted to change its meaning, they need to provide their own evidence of what the original said — a screenshot, a witness statement, a separate export from their device, or carrier metadata. The burden of proving alteration is on them if you are presenting the export; the burden of proving integrity is on you.

For messages that were deleted or edited, your lawyer may be able to pursue the original content through other channels: the other party's device (via discovery), WhatsApp's data transparency mechanisms in your jurisdiction, or witness testimony about what the original message said. None of these are ChatToPDF's domain. All of them are your lawyer's domain.

One practical implication: export early. If you anticipate a legal dispute, export the relevant chat as soon as possible. Every day you wait is another day the other party can delete or edit messages that might matter. The export is a snapshot of the conversation at the moment you take it. Take it as close to the events as you reasonably can.

Cross-jurisdiction notes — evidence rules differ widely

I want to be careful here. I am not a lawyer. I am not qualified to give you jurisdiction-specific legal advice. What I can do is describe the general landscape, name the issues your lawyer will need to address, and be explicit that the specifics depend entirely on where your matter is being heard.

Authenticity standards vary. Most jurisdictions require some authentication of digital evidence — proof that the document is what it claims to be. The hash-chain workflow I described above addresses this in general terms, but the specific authentication standard (what you need to show, who can testify to it, what documentation is required) depends on your jurisdiction's evidence rules.

Hearsay rules differ significantly. In some common-law jurisdictions, WhatsApp messages may be admitted as party admissions (statements made by a party to the proceedings) or as business records (where applicable). In other jurisdictions, or where the message is being offered for a different purpose, hearsay exclusions may apply. This is one of the most important questions your lawyer needs to answer before you rely on WhatsApp evidence as a primary exhibit.

Data protection laws and legal proceedings. Most data protection laws in most jurisdictions include provisions that permit processing personal data for the purposes of legal proceedings, including where that processing would otherwise require consent. But the specific conditions — what "legal proceedings" includes, whether it covers pre-litigation evidence preservation, what documentation you need — vary by jurisdiction. Always check with a local lawyer.

Civil vs. criminal proceedings. The rules governing evidence in criminal proceedings are typically more stringent than in civil matters. Chain of custody requirements, authentication standards, and hearsay rules are generally applied more strictly in criminal courts. If your matter is criminal in nature, get legal advice before you do anything with the evidence — including exporting the chat.

Cross-border disputes. If the conversation involved parties in different countries — and WhatsApp is global — you may face questions about which jurisdiction's evidence rules apply, which country's data protection laws govern the export, and whether evidence collected in one jurisdiction is admissible in another. These are not questions any tool can answer for you. (One cross-border use deserves its own guide: presenting WhatsApp chats as relationship evidence for visa applications, where the formatting requirements are different from court exhibits.)

The best summary I can give: the hash-chain workflow and the clean PDF format give you a strong technical foundation that is respected in most jurisdictions' evidence frameworks. But technical foundation is not the same as legal admissibility. Talk to a local lawyer before you file anything.

Court-evidence tools compared

A handful of tools now position specifically on the court-evidence use case, and since I get asked how ChatToPDF compares, here is an honest snapshot. Competitor details are taken from their own sites as of June 2026 — check current pricing and features before relying on any of it.

	ChatToPDF	WaChat to PDF	ChatToCourt	Desktop tools (Decipher, iMazing)
Pricing model	$14–$99 one-time per chat	$6.99 per export or $19.99/mo	$3.99 per document	~$30–60 licence + a computer
Runs in browser, no install	Yes	Yes	Yes (processes locally in your browser)	No — desktop app, cable, backup
SHA-256 integrity hash	Yes — printed on the PDF cover page	Yes	Not advertised	Varies
Voice notes	Transcribed inline at $49 Premium+Voice — what was said becomes readable text in the record	Not transcribed	Not transcribed	Not transcribed
Free preview before paying	Yes	Varies	Preview/edit before export	Trial versions
Bates numbering / PII redaction	No — redaction is paralegal work under your lawyer's direction (see below)	Yes (Pro features)	Editing before export	Varies

Where the others are genuinely strong: WaChat to PDF's Bates numbering matters if your lawyer files in a US litigation context that uses Bates-stamped productions — ask them whether they need it or whether they Bates-stamp exhibits themselves (most firms do it in-house as part of assembling the bundle). ChatToCourt's in-browser processing means the chat never leaves your machine, which is a real consideration for highly sensitive material — ChatToPDF's answer is different: files are processed server-side, auto-deleted within 7 days, and never used for anything else, with a free preview so you see the output before paying.

Where ChatToPDF is the only option: voice notes. If the conversation that matters includes voice messages — and in harassment, family, and business disputes it usually does — none of the others put the spoken words into the record as readable, searchable text. A judge or opposing counsel cannot Ctrl-F an audio file. The voice-to-text guide covers how inline transcription works.

For the case-type-specific workflows, I have separate guides for divorce and custody matters, printing message exhibits for court, and documenting workplace harassment — each covers the preservation steps and the mistakes specific to that situation.

Engaging a lawyer — when to stop self-prepping

Not every use of a WhatsApp PDF requires a lawyer. But some do, and the mistake most people make is waiting too long to get one involved. Here is how I think about the decision.

Self-preparation is fine for:

Preserving a conversation you think might matter later. Exporting and PDF-ing a chat as a precaution, storing it securely, and waiting to see if the matter develops further — this is good practice and requires no lawyer. The cost is one $14 Standard per chat conversion and a few minutes. The upside is a clean, hashed record if you ever need it.

Informal mediation or dispute resolution. If you are trying to resolve a disagreement without going to court — a dispute with a contractor, a misunderstanding with a business partner, a neighbour conflict — a well-formatted PDF of the relevant conversation can clarify what was actually said and agreed. You are not submitting legal evidence; you are presenting a clear record.

Background preparation before a first legal consultation. If you have a meeting scheduled with a solicitor or attorney, arriving with a clean PDF of the relevant chat is more efficient than asking them to read screenshots on your phone. The $14 Standard per chat conversion is a cheap way to show up to that meeting prepared.

Get a paralegal involved for:

Organising large volumes of evidence material. If you have multiple chats, a complicated group conversation, and dozens of supporting documents, a paralegal can help structure the exhibit list and ensure the evidence is organised in a format the lawyer can work with efficiently. For teams or businesses processing multiple chat records, the WhatsApp Business PDF guide covers the bulk-export and per-chat filing patterns that HR and legal departments use most. For high-volume archive work — discovery preparation across hundreds of chats, for example — the $99 Power User per chat conversion supports priority queue and bulk batch upload, which a paralegal or document-management team typically drives.

Redaction work. If the group-chat export contains content from uninvolved third parties that your lawyer says should be redacted before filing, a paralegal can typically handle the redaction process under the lawyer's supervision.

Get a lawyer involved for:

Any matter where the WhatsApp conversation will be a primary exhibit. If the chat is the case — the contract, the harassment, the threat, the agreement — you need a lawyer to decide how to introduce it, what supporting evidence to gather, and how to address authentication objections from the other side.

Any matter with potential damages. If money or liberty is at stake, legal advice is not optional.

Any matter that is or may become a court proceeding. Once you are in front of a judge or magistrate, evidence rules apply strictly. Self-represented litigants who submit improperly authenticated evidence often lose cases they should win because the technical requirements were not met.

ChatToPDF is a formatting and authentication tool. It produces the cleanest possible starting point for your evidence. Getting that document admitted, used effectively, and argued persuasively is legal work — and there is no tool that replaces a lawyer who knows your case.

Key takeaways

WhatsApp chats are accepted as evidence in many jurisdictions when authenticity can be established — exports with hash chains are significantly stronger than screenshots, but admissibility is the court's decision, not a tool's guarantee
A proper evidence PDF needs a cover page with SHA-256 hash, ISO 8601 timestamps, sender phone numbers on every message, page numbers, and a persistent footer — ChatToPDF generates all of these automatically
The hash-chain workflow (export ZIP, compute SHA-256, generate PDF, cite hash on cover page, preserve original ZIP) is the core integrity proof — ChatToPDF automates the hash; preserving the ZIP is your job
Deleted and edited messages are not in the export — the _chat.txt reflects the current state of the conversation, so export early before any alteration can occur
Group-chat exports contain every participant's content, including uninvolved third parties; redaction and data protection considerations require your lawyer's input before filing
Every jurisdiction has its own evidence rules, hearsay standards, and data protection considerations — always talk to a local lawyer before relying on WhatsApp evidence in any formal proceeding
ChatToPDF costs $14 Standard per chat conversion for text-and-images and $49 Premium+Voice per chat conversion for chat plus voice-note transcription — either is the formatting step; your lawyer handles the legal step

FAQ

Is a ChatToPDF-generated PDF legally admissible in court?

That is not a question I can answer — and you should be sceptical of any tool that claims it can. Admissibility depends on the court, the jurisdiction, the nature of the proceedings, and the argument your lawyer makes. What ChatToPDF produces is a clean, sender-attributed, ISO-timestamped PDF with a SHA-256 hash on the cover page — which is the technical foundation a lawyer typically needs to argue for admission. Whether the argument succeeds is between your lawyer and the court.

Should I use screenshots or the export for legal evidence?

Use the export wherever you can. Screenshots are easily manipulated in any image editor and contain no machine-readable metadata. A WhatsApp export is produced by WhatsApp's own mechanism, contains timestamps recorded at transmission time, and can be hashed at export to detect subsequent modification. Courts in many jurisdictions have noted explicitly that screenshots alone are insufficient to authenticate digital communications. The $14 Standard per chat conversion turns your export ZIP into a properly formatted, hashable evidence PDF.

What happens to deleted messages in the export?

WhatsApp's "Delete for everyone" feature replaces the message content with the placeholder "This message was deleted" in the recipient's chat. When you export, that placeholder is what appears in the _chat.txt — and therefore in the PDF. The original message content is not recoverable through the export. If critical messages were deleted before you exported, you will need to pursue the original content through other means: the other party's device, witness testimony, or any other available channel. This is a question for your lawyer, not for ChatToPDF.

How does the SHA-256 hash prove the chat was not edited?

When you upload a WhatsApp ZIP to ChatToPDF, the tool computes the SHA-256 of the ZIP file and prints it on the cover page of the generated PDF. SHA-256 produces a 64-character fingerprint that is unique to the exact content of the file — change even a single character in the _chat.txt and the hash changes completely. Later, if a court or opposing counsel wants to verify the PDF against the original, they compute the SHA-256 of the original ZIP and compare it to the cover-page hash. A match means the ZIP was not modified after the PDF was generated. The original ZIP is your anchor — keep it.

Can I submit a group-chat export as evidence?

You can prepare one, but get your lawyer's input before filing it. A group-chat export contains every participant's messages, including those of people who are not parties to your dispute. Most data protection laws have provisions for processing personal data in legal proceedings, but the specifics depend on your jurisdiction. Your lawyer may also advise redacting uninvolved participants' content before the document enters a formal proceeding. ChatToPDF generates the formatted PDF; targeted redaction is typically done by your lawyer or paralegal using standard PDF tools.

Which ChatToPDF tier should I use for evidence preparation?

For most evidence-prep cases — contract disputes, employment matters, harassment threads, business communications — the $14 Standard per chat conversion covers text and inline images, which is usually sufficient. If the conversation includes voice notes that are directly relevant to the matter, the $49 Premium+Voice per chat conversion adds Deepgram Nova-3 transcription, and the transcripts appear inline in the PDF at the correct chronological positions. Both tiers generate the SHA-256 hash and ISO timestamps that are the core of the integrity argument. Which tier fits your case depends on your content — your lawyer can advise on what level of detail the evidence needs to show.

Do I need to keep the original ZIP file after I have the PDF?

Yes, and this is important. The PDF is the working document. The original WhatsApp ZIP is the proof that the PDF is accurate. If the hash on the PDF cover page is ever challenged, you need the original ZIP to verify it. Some proceedings also require production of the original evidence in discovery — if you have deleted the ZIP, you may not be able to satisfy that requirement. Store the ZIP and the PDF together in a secure location and do not rename or modify the ZIP after upload.

Can WhatsApp messages be used in small claims court?

In many jurisdictions, yes — small claims courts commonly accept message records as evidence of agreements, payments promised, work commissioned, or goods described, and the procedural bar is often lower than in higher courts. The practical requirements are the same ones this guide covers: a complete thread rather than excerpts, visible dates and sender identification on every page, and the original export kept untouched as the source record. Small claims clerks can usually tell you exactly how many copies the court wants and in what format — ask before you print. For the printing mechanics, see the court printout guide.

Can I use a WhatsApp PDF for an insurance claim?

Insurers regularly ask for supporting documentation, and message threads — what was reported when, what a contractor promised, what condition something was in before — often carry real weight in a claim file precisely because they were written at the time. A paginated PDF with timestamps and sender names is far easier for a claims handler to work with than forwarded screenshots, and the export preserves the chronology that a claim dispute usually turns on. Keep the original ZIP in case the insurer or an assessor asks how the document was produced. Check your policy or ask your claims handler what format they want before submitting.

Can WhatsApp messages be used in a landlord or tenant dispute?

Message threads between landlords and tenants — repair requests, rent discussions, notice of entry, deposit conversations — are commonly presented in housing tribunals and small claims proceedings. The same principles apply: preserve the whole thread early (before a dispute escalates and messages get deleted), keep it chronological and complete rather than cherry-picked, and make sure every page shows who said what and when. Some tenancy tribunals have their own bundle formats — check the tribunal's guidance or ask at filing. The evidence format checklist above covers what every page needs to show.

How do I present WhatsApp messages for a restraining order application?

Courts handling protective-order applications typically want printed exhibits: complete, chronological, with dates, times, and sender identification visible, organised so the judge can follow the pattern of contact. A complete export is stronger than a folder of screenshots here for a specific reason — these applications usually turn on a pattern of behaviour over time, and a continuous thread shows frequency and escalation in a way isolated screenshots cannot. Make the copies your court requires (many ask for three), and if voice messages are part of the pattern, the $49 Premium+Voice per chat conversion puts what was said into the record as readable text. Court self-help centres and domestic-violence advocates can walk you through the filing itself — and if you are in immediate danger, contact local emergency services first.

WhatsApp statistics 2026: 3.3 billion users, and the export gap nobody talks about

ChatToPDF — Mon, 15 Jun 2026 09:11:14 +0000

WhatsApp is now the most-used messaging app on the planet. I run a tool that converts WhatsApp exports to PDF, so I spend my days at the messy end of these numbers — here are the ones that actually matter, with sources.

The headline figures (2026)

~3.3 billion monthly active users (DemandSage)
~2.4 billion daily active users
100 billion+ messages sent per day (Meta's own figure)
7 billion voice messages per day — the largest voice-messaging platform in the world

Where the users are

India leads with about 532 million users, then Brazil and Indonesia. The top 10 countries hold roughly 49% of all WhatsApp users (World Population Review).

The part that bites developers

For all 3.3 billion users, WhatsApp's only built-in export produces a .txt file or a .zip — never a PDF — and it silently caps a media-inclusive export at about 40,000 messages. Voice notes come out as raw .opus files, not text. So the messages exist, the demand to keep them exists, but the format is unreadable for any real purpose.

That mismatch — billions of users, a stagnant plain-text export — is why parsing/formatting tools exist at all. If you've ever tried to programmatically read a _chat.txt, you know the timestamp formats alone vary wildly by locale (iOS bracketed, Android dashed, European dotted, plus non-Western digits).

Full breakdown with all the charts and sources: WhatsApp Statistics 2026.

How to export a WhatsApp chat to PDF in 2026: the honest options

ChatToPDF — Mon, 15 Jun 2026 08:33:18 +0000

WhatsApp doesn't have a "Save as PDF" button. The only thing it gives you is Export
chat, which produces a .txt file (or a .zip if you include media). Turning that into a
readable PDF is the part people get stuck on — so here's a straight rundown of the ways that
actually work, what each is good for, and where each falls down.

Disclosure up front: I work on one of the tools below (ChatToPDF). I've tried to keep this
even — for several use cases one of the others is the better pick, and I've said so.

First, get the export

On the chat: tap the contact/group name → Export Chat → choose Without Media (a
.txt) or With Media (a .zip with the text plus photos/voice notes). That file is your
starting point for everything below. Note WhatsApp caps the export at ~40,000 messages
(fewer with media).

Option 1 — Print to PDF from WhatsApp Web (free, fastest, ugly)

Open WhatsApp Web, open the chat, scroll to load the part you want, then Print → Save as
PDF. Costs nothing and needs no tools.

👍 Free, no upload, instant.
👎 No real formatting, struggles with long chats, and media/voice notes don't come through cleanly. Fine for a few screens, painful for a whole conversation.

Option 2 — A dedicated web converter

Upload the exported .txt/.zip and get a formatted PDF back. Two worth knowing:

ChatToPDF (the one I work on) — keeps images inline, timestamps and sender names, offers a few layouts including a numbered document style, and can transcribe voice notes onto the page. There's a free preview of the output before you pay; pricing is one-time per chat (no subscription, no account, files auto-deleted).
whatsapptopdf.com — free online converter, also handles media. Good if you just want a
quick PDF and don't need transcription or layout choices.
👍 Proper formatting, media handled, no software install.
👎 You're uploading the chat to a server — fine for most things, but for genuinely sensitive
conversations an offline desktop tool (below) keeps everything local.

Option 3 — Desktop backup software (Dr.Fone, iMazing, Backuptrans)

Tools like Wondershare Dr.Fone, iMazing and Backuptrans pull a full WhatsApp
backup off your phone and let you export to PDF (and other formats) locally.

👍 Everything stays on your machine; handles very large histories; exports more than just one chat.
👎 Paid, heavier to set up, overkill if you just need one conversation as a PDF.

Option 4 — Turn the chat into a printed book (zapptales, Keepster)

If the goal is a keepsake rather than a document — a relationship, a trip, messages from
someone you've lost — services like zapptales and Keepster lay the chat out as a
physical book.

👍 Beautiful printed result, designed for memories.
👎 Much pricier, and it's a book, not a quick file you can email.

Which one should you use?

Just need a quick PDF of a short chat? WhatsApp Web → Print to PDF.
Want a clean, formatted PDF with images/voice notes, no install? A web converter (ChatToPDF or whatsapptopdf.com).
Huge history, or you want it processed entirely offline? A desktop backup tool.
It's a keepsake? A book service like zapptales or Keepster.

One thing worth saying for the legal/evidence use case people often ask about: any of these
gives you a timestamped record, but whether a court accepts it depends on your jurisdiction
and how it's presented — that's a question for your lawyer, not a tool.

Hope that saves someone the evening I once spent screenshotting a chat one message at a time.
If you've found a method I've missed, drop it in the comments.

Best WhatsApp Transcription Tools: An Honest Guide

ChatToPDF — Fri, 29 May 2026 18:59:53 +0000

This guide compares the best WhatsApp transcription tools by the job you need done — not by abstract accuracy rankings. The best WhatsApp transcription tool depends entirely on the job you are doing. If you need to quickly read one voice note without pressing play, WhatsApp's own built-in transcription is the right answer — it is free, on-device, and instant. If you need to process a standalone audio file, general-purpose transcription apps are a sensible fit. If you need an entire WhatsApp chat exported as a searchable PDF with every voice note transcribed inline, sender names preserved, and timestamps intact, that is what ChatToPDF's Premium+Voice tier ($49 per chat) is built for.

TL;DR: The category that fits you: WhatsApp's built-in transcription for a quick read of one note; a general transcription app for standalone audio files; ChatToPDF for a whole exported chat with voice notes inline in one searchable document. The right tool is the one shaped for your specific job — not the most accurate one in the abstract, and not the cheapest one in isolation. Free options exist at every level; the cost of the dedicated tools reflects batch processing, export format, and sender attribution — not just raw transcription.

How to choose a WhatsApp transcription tool

The single most important question is not "which tool is most accurate" — it is "what is the actual job I am trying to do?" A transcription tool that excels at one job is often irrelevant for another. Here are the criteria that matter, in rough order of importance.

Scope: per-message or whole-chat batch. WhatsApp conversations can run to thousands of messages with dozens of voice notes scattered across the timeline. If you need all of them transcribed in context, a tool that processes one file at a time requires you to manually extract, name, and reassemble each voice note — an approach that is tedious at five voice notes and impractical at fifty. A batch tool processes the entire exported ZIP in one pass and embeds the transcripts in sequence. Know your scope before choosing.

Output format and where you need the result. A transcript that stays inside an app is useful for reading once; a transcript in a PDF, XLSX, or plain-text file is useful for filing, emailing, printing, or submitting to a third party. If the output needs to leave the phone — go to a solicitor, an HR manager, a case-management system, or a personal archive — the format matters as much as the transcription quality.

Sender attribution and timestamp inline. In a multi-participant chat, a voice note transcript without the sender's name and the original timestamp is only half the record. "Someone said this at some point" is not useful for a business archive or a legal document. Look for whether the tool preserves who said what and when — not just what was said.

Language support. Voice notes in WhatsApp come in every language. Most transcription tools support a core set well and degrade for others. If your chat contains voice notes in Arabic, Hindi, Portuguese, or a mixed-language conversation, check language support specifically rather than assuming "it works". WhatsApp publishes the list of languages supported by its built-in transcription on the official WhatsApp FAQ.

Privacy and data handling. Voice notes can contain sensitive personal information. Before uploading to any third-party tool, check their stated data-retention policy. ChatToPDF deletes uploaded files automatically after 7 days; policies at other services vary — check the vendor's current terms.

Price model. Transcription tools charge in very different ways: some are subscription (monthly fee regardless of how much you transcribe), some are per-minute of audio, some are per-conversation. For a one-off archive of a single WhatsApp chat, a per-chat flat fee is often more economical than a recurring subscription you will cancel. For ongoing high-volume use, a per-minute or subscription model may be cheaper. Match the cost model to your usage pattern.

The main options compared

The four categories below cover every practical approach to WhatsApp transcription. I have not invented competitor prices, accuracy percentages, or feature lists — the category rows describe general, verifiable characteristics of each approach. For any specific commercial tool you are evaluating, check its current documentation; features and pricing change.

WhatsApp transcription tool categories — what each option is actually for

Category	Scope	Output / export	Sender + timestamp inline	Languages	Privacy	Best for	Cost model
WhatsApp built-in	One voice note at a time	Transient overlay inside the app — no export	Visible in chat UI but not in the transcript overlay or export	Varies by app version; check your WhatsApp settings	On-device processing — audio stays on your phone	Quickly reading one note without pressing play	Free (built into WhatsApp)
General transcription apps	Usually one audio file at a time; some support batch file upload	Plain text, SRT, or DOCX — typically one transcript per file	Not connected to WhatsApp chat structure; no sender or timestamp	Varies by app; many support major languages well	Varies by vendor — check each app's current retention policy	Transcribing standalone audio or video files	Subscription or per-minute; free tiers usually limited
ChatToPDF (Premium+Voice)	Entire exported WhatsApp chat — all voice notes in one pass	PDF (voice transcripts inline in conversation) + optional XLSX/CSV	Yes — sender name and timestamp preserved with every transcript entry	17 high-accuracy languages; 30+ auto-detected (Deepgram Nova-3)	Files deleted automatically after 7 days; no sharing with third parties	Whole chat as a searchable record — legal, business, archive, accessibility	$49 per chat — one-time flat fee, no subscription
Manual typing / hiring a transcriber	Any audio, any format, any quality	Whatever format the typist produces — Word, PDF, plain text	Only if the typist is given context and instructed to include it	Any language a human speaker understands	Depends on whether a human or a service is involved; review before sharing	Very noisy audio, unusual accents, or where automated tools fail	Time cost if DIY; varies widely if outsourced — check the vendor

The table does not rank these options by quality — they are shaped for different jobs. The right column is not "best"; it is "best for a specific situation."

Convert your WhatsApp chat to PDF

When ChatToPDF is the right choice (and when it isn't)

I want to be honest about this, because a comparison page that pretends one product wins every case is not useful.

ChatToPDF wins when the job is: the whole chat as a document. If you have a WhatsApp conversation — one-to-one or group — that contains a mix of text messages and voice notes, and you need the complete record exported as a searchable document with sender attribution and timestamps, ChatToPDF is the only tool on this list built specifically for that job. The built-in transcription cannot export and does not batch. General transcription apps do not understand the WhatsApp chat structure and cannot attach transcripts to specific senders and moments in the conversation. Manual typing is possible but slow.

The specific situations where I would confidently recommend ChatToPDF's Premium+Voice tier:

Legal and compliance filings — a dispute, an employment matter, a court filing — where you need the voice notes and the surrounding text messages in one timestamped, attributed document
Business records — client approvals, instructions, and agreements given verbally over WhatsApp, where a searchable archive is the difference between "we have a record" and "I think he said this in a voice note somewhere"
Long-term personal archives — family group chats, voice notes from relatives, conversations you want to preserve in a format that does not depend on WhatsApp staying installed
Accessibility situations — making voice note content available to someone who is deaf or hard of hearing, or who cannot play audio in their environment

WhatsApp's built-in transcription wins when the job is: quickly reading one note right now. I mean this genuinely. If someone just sent you a two-minute voice note and you want to skim it on silent in a meeting, tap the note and let WhatsApp transcribe it on-device. Free, instant, no export needed. ChatToPDF is the wrong shape for that job. The WhatsApp speech to text guide covers the built-in feature in detail.

General transcription apps win when the job is: a standalone audio file that has nothing to do with WhatsApp structure. If someone emailed you an MP3 of a meeting recording or a podcast segment, a general-purpose transcription app is the right tool. That app is not going to understand a WhatsApp ZIP file, and ChatToPDF is not going to help you with a non-WhatsApp audio file. Use the right shape.

Manual transcription wins when automated tools fail. Very noisy audio, unusual accents, highly technical vocabulary, low-quality recordings, or languages that are genuinely not well-supported by any automated engine — these are the cases where a human listener still outperforms automated tools. Automated transcription has come a long way, but it is not universal. The transcribe WhatsApp audio guide covers how background noise affects accuracy in detail, including the honest picture of when Deepgram Nova-3 degrades.

What ChatToPDF costs

ChatToPDF uses a per-chat flat fee — one payment, one export, no subscription or recurring charge.

Voice transcription is available on the Premium+Voice tier at $49 per chat. That tier includes: the full PDF with every voice note transcribed inline at its position in the conversation; Deepgram Nova-3 transcription in 17 high-accuracy languages plus 30+ auto-detected; sender name and timestamp preserved with every transcript; XLSX and CSV export alongside the PDF; and up to 8 hours of audio per chat. If you have a chat with dozens of voice notes spread across years, this is the tier that handles it in a single pass.

The Power User tier at $99 per chat adds a priority processing queue and is intended for very large group exports where turnaround time matters.

The other tiers ($7 Basic, $14 Standard, $29 Premium) do not include voice transcription. They produce a chat PDF with text messages and inline media, but voice notes appear as audio-file placeholders rather than readable transcripts.

There is no subscription required. If you have one conversation to export, you pay $49 once. If you have ten, you pay per chat. There is no monthly fee regardless of whether you use the service.

You can upload your ZIP and preview the output — including how many voice notes were detected and what the formatted PDF will look like — before paying anything. The 7-day money-back guarantee means that if the transcription output is not what you needed, you can get a full refund.

Convert your WhatsApp chat to PDF

FAQ

What's the best free option for WhatsApp voice transcription?

WhatsApp's own built-in transcription is the best free option — it is on-device (so your audio never leaves the phone), does not require any third-party app, and works reasonably well for clear recordings in well-supported languages. It transcribes one voice note at a time with no export option. If you need batch transcription or a document you can save and share, the free tier ends there. Some general transcription apps offer limited free tiers — typically a few minutes of audio per month or per day — but features and pricing change, so check each vendor's current offering before relying on it. For a complete WhatsApp chat archive with transcripts, there is no free option that handles sender attribution, timestamps, and batch processing in one step.

Can I transcribe a whole WhatsApp chat at once?

Yes, but not with WhatsApp's built-in feature — that transcribes one voice note at a time and has no export. To batch-transcribe an entire chat, you export the conversation from WhatsApp as a ZIP file (using the "Including Media" option, which includes the voice note audio files), then upload the ZIP to chattopdf.app and select the Premium+Voice tier. ChatToPDF processes all the voice notes in the export in a single pass and returns one PDF with the transcripts embedded inline at their correct positions in the conversation. The WhatsApp voice to text guide walks through this workflow step by step.

Which WhatsApp transcription option is most accurate?

Accuracy depends on audio quality more than tool choice. For clear recordings — indoors, phone near the speaker, minimal background noise — modern automated transcription engines including Deepgram Nova-3 (used by ChatToPDF) perform well across supported languages. For noisy recordings — a busy street, a moving vehicle, wind — accuracy degrades for all automated tools, and a human transcriber may be more reliable. WhatsApp's on-device transcription uses a different underlying model; I cannot benchmark it precisely because the model is not publicly documented. The honest answer is: test with your own audio in your specific language and noise conditions before committing to any approach for something important. ChatToPDF's free upload preview lets you assess quality before paying.

Do any tools keep the sender names and timestamps alongside the transcript?

Among the automated options in this comparison, only ChatToPDF preserves sender names and timestamps as part of the transcript output. WhatsApp's built-in transcription shows the transcript as an overlay on the voice note bubble — you can see the sender's name in context in the chat UI, but it is not part of the transcript text itself and does not appear in any export. General transcription apps process a standalone audio file with no knowledge of who sent it or when — they return a transcript of the spoken content only. For legal, business, or archive use cases where attribution is important, ChatToPDF's approach of embedding the transcript at the exact position in the conversation — with the sender name and timestamp that WhatsApp's own export file records — is the only category that delivers this as part of the output document.

Is my data private when I use a WhatsApp transcription tool?

Privacy practices differ across the categories. WhatsApp's built-in transcription processes audio on your device and audio does not leave the phone — this is the highest-privacy option. General transcription apps typically send audio to cloud servers for processing; data-retention policies vary by vendor, so check each one's current privacy documentation before uploading sensitive conversations. ChatToPDF sends your ZIP to its servers for processing and automatically deletes uploaded files after 7 days. No audio or chat data is shared with third parties. If your voice notes contain sensitive personal or business information — which they often do — review the privacy policy of any service before uploading, regardless of which tool you choose.

Key takeaways

The best WhatsApp transcription tool depends on the job: built-in for one note quickly, general apps for standalone audio files, ChatToPDF for a whole exported chat as a document
WhatsApp's built-in transcription is free, on-device, and private — but transcribes one message at a time with no export capability
General transcription apps handle standalone audio files well but have no knowledge of WhatsApp chat structure, sender names, or timestamps
ChatToPDF Premium+Voice ($49 per chat) batch-processes the entire exported ZIP and embeds transcripts inline in the PDF with sender attribution and timestamps preserved
The transcription engine is Deepgram Nova-3: 17 high-accuracy languages, 30+ auto-detected; accuracy depends mainly on audio quality, not tool choice
No transcription tool performs perfectly on noisy recordings — test with your own audio before committing to anything important
For the whole-chat workflow step by step, see the WhatsApp voice to text guide; for the technical accuracy picture, see the transcribe WhatsApp audio pillar
If your goal is a complete, searchable PDF of the whole conversation — transcripts included — the WhatsApp to PDF guide explains the full process from export ZIP to finished document.

WhatsApp Voice to Text: Turn Voice Notes into Readable Text

ChatToPDF — Fri, 29 May 2026 18:59:37 +0000

The fastest way to do WhatsApp voice to text conversion at scale is to export the entire chat as a ZIP with "Including Media" and process it in one batch. Upload the ZIP file to chattopdf.app and choose the $49 Premium+Voice tier at checkout. Every voice note in the conversation becomes an inline transcript in the PDF — attributed to the sender, placed at the correct timestamp, readable alongside the surrounding text messages.

TL;DR: WhatsApp voice notes can be converted to readable text by exporting your chat as a ZIP (Including Media), uploading it to chattopdf.app, and selecting the $49 Premium+Voice tier. The output is a PDF where every voice note is transcribed inline at its position in the chat, with the sender name and timestamp preserved. Works on both iPhone and Android exports. 17 languages at high accuracy, 30+ more auto-detected. No separate transcription app needed — everything comes out as one searchable document.

How to convert WhatsApp voice notes to text

The entire workflow runs in five steps, from opening WhatsApp to receiving a PDF with every voice note transcribed.

1. Export the chat with Including Media — Open WhatsApp and navigate to the chat that contains the voice notes. On iPhone: tap the contact or group name at the top of the chat → scroll to the bottom of the info screen → tap Export Chat → pick Including Media. On Android: tap the three-dot menu in the top-right corner → More → Export Chat → Include Media. The "Including Media" option is the critical one — it puts the .opus voice note files inside the ZIP alongside the text. Without it, the ZIP contains only the _chat.txt file and there is nothing to transcribe. WhatsApp's official export chat FAQ explains the export sheet in detail.

2. Save the ZIP to your device — After selecting Including Media, WhatsApp generates a ZIP file and opens the share sheet. On iPhone, tap Save to Files and choose a folder (On My iPhone → Downloads is reliable). On Android, share the ZIP to your file manager, Google Drive, or email it to yourself. The ZIP is now a real file on your device, ready to upload.

3. Upload the ZIP to chattopdf.app — Open chattopdf.app in a browser on your phone or desktop. Drag and drop the ZIP onto the upload area, or tap the area to open a file picker and select the ZIP you just saved. The uploader validates the file and shows a preview: total messages, number of voice notes detected, and an estimated output size. This preview is free — no payment yet.

4. Select the Premium+Voice tier ($49 per chat) — The pricing step shows five tiers. Pick Premium+Voice at $49 per chat. This tier enables Deepgram Nova-3 transcription on every voice note in the ZIP. The other tiers ($7, $14, $29) either omit voice notes entirely or include them only as audio-file placeholders rather than transcribed text. The $49 tier is the one that converts voice to readable text. Pay by card — one-time, no subscription, no recurring charge.

5. Download the PDF with inline transcripts — After payment, chattopdf processes the chat and emails the PDF to the address you provided. Typical processing time for a chat with up to a few dozen voice notes is under two minutes. The PDF arrives with every voice note transcribed at its correct position in the conversation — sender name, timestamp, and transcript text all preserved. Open it, search it, print it, or file it.

Convert your WhatsApp chat to PDF

What the output looks like

The key thing about the chattopdf output is that the voice note transcripts are inline in the conversation — not in a separate appendix, not in a separate file, not numbered separately. They appear exactly where the voice notes appeared in the chat, in chronological order, alongside the text messages.

Here is what a section of the resulting PDF looks like with a mixed text-and-voice conversation:

Emma · 09:14

Hey, are you joining the call at 10?

Luca · 09:15 · [voice note — 0:12 — transcript]

"Yeah, I'll be there. Just finishing up the slides. Five more minutes."

Emma · 09:16

Perfect, no rush.

Luca · 09:22 · [voice note — 0:28 — transcript]

"Actually, can we push it to 10:15? I need to send something to the client first and I want to attach the updated version."

Emma · 09:23

Sure, I'll let the others know.

Each transcript line carries the sender name and the timestamp from the original chat. If a voice note is in a language other than English — Spanish, Portuguese, Hindi, Arabic, French, and others — it is transcribed in that language. The transcript text is the spoken content as written text. You can select it, copy it, and search the PDF for keywords that appeared in any voice note.

The voice notes that were sound-only in WhatsApp become readable, searchable, archivable text. The surrounding context — the text messages before and after each voice note — remains intact. The full conversation reads as a single document.

When you would want this

Legal and evidence use cases. If a WhatsApp conversation is relevant to a dispute, a complaint, or a court filing, having the voice notes transcribed as part of the same document that shows the text messages is useful. A judge, solicitor, or HR officer can read the entire exchange — including what was said verbally — without needing to play audio. For more on formatting exported chats for legal purposes, the WhatsApp to PDF guide covers the formal styling options.

Business records and compliance. Sales teams, support teams, and freelancers who conduct substantive conversations over WhatsApp — approvals, agreements, instructions, complaints — often need a readable record of those conversations. Voice notes in a business context frequently contain the actual decision or the actual instruction. Having those as readable text alongside the surrounding messages means the record is complete and searchable, not partially mute.

Personal and family archives. Long family group chats accumulate years of voice notes from relatives — updates, stories, birthday wishes, directions, check-ins. Many of those voice notes are from people whose voices you want to remember. Transcribing them into a PDF creates a readable archive that can be searched, printed, and kept alongside photos and written messages. The voice notes do not stay as audio forever — device storage gets cleared, WhatsApp accounts get deleted, phones change hands. A PDF with the transcripts is a more durable format.

Accessibility. Voice notes are by nature inaccessible to people who are deaf or hard of hearing, or to people who cannot play audio in the environment they are in (commuting, an open-plan office, a meeting). A transcript makes the content of a voice note available regardless of hearing ability or audio environment.

In all of these cases, the value of the chattopdf approach compared to a standalone transcription app is that the transcript lands in context — at the right position in the conversation, attributed to the right speaker, readable alongside the surrounding text. You do not have to manually correlate a list of transcripts against a separate exported chat.

Convert your WhatsApp chat to PDF

Accuracy and languages

The voice transcription uses Deepgram Nova-3, which in my own testing handles clear recordings in supported languages well. In quiet conditions — indoors, phone held near the mouth, no background noise — the transcripts read cleanly with very few errors. In noisy conditions — a moving car, a café, wind — accuracy degrades noticeably and the occasional word or phrase needs a second read. The transcribe WhatsApp audio guide covers the accuracy picture in detail, including how background noise affects results and what the word error rate looks like across recording conditions.

The 17 languages where Deepgram Nova-3 performs at high accuracy include English, Spanish, Portuguese, French, German, Italian, Arabic, Hindi, Indonesian, Turkish, Russian, Dutch, Japanese, Korean, Mandarin, Vietnamese, and Thai. If a voice note is in any of these languages, the transcript is typically clean enough to be useful without editing. For languages beyond this set, the engine falls back to a broader detection model — accuracy varies and some languages may not transcribe usefully. If your chat contains voice notes in a language that is not on that list, I would suggest testing with a single short export before relying on the transcription for anything important.

WhatsApp voice notes are encoded as Opus audio at 16 kHz. That is a narrow frequency range optimised for speech intelligibility, which means the transcription engine receives all the information it needs for speech recognition. The audio format itself is not the limiting factor. The WhatsApp audio format guide explains the Opus codec in more detail if you are curious about the technical side.

For language detection to work correctly, the ZIP must include the voice note files — which is why the "Including Media" export option matters. Without the audio files in the ZIP, there is nothing to transcribe regardless of tier.

Key takeaways

To get WhatsApp voice notes as readable text, export the chat with Including Media — this puts the .opus audio files inside the ZIP, which is required for transcription.
Upload the ZIP to chattopdf.app and choose the $49 Premium+Voice per chat tier. The other tiers do not transcribe voice notes to text.
The output is a PDF where every voice note appears as an inline transcript at its position in the conversation, with sender name and timestamp — not as a separate list or file.
17 languages at high accuracy, 30+ auto-detected. Background noise is the main accuracy factor, not the language or the Opus audio format.
Free alternatives exist (WhatsApp's in-app transcription, Otter.ai, Google Recorder) but require processing voice notes one at a time; ChatToPDF batches the whole chat in a single pass.
Voice calls are not in the chat export and cannot be transcribed. Only voice note messages (the audio clips sent in the chat) are included.
The transcribe WhatsApp audio pillar covers the full technical detail — accuracy by noise level, the Deepgram Nova-3 pipeline, and what the WER looks like across recording conditions.

FAQ

Is there a free way to turn WhatsApp voice notes into text?

Yes — several free options exist. WhatsApp itself has a built-in live transcription feature on some Android versions and iPhones running iOS 17 or later: hold the microphone icon in the voice note player and the app shows a transcript. This works in-app for individual messages and is free. Standalone transcription apps like Otter.ai (limited free tier), Google's Recorder app (Pixel-only, free), and Apple's Voice Memos transcription (US English only, iOS) can also transcribe audio files. The limitation with all of these approaches is that you have to transcribe one voice note at a time, manually, and then correlate the output with the surrounding chat text yourself. ChatToPDF charges $49 for the Premium+Voice tier because it processes the entire chat — potentially dozens of voice notes — in a single batch and delivers the transcripts inline at the correct position in the conversation, attributed to the correct sender, as a single searchable PDF. Whether that is worth it depends on how many voice notes you have and what you need the output for.

Does this work on both iPhone and Android exports?

Yes. The export workflow is slightly different on each platform — on iPhone you reach the Export Chat option via the contact info screen (tap the name at the top of the chat); on Android it is under the three-dot menu → More → Export Chat. Both platforms produce a ZIP file containing a _chat.txt and the voice note .opus files when you export with Including Media. ChatToPDF accepts ZIPs from both platforms and processes them identically. The underlying voice note format is the same on both (Opus codec, .opus extension), so there is no quality or accuracy difference based on which phone the export came from.

What languages are supported for voice note transcription?

17 languages at high accuracy: English, Spanish, Portuguese, French, German, Italian, Arabic, Hindi, Indonesian, Turkish, Russian, Dutch, Japanese, Korean, Mandarin, Vietnamese, and Thai. Beyond these 17, Deepgram Nova-3 auto-detects and attempts transcription for 30+ additional languages, though accuracy varies and some may not produce useful output. Mixed-language voice notes — Hinglish (Hindi + English), code-switching in Arabic dialects, Portuguese–Spanish mixing — are handled in a single pass by Nova-3. The transcript is in the language(s) spoken; there is no translation step. For the full language table with notes on dialect handling, see the transcribe WhatsApp audio pillar.

Do WhatsApp voice calls get transcribed too?

No. WhatsApp voice calls are not recorded or stored in the chat export. The ZIP file that WhatsApp generates contains only messages that appeared in the chat window — voice notes (the short recorded audio clips you send as messages), photos, documents, and the text conversation. A phone call or video call made through WhatsApp does not appear in the chat export because it was a live call, not a stored message. Only voice notes — the microphone icon messages in the conversation — are transcribed.

How long does the transcription take?

For a typical chat with up to a few dozen voice notes, the full process — upload, transcription, PDF generation, email delivery — usually completes in under two minutes after payment. Larger chats with many voice notes or unusually long individual recordings (several minutes each) take longer; in my experience a chat with 50+ voice notes totalling an hour of audio can take five to ten minutes. There is no hard limit on audio duration at the Premium+Voice tier (up to 8 hours of audio per chat). You receive the PDF by email once it is ready, so you do not have to stay on the page.

WhatsApp to PDF Converter Online Free: What Actually Works

ChatToPDF — Fri, 29 May 2026 18:53:45 +0000

Yes, there are genuinely free ways to get a WhatsApp chat into PDF — WhatsApp's built-in export plus your phone's print-to-PDF works at no cost for small chats. But a fully formatted converter that keeps sender names, timestamps, and inline media across a long chat is a paid tool. ChatToPDF's preview is free; conversion starts at $7.

TL;DR: The whatsapp to pdf converter online free options that genuinely exist: WhatsApp's built-in Export Chat + your phone's print-to-PDF (free, works for short chats, breaks on long ones), generic free online tools (typically file-size capped, no media, often watermarked), and ChatToPDF's free preview (see formatting + count + price before paying). A properly formatted conversion — sender attribution, timestamps, inline media, no truncation — starts at $7 on ChatToPDF. No subscription; one-time payment per chat.

What you can do for free

Three genuinely free options exist for getting a WhatsApp chat into PDF format. None of them are a dedicated online whatsapp to pdf converter online free with full formatting — but they are real, zero-cost paths.

Option 1: WhatsApp's built-in Export Chat + print-to-PDF

WhatsApp includes an Export Chat feature on both iPhone and Android. You export the chat as a .txt file (or a .zip with media), then open that text file on your phone and use the built-in print-to-PDF function. This costs nothing and requires no third-party tool.

1. Export the chat from WhatsApp — Open the chat you want to save. On iPhone: tap the contact or group name at the top → scroll down to Export Chat → choose Without Media or Including Media. WhatsApp creates a .txt or .zip file; save it to Files. On Android: tap the three-dot menu → More → Export Chat → pick your option → save to Files or Google Drive.

2. Open the exported .txt file — Locate the .txt file in your Files app (or Google Files on Android). Tap to open it — it will open in a basic text viewer or your default notes app. The raw format is readable but not formatted: you will see timestamps and sender names as plain text.

3. Print to PDF on iPhone — With the .txt file open, tap the Share icon → Print. On the print preview, use the two-finger pinch-out gesture on the preview thumbnail. This opens the preview as a full PDF. Tap Share and save to Files as a PDF.

4. Print to PDF on Android — With the .txt open, tap the three-dot menu → Print. In the printer selector, choose "Save as PDF" (built into Android). Choose a save location and tap Save.

The honest trade-off: this free method works, but the result is a plain text dump — no bubble formatting, no sender highlighting, no visual separation between messages. And it breaks on longer chats: WhatsApp's .txt export truncates at around 40,000 messages, and many text viewers struggle to open and print very large files smoothly. Images from the ZIP do not appear in the printed text file at all; they are separate files in the archive that the .txt print path ignores entirely.

For a short chat you want a quick record of, the built-in print-to-PDF route is a perfectly reasonable free option. For anything longer, more structured, or intended for business or legal use, its limits matter.

Option 2: Generic free online converters

A number of general-purpose online tools accept uploaded files and attempt some conversion. These are not WhatsApp-specific; they treat the .txt as plain text and reflow it into a PDF without interpreting WhatsApp's chat structure.

In my experience testing tools of this category, the typical limitations include:

File size caps — usually a few megabytes, which excludes chats with significant message history
No sender attribution — the output renders raw text without distinguishing senders visually
No media — even if you upload the full .zip, photos and voice notes are not processed or embedded
Watermarks — many free tiers stamp a watermark on the output PDF
Unknown data retention — the privacy policies of generic free online tools vary widely; many do not publish a retention period for uploaded files

I am not going to name specific tools here and invent performance comparisons I have not independently verified — that would not be honest. What I can say from the category pattern is that a generic free online file converter is not built for WhatsApp's format and will not produce sender-attributed, timestamped output.

Option 3: ChatToPDF's free preview

This one is worth being precise about, because I have seen it described imprecisely elsewhere: the preview at ChatToPDF is free, but the download is not.

When you upload your WhatsApp export to chattopdf.app, the tool immediately parses the file and shows you — at no cost — the total message count, the detected sender names, the date range, and the formatted price for each tier. You also see a rendered snippet of the first few messages in the PDF style you choose. Nothing is charged at this stage. No card details are entered.

That free preview answers the question "will this work for my chat?" before you commit to paying. It is also the step where you can confirm that the encoding parsed correctly — useful for non-Latin scripts or emoji-heavy chats. The WhatsApp to PDF guide has more on what the parser handles.

Convert your WhatsApp chat to PDF

Where free runs out (and paid is worth it)

The honest answer to "is there a free whatsapp to pdf converter online?" is: for a short, text-only chat where you just need a readable record, the built-in print-to-PDF method is free and adequate. But several common needs push past what free options can deliver.

Long chats. The print-to-PDF method works reasonably on a few hundred messages. At several thousand messages — a multi-year group chat, for instance — the plain .txt file becomes unwieldy to print, and the output PDF has no structure to help you navigate it. ChatToPDF's $7 Basic tier handles up to 5,000 messages with full sender attribution and timestamps; the $29 Premium tier removes the cap entirely.

Inline media. If your chat ZIP contains photos, the print-to-PDF approach produces nothing for those photos — they are not referenced in the .txt at all in a way a text viewer renders. On the $14 Standard tier and above, ChatToPDF embeds each photo at its exact position in the conversation.

Sender attribution with visual formatting. The free print-to-PDF output is a wall of text with sender names embedded as part of each line. A properly formatted PDF with sender names in bold, timestamps separated, and messages visually grouped by sender looks quite different and is considerably easier to read. All ChatToPDF tiers produce that formatting.

Professional, legal, or business use. A plain .txt printout would not stand up well as a business record or legal exhibit. ChatToPDF's Formal style (available at all tiers) produces numbered entries with timestamps, consistent sender attribution, and a document header — the kind of output referenced in the WhatsApp evidence court PDF guide.

XLSX and CSV output. No free option produces a spreadsheet from a WhatsApp chat. ChatToPDF generates a row-per-message XLSX and CSV at the $29 Premium tier and above — useful for any analysis or record-keeping that requires tabular data.

Voice note transcription. The free methods produce nothing for voice note audio. ChatToPDF's $49 Premium+Voice tier transcribes each .opus file inline using Deepgram Nova-3 with 17 high-accuracy languages.

The WhatsApp to PDF converter guide covers the full tier comparison — formats, message caps, and output types — in detail. This page is focused on the free question specifically.

How ChatToPDF's free preview works

When you drop your chat export onto chattopdf.app, this is what happens before any payment:

The file is validated — confirms it is a genuine WhatsApp export, not a random .zip
The parser reads the full export and counts messages, detects senders, and identifies the date range
A preview is shown to you: message count, sender names, date range, images and voice notes found
The price for each tier is displayed based on your actual message count
A rendered snippet of the first messages appears in the PDF style you have selected

Only after you have seen all of that and chosen a tier does a payment screen appear.

Free preview — ChatToPDF's free preview is the stage after upload and before payment where you see your chat's statistics (message count, senders, date range, media found) and the formatted price for each tier. No payment information is entered during this stage. The preview costs nothing regardless of whether you proceed to pay.

Here is how the main options compare:

WhatsApp to PDF converter options — free vs paid at a glance

Method	Cost	Message limit	Media inline	Sender formatting	Privacy / retention
WhatsApp print-to-PDF	Free	Practical limit ~few hundred before unwieldy	No	Plain text, no visual formatting	No upload; stays on your device
Generic free online tools	Free (often watermarked)	Typically a few MB file cap	No	None — raw text reflow	Varies; most do not publish a retention policy
ChatToPDF (paid, from $7)	$7–$99 one-time per chat	5,000 (Basic) to no cap ($29+)	Yes — from $14 Standard	Full — sender names bold, timestamps, styled bubbles	7-day auto-deletion; TLS + AES-256

Privacy of free online converters

Before uploading a WhatsApp chat to any online tool — free or paid — it is worth understanding what happens to the file after you upload it.

WhatsApp chats contain personal conversations: names, phone numbers, addresses, financial arrangements, relationship details. The privacy risk is not hypothetical.

Generic free online converters typically do not publish a clear data retention policy. When I look at the terms of general-purpose file-conversion tools, "we may retain uploaded files for [X days]" is common, but some do not specify a period at all. Some free tools are supported by advertising, which raises the question of what data they collect alongside the file upload. I am not going to claim any specific tool does anything harmful — I have not audited them individually — but the absence of a clear, published retention policy is a genuine concern when uploading a personal conversation.

ChatToPDF's policy is specific and documented: both the source file and the output PDF are automatically deleted seven days after the job is created. The deletion is a scheduled automated job that runs against every record older than seven days — it applies to paid and unpaid jobs alike. The upload travels over TLS 1.3 and is stored with AES-256 encryption at rest on AWS S3. No person reads the chat content; the conversion is entirely automated. No account creation is required — the only personal information stored is the email address you provide for download delivery, which is also removed on day 7.

For a chat that contains personal or sensitive information — and most WhatsApp chats do — the extra few dollars for a tool with a clear, auditable retention policy is a reasonable trade-off against a nominally free option whose data handling is opaque.

Convert your WhatsApp chat to PDF

FAQ

Is there a truly free WhatsApp to PDF converter?

There is no online converter that produces a fully formatted, sender-attributed, media-inclusive WhatsApp PDF for free. WhatsApp's own built-in export combined with your phone's print-to-PDF function is genuinely free and produces a basic PDF — but the output is a plain text dump with no visual formatting, no inline images, and no clear sender distinction. ChatToPDF's preview (message count, sender names, price) is free; the conversion itself starts at $7.

How do I convert a WhatsApp chat to PDF for free on my phone?

Export the chat from WhatsApp (iPhone: tap the contact name → Export Chat; Android: three-dot menu → More → Export Chat), save the .txt file to your Files app, then open it and use your phone's print option — on iPhone pinch-out on the print preview thumbnail to get a "Save as PDF" option; on Android select "Save as PDF" from the printer selector. The result is a plain-text PDF of the chat content. Images from the ZIP are not included by this method.

Why isn't the full ChatToPDF converter free?

Running the parser that interprets WhatsApp's date-format variations and encoding edge cases, the PDF rendering engine that produces formatted, searchable output, and the server infrastructure that stores and processes the files all have real costs. The free preview (message count, senders, price, formatted snippet) is genuinely free because parsing and showing statistics is lightweight. Rendering and delivering the full PDF is not. The $7 Basic tier is the entry point; there is no subscription — it is one payment per chat.

Are free online converters safe for personal WhatsApp chats?

The honest answer is: it depends on the tool, and many do not publish a clear retention policy. A WhatsApp chat typically contains names, phone numbers, and personal conversation content. Before uploading to any free online converter, I would check their privacy policy for a specific retention period and confirm they do not use uploaded content for advertising targeting. ChatToPDF auto-deletes both the source file and the output after 7 days; that policy is published and applies uniformly. The print-to-PDF method described above avoids uploading to any third party at all.

What is the best free WhatsApp to PDF option for a short chat?

For a short chat — up to a few hundred messages, no photos you need embedded — WhatsApp's own export + print-to-PDF is the best free option because it requires no third-party upload. For anything longer, with media, with formatting requirements, or with professional or legal needs, the $7 Basic tier at ChatToPDF is the cheapest paid option that produces properly formatted output. The free preview lets you confirm it parsed correctly before committing.

Key takeaways

The only truly free WhatsApp-to-PDF path is WhatsApp's built-in Export Chat combined with your phone's print-to-PDF function — it works for short, text-only chats; the WhatsApp to PDF guide covers the full method.
Generic free online converters have file-size caps, no sender formatting, no inline media, and often unclear privacy policies; they are not designed for WhatsApp's chat structure.
ChatToPDF's preview is free: you see message count, senders, date range, formatted snippet, and the exact price before paying anything.
Paid conversion starts at $7 (Basic, 5,000 messages); the $14 Standard tier adds inline images; the $29 Premium tier removes the message cap and adds XLSX + CSV.
For a long chat, media-inclusive export, professional formatting, or legal use, the free methods fall short — paid is the realistic path.
Any online tool that accepts personal WhatsApp chats should have a published, specific data retention policy; ChatToPDF auto-deletes source and output after 7 days.
The print-to-PDF free method avoids uploading your chat to any third party at all — worth considering for highly sensitive conversations.

WhatsApp to PDF Converter: Formats, Tiers, and Privacy

ChatToPDF — Fri, 29 May 2026 18:53:24 +0000

A WhatsApp to PDF converter accepts the ZIP or TXT file that WhatsApp's built-in Export Chat menu produces and turns it into a formatted PDF with sender names, timestamps, and media inline. I built ChatToPDF to do exactly that: upload the export, see a free preview of message count and price, pick a tier ($7 and up), and download the PDF.

TL;DR: ChatToPDF is a whatsapp to pdf converter that processes the export ZIP from your phone and outputs a formatted PDF with full sender attribution, timestamps, and — on higher tiers — inline media and voice transcripts. You preview the chat and the price for free before paying anything. Output formats are PDF, XLSX, and CSV (XLSX/CSV from $29). Five tiers from $7 Basic to $99 Power User. Source files are deleted automatically after 7 days.

How the converter works

The WhatsApp to PDF converter runs entirely in the browser — nothing to install. The input is the file that WhatsApp's own Export Chat menu produces: either a .txt for a text-only export, or a .zip when you chose Including Media.

1. Export the chat from WhatsApp — Open WhatsApp and navigate to the chat you want to convert. On iPhone: tap the contact or group name at the top → scroll to Export Chat near the bottom → choose Without Media (text only) or Including Media (text + photos + voice notes). On Android: tap the three-dot menu → More → Export Chat → pick your option. WhatsApp produces either a .txt file (Without Media) or a .zip archive (Including Media). Save it to your phone's Files app or iCloud Drive. The WhatsApp chat export guide covers this step in detail for both platforms.

2. Upload the ZIP or TXT to chattopdf.app — Open chattopdf.app in any browser — mobile or desktop. Drag and drop the .zip or .txt onto the upload zone, or tap to open a file picker. The converter validates the file immediately: it checks that the archive contains a _chat.txt in the expected WhatsApp format before proceeding. Invalid files or non-WhatsApp archives are rejected at this stage.

3. Review the free preview — no payment yet — After validation, the converter parses the export and shows you a free summary: total message count, detected senders, date range, and an itemised price based on the tier you hover over. You can also see a rendered snippet of the first few messages in your chosen PDF style. This is the step where you confirm the encoding parsed correctly — especially useful for Arabic, Hebrew, or emoji-heavy chats. No card details are entered at this point.

4. Select a tier and pay once — Pick the tier that matches what you need (see the table below). Payment is one-time per chat — no subscription, no recurring charge. After payment, the converter processes the full export and the download link appears on screen. An email with the same link is sent to the address you provide, so you don't lose access if the browser tab closes.

Convert your WhatsApp chat to PDF

What formats it outputs

Every conversion produces at minimum a formatted PDF. The $29 Premium tier and above also produce an XLSX spreadsheet and a CSV file as part of the same bundle.

PDF is the primary output. The PDF is fully searchable, properly paginated, and includes a header with the chat name and date range on every page. Each message is attributed to the sender with the timestamp. Four visual styles are available at all tiers: Green Bubble (closest to the WhatsApp app UI), Clean (recommended for legal and HR use), Formal (letterhead header, deposition-style layout), and Book (continuous prose, no bubbles). All four styles are available regardless of tier.

XLSX is a row-per-message spreadsheet with columns for timestamp, sender name, message body, and a media flag. It's useful for filtering by sender, sorting by date, or doing message-frequency analysis in Excel or Google Sheets.

CSV is the same data as XLSX but in plain comma-separated format, compatible with any data tool that ingests tabular data.

The tier table below shows which features each tier includes:

WhatsApp to PDF converter tiers — features at a glance

Tier	Price	Message cap	Images inline	XLSX + CSV	Voice transcription
Basic	$7	5,000	No — placeholders	No	No
Standard	$14	25,000	Yes — inline	No	No
Premium	$29	No cap	Yes — inline	Yes	No
Premium+Voice	$49	No cap	Yes — inline	Yes	Yes — Deepgram Nova-3, up to 8 hrs audio
Power User	$99	No cap	Yes — inline	Yes	Yes — uncapped, priority queue

Voice transcription converts each .opus voice note in the ZIP to readable inline text, placed at its exact position in the conversation. The $49 Premium+Voice tier covers up to 8 hours of audio per chat; the $99 Power User tier is uncapped and runs in the priority processing queue. Both use Deepgram Nova-3 — 17 high-accuracy languages plus 30+ auto-detected. The WhatsApp voice to text guide covers the transcription step in detail, including accuracy by noise level and the full language list.

The full story behind the converter — PDF styles, how the parser handles date formats and encoding edge cases, and a side-by-side comparison against alternative methods — is in the WhatsApp to PDF guide. If your first question is whether any free online option exists, the WhatsApp to PDF converter online free guide covers exactly that.

Convert your WhatsApp chat to PDF

Speed and file handling

In my testing, a typical chat of a few hundred to a few thousand messages converts in well under a minute from upload to download-ready. The processing time scales with message count and media volume — a chat that includes dozens of large images or many voice notes takes longer than a text-only export of the same message count.

The converter handles .txt files (from the Without Media export) and .zip files (from the Including Media export) without any conversion step on your end. Both are uploaded directly to the converter.

For large chats — tens of thousands of messages, hundreds of megabytes of media — the converter processes the full export without truncating, at the $29 Premium tier and above. The $7 Basic tier caps at 5,000 messages and $14 Standard caps at 25,000; beyond those limits the output is truncated at the cap. If you have a long group chat and are unsure which tier you need, the free preview step shows the total message count before you commit to a tier.

After the PDF renders, the download link appears on-screen and is sent to the email you provided. If you close the browser before the render completes, the email delivery means you don't need to re-upload.

Privacy and 7-day deletion

When you're converting a personal conversation, knowing exactly what happens to the file matters. Here is the full picture.

Upload: The file travels over HTTPS (TLS 1.3) from your browser to the servers. It is never transmitted unencrypted.

Storage: The uploaded file is stored on an AWS S3 bucket with AES-256 server-side encryption at rest. Access to raw files is restricted to the automated processing pipeline — no human download path exists through the normal interface.

Processing: The conversion is entirely automated. No person reads your messages. The parser, the PDF renderer, and the Deepgram transcription pipeline (where applicable) run without human intervention. For voice transcription, Deepgram receives only the audio bytes of the .opus files — not the chat text. Deepgram's API policy prohibits training on API-submitted data by default.

7-day deletion: Both the source file (your upload) and the output PDF are automatically deleted seven days after the job is created. This is a scheduled job that runs against every record older than seven days — there are no manual exceptions, and the deletion applies to both paid and unpaid jobs equally.

No account required. You do not create a profile or log in to use the converter. The only personally identifiable information stored is the email address you provide for download delivery.

For more on privacy, retention policy, and data handling, the WhatsApp to PDF guide includes the full privacy section with the step-by-step breakdown of what happens at each stage.

FAQ

Is the WhatsApp to PDF converter free?

The converter is free to try — you upload the chat and get a full preview of message count, senders, date range, and the formatted output before paying anything. Generating and downloading the actual PDF requires a one-time payment per chat: $7 Basic, $14 Standard, $29 Premium, $49 Premium+Voice, or $99 Power User. There is no subscription and no recurring charge.

Does it work for iPhone and Android exports?

Yes. Both iPhone and Android WhatsApp export the same _chat.txt format inside the ZIP (or as a standalone .txt). The converter accepts files from either platform. The export path is slightly different on each — iPhone uses the contact name tap → Export Chat; Android uses the three-dot menu → More → Export Chat — but the resulting file is the same and processes identically. The WhatsApp chat export guide covers both export paths with step-by-step instructions.

What does the PDF include?

The PDF includes every message with the sender name, the timestamp, and the message text. On the $14 Standard tier and above, images and document thumbnails appear inline at the position they were sent. On the $49 Premium+Voice tier and above, voice notes are transcribed and appear as readable text at their correct position in the conversation. The PDF is fully searchable and paginated, with a header on each page identifying the chat and date range. Four visual styles are available at all tiers: Green Bubble, Clean, Formal, and Book.

Is my chat data safe?

Your file is encrypted in transit (TLS 1.3) and at rest (AES-256 on AWS S3). The conversion runs entirely on automated software — no person reads your messages. Both the source file and the output PDF are automatically deleted 7 days after the job is created. Deepgram receives only voice note audio bytes (not the chat text) if you use the $49+ voice transcription tier. No account creation is required.

Do I need to download an app?

No. The converter runs in any browser — mobile Safari, Chrome, Firefox, Samsung Internet. You access it at chattopdf.app and upload the export file directly from your phone or computer. There is no desktop application, no browser extension, and no app to install. The output PDF is delivered on-screen and by email.

Key takeaways

A WhatsApp to PDF converter turns the export ZIP from your phone into a formatted, sender-attributed PDF — no desktop app or USB cable needed.
ChatToPDF previews message count, senders, and price for free before you pay anything.
Five tiers from $7 to $99 per chat, one-time payment — no recurring billing.
Output formats are PDF (all tiers), XLSX, and CSV ($29 Premium and above).
Voice notes are transcribed inline on the $49 Premium+Voice tier using Deepgram Nova-3 — 17 high-accuracy languages, 30+ auto-detected.
Source files and output PDFs are automatically deleted 7 days after conversion — no data kept beyond that.
Works on both iPhone and Android exports; accepts .zip and .txt files directly from WhatsApp's Export Chat menu.

Transcribe WhatsApp Audio: Voice Notes to Text PDF (2026)

ChatToPDF — Fri, 29 May 2026 18:45:18 +0000

To transcribe WhatsApp audio, export your chat with media included, upload the ZIP to ChatToPDF, and select the $49 Premium+Voice tier. Every voice note becomes searchable text placed inline in conversation order — with the original sender's name and timestamp — using Deepgram Nova-3 across 17 high-accuracy languages including English, Spanish, Hindi, and Arabic.

TL;DR: To transcribe WhatsApp audio, export your chat with media included, upload the ZIP to ChatToPDF, and pick a voice-enabled tier. The $29 Premium per chat conversion does not transcribe voice notes — it preserves them as placeholder references. The $49 Premium+Voice per chat conversion runs Deepgram Nova-3 across 17 high-accuracy languages (English, Spanish, Hindi, Arabic, and 14 more) and covers up to 8 hours of audio in one chat. The $99 Power User per chat conversion uses the same Nova-3 model with no audio cap and priority queue processing.

What "transcribe WhatsApp audio" actually means (and why it's harder than it sounds)

People use the phrase "transcribe WhatsApp audio" to mean at least three different things. Some want to transcribe live voice calls — which WhatsApp does not expose through any developer API and which is technically a separate product category from what I'm describing here. Some want to convert audio files they've saved from WhatsApp to text, treating the .opus file as a standalone input. And some — the largest group — want every voice note inside an exported WhatsApp chat converted to readable text so the whole conversation makes sense as a document.

ChatToPDF is built for that third use case. The problem it solves is specific: you export a WhatsApp chat that contains both text messages and voice notes, and what you get back from WhatsApp is a ZIP containing a _chat.txt and a folder of media files. The _chat.txt has lines like <attached: 00000012-AUDIO-2024-03-15-09-22-31.opus> where the voice note belongs. Nothing converts those into readable text for you unless you build something to do it.

Here's the part nobody tells you: even when people find a transcription tool, they often run into a structural problem. The tools that handle generic audio files — upload an MP3, get text back — don't know where in a conversation that audio belongs. They transcribe the file but lose the context. You end up with a separate text block with no sender name, no timestamp, no indication of what was said before or after. For a legal matter, a business record, or a family archive, that context is the whole point.

What I built does the following: it reads the _chat.txt to understand the conversation structure, matches each .opus reference to the correct audio file in the ZIP, transcribes the audio, and inserts the transcript back at exactly the right position in the conversation — with the sender's name and the original timestamp preserved. The result is a single PDF where text messages and voice note transcripts alternate naturally, exactly as the conversation happened.

That's the problem this guide is about.

Voice notes are not files — they're an in-app stream

Voice notes are not a fringe feature. WhatsApp users send roughly 7 billion voice messages a day (Backlinko) across a base of about 3.3 billion monthly active users (DemandSage) — which WhatsApp has said makes it the largest voice-messaging platform in the world. (More in the full WhatsApp statistics breakdown.)

"WhatsApp users send over 7 billion voice messages a day." — WhatsApp

That volume is exactly why "I'll listen later" stops working once a chat has dozens of them. But getting those notes out as searchable text is harder than it looks, because of how WhatsApp stores them.

WhatsApp voice notes look like audio files inside the app — a waveform bar, a duration, a play button — but they aren't stored the way most people expect. When you record a voice note in WhatsApp by holding the microphone button, WhatsApp encodes the audio using the Opus codec and saves it as a .opus file in a private directory on your device. That directory is not accessible through normal file browsing on either iPhone or Android. You cannot navigate to it in the Files app and find your voice notes sitting there.

The only way to extract those .opus files is through WhatsApp's own Export Chat menu, with "Including Media" selected. When you export that way, WhatsApp packages the _chat.txt message log alongside the media folder — and that's where the .opus files appear. On iOS, they end up inside the ZIP. On Android, older versions of WhatsApp would export to a folder in internal storage; newer versions create a ZIP through the share sheet, matching iOS behaviour.

The Opus codec itself is worth understanding briefly because it explains why accuracy can vary. Opus was designed for voice-over-IP — low latency, good compression, good quality even at low bitrates. WhatsApp uses 16 kHz mono audio at around 16 kbps. The resulting files are tiny: a 60-second voice note typically weighs between 80 KB and 120 KB. That's efficient for mobile data, but 16 kHz mono at 16 kbps is not studio-quality audio. It's optimised for intelligibility across a mobile connection, not for transcription accuracy. Background noise, a voice recorded while driving, or someone speaking from across a room can push the effective quality down further.

Opus codec — The audio codec WhatsApp uses to encode voice notes: 16 kHz sample rate, mono channel, approximately 16 kbps bitrate. Opus was designed for voice-over-IP — maximising intelligibility at low bandwidth — not for high-fidelity recording. This compression level is sufficient for casual listening but below the quality threshold at which most speech-to-text engines were originally trained, which is why the transcription model's ability to handle compressed, mobile-recorded audio matters as much as its general accuracy.

This is why the transcription model matters. A generic speech-to-text engine trained on studio audio or podcast recordings will struggle with 16 kHz mono Opus compressed at 16 kbps. The engine I picked was chosen specifically because it handles this kind of audio well. More on that in the next section.

One more structural point: each WhatsApp voice note is a single-sender recording. WhatsApp's push-to-talk model means one person records, then stops, then the other person records their reply. This is actually a transcription advantage — unlike a recorded phone call where two voices overlap on the same audio track, each .opus file in a WhatsApp export belongs to exactly one sender. ChatToPDF uses the metadata from _chat.txt to attribute each transcript to the correct person, which is how you get a conversation that reads clearly even when both people swap back and forth in voice notes.

Convert your WhatsApp chat to PDF

The transcription engine I picked, and why

I evaluated several transcription APIs before settling on Deepgram as the engine behind ChatToPDF's voice transcription. The other serious contenders were AssemblyAI, Whisper (OpenAI's open-source model), and a handful of cloud providers' generic speech APIs. Here's the honest reasoning behind my choice.

Whisper is impressive for a free model, but I ran accuracy tests on a set of real WhatsApp .opus files across English, Spanish, Hindi, and Arabic, and it showed consistent weaknesses on code-switching (a voice note that mixes two languages mid-sentence) and on non-US English accents. It also doesn't offer commercial SLAs or uptime guarantees, which matters when paying users are waiting for their output.

AssemblyAI is genuinely good and I used it in an early prototype. The accuracy on English was comparable to Deepgram, but language support breadth and the API response consistency on Opus-encoded audio at 16 kHz mono made Deepgram the better fit for the multilingual use case I was building toward.

Word error rate (WER) — The standard metric for measuring transcription accuracy: the percentage of words in the output that are wrong relative to a reference transcript, calculated as (substitutions + insertions + deletions) ÷ total reference words × 100. A WER of 5% means roughly 1 word in 20 is incorrect. Lower is better. WER varies by language, speaker accent, background noise, and audio encoding quality — which is why the same model can achieve 3–5% WER on clean studio audio and 20–30% WER on a noisy outdoor recording.

Deepgram Nova-3 is the current-generation model with a word error rate of approximately 3–5% on clean, noise-free English audio and 8–15% on noisier recordings. Those numbers hold up on 16 kHz mono Opus, which is the format that matters for WhatsApp exports. Nova-3 is the model used for both the $49 Premium+Voice per chat conversion and the $99 Power User per chat conversion — the difference between those tiers is the audio cap (8 hours versus uncapped) and queue priority, not the model.

Where Nova-3 visibly outperforms older speech-to-text engines is in three places: regional accents (South African English, Indian English, Brazilian Portuguese), technical vocabulary (names, addresses, product terms that a generic model would mishear), and code-switched audio where a speaker moves between languages inside a single voice note. Those are the specific failure modes that motivated the engine choice. The $29 Premium per chat conversion does not include transcription at all — it preserves voice notes as placeholder references in the PDF without running the audio through any model.

The pipeline works like this: your ZIP lands on ChatToPDF's server, the .opus files are extracted, each is submitted to Deepgram's API over an authenticated HTTPS call with language detection set to automatic, and the transcript returns — typically within two to five seconds per minute of audio. The transcripts are then stitched back into the conversation at the correct positions before the PDF renders.

One deliberate choice in the pipeline: I do not pre-process or re-encode the .opus audio before sending it to Deepgram. Some tools convert Opus to WAV or MP3 first, reasoning that a different format might improve accuracy. In practice, Deepgram's API handles Opus natively and converting adds latency without improving results on this audio type. The raw .opus file goes straight to the inference endpoint.

Accuracy on the 17 languages ChatToPDF supports today

ChatToPDF's high-accuracy language tier covers 17 languages. These are the languages where I'm confident enough in the transcription quality to call it production-ready for documents, legal records, and business use:

English (en) — WER 3–5% on clean audio. Includes UK, US, Australian, South African, and Indian English variants. All English variants are handled by the same Nova-3 model on the $49 Premium+Voice per chat conversion.

Spanish (es) — WER 4–6% on $49 Premium+Voice per chat conversion. Handles Latin American and Castilian variants. Common homophone confusion (haya/halla, tubo/tuvo) is partially mitigated by context inference.

Portuguese (pt) — WER 4–7%. Covers Brazilian and European Portuguese. Code-switching between Portuguese and English is a common pattern in Brazilian WhatsApp chats; Nova-3 handles this well.

French (fr) — WER 4–6%. Standard and Canadian French.

German (de) — WER 4–6%. Compound nouns transcribe accurately on Nova-3, including long compound forms typical of business and legal vocabulary.

Italian (it) — WER 5–7%.

Arabic (ar) — WER 7–10%. Modern Standard Arabic transcribes well; dialectal Arabic (Egyptian, Gulf, Levantine) has wider variance. The $49 Premium+Voice per chat conversion is the recommended tier for Arabic voice notes.

Hindi (hi) — WER 6–9% on pure Hindi. Code-switched Hinglish (Hindi with English insertions) is where Nova-3 makes the biggest difference over older transcription engines — more on this in the sample transcript section below.

Indonesian (id) — WER 5–8%. One of the most common languages in ChatToPDF's user base, given WhatsApp's heavy penetration in Southeast Asia.

Turkish (tr) — WER 5–8%.

Russian (ru) — WER 5–8%.

Dutch (nl) — WER 4–6%.

Japanese (ja) — WER 7–10%. Katakana loanwords and proper nouns can introduce errors; overall accuracy is strong for conversational speech.

Korean (ko) — WER 6–9%.

Chinese (zh) — WER 7–10%. Mandarin. Regional dialects and tonal homophones can affect accuracy on challenging recordings.

Vietnamese (vi) — WER 7–10%.

Thai (th) — WER 8–12%. Tone markers and consonant clusters in fast speech are the main challenge.

Beyond these 17, Deepgram Nova-3 supports 30+ additional languages at a wider accuracy range. If your language is not in the high-accuracy list above, the $49 Premium+Voice per chat conversion still produces a best-effort transcript using Nova-3's broader language detection — just expect accuracy closer to 15–20% WER on challenging audio in the lower-tier languages.

Automatic language detection is on by default. ChatToPDF sends each .opus file to Deepgram without specifying a language, and Deepgram detects the dominant language in the first few seconds. This is accurate for single-language recordings. For heavy code-switching — a voice note that is genuinely 50/50 two languages — the detector picks one as primary and applies that model to the full clip. You'll see some accuracy loss on the secondary language in those cases.

Sample transcript: Spanish voice note → text (real example)

This is a real WhatsApp voice note transcribed at the $49 Premium+Voice per chat conversion level. The sender was a native speaker of Colombian Spanish, recorded on an Android device in a quiet indoor environment. Duration: 18 seconds. File size: ~28 KB in .opus format.

Original audio (paraphrased):
A casual voice note confirming a next-day appointment, expressing concern about the other person's health, and requesting a text reply if plans change.

Transcript output in the PDF:

🎤 [Voice note — 0:18] "Hola, ¿cómo estás? Te llamo para confirmar la cita de mañana a las tres de la tarde. Si no puedes, mándame un mensaje. ¿Vale?"

The sender is attributed in the PDF with the name from _chat.txt, the timestamp is the one WhatsApp recorded when the voice note was sent, and the transcript sits inline between the text messages immediately before and after it in the conversation.

A few things to notice about this example. The formal register marker ¿Vale? — closer to "Okay?" or "Alright?" in meaning — transcribed correctly rather than being confused with bale or omitted. The time expression a las tres de la tarde ("at three in the afternoon") rendered accurately, which matters for a scheduling confirmation where an error would be misleading. The spoken upward inflection on ¿cómo estás? was not ambiguous enough to produce a transcription error.

Where does Spanish accuracy break down? The most common errors I see are homophones: haya (subjunctive of haber) versus halla (from hallar, to find), tubo (tube) versus tuvo (past tense of tener). In fast casual speech, these are phonetically identical. Nova-3 uses surrounding context to infer the correct spelling most of the time, but it is not perfect. In a document that will be used as a legal record, I'd recommend a light human review of any voice notes where the transcript will be cited verbatim.

If you don't need transcription at all — for example, you only want the text messages converted to PDF and you're happy with placeholder references for the voice notes — the $29 Premium per chat conversion handles that case at a lower price point. The $49 Premium+Voice per chat conversion is the right step up when you need the actual spoken Spanish to appear as readable text in the document.

Sample transcript: Hindi (mixed Hinglish) → text (real example)

Code-switching — The linguistic practice of alternating between two or more languages within a single utterance or conversation — for example, a Hindi speaker inserting English words, phrases, or whole clauses mid-sentence (Hinglish). Code-switching is widespread in multilingual communities and extremely common in WhatsApp voice notes from South Asia, Southeast Asia, and Latin America. It is hard for speech-to-text engines because a model trained primarily on one language may misinterpret or drop words from the other, especially when the switch happens mid-phrase without a pause.

This is where Nova-3 distinguishes itself from earlier generations of speech-to-text engines. Hinglish — Hindi with embedded English words, phrases, and sometimes full clauses — is one of the most common real-world code-switching patterns I see in ChatToPDF's user base. Older STT engines (including the model Deepgram itself shipped two generations ago) miss approximately 15% of code-switched English insertions in a typical Hinglish voice note. Nova-3 closes most of that gap.

Here is a real transcript from the $49 Premium+Voice per chat conversion:

🎤 [Voice note — 0:22] "Yaar, kal meeting hai 3 baje, please attend karna. Project deadline aa rahi hai aur boss bahut strict hai."

Translated: "Mate, there's a meeting tomorrow at 3, please attend. The project deadline is coming up and the boss is very strict."

The code-switching here is characteristic: meeting, attend, project deadline, and strict are English insertions inside an otherwise Hindi sentence. Nova-3 transcribed all of them correctly. An older Deepgram model I tested against the same file produced miiting for meeting (phonetic Hindi rendering), omitted attend entirely, and produced project ka deadline with inconsistent capitalisation. That difference is what motivated the model upgrade in the pipeline.

The difference matters when you're using the transcript as a workplace record. If someone's manager is reviewing a voice note transcript as documentation of a project commitment and the word deadline doesn't appear in the text, that's not a minor accuracy quibble — it's a missing piece of information.

Sender attribution works the same as with Spanish: the name from _chat.txt appears in the PDF with the Deepgram transcript, and the timestamp from the WhatsApp metadata anchors it to the correct position in the conversation.

One note on Hindi specifically: if the voice note is in Devanagari-dominant Hindi (formal, written-speech-style Hindi with minimal English), accuracy is consistently strong across the supported tiers. The $49 Premium+Voice per chat conversion is the right entry point for any Hindi voice notes you want transcribed; the $99 Power User per chat conversion covers the same accuracy with no audio cap and queue priority. The $29 Premium per chat conversion preserves the voice notes as placeholders only — no transcription runs at that tier.

The $49 Premium+Voice tier — what's in it and what's not

The $49 Premium+Voice per chat conversion is the tier I built specifically for voice-heavy chats. Here is exactly what it includes and what it doesn't.

What's in the $49 Premium+Voice per chat conversion:

Deepgram Nova-3 transcription — the current-generation model with 3–5% WER on clean audio, strong accent handling, and reliable code-switching support
All 17 high-accuracy languages — English, Spanish, Portuguese, French, German, Italian, Arabic, Hindi, Indonesian, Turkish, Russian, Dutch, Japanese, Korean, Chinese, Vietnamese, Thai — plus 30+ more via Nova-3's automatic language detection
Up to 8 hours of audio in a single chat — covers the vast majority of voice-heavy conversations; if your chat exceeds 8 hours of total recorded audio, the $99 Power User per chat conversion lifts that cap
No message ceiling — no upper bound on the number of messages in the chat you're converting
Sender attribution on transcripts — every transcript in the PDF carries the WhatsApp sender name from the export metadata
Timestamps preserved — the original WhatsApp timestamp appears alongside each transcript, not the transcription time
Three output formats — PDF, XLSX, and CSV all included; the XLSX is useful if you want to filter or sort by sender and timestamp
Seven-day source file retention — encrypted at rest (AES-256), in transit (TLS 1.3)

What's not in the $49 Premium+Voice per chat conversion:

Real-time transcription — this tier processes already-recorded voice notes from an export ZIP; it is not a live transcription service (I explain why in the next section)
Custom vocabulary lists — you cannot upload a glossary of names or technical terms to improve accuracy on specific vocabulary; Deepgram's general-purpose model handles most names correctly but will occasionally mishear rare proper nouns
Speaker identification beyond WhatsApp metadata — within a single voice note where the sender records while another person is talking in the background, both are transcribed but only attributed to the WhatsApp sender. ChatToPDF does not run speaker diarisation on the audio itself.
Automatic translation — the transcript appears in the source language of the voice note. If a voice note is in Spanish, the transcript is in Spanish. ChatToPDF does not translate transcripts.

The tier above this one — $99 Power User per chat conversion — includes everything in $49 Premium+Voice per chat conversion plus priority queue processing and bulk-chat handling. If you're converting a single chat and speed isn't critical (most conversions complete in under three minutes), the $49 Premium+Voice per chat conversion is the right level.

For reference, the full tier stack: $7 Basic per chat conversion (text only, 5,000-message cap), $14 Standard per chat conversion (images, 25,000-message cap), $29 Premium per chat conversion (no cap, XLSX/CSV, voice notes preserved as placeholders), $49 Premium+Voice per chat conversion (Nova-3 transcription, 17-language high-accuracy, 8-hour audio cap), $99 Power User per chat conversion (Nova-3 transcription, no audio cap, priority queue, bulk scenarios).

Why I don't transcribe in real time (and won't add it)

This comes up often enough that it deserves a straight answer. People ask why ChatToPDF doesn't listen to voice notes as they arrive — transcribing each one the moment it's sent — rather than requiring a ZIP export after the fact.

The short version: WhatsApp doesn't give developers access to incoming messages or audio in real time. There is no official WhatsApp Business API endpoint that surfaces voice notes as they arrive. The only supported third-party access path is through the Export Chat mechanism, which is a point-in-time snapshot of the conversation history. Building real-time transcription on top of WhatsApp would require intercepting the app's local storage on the device, which is both technically fragile and outside the terms of WhatsApp's platform policies.

But there's a more practical reason I haven't tried to build around that constraint. The use case for transcribing WhatsApp audio is almost entirely retrospective. Someone receives thirty voice notes over the course of a dispute and wants a readable record. A business team uses voice notes for project updates and needs them searchable. A family sends voice notes for years and wants to archive them before a phone upgrade. None of these involve a "right now, as it arrives" requirement. They're all "I have a set of recordings I need converted."

Async batch processing is also more accurate. Real-time speech-to-text operates under latency constraints that push the model toward faster (and less accurate) inference. Deepgram's batch mode runs on the full audio file, which allows the model to use future context — what came after a word — to resolve ambiguous phonemes. On a 30-second voice note, the difference in WER between real-time and batch modes can be 2–4 percentage points. That's meaningful on the accuracy scale.

There's also the battery and network question. Running an open WebSocket connection that streams audio fragments to an inference API in real time would drain a phone battery noticeably over a long conversation. It would require an active internet connection for every voice note received, not just when you choose to convert. And it would create a continuous data flow of your conversations to a third-party server — which I'm not comfortable asking users to accept.

The export-and-upload model is slower in clock time — you have to wait until you're ready to convert, then run the export, then upload. But for the actual use cases people have, that's fine. Nobody is trying to transcribe a voice note they received three seconds ago for a real-time document. They're converting a chat they want to keep.

Convert your WhatsApp chat to PDF

Privacy: where your audio goes and where it doesn't

This is the part I want to be specific about because the nature of voice notes — audio recordings of real conversations — means the privacy stakes are higher than with text messages alone.

Here is the exact data path for a voice note submitted through the $49 Premium+Voice per chat conversion:

Step 1 — Upload. Your ZIP file is transmitted from your browser to ChatToPDF's server over HTTPS (TLS 1.3). The connection is encrypted in transit. The ZIP lands in a temporary processing directory, not in permanent storage, while extraction runs.

Step 2 — Extraction. The .opus files are extracted from the ZIP. Each file is matched to its _chat.txt reference by filename pattern. At this point, the audio files exist only on ChatToPDF's processing server.

Step 3 — Deepgram API call. Each .opus file is submitted to Deepgram's inference API over an authenticated HTTPS call. This is the one moment where audio bytes leave ChatToPDF's own infrastructure. Deepgram's data policy for API submissions specifies that audio submitted via the API is processed ephemerally — it is used to generate the transcript and then discarded. Deepgram does not retain API-submitted audio and does not use it for model training. The transcript text is what comes back.

Step 4 — Storage. The transcript is bundled into the PDF and stored encrypted at rest (AES-256) in AWS S3. The source ZIP, including the .opus files, is also stored encrypted for seven days.

Step 5 — Delivery. The PDF download link appears on-screen and in your email. The link is tied to your job ID. It is not guessable and is not indexed anywhere.

Step 6 — Auto-deletion. Seven days after the job is created, the source ZIP and the output PDF are deleted from storage automatically. This is a scheduled deletion job, not a manual process. There are no exceptions and no extensions.

Where your audio does not go: It does not go to any analytics platform. It is not used to train ChatToPDF's models (ChatToPDF does not train models). The text content of your voice notes is not visible to ChatToPDF staff — the processing is fully automated. No third party receives the text of your chat messages.

The only potential gap in this description is the Deepgram step. I can control what happens on ChatToPDF's servers completely. I cannot make representations about Deepgram's internal processes beyond what their public data policy says. If your voice notes contain information that is legally privileged or genuinely classified, I'd recommend having your legal team review Deepgram's enterprise data processing terms before uploading. For the vast majority of use cases — personal conversations, business team chats, family voice note archives — the standard pipeline is appropriate.

Edge cases: background noise, multiple speakers, voice-changing effects

Real WhatsApp voice notes are not recorded in sound-proofed studios. They're recorded in cars, kitchens, street-level meetings, and noisy cafés. Here's how each of those scenarios affects transcription accuracy, and what ChatToPDF does when accuracy drops to an unacceptable level.

Background noise by environment.

A voice note recorded in a quiet indoor environment — an office, a bedroom, a still room — performs at the accuracy rates I cited in the language section above: 3–5% WER on $49 Premium+Voice per chat conversion for the 17 high-accuracy languages.

A voice note from a busy indoor environment (a restaurant, a marketplace, a busy office) can see WER rise to 10–15% on the $49 Premium+Voice per chat conversion. Deepgram's Nova-3 applies noise cancellation during inference, which helps, but it does not eliminate the effect of competing audio.

An outdoor recording — street noise, wind, traffic — can push WER to 15–20% for the same tier.

A voice note recorded during a moving vehicle trip, with road noise and engine sound, is the most challenging single scenario I've tested. WER on these can reach 25–30% even with Nova-3. This is not a transcription engine limitation — it reflects the physics of audio captured on a phone mic at 16 kHz in a noisy environment. The audio quality going in determines the transcript quality coming out.

Multiple speakers within a single voice note.

As explained earlier, each WhatsApp voice note belongs to one sender — the person who pressed the push-to-talk button. ChatToPDF attributes the transcript to that sender. However, if the sender records while another person speaks audibly in the background (a phone conversation the sender is having, a TV playing in the background that includes voice, another person in the same room speaking loudly), Deepgram will transcribe the background voice too — it doesn't silently discard non-primary speakers. The transcript will interleave both voices, attributed to the WhatsApp sender. This can produce confusing output when the background speech is intelligible enough to transcribe.

ChatToPDF cannot currently isolate the primary speaker and discard background voices within a single .opus clip. Speaker diarisation — identifying which audio segments came from which person in the same audio file — is a feature I'm evaluating for a future tier, but it requires additional infrastructure and is not in the current release.

Voice-changing effects.

Some WhatsApp users send voice notes with audio effects applied — the deep-voice filter available in WhatsApp itself (Android), Snapchat-style voice changes before sharing, or just audio that has been pitch-shifted or reverbed before sending. Deepgram's model is trained on natural speech. Modified audio can push WER above 40% in extreme cases — a voice note sent through a deep-bass filter to make someone sound like a robot will mostly fail to transcribe.

For clips where confidence falls below the threshold I've set in the pipeline — currently defined as an average word-confidence score below 0.6 across the clip — ChatToPDF marks the transcript in the PDF as [low-confidence transcription — audio quality insufficient] rather than outputting a text block that might be taken as authoritative. You'll see this marker in the final PDF alongside the voice note's position in the conversation. It's better to flag an uncertain result than to return a plausible-looking transcript that is 40% wrong.

FAQ

What file format do WhatsApp voice notes use, and does ChatToPDF handle it?

WhatsApp records voice notes using the Opus audio codec at 16 kHz mono, saved as .opus files. ChatToPDF extracts .opus files directly from your WhatsApp export ZIP and submits them to Deepgram's inference API in their native format — no re-encoding step required. Both iPhone and Android exports produce .opus files, so the format handling is the same on both platforms.

How accurate is the WhatsApp audio transcription?

Accuracy depends on the tier and the audio quality. The $49 Premium+Voice per chat conversion uses Deepgram Nova-3, which achieves approximately 3–5% word error rate on clean, noise-free audio in the 17 supported high-accuracy languages. The $99 Power User per chat conversion uses the same Nova-3 model with no audio cap and priority queue processing. The $29 Premium per chat conversion does not transcribe — it preserves voice notes as placeholder references in the PDF. Background noise, accents, and code-switching between languages all affect accuracy on the transcribing tiers. I mark low-confidence clips (below a 0.6 average word-confidence score) as [low-confidence transcription] in the PDF rather than presenting a potentially misleading transcript.

Does ChatToPDF transcribe voice notes in languages other than English?

Yes. The $49 Premium+Voice per chat conversion and $99 Power User per chat conversion support 17 high-accuracy languages: English, Spanish, Portuguese, French, German, Italian, Arabic, Hindi, Indonesian, Turkish, Russian, Dutch, Japanese, Korean, Chinese, Vietnamese, and Thai. Both tiers use Deepgram Nova-3 across these languages and detect 30+ additional languages at a wider accuracy range. Language is detected automatically — you don't need to specify it before uploading. The $29 Premium per chat conversion does not transcribe voice notes — it preserves them as placeholder references in the PDF.

Do I need to do anything differently when exporting from WhatsApp if I want voice transcripts?

Yes — one critical step. When you export your chat from WhatsApp, choose "Including Media" rather than "Without Media." Voice notes (.opus files) are only included in the export when you select Including Media. If you export Without Media, the _chat.txt will contain references like <attached: 00000012-AUDIO-2024-03-15-09-22-31.opus> but no actual audio files. ChatToPDF cannot transcribe a voice note it doesn't have. See the WhatsApp chat export guide for the full step-by-step export process.

Will the voice transcripts appear in the right place in the PDF?

Yes. ChatToPDF reads the message log in _chat.txt to understand the conversation structure, matches each .opus reference to the corresponding audio file by filename, and inserts the transcript at exactly the position in the conversation where the voice note was sent. The sender's name from the WhatsApp metadata and the original timestamp both appear alongside the transcript. The output is a single document where text messages and voice note transcripts alternate in the correct chronological order.

What happens to my audio files after the transcription is complete?

Your audio files are stored encrypted at rest (AES-256) on ChatToPDF's servers for seven days after the job is created, then deleted automatically. The only third-party service that receives the audio bytes is Deepgram, and only during the transcription step — Deepgram processes audio submitted via API ephemerally and does not retain it. No human listens to your recordings. The transcripts themselves are deleted along with the source files at the seven-day mark. For more detail on the full data flow, see the WhatsApp to PDF privacy section.

Can ChatToPDF tell apart two different people speaking in the same voice note?

Not currently. Each WhatsApp voice note is attributed to the person who sent it, using the sender information from _chat.txt. Within a single voice note, if the sender and another person both speak (for example, the sender is having a phone conversation while recording), both voices are transcribed but attributed to the WhatsApp sender. ChatToPDF does not currently run speaker diarisation inside individual audio clips. For voice notes where background voices are audible and intelligible, you may see interleaved speech in the transcript.

How do I convert WhatsApp voice to text on Android?

On Android you have two routes. WhatsApp's built-in voice-message transcription (where available in your region) converts one note at a time — tap and hold a received voice note and choose Transcribe; the text shows inside the app but can't be exported. To turn many voice notes into a single searchable record, export the chat with Including Media and upload the ZIP to ChatToPDF — the $49 Premium+Voice per chat conversion transcribes every .opus note via Deepgram Nova-3 and places each transcript at its position in the conversation with the sender's name and timestamp.

How do I convert WhatsApp voice to text on iPhone?

On iPhone, WhatsApp's in-app transcription (when enabled under Settings → Chats → Voice message transcripts) reads back a single received note as text — handy for one message, but it stays inside the app and covers limited languages. For a whole chat's worth of voice notes in one document, export the chat (Including Media) and upload the ZIP to ChatToPDF. Both iPhone and Android exports produce the same .opus files, so the $49 Premium+Voice per chat conversion transcribes them identically into a dated, sender-attributed PDF.

Why is WhatsApp voice-to-text not working?

WhatsApp's built-in voice-to-text often fails for a few reasons: the feature isn't yet available in your country, the voice-message language isn't one the in-app transcriber supports, the note is too long, or transcripts are switched off in Settings → Chats. It also only handles received notes one at a time and can't export the result. If the in-app feature won't cooperate — or you need more than one note as text — export the chat and run it through ChatToPDF instead, which transcribes 17 high-accuracy languages from the exported .opus files regardless of the in-app feature's availability.

Is there a free WhatsApp audio to text converter online?

You can preview a WhatsApp audio-to-text conversion before paying — upload the export and ChatToPDF shows a watermarked preview so you can check the transcript quality and placement first. Full transcription runs on the $49 Premium+Voice per chat conversion. Free online "voice note to text" tools usually accept one clip at a time, strip out who said what and when, and can't read WhatsApp's .opus format directly — so for a multi-note chat they fall apart. ChatToPDF transcribes the whole conversation at once with sender names and timestamps intact.

Can WhatsApp transcribe voice notes longer than two minutes?

WhatsApp's built-in transcription automatically handles voice messages up to about two minutes. For anything longer you have to tap and hold the note and choose Transcribe to trigger it manually — and even then the transcript stays inside the app, can't be exported, and isn't saved to the chat log. There's also no way to run it across many notes at once. ChatToPDF has no per-note length cap: the $49 Premium+Voice per chat conversion transcribes every voice note in the export regardless of length, up to 8 hours of audio across the whole chat, and places each transcript inline with the sender's name and timestamp. A six-minute voice note and a ten-second one are handled the same way, in a single pass.

Can I translate WhatsApp voice messages to another language, not just transcribe them?

ChatToPDF transcribes — it converts the spoken audio into written text in the same language that was spoken. It does not translate that text into a different language. A Spanish voice note comes back as Spanish text; a Hindi note comes back as Hindi (or Hinglish) text. Transcription and translation are two separate steps, and conflating them is a common source of confusion. Across the 17 high-accuracy languages, the transcript reads as a faithful written version of what was said. If you need the result in another language, transcribe first with ChatToPDF, then run the PDF text through a translation tool of your choice — that order produces a far cleaner result than asking any tool to listen and translate in one pass, because translation works better on clean text than on raw audio.

Do I need to install an app to transcribe WhatsApp audio?

No. ChatToPDF runs entirely in the browser — there is nothing to download or install on your phone or computer. You export the chat from WhatsApp (Including Media), open chattopdf.app in any browser, upload the ZIP, and the transcripts come back as a PDF by email. The only software involved is WhatsApp itself, which you already have. This is deliberate: a voice-note archive you might need for a legal matter or a business record should not depend on a separate app staying installed and supported. WhatsApp's own built-in transcription is also no-install, but it reads one note at a time and can't export — see WhatsApp speech to text for where that feature's limits begin.

Key takeaways

To transcribe WhatsApp audio, export your chat with "Including Media" selected — the .opus voice note files must be inside the ZIP
The $29 Premium per chat conversion does not transcribe — it preserves voice notes as placeholder references; the $49 Premium+Voice per chat conversion runs Deepgram Nova-3 (3–5% WER on clean audio, 17 high-accuracy languages, up to 8 hours of audio); the $99 Power User per chat conversion is the same model uncapped with priority queue
Each transcript is inserted at the exact position in the conversation with the WhatsApp sender's name and original timestamp preserved
Code-switching languages like Hinglish need the $49 Premium+Voice per chat conversion or higher — Nova-3 closes most of the gap that older STT engines opened on mid-sentence English insertions in Hindi voice notes
Background noise is the biggest accuracy variable: studio conditions yield 3–5% WER; outdoor or vehicle recordings can reach 20–30% WER even on Nova-3
Audio submitted to Deepgram for transcription is processed ephemerally — it is not retained and not used for training; source files auto-delete from ChatToPDF servers after 7 days
Clips where average word-confidence falls below 0.6 are marked [low-confidence transcription] in the PDF rather than silently returning a potentially incorrect transcript

For the full chat-to-PDF workflow — including how to export on iPhone and Android, what the ZIP contains, and how all five tiers compare for non-voice conversions — see the WhatsApp to PDF guide. If you're on Android and need to move the export to a different device before uploading, the WhatsApp Android to iPhone transfer guide covers that process.

WhatsApp to PDF: Convert your chat in 30 seconds (2026)

ChatToPDF — Fri, 29 May 2026 18:45:03 +0000

To convert a WhatsApp chat to PDF, use WhatsApp's built-in Export Chat menu to save the chat as a ZIP file, then upload it to ChatToPDF. The tool parses your export and generates a formatted PDF with sender names, timestamps, and media inline. Pricing starts at $7 ($14 with photos and media), and you preview free before paying.

TL;DR: I built ChatToPDF because I needed a WhatsApp to PDF tool for a court case, and every existing option either charged a recurring fee or required a desktop with a USB cable. This guide walks through the export, the upload, the four PDF styles, and the voice-transcription tier — about 30 seconds end-to-end on a normal-sized WhatsApp to PDF conversion.

Why I built this

I needed a WhatsApp chat as a PDF for a legal matter. Not a screenshot stack. Not a forty-page print-to-PDF disaster. A proper document with dates, sender names, and readable timestamps that a solicitor or a court clerk could actually open and verify.

I spent two hours searching before I gave up on existing tools. Backuptrans is genuinely good software — but it requires a Windows or Mac desktop, a USB cable, and a licensed iTunes or Android backup. I had a phone. iMyFone is the same story: desktop app, cable, backup file. Wondershare charges a recurring fee per year. The iOS print-to-PDF workaround — long-press, share, Print, pinch to expand — works for maybe 40 messages. My chat had over 8,000.

Here's the part nobody tells you: every one of these workflows was designed when smartphones were secondary devices. They all assume you'll eventually get back to a computer. I was in a situation where I needed the document the same morning I searched for it. No cable, no desktop, no twenty minutes.

So I built ChatToPDF. The premise was simple: WhatsApp's own Export Chat menu already does the hard work. It packages your messages into a _chat.txt file and bundles any media alongside it. I just needed a web-based tool that could accept that export and turn it into a clean, court-ready PDF — without charging me every month for the privilege.

The scale of the problem is bigger than it looks. WhatsApp has roughly 3.3 billion monthly active users as of 2026 (DemandSage), who together send more than 100 billion messages a day, including about 7 billion voice messages a day (Backlinko). (For the full breakdown, see the WhatsApp statistics page.)

"WhatsApp users send over 7 billion voice messages a day." — WhatsApp

When even a sliver of those conversations need to leave the app — for a court bundle, a keepsake, or a record before switching phones — the only thing WhatsApp hands you is a raw .txt export. Turning that into a readable, dated, sender-attributed document is the entire gap ChatToPDF fills.

_chat.txt — The plain-text message log inside every WhatsApp export. It records each message in the format [DD/MM/YYYY, HH:MM:SS] Sender Name: message text. When you export with Including Media the _chat.txt sits at the root of the ZIP alongside any photos, voice notes, and documents; when you export Without Media it is delivered as a standalone .txt file.

The per-chat pricing came directly from that original frustration. I didn't want a recurring bill for a tool I might use twice a year. I wanted to pay for the conversion I needed today and nothing more. That's how it works: you pay once per chat you're converting, and that's the whole transaction.

Three years of real-world use have taught me a lot about edge cases: Arabic RTL chats, 80,000-message group threads, voice-note-heavy conversations, exports with encoding quirks from older Android versions. Every one of those has shaped what the tool does now. This guide covers the full workflow — from the Export Chat tap to the downloaded PDF.

Export the chat from WhatsApp

WhatsApp's Export Chat feature has been available on both iPhone and Android for several years, but it's not obvious to find. Most people tap into the chat settings looking for a "Download" button and come up empty. The actual path is a few taps deeper than you'd expect.

Export Chat (Including Media) — WhatsApp's built-in menu option that packages a conversation into a shareable file. Choosing "Including Media" produces a ZIP archive containing the _chat.txt message log plus every photo, voice note, video, and document exchanged in the chat. Choosing "Without Media" produces a smaller .txt file with message text and timestamps only, omitting all attachments.

1. Open the chat you want to export — Open WhatsApp and navigate to the individual or group chat you want to convert to PDF. You can export any chat you're a participant in — individual conversations, group chats, and even archived chats all work the same way. Make sure you're inside the chat thread itself, not on the main chat list screen.

2. Tap the chat name at the top — On iPhone, tap the contact name or group name displayed at the top of the screen. This opens the Contact Info or Group Info panel. On Android, tap the three-dot menu (⋮) in the top-right corner, then tap More. Both paths lead to the same Export Chat option, just through different menus. The contact name tap on iPhone is the step most people miss — many users try the three-dot menu on iOS and don't find the export option there.

3. Scroll to Export Chat — On iPhone, scroll down past the participants list, mute settings, and media thumbnails. Export Chat appears near the bottom of the Contact Info screen. On Android, after tapping More, Export Chat appears directly in the short submenu list. Tap it on either platform to trigger the format prompt.

4. Choose Without Media for fastest results — WhatsApp asks: "Without Media" or "Include Media." Without Media exports only the message text and timestamps — the resulting file is typically under 1 MB regardless of how long the chat is. Include Media bundles every photo, video, audio file, and document into a ZIP, which can reach hundreds of megabytes for active chats. Choose Without Media if you want speed and you're primarily interested in the text record. Choose Include Media if you need photos and attachments to appear inline in the PDF. ChatToPDF handles both — the $14 Standard per chat conversion includes image rendering; the $7 Basic per chat conversion covers text only. After your choice, WhatsApp's share sheet opens and you can save the file to your preferred location.

According to WhatsApp's official export documentation, the exported file format is a plain .txt file (named _chat.txt) which WhatsApp wraps inside a .zip when media is included. That .txt file is what ChatToPDF parses — so even if WhatsApp changes the ZIP structure in a future update, the underlying format is stable.

One practical note: iOS typically hands you the share sheet immediately after you confirm the media choice. Tap Save to Files and pick a folder you'll remember — something like iCloud Drive > Downloads. If you AirDrop it to yourself and then forget where it landed, you'll spend more time hunting for the file than the conversion takes. Android's share sheet offers Google Drive, Gmail, and a Files app option; any of these works as long as you can navigate back to the file in your browser within the next few minutes.

Choose ZIP or TXT

The file WhatsApp gives you depends on which export option you chose.

WhatsApp export ZIP — The archive file produced when you export a WhatsApp chat with the Including Media option. It contains the _chat.txt message log at the root plus every media attachment referenced in it — .opus voice notes, .jpg/.webp images, .mp4 videos, and any documents sent in the conversation. ChatToPDF accepts this ZIP directly and renders all supported media inline in the output PDF.

Without Media → a .txt file. The full message history is inside, with each message formatted as [DD/MM/YYYY, HH:MM:SS] Contact Name: message text. ChatToPDF accepts this directly — drag the .txt onto the upload zone and it parses immediately.

Include Media → a .zip file. The ZIP contains the _chat.txt plus every media attachment referenced in it. The ZIP can include .opus audio files (WhatsApp's format for voice notes), .jpg and .webp images, .mp4 videos, .pdf documents, and .vcf contacts. ChatToPDF extracts and processes all of these. Voice notes in .opus format are what the Premium+Voice tier transcribes via Deepgram; images are what the Standard tier renders inline.

Which should you upload? If you only need the text record — for a legal submission, a content audit, or archiving purposes — the .txt is smaller and faster. If you want photos, images, or audio transcripts in the output, upload the .zip. You can always export again with Include Media if you started with Without Media.

One edge case worth knowing: WhatsApp caps the media-included ZIP at 10,000 messages on some Android builds. If your chat is larger than that, WhatsApp will silently truncate the export. The text-only export does not have this cap. If you're working with a long group chat, check the message count in the exported _chat.txt against what WhatsApp's chat info screen shows. If they don't match, export in multiple date-range segments or contact me — there's a workaround for this via the WhatsApp chat export guide I put together separately.

Upload and preview

Drop your .zip or .txt onto the upload zone at chattopdf.app/upload. You'll see a progress indicator move through four stages: uploading, parsing, rendering, and ready.

The validation step is where ChatToPDF checks that the file is a genuine WhatsApp export. It runs a Zod schema check against the _chat.txt structure — looking for the expected [date, time] name: message format — and rejects files that don't match. This prevents accidental uploads of other text files and flags ZIP archives that don't contain a _chat.txt at all.

After validation, the parser runs. It extracts sender names, timestamps, message bodies, and media references. You'll see a free preview of the first ten messages before you pay anything. The preview shows the message count, the date range of the chat, the detected senders, and a rendered snippet of the first few lines in the style you've selected. This is useful for confirming that the encoding parsed correctly — particularly for chats that include Arabic, Hebrew, or emoji-heavy content.

Once you're happy with the preview, you select a tier and pay. The full PDF renders immediately after payment confirmation and the download link appears on-screen. You also get an email delivery with the download link, which is useful if you're on a slow connection or your browser closes before the render completes.

Convert your WhatsApp chat to PDF

The four PDF styles

ChatToPDF offers four visual styles for the rendered PDF. You pick the style in the upload flow before paying — the free preview shows a snippet in whatever style you've selected.

Green Bubble is the closest to what WhatsApp actually looks like on screen. Messages from the other sender appear in rounded green bubbles on the right (mirroring WhatsApp's green), and your own messages appear in light-grey bubbles on the left. Timestamps sit below each bubble. This style works well when you're sharing the PDF with someone who already knows what WhatsApp looks like — for example, a family member who needs to read the chat in a format that feels familiar. It's also the most visually engaging of the four.

Clean strips away the bubble design entirely. Messages are laid out as body text with the sender name in bold and the timestamp in a smaller secondary colour beside it. Each message is a simple text block, no border, no background. This is my most-recommended style for legal and business use. Courts, solicitors, and HR departments typically prefer documents that don't look like screenshots of an app. Clean outputs resemble a standard email chain or transcript.

Formal goes one step further toward document style. It uses a letterhead-style header at the top of the first page (chat name, date range, participant list), and each message is formatted with the sender name in small caps, the timestamp on the right margin, and the message body in indented body text. It reads like a deposition transcript. If you're submitting a WhatsApp chat as evidence in a formal legal proceeding, Formal is the style to pick — see the dedicated WhatsApp evidence court PDF guide for the full workflow on hash chains, metadata, and admissibility considerations. For HR, customer-service, and contract-trail use cases, the WhatsApp Business PDF guide walks through the bulk and team archiving patterns.

Book renders the chat as chronological prose. Sender names appear in italics before each message, and the text flows continuously like a novel. There are no bubbles, no tables, no timestamp columns — just the conversation as readable text. This style is surprisingly useful for long family or friend group chats that you want to preserve as a readable record, almost like a memoir of a conversation.

Each style produces a properly paginated PDF with page numbers and a header identifying the chat and date range. All four styles are available at every pricing tier.

Pricing tiers

ChatToPDF charges per chat conversion. You're paying for the specific chat you're converting today, not for access to the tool over time. There is no recurring billing.

$7 Basic per chat conversion covers text-only PDF export. Images, voice notes, and other media are noted in the PDF as [image omitted] or [voice note omitted] but not rendered. The message limit for Basic per chat conversion is 5,000 messages. If your chat exceeds that, the output is truncated at the 5,000-message mark.

$14 Standard per chat conversion includes full image rendering. Photos, stickers, and document thumbnails appear inline in the PDF, positioned at the point in the conversation where they were sent. The message limit for Standard per chat conversion is 25,000 messages — enough for most individual and small group chats.

$29 Premium per chat conversion removes the message ceiling entirely. There is no per-chat message cap on Premium per chat conversion. Voice notes are included in the PDF as placeholder text noting the audio file name, but transcription requires a higher tier. Premium per chat conversion also includes the XLSX and CSV spreadsheet outputs, which are useful if you need to analyse message frequency or filter by sender.

$49 Premium+Voice per chat conversion adds Deepgram Nova-3 voice transcription. Every .opus voice note in the export gets transcribed and inserted inline in the PDF, in the correct chronological position. Nova-3 supports 17 high-accuracy languages, plus 30+ more with automatic language detection — it handles code-switched conversations (a message in English followed by a voice note in Zulu, for example) without configuration. The $49 tier covers up to 8 hours of audio across the chat. No message cap.

$99 Power User per chat conversion covers bulk and group chat scenarios, priority processing queue, and all features from the tiers above. It's designed for situations where you have multiple chats to process at once or a very large group thread — 80,000+ messages — that benefits from dedicated queue priority. All outputs (PDF, XLSX, CSV, voice transcripts) are included.

Each tier covers exactly one chat conversion. If you convert three chats on three different days, you pay three times. The pricing is intentionally transparent because the alternative — a recurring fee that charges you every month whether you use it or not — is what I was trying to avoid when I built this.

For a focused breakdown of what the converter produces at each tier — output formats, the free preview step, speed, and privacy — see the WhatsApp to PDF converter page.

Voice transcription

Voice notes are one of the trickiest parts of WhatsApp exports. The _chat.txt file contains a reference like <attached: 00000012-AUDIO-2024-03-15-09-22-31.opus>, but the actual audio is inside the ZIP as a .opus file. WhatsApp uses the Opus codec for all voice notes — it's efficient and high quality, but it's not a format most people are familiar with (the WhatsApp audio format guide covers the codec in detail, including how to play .opus files directly).

The $49 Premium+Voice per chat conversion and the $99 Power User per chat conversion both use Deepgram's Nova-3 model to transcribe these .opus files automatically. The difference between the two tiers is the audio cap and queue priority — $49 covers up to 8 hours of audio in one chat, $99 is uncapped and runs in the priority queue. The transcription model is the same. Here's how the pipeline works:

ChatToPDF extracts all .opus files from the uploaded ZIP.
Each file is matched to its reference in _chat.txt using the filename and timestamp.
The audio is submitted to Deepgram Nova-3 with automatic language detection enabled.
The transcription returns within seconds for most clips (WhatsApp voice notes cap at 10 minutes per clip).
The transcript is inserted into the PDF at the exact position in the conversation where the voice note was sent, formatted as: 🎤 [Voice note — 0:32] "transcript text here".

Nova-3 is Deepgram's highest-accuracy model as of 2026. It handles mixed-language audio particularly well — a voice note that starts in Portuguese and switches to English mid-sentence will transcribe both halves correctly without you specifying languages in advance.

For chats where the sender speaks a language with a strong regional accent — South African English, Indian English, Brazilian Portuguese — I've found Nova-3 performs meaningfully better than generic transcription models. Accuracy rates vary by audio quality (background noise, distance from microphone) but on clean recordings the transcripts are typically ready to use without editing.

Voice notes that appear on the $7 Basic per chat conversion and $14 Standard per chat conversion are not transcribed. They appear in the PDF as [Voice note — 00000012-AUDIO-2024-03-15-09-22-31.opus]. If you later want to upgrade the same export to include transcripts, you'd need to re-upload and select a higher tier — there's no post-purchase upgrade at this time.

If you're weighing this against doing the transcription another way, the WhatsApp speech-to-text guide covers the built-in per-message transcription WhatsApp added natively, and the transcription tools comparison lines up the batch options — including the free ones — honestly.

One thing worth knowing: if a voice note file is missing from the ZIP — perhaps because you chose Without Media when exporting — the transcription tier still works for any voice notes that are present. You'll just see the placeholder text for any that are missing. If voice transcription is the primary reason you're converting, always choose Include Media during the WhatsApp export step.

For a deeper look at how the transcription works across languages and audio quality levels, I put together a dedicated guide at /blog/transcribe-whatsapp-audio, plus a step-by-step WhatsApp voice to text walkthrough.

iPhone vs Android differences

The WhatsApp export experience differs between iOS and Android in a few ways that are worth knowing before you start. Both platforms export the same _chat.txt format, but the path to get there and the default share-sheet behaviour are different.

iPhone export path:

Open the chat → tap the contact name or group name at the top of the screen
Scroll down past participants, media, and settings
Tap Export Chat
Choose Without Media or Including Media
iOS share sheet appears — tap Save to Files and choose a folder (iCloud Drive > Downloads is a good default)

On iPhone, the export produces either a .txt file (Without Media) or a .zip file (Including Media) and saves it wherever you directed the share sheet. The file is ready to upload immediately.

Android export path:

Open the chat → tap the three-dot menu (⋮) in the top-right corner
Tap More
Tap Export Chat
Choose Without Media or Including Media
Android share sheet appears — save to Files or Google Drive

On Android the path is slightly shorter (three-dot menu is one fewer tap than the contact name workaround on iPhone), but the share sheet behaviour varies more between Android manufacturers. On Samsung devices, the default is often to share to the Gallery or Messages app rather than Files — make sure you're saving to a location you can navigate back to in a browser.

Date format differences: WhatsApp exports use different date formats depending on your phone's locale settings. A UK iPhone formats dates as DD/MM/YYYY, a US Android as MM/DD/YYYY. ChatToPDF detects the format automatically by analysing the first ten timestamps in the _chat.txt file and resolving ambiguous dates (like 01/03/2024, which could be January 3 or March 1) using the overall date sequence. In most cases this is correct. If you notice a date parsing error in the preview, the locale selector in the upload flow lets you override the detected format.

Emoji rendering: iOS exports embed Apple Color Emoji into the _chat.txt as Unicode code points; Android exports typically use Noto Color Emoji. ChatToPDF renders both consistently using a fallback font chain that covers both emoji sets, so a conversation between an iPhone user and an Android user will display all emoji correctly in the output PDF.

For a full side-by-side breakdown of the two export flows including screenshots from WA v24.x, see /blog/whatsapp-android-to-iphone.

Privacy and 7-day deletion

When you're converting a personal conversation — especially one that involves a legal matter, a relationship dispute, or anything sensitive — you want to know exactly what happens to the file after you upload it.

Here's what happens, step by step:

Upload: Your file is transmitted over HTTPS (TLS 1.3) from your browser to the ChatToPDF servers. It never travels unencrypted in transit.

Storage: The uploaded file is stored on an AWS S3 bucket with server-side encryption (AES-256) at rest. The only access path to the raw file is through the processing pipeline — no employee or contractor can download raw chat files through a normal interface.

Processing: The conversion runs on a server with no human in the loop. Your messages are read by the parser software, not by a person. After rendering, the PDF is stored encrypted and linked to your unique job ID.

Delivery: You receive the download link on-screen immediately after processing and in an email. The link is tied to your job ID and is not guessable.

Deletion: Seven days after the job is created, both the source file and the output PDF are automatically deleted from storage. This is not manual — it's a scheduled deletion job that runs against every job record older than seven days. There's no exception for unpaid or incomplete jobs; those are deleted on the same schedule.

No third-party services receive the content of your chat. Deepgram receives the audio bytes of .opus voice notes (and only those files, not the full chat text) when you use the Premium+Voice or Power User tiers. Deepgram's data handling for API submissions follows their enterprise privacy policy, which prohibits training on API-submitted data by default.

There's no account creation required to use ChatToPDF. You don't create a profile, you don't log in, and I don't store any personally identifiable information beyond the email address you provide for download delivery — and that's only so I can send you the link if your browser closes before the render completes.

For organisations with specific data retention or compliance requirements, I'm happy to discuss custom processing arrangements via the contact form. The standard pipeline described above is what the vast majority of users need.

Common issues

Most conversions go through without a hitch. Here are the issues I see most often and how to handle them.

"File not recognised" error on upload. This usually means the ZIP doesn't contain a _chat.txt file, or the .txt file doesn't match the expected WhatsApp format. Re-export from WhatsApp — don't rename the file before uploading, and don't open and re-save it in a text editor (which can change the encoding from UTF-8 to UTF-16 and break the parser).

Date order looks wrong in the PDF. The parser auto-detects your date format but can misread ambiguous dates in short chats. Use the locale override in the upload flow (flag icon next to the file name) to set your locale manually. UK and Australia use DD/MM; US uses MM/DD.

Voice notes appear as placeholders on a Premium+Voice tier. Check that you exported with Including Media, not Without Media. The .opus files need to be inside the ZIP for transcription to work. See the voice transcription section above for the full explanation, or refer to /blog/transcribe-whatsapp-audio.

RTL text (Arabic, Hebrew) displaying incorrectly. ChatToPDF preserves Unicode bidirectional control characters (U+200E, U+200F) from the export, and the PDF renderer uses a right-to-left layout for messages where the dominant script is RTL. If you're seeing RTL content rendered LTR, use the contact form — this is usually a character encoding edge case that I can fix manually for your export within the same day.

Emoji showing as boxes. This can happen if you're viewing the PDF in a very old PDF reader that doesn't support Unicode emoji. Try opening the PDF in a modern browser (Chrome, Firefox, Edge, Safari) or Adobe Acrobat 2020+. The emoji are in the PDF correctly — the rendering issue is on the viewer side.

When the PDF won't behave — troubleshooting

Most of the time the export → ChatToPDF path just works. When something on the WhatsApp side goes sideways, here's the specific fix:

WhatsApp won't open a PDF you were sent — the five causes, in order
A PDF in WhatsApp won't finish downloading — storage, network, auto-download settings
Recovering a PDF that was in a WhatsApp chat — Media folders, backup restore, the durable fix
WhatsApp opens PDFs in the wrong app — setting the default reader on Android and iOS
"Cannot open file" on a WhatsApp PDF — partial download vs corrupt file
WhatsApp PDF won't open on iPhone — the iOS-specific checklist
Xiaomi / Redmi / Poco won't open a WhatsApp PDF — the MIUI battery and permission traps
Is there a "100 KB" WhatsApp PDF limit? — no, and here's the real number
Dual / cloned WhatsApp and a "missing" PDF — sandboxed clone storage
Emojis show as boxes in a converted WhatsApp PDF — font coverage, and how the ChatToPDF output renders them

ChatToPDF vs the alternatives

I'm not the only way to get a WhatsApp chat into a PDF. Here's an honest look at how ChatToPDF stacks up against the tools and workarounds people actually reach for:

Ways to get a WhatsApp chat into a document — key differences at a glance

Method	Sender names & formatting	Media inline	Searchable text	Effort	Best for
ChatToPDF (formatted PDF)	Yes — every message attributed with timestamps	Yes (Standard tier and above)	Yes	Low — upload ZIP, pay, download	Legal evidence, HR records, archiving, court submissions
Screenshots	Visible on screen but not structured data	Yes (if visible on screen)	No — images only	High — scroll and capture every screen manually	Quick reference for a handful of messages
Print to PDF (phone built-in)	Partial — app UI captured, no metadata layer	Only what fits on screen	Varies by viewer	Medium — works but breaks on long chats (~40 messages max)	Very short chats where formatting doesn't matter
Desktop app (e.g. Backuptrans)	Yes	Yes	Yes	High — requires desktop, USB cable, and backup file	Power users with technical setup already in place
Manual copy-paste	Only if you paste and format manually	No	Yes	Very high — impractical beyond ~20 messages	A few isolated quotes needed urgently

ChatToPDF vs iLovePDF (for WhatsApp) — why a general PDF toolkit can't do the chat job
ChatToPDF vs Smallpdf — same story, different toolkit
ChatToPDF vs Backuptrans — the powerful desktop tool, and what it costs you in time
ChatToPDF vs iMyFone — the recovery suite with a PDF export buried in it
ChatToPDF vs your phone's "Print to PDF" — the free workaround, and where it breaks down
ChatToPDF vs screenshotting the chat — why images of text aren't a real archive
WhatsApp to PDF converter online free — what's genuinely free versus where you need to pay $7+

FAQ

Does ChatToPDF charge a recurring fee?

No. Each pricing tier covers one chat conversion — $7 Basic per chat, $14 Standard per chat, $29 Premium per chat, $49 Premium+Voice per chat, or $99 Power User per chat. Converting a second chat means paying again for that second conversion. There is no recurring billing, no auto-renewal, and no account to manage.

Will ChatToPDF read my chat?

No human reads your chat. The conversion runs entirely on server software — the parser, the PDF renderer, and the Deepgram voice transcription (where applicable) are all automated. Source files are deleted automatically 7 days after the job is created. No training data is extracted. No third parties receive the text of your messages.

What's the largest chat I can convert?

The $29 Premium per chat conversion and above have no message cap. The $7 Basic per chat conversion stops at 5,000 messages and the $14 Standard per chat conversion stops at 25,000 messages. For very large group chats — 50,000 messages or more — the $99 Power User per chat conversion includes priority queue processing, which handles those more efficiently.

Does ChatToPDF work on iPhone and Android?

Yes. The export step runs on your phone using WhatsApp's built-in Export Chat menu. The upload and conversion run in any browser — mobile Safari, Chrome, Firefox, and Samsung Internet all work. You don't need to install anything. The download link is delivered by email as a backup in case your browser session ends before the render completes.

Can I get a PDF that includes photos and images from the chat?

Yes. Upload the ZIP export (choose Including Media when exporting from WhatsApp) and select the $14 Standard per chat conversion or above. Images appear inline in the PDF at the position they were originally sent. The $7 Basic per chat conversion is text-only and notes images as placeholders.

What if I only need part of a long chat?

WhatsApp's Export Chat exports the full conversation history without a date filter. If you need only a specific date range, upload the full ZIP and note in the contact form which date range you need — I can trim the output manually for you at no extra charge on any paid conversion. Alternatively, the XLSX output included in the $29 Premium per chat conversion lets you filter rows by date in Excel or Google Sheets.

How do I save a WhatsApp chat as a PDF on iPhone?

To save a WhatsApp chat as a PDF on iPhone: open the chat, tap the contact or group name at the top, scroll down and tap Export Chat, then choose Without Media (text only) or Including Media (adds photos and voice notes). When the iOS share sheet opens, tap Save to Files. Upload that file to ChatToPDF and you get a dated, sender-attributed PDF in about 30 seconds. The export step is identical on any iPhone running a current WhatsApp version.

How do I export a WhatsApp chat to PDF with media (photos and images)?

To export a WhatsApp chat to PDF with media, choose Including Media when you tap Export Chat in WhatsApp — this produces a ZIP containing the _chat.txt log plus every photo, video, and voice note. Upload that ZIP to ChatToPDF and select the $14 Standard per chat conversion or above. Photos appear inline in the PDF at the exact position they were sent. Choosing Without Media exports text only, so images can't be rendered.

Is there a free WhatsApp to PDF converter online?

You can preview your converted WhatsApp chat free online before paying — the upload, parsing, and a watermarked preview of the formatted PDF cost nothing, so you can confirm the layout, dates, and sender names are correct first. The full, watermark-free download starts at $7 per chat. Genuinely free browser tools (and your phone's Print to PDF) break on long chats and lose sender attribution; the free converter breakdown explains exactly where free runs out.

How do I print a WhatsApp chat to PDF?

The reliable way to print a WhatsApp chat to PDF is to Export Chat from WhatsApp and convert the file — your phone's built-in Print to PDF only captures what fits on screen and breaks past roughly 40 messages. Upload the export to ChatToPDF and you get a continuous, paginated PDF with every message, timestamp, and sender name intact, which you can then send to any printer. See the full walkthrough at print a WhatsApp chat to PDF.

Can I turn a WhatsApp chat into a printable book or keepsake?

Yes — indirectly, and it's one of my favourite uses. ChatToPDF gives you a clean, paginated PDF of the whole conversation with names, dates, and — on the media-capable tiers — the photos in place. That PDF is exactly the file a print-on-demand or photo-book service needs: upload it to an online book printer or a local print shop and you get a physical keepsake — a year of messages with a partner, a family group chat, a late relative's voice notes transcribed inline. ChatToPDF doesn't bind the book itself, but it produces the print-ready document, which is the hard part: getting every message out of WhatsApp in a readable, correctly ordered layout. If a printed book is the goal, pick a tier that includes media so the images come through.

How do I email a WhatsApp chat as a PDF?

Two easy routes. The simplest: export the chat, upload it to ChatToPDF, and the finished PDF is emailed to the address you enter at checkout — so it arrives in your inbox ready to forward to anyone. If you'd rather do it yourself, WhatsApp's Export Chat sheet also offers Mail or Gmail as a share target, but that emails the raw .txt/.zip export, not a readable document — the recipient still can't open it as a normal file. For an actual PDF someone can read, print, or file, convert first and then forward the PDF. This matters when you're sending a conversation to a solicitor, an HR contact, or an insurer who expects a document, not a chat-export file.

Can I export a WhatsApp chat to PDF without the photos (text only)?

Yes. If you only want the words — for a smaller file, a cleaner read, or because the images aren't relevant — export the chat from WhatsApp with "Without Media." That produces a text-only export, and ChatToPDF turns it into a PDF of just the messages, timestamps, and sender names, with no photos or attachments. It's the right choice for a long conversation where what was said matters more than what was shared, and it keeps the file small enough to email easily. If you later want the photos too, re-export with Including Media and convert again. One caveat: voice notes also need Including Media — Without Media strips the audio, so there is nothing to transcribe.

How do I save a WhatsApp chat to my computer (PC or laptop)?

WhatsApp won't let you export straight from a computer — the Export Chat option only exists in the phone app. So the reliable route is: on your phone, open the chat → Export Chat → choose Including Media (or Without Media for text only) → save or email the ZIP to yourself, then open it on your PC or laptop. To turn it into a readable document rather than a raw export, open chattopdf.app in your computer's browser, upload the ZIP, and download the finished PDF straight to your machine. The whole thing runs in the browser — nothing to install — and you end up with the conversation saved locally as a PDF you can file, print, or back up. WhatsApp Web and WhatsApp Desktop can't export a chat themselves, which is why the export still has to start on the phone.

How do I save my WhatsApp chats forever so I don't lose them?

WhatsApp chats are more fragile than they feel — they live on one phone, tied to one account, and a lost phone, a failed backup, or a closed account can take years of messages with them. WhatsApp's own backup helps you move to a new phone, but it's still the same data inside the same app, in a format only WhatsApp reads. To keep a conversation permanently and independently, export it (Export Chat → Including Media) and convert the ZIP to a PDF at chattopdf.app. A PDF is durable and universal: it opens on any device, prints, backs up to any cloud, and doesn't depend on WhatsApp continuing to exist. For the chats that genuinely matter, a one-time PDF is the closest thing to keeping them forever — and you can take it a step further and have it printed as a book.

Key takeaways

ChatToPDF converts WhatsApp chats to PDF in about 30 seconds — no signup, no recurring billing
Pricing is per-chat-conversion: $7 Basic per chat to $99 Power User per chat, one payment covers one chat
Voice notes are transcribed on the $49 Premium+Voice per chat conversion and $99 Power User per chat conversion via Deepgram Nova-3 (17 high-accuracy languages, plus 30+ more auto-detected)
Source files auto-delete after 7 days; no human reads the chat content
Works on both iPhone and Android exports — both .txt and .zip files are accepted

Convert your chat now — from $7 per chat

Related guides

WhatsApp to PDF converter — what the converter accepts, the output formats, and how each tier compares.
Free WhatsApp to PDF converter online — what's genuinely free, where free runs out, and how the free preview works.
How to export a WhatsApp chat — the export step in full, for iPhone and Android.
Export a WhatsApp chat on iPhone — the iOS-only workflow, every tap.
Transcribe WhatsApp voice notes — turn voice notes into searchable text inside the PDF.
Move WhatsApp from Android to iPhone — transfer the export across devices before converting.

DEV Community: ChatToPDF

Why WhatsApp Export Parsers Break: 14 Formats Tested

Why one WhatsApp timestamp regex fails

The timestamp families a parser meets

Normalize before matching

Use ordered format families

Treat ambiguous numeric dates honestly

Parse messages as state, not isolated lines

How the 24-case benchmark works

A safer implementation shape

Production checklist and limitations

FAQ

What format is a WhatsApp exported chat?

Can one regex parse every WhatsApp export?

How do I parse multiline WhatsApp messages?

Why does a parser swap the day and month?

Is the 24 out of 24 benchmark result universal?

Key takeaways

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

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

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

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

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

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

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

Exporting on iPhone

Exporting to your computer — the three honest options

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

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

Pricing and tier guidance

Related guides — exporting WhatsApp chats deeper

When the export itself goes wrong — troubleshooting

Key takeaways

FAQ

What does an exported WhatsApp chat actually contain?

How do I export a WhatsApp chat on iPhone?

What is the 40,000-message limit and how do I work around it?

Why do some contacts appear as phone numbers in my group chat export?

Can I export a WhatsApp chat directly from a computer?

Is it safe to upload my WhatsApp export to ChatToPDF?

Which ChatToPDF tier do I need for a group chat export?

WhatsApp Evidence Court PDF: Format, Authenticity, Hash Chains (2026)

Why courts accept WhatsApp chats as evidence — and what makes them refuse

The format checklist — what a usable evidence PDF must show

Authenticity: how to prove the chat was not edited

Metadata you must preserve — timestamps, sender phone numbers, chat title

Screenshots vs exports — why screenshots get rejected

The hash-chain workflow — from export to filed PDF

Group-chat evidence — the consent and admissibility issues

Edited and deleted messages — what shows up, what does not

Cross-jurisdiction notes — evidence rules differ widely

Court-evidence tools compared

Engaging a lawyer — when to stop self-prepping

Key takeaways

FAQ

Is a ChatToPDF-generated PDF legally admissible in court?

Should I use screenshots or the export for legal evidence?

What happens to deleted messages in the export?

How does the SHA-256 hash prove the chat was not edited?

Can I submit a group-chat export as evidence?

Which ChatToPDF tier should I use for evidence preparation?

Do I need to keep the original ZIP file after I have the PDF?

Can WhatsApp messages be used in small claims court?

Can I use a WhatsApp PDF for an insurance claim?

Can WhatsApp messages be used in a landlord or tenant dispute?

How do I present WhatsApp messages for a restraining order application?

WhatsApp statistics 2026: 3.3 billion users, and the export gap nobody talks about

The headline figures (2026)

Where the users are

The part that bites developers

How to export a WhatsApp chat to PDF in 2026: the honest options

First, get the export

Option 1 — Print to PDF from WhatsApp Web (free, fastest, ugly)

Option 2 — A dedicated web converter

Option 3 — Desktop backup software (Dr.Fone, iMazing, Backuptrans)

Option 4 — Turn the chat into a printed book (zapptales, Keepster)

Which one should you use?

Best WhatsApp Transcription Tools: An Honest Guide

How to choose a WhatsApp transcription tool

The main options compared

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