WhatsApp has two separate paths for sending a video, and they do not share a size limit. Almost every "video too large" problem comes down to using the path with the small cap when the path with the large cap would have worked.
That is also why the advice you find online contradicts itself. Search this problem and you will be told the limit is 16MB, or 64MB, or 100MB, or 2GB — from pages that are each describing a different path without saying so.
The two paths
When you attach a video, WhatsApp offers you a choice that looks cosmetic and is not:
- Gallery / Camera (the media path). The video is sent as a video: it plays inline in the chat, shows a thumbnail, and scrubs without downloading. To make that work, WhatsApp re-encodes it. This path has a much lower size ceiling.
- Document (the file path). The video is sent as a file. No inline preview — the recipient taps to download it, then opens it in their own player. WhatsApp does not re-encode it.
The file path's ceiling is the one WhatsApp has stated publicly: "you can now send files within WhatsApp up to 2GB in size at a time, protected by end-to-end encryption" — an increase, in WhatsApp's words, "from the previous limit of 100MB."
The media path's ceiling is much lower. WhatsApp does not publish it as prominently, and the third-party numbers floating around disagree with each other, so check the current value in WhatsApp's official Help Center rather than trusting a blog post — including this one.
What this means in practice
If your goal is "get this video to this person intact," send it as a document. Two gigabytes covers essentially any phone recording, and the file arrives byte-for-byte identical — no re-encode, no quality loss.
The trade you are making is real, though, and worth stating plainly:
| Media path | Document path | |
|---|---|---|
| Plays inline in chat | Yes | No — must download first |
| Thumbnail preview | Yes | No |
| Re-encoded by WhatsApp | Yes | No |
| Size ceiling | Low (see official docs) | 2GB |
For a clip you want someone to glance at in the chat, the media path is the better experience — if it fits. For a wedding video, a screen recording, or anything you want to survive intact, the document path is correct and no compression is needed at all.
What "not re-encoded" actually buys you
"The file arrives unchanged" sounds like a technicality. It is the whole difference, and it is worth being concrete about what survives.
Generational loss stops. Every lossy re-encode discards detail permanently, and the damage accumulates. A clip that has already been exported from an editor has been encoded once. Send it through a path that re-encodes and it has been encoded twice — and if the recipient forwards it onward, three times. Each pass works from the previous pass's artefacts, not from your original. The document path takes your file out of that chain entirely.
The things that degrade first are the things people notice. Fine texture, gradients in skies and skin, and fast motion are where a second encode shows up soonest — as banding, smearing, or blocks that appear only when something moves. A talking head on a plain background survives re-encoding well. Anything with grain, confetti, water, or a hand-held camera does not.
Metadata and audio come through intact too. Timestamps, rotation flags, and the original audio track arrive as they were, which matters if the video is going to be edited further rather than just watched.
This is why "send as a document" is the right default for anything you would be annoyed to lose quality on, and why it is not merely a workaround for a size limit.
How to send as a document
The exact wording differs slightly by platform, but the shape is the same: in the chat, tap the attachment / paperclip control, and choose Document rather than Gallery, Photos, or Camera. Then browse to the video file itself.
The step people miss: on phones, videos live in the photo library, and the Document picker browses files. You may need to use your phone's file manager (or the "Browse" option inside the picker) to reach the video rather than expecting it in a photo grid.
When you actually do need to compress
The document path does not help in two cases: the recipient genuinely wants to watch it inline, or the file is over 2GB. Then the video has to get smaller before WhatsApp sees it.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs inside your browser tab. The file is read from disk, re-encoded locally, and handed back — it is never uploaded to a server, so there is no second upload limit standing between you and fixing the first one.
Compressing it yourself is also better than letting WhatsApp do it, for a reason that is not obvious: if you hand WhatsApp a file that already fits, it has far less work to do. Feed it a 4K original on the media path and it will compress aggressively, on its own terms, with no say from you. Hand it something already sized for a phone screen and the result looks much closer to what you chose.
If you want to understand which settings actually matter, how to compress a video without losing quality covers the trade-offs — the short version is that resolution and bitrate do nearly all the work, and reducing either is far less visible than people fear.
If it still will not send
Size is the usual cause but not the only one. Worth ruling out, roughly in order of how often they bite:
- Codec. iPhones record in HEVC (H.265) by default. It is efficient, but not universally handled. Re-encoding to H.264 in an MP4 container is the standard fix — the compressor above outputs exactly that, so it addresses codec and size in one pass. For a QuickTime file off a Mac or iPhone, MOV to MP4 does the same.
- Duration. There are limits on how long a video can be on some send paths. WhatsApp shows a distinct "too long" message rather than "too large" when this is what happened — read the error text carefully, because the two have different fixes.
- Storage and connection. A large transfer needs free space on the device and a stable connection. Wi-Fi is worth switching to before blaming the file.
FAQ
What is WhatsApp's file size limit? It depends on the path. Sent as a document, WhatsApp states a 2GB limit, up from a previous 100MB. Sent as a video through the media path, the ceiling is considerably lower — check WhatsApp's official Help Center for the current number, since third-party pages disagree with each other on this one.
Does sending as a document reduce quality? No. That is the point of it. The file arrives as you sent it, with no re-encoding. The cost is that it will not preview or play inline in the chat.
Why does WhatsApp make my video look bad? Because on the media path it re-encodes your video so it can stream inline, and it makes that decision without you. Compressing it yourself first, or sending it as a document, both take that decision back.
Can I send a video longer than the duration limit? Sending it as a document sidesteps the media path entirely, which is generally the practical answer. If the video is long and large, trimming or compressing first is the more reliable route.
Is it safe to use an online compressor for personal videos? It depends entirely on whether the tool uploads your file. Most "online video compressor" sites send your video to their servers and keep a copy for some period. The compressor on this page runs in your browser and never uploads anything. See all Clapr tools for the rest.
The 2GB document limit is quoted from WhatsApp's official announcement. Media-path limits are deliberately not given a number here because we could not verify one against an official source — check WhatsApp's Help Center directly.
