Two problems wearing the same costume
When someone tells me their WhatsApp zip export too big to deal with, I've learned to ask one follow-up: too big how? Because there are two completely separate things hiding behind that complaint, and they have nothing to do with each other.
The first is a literal file-size problem. You ran Export Chat, picked Including Media, and the ZIP that came out is 300 MB, 480 MB, sometimes more. Now your email client refuses the attachment, AirDrop chokes, and the upload bar on whatever tool you're using crawls. The chat itself is fine — it's the photos and videos riding along with it.
The second is a missing-messages problem, and people often describe that as "too big" too — as in "the chat is too big for WhatsApp to export it all". The export only goes back two years when you know the chat started in 2018. Nothing failed. WhatsApp just quietly truncated it. This is the 40,000-message cap, and it's the reason people search for "whatsapp export only some messages" and "whatsapp export not all messages".
I'll take both in turn. If you're not sure which one you've got: open the ZIP, check its size on disk, and open _chat.txt to look at the earliest timestamp. A huge ZIP with a recent first message means you've got both.
Problem 1 — the ZIP is huge (Including Media did that)
WhatsApp's Export Chat menu asks you one question that decides everything about file size: Without Media or Including Media.
Without Media writes only _chat.txt — every message in plain text, with photos and videos shown as <Media omitted> placeholders, and voice notes and documents replaced the same way. The result is tiny: a few thousand messages is usually well under 1 MB. It exports in seconds, emails without complaint, and uploads to any converter instantly. This is the right call when you only need the words — documentation, a record for a solicitor, archiving before you switch phones. The placeholder lines aren't pretty, but for a text record they're irrelevant.
Including Media bundles _chat.txt plus every attached file — images as .jpg or .webp, voice notes as .opus or .m4a, videos as .mp4, documents in their original format. On a chat where people have shared hundreds of photos and a few videos, that ZIP balloons fast. A media-heavy family group can hit 100 MB without trying; a years-long couple's chat full of photos and clips can pass 400 MB. That's the bloat. (There's also a quiet ceiling inside this option: WhatsApp only bundles media for roughly the most-recent 10,000 messages, so older photos still show as <Media omitted> even on an Including Media export — another reason the ZIP isn't quite the complete archive people assume.)
So how big is too big? Roughly: anything over 25 MB is awkward for most email providers (Gmail caps attachments at 25 MB and quietly converts bigger ones to a Drive link; Outlook around 20 MB). AirDrop has no hard limit but gets flaky over a couple hundred megabytes on a weak connection. If your ZIP is in the tens or hundreds of megabytes and you tried to email it, that's your whole problem — the file is fine, the transport isn't.
The fix is one of two things. If you don't actually need the photos in your end result, re-export with Without Media and you're done — tiny ZIP, no transport drama. If you do need the photos, keep the Including Media ZIP and move it the right way, which is the next section. WhatsApp's own help on exporting chat history documents the Without/Including Media choice but doesn't mention either size implication — you find that out the hard way. My export-mechanics walkthrough has the full menu path on every platform if you need to redo the export from scratch.
Moving a big ZIP off your phone without it failing
If you're keeping the Including Media ZIP, the trick is picking a transfer method that doesn't have a size cap or a corruption risk. Email is the worst choice for a big one. Here's how the options actually stack up.
On iPhone, when the share sheet appears after Export Chat, tap Save to Files — pick iCloud Drive or On My iPhone, choose a folder you'll remember, and the ZIP lands there at full size with no truncation. From a Mac, AirDrop the same file straight across; it handles hundreds of megabytes fine on a good connection. For very large exports, plug the iPhone into a computer and pull the file via Finder. The cluster-5 guide how to export a large WhatsApp chat on iPhone walks the Files-and-AirDrop route step by step — that's the one I point people to when the ZIP is genuinely heavy.
On Android, the share sheet after Export Chat usually offers Save to Drive or your file manager directly — Google Drive eats a 500 MB ZIP without blinking, then you download it on your computer from drive.google.com. A USB cable is the other reliable path: plug in, set the phone to file-transfer mode, and copy the ZIP out of the download/share location. What you want to avoid on both platforms is emailing it (attachment caps truncate the file or refuse it) and re-zipping or renaming the ZIP after the fact — both can leave you with a "damaged" archive that won't open.
One thing that quietly avoids all of this: if your destination is a PDF, you don't have to get the ZIP onto a computer at all — you can upload it from your phone. ChatToPDF accepts the WhatsApp export ZIP directly in a mobile browser, so a 300 MB Including Media ZIP goes straight from your phone's Files app to the upload zone with no email hop in the middle.
Problem 2 — the export is truncated at ~40,000 messages
This is the other thing people mean by "too big" — the chat is so large that WhatsApp won't give you all of it. And it won't tell you.
Here's the part nobody warns you about: WhatsApp caps every export at roughly 40,000 messages. Not a soft warning, not a "this chat is large, continue?" dialog — it just takes the most-recent 40,000 messages, writes them to _chat.txt, and stops. If your chat has 70,000 messages over six years, the exported file covers only the most-recent 40,000. The older 30,000 simply aren't in it. (The figure has historically sat around 40,000; treat "whatsapp 40000 message limit" as the working number rather than a hard constant — WhatsApp has never published it.)
How to tell it happened: open _chat.txt in any text editor and look at the very first timestamp. If a chat you know started in 2018 only shows messages from 2022 onward, you hit the cap. That's the entire diagnosis — there's no error message to find.
The workarounds, honestly:
- Accept the cap. For most personal cases — archiving before a phone switch, handing a chat to a lawyer — 40,000 messages is several years of normal daily messaging. Only very active group chats and very long couple's chats bump into it at all.
- Export sub-ranges by archiving or clearing. WhatsApp always exports the most-recent N messages, so if you clear (or archive) the recent slice, the next export reaches further back. This is destructive and fiddly — you'd clear recent messages from your phone, export the now-oldest 40,000, then restore from backup — and I only suggest it if the old history genuinely matters. There's no date-range picker; this is the closest WhatsApp gives you.
- Read the database directly. Tools like Android Backup Extractor (Android, needs root or a full local backup) or iMazing (iPhone, needs an unencrypted-ish backup) can pull the full message store. That's a real project, not a five-minute fix.
Going forward, the practical move is to export early and export often — if every new export overlaps with your last one, you build a continuous archive even though no single export reaches all the way back. The export-mechanics pillar covers the cap and the locale-specific date formats in more depth; if your current export stalls on "Preparing file…" rather than truncating, that's a different failure — see WhatsApp chat export stuck on preparing.
What ChatToPDF does with a large WhatsApp export
Once you've actually got a ZIP — huge or otherwise — converting it to a clean, sender-attributed PDF is the easy part, and the tier you pick scales with how big it is.
$14 Standard per chat conversion handles exports up to 25,000 messages and embeds the photos inline, so an Including Media ZIP comes out as a PDF with the images in place rather than <Media omitted> placeholders. This covers the large majority of individual chats — 25,000 messages is two to three years of steady conversation. Upload the ZIP straight from your phone or computer; you get a free preview of the first ten messages before paying.
$29 Premium per chat conversion removes the message-count ceiling entirely and takes the full media bundle, so a chat that's pushing the 40,000-message cap on the WhatsApp side converts whole. It also adds an XLSX/CSV export alongside the PDF if you want the messages as structured data.
$99 Power User per chat conversion is the one for several large chats at once — a business dispute with five long conversations, a family archive across multiple groups. No message ceiling, full media, priority-queue processing, and you handle each chat as its own conversion under one heavier tier rather than paying the per-chat rate five times. (The whatsapp-to-pdf pillar note on output sizing covers why even a media-heavy chat PDF stays well under WhatsApp's own 100 MB send limit, if you're planning to share the result back through WhatsApp.)
None of these care that your ZIP is 480 MB — the size that breaks email doesn't break the upload. And if the export was truncated at 40,000 messages on WhatsApp's side, no tool can recover what isn't in the file; ChatToPDF converts faithfully whatever the ZIP actually contains, cap and all.
Key takeaways
- "WhatsApp zip export too big" means one of two things: a literally huge ZIP (you picked Including Media on a photo-heavy chat) or a truncated export (the ~40,000-message cap cut off older history) — check the ZIP size and the first timestamp in
_chat.txtto tell which - Without Media exports
_chat.txtonly — usually under 1 MB; Including Media bundles every photo, video and voice note and can pass 400 MB on a media-heavy chat - Anything over ~25 MB is awkward for email (Gmail caps attachments at 25 MB) — move a big ZIP via Save to Files, Google Drive, AirDrop, or a USB cable instead, and never re-zip or rename it
- WhatsApp silently caps an export at roughly 40,000 messages with no warning — there's no date-range filter; the only real options are accepting the cap, archiving the recent slice and re-exporting, or reading the database with a desktop tool
- Going forward, export early and often so each export overlaps the last and you build a continuous archive
- ChatToPDF takes the ZIP directly (no unzipping, upload from your phone): the $14 Standard per chat conversion handles up to 25,000 messages with inline photos, the $29 Premium per chat conversion removes the ceiling, the $99 Power User per chat conversion is for batching several large chats
FAQ
My WhatsApp ZIP export is too big to email — what do I do?
That's the Including Media option doing its job: it bundles every photo, video and voice note alongside _chat.txt, so a media-heavy chat's ZIP can run to hundreds of megabytes. If you don't need the photos in your end result, re-export with Without Media and you'll get a tiny text-only ZIP. If you do need them, keep the big ZIP and transfer it via Save to Files (iPhone), Save to Drive or a USB cable (Android), or AirDrop to a Mac — anything except an email attachment, since most providers cap those around 20–25 MB. To turn it into a PDF, upload the ZIP straight from your phone to chattopdf.app; the $14 Standard per chat conversion handles it with photos inline.
Why does my WhatsApp export only have some messages, not all of them?
WhatsApp caps every export at roughly 40,000 messages — it takes the most-recent 40,000, writes them to _chat.txt, and stops, with no warning or truncation notice. If a chat you know started years ago only shows recent messages in the exported file, you hit the cap. There's no date-range filter to work around it; your options are accepting the cap (40,000 messages is several years of normal messaging), clearing the recent slice and re-exporting to reach further back (destructive, restore from backup afterward), or using a desktop tool like Android Backup Extractor or iMazing to read the message database directly.
What's the WhatsApp 40000 message limit and is there a way around it?
It's an undocumented ceiling on the Export Chat feature: an export contains at most about 40,000 messages, always the most-recent ones. WhatsApp has never published the exact figure, but 40,000 is the working number. There is no built-in workaround — no date range, no "export from this date" option. The honest fixes are to accept it (it's enough for most personal archives), to archive or clear recent messages so the next export reaches older history, or to extract the full database with a third-party desktop tool that needs a local backup or root access. Going forward, exporting frequently so each export overlaps the last builds a continuous record without ever needing a single export to span everything.
Can ChatToPDF handle a 500 MB WhatsApp export ZIP?
Yes — the file size that breaks an email attachment doesn't break the upload. ChatToPDF accepts the WhatsApp export ZIP directly, including large Including Media bundles, and you can upload it straight from your phone's Files app. The $14 Standard per chat conversion handles exports up to 25,000 messages with photos embedded inline; the $29 Premium per chat conversion removes the message ceiling for the very largest single chats; the $99 Power User per chat conversion is for batching several large chats at once. What no tool can do is recover messages WhatsApp truncated on its side — if the export hit the ~40,000-message cap, the PDF reflects whatever the ZIP actually contains.
I'm Paul. I built ChatToPDF after watching a friend try to print a 4-year-old WhatsApp chat across forty-something one-page PDFs. I write here about exporting WhatsApp chats, converting them to PDF, transcribing voice notes, and the messy edge cases nobody else writes about (40,000-message export limits, broken emojis, RTL Arabic, Samsung Secure Folder).