WhatsApp Export Size Limit: Why Long Chats Come Back Trimmed
You export a conversation that has been running for six years, open the file, and the first message is from last spring. Nothing warned you. Nothing failed. WhatsApp counts backwards from your newest message, takes as much as it is willing to hand over, and stops - and the part it leaves behind is the oldest part, which is usually the part you wanted most.
How the cap actually works
The export feature does not start at the beginning of a chat and work forwards. It starts at the most recent message and works backwards. When it hits its ceiling, it stops and packages up what it has. That single detail explains almost every complaint about short exports: the messages that go missing are never the recent ones.
The figures people report consistently are roughly 40,000 messages when you choose Without media, and roughly 10,000 when media is attached. One export guide describes the feature as allowing "up to 40,000 messages per chat without media, or up to 10,000 messages if media files are included", and another states it plainly in terms of recency: you get the 40,000 most recent messages. These numbers do not appear on WhatsApp's own help pages, so treat them as the practical ceiling that users hit rather than a published specification. They may shift, and they may behave differently on a very media heavy chat. What does not shift is the direction: newest first, oldest dropped.
WhatsApp's help page does hint at this. It tells you that if you pick Include media, "the most recent media sent will be added as attachments". Recent, not all. That is the official acknowledgement that an export is a slice of a chat rather than the chat itself.
Why the file looks broken rather than trimmed
The reason this catches people out is that there is no message, no warning and no note at the top of the transcript. A troubleshooting write up puts it well: when a chat exceeds the cap, WhatsApp "silently exports only the most recent messages up to the cap". The export appears to succeed. The zip opens. The transcript reads normally. It just begins in the middle of nowhere, halfway through a conversation about a dentist appointment, and your instinct is that something corrupted the file.
It did not. You are holding a complete, valid export of the newest portion of a chat that was too long to fit.
Four different causes that look identical
Before you accept that the cap is your problem, it is worth ruling out the other three, because they produce the same symptom - a file that is smaller or emptier than you expected.
The message cap. Covered above. The tell is that the transcript starts abruptly at a recent date and runs cleanly to the present.
The share destination's own limit. This one is sneaky, because it has nothing to do with WhatsApp. If you email a media heavy export to yourself, you are fighting your mail provider. Gmail caps attachments at 25 MB for personal accounts, applies that to the total attachment size, and will automatically strip an oversized attachment and replace it with a Google Drive link. Outlook is tighter still: Microsoft documents a 20 MB limit for internet email accounts such as Outlook.com or Gmail, and a 10 MB default for Exchange business accounts, with the limit covering the message as well as the attachment. A chat export with a few hundred photos in it will sail past all of those.
Advanced Chat Privacy. If someone in the conversation has switched this on, there is no export at all. WhatsApp's own announcement says the setting lets you "block others from exporting chats", alongside stopping media auto downloading to participants' phones and keeping messages out of AI features. The Electronic Frontier Foundation's analysis confirms it is off by default and set conversation by conversation rather than globally, which is why an export that worked for one chat last month can simply refuse for a different chat today. Nothing you do on your end will get round it.
Disappearing messages that already expired. WhatsApp's help page on the feature explains that messages can be set to vanish after 24 hours, 7 days or 90 days, and that the setting applies to new messages rather than earlier ones. Anything that expired before you tapped Export chat was already gone from the conversation. The export cannot include what was no longer there.
Choosing Without media lifts the ceiling fourfold
If your goal is the words - a full record of what was said and when - then exporting Without media is the single most effective thing you can do. It takes you from roughly 10,000 messages to roughly 40,000, which is four times the history in one file.
You do not lose the structure of the conversation by doing this. A breakdown of the export formats notes that the transcript is a plain UTF-8 text file, and that where media used to sit you get a placeholder instead. Every message line, every sender name and every timestamp survives. You simply see a note where a photo was, rather than the photo. If you want the images and voice notes as well, treat that as a separate job and see how to save the photos and voice notes from a chat, rather than trying to make one export carry everything.
Save it into Files or Drive, never email it to yourself
Emailing the archive to your own address feels like the tidy option, and it is the most common way people end up with nothing usable. Given the 25 MB and 20 MB ceilings above, a media export of a long chat will either bounce or arrive gutted.
On iPhone, choose Save to Files. On Android, share it into Drive or a file manager so it lands in local storage. An export normally arrives as a zip holding the transcript plus any media files alongside it, none of it encrypted, so once it is sitting in a folder you can copy it to a computer at your leisure. The step by step routes for both platforms are in how to export a WhatsApp chat on iPhone and Android.
One chat at a time, from the phone
There is no bulk export. Each conversation has to be exported separately as its own file, and it has to be done from the mobile app: WhatsApp Web and the desktop application do not offer the feature. WITNESS's documentation guide makes the same point, noting that the desktop and web clients do not allow mass download and export of messages and media, though you can save individual images from them.
So if you are archiving several long threads, budget a few minutes per conversation and work through them deliberately. That constraint is actually useful: it forces you to decide which chats genuinely matter rather than trying to hoover up everything.
Building an archive from repeated exports
Here is the honest workaround for a chat that is already over the cap. You cannot reach back past the ceiling, but you can stop the problem getting worse.
Export the chat today. That file covers everything from the cap boundary up to now. In six months, export it again. That second file overlaps the first and extends to the new present. Keep going, and you end up with a set of files, each covering a window, that together form a continuous record from the day you started. It is not elegant, but it works, and it means a conversation you care about never silently loses another year.
Name each zip with the export date so the windows are obvious later, and keep them together in one folder. Because each file is a valid export in its own right, savemychats renders each one as its own readable page or PDF, so you get a sequence of documents rather than one enormous file. If the end goal is something you can hold, turning a chat into a printable PDF works the same way per file. And if you are doing this because you are changing devices, read how to back up a chat before switching phones first, because the order of operations matters.
What none of this can do
savemychats works only on the file WhatsApp handed you, entirely in your own browser, with no upload to any server. That is the whole design, and it sets a hard boundary on what is possible.
It cannot recover deleted messages. It cannot read an iCloud or Google Drive backup, which are opaque encrypted files intended only for restoring WhatsApp onto a phone. It cannot bring back disappearing messages that had already expired. And it cannot restore anything WhatsApp trimmed out before the export file existed. If the transcript starts in March 2023, March 2023 is where your archive starts. No tool that reads the file can conjure up what the file does not contain.
Two related dead ends are worth naming so you do not waste time on them. First, an export is a reading copy, not a backup: as one export explainer puts it, the resulting text or spreadsheet file is not a WhatsApp backup file, and while you can open it outside the app you cannot import it so the messages reappear inside WhatsApp. Moving a conversation to a new phone needs WhatsApp's own transfer or backup and restore route. Second, requesting your account information will not help. WhatsApp's help page says the report covers account details and settings and "won't include your messages", and points you at chat export instead. It is requested from Settings, then Account, then Request account info, is unavailable on Web and Desktop, and takes around three days to arrive - three days for a file that contains none of the older messages you were hoping to find.
The practical takeaway is unglamorous but useful. Export sooner rather than later, choose Without media when the words are what matter, save into Files or Drive rather than your inbox, and repeat the export periodically so the archive keeps growing forwards even though it cannot grow backwards.
Ready to save yours? SaveMyChats turns a WhatsApp export into a beautiful web page or PDF — right in your browser, with nothing uploaded. Open SaveMyChats →