WhatsApp will not resize an oversized video for you, so the file has to fit before you send it. The app's own help pages give conflicting caps, from 16 MB to 100 MB, so compress with margin, and you can do that in a browser tab without uploading the clip anywhere.
A short 4K or 60 fps recording from a modern phone can run tens of megabytes, several times the lower figures the help pages list. Moving it to 720p at 30 fps, which is what WhatsApp itself targets on a fast connection, and a balanced quality level usually brings a phone clip into range while keeping it watchable on a small screen.
If the video is genuinely long or quality matters, sending it as a document is the better answer: the help pages allow documents up to 2 GB. The rest of this page covers what those pages actually say, the settings that work, and the cases where compression is the wrong tool.
What makes this annoying is that the failure is not loud. You pick a clip, tap send, and either the upload stalls or WhatsApp shows a message about the video being too long, with no size shown and no way to fix it inside the app. So you start guessing, and guessing wastes an hour.
Video Compressor
Set resolution, frame rate and quality, then download an MP4 that plays inline on a phone. The file never leaves your device.
What WhatsApp actually allows
WhatsApp does not publish one clean number, and its own help pages contradict each other. That is not a quirk of this article. It is what the pages say when you open them side by side.
| WhatsApp help page | Video limit it states |
|---|---|
| How to send media (faster connection) | 100 MB, 720p resolution |
| How to send media (slower connection) | 64 MB, 480p resolution |
| Can't send longer videos (troubleshooting) | 64 MB on all platforms, 32 MB at 360p on a slower connection |
| I get a message that my video is too long (older page) | 16 MB for all media, about 90 seconds to 3 minutes of video |
The newest phrasing is on the "How to send media" page, which describes a default video size limit rather than a hard wall and ties it to connection speed. The troubleshooting page uses a flat figure. The oldest page, still reachable, gives a third number. Because they disagree, treat the smallest figure you might meet as your target and leave room above it.
Two points are consistent, and they matter more than the headline number. First, WhatsApp compresses media when you share it, so the version your contact receives is already lower quality than the original, and the standard and HD options only change how much is applied. Second, WhatsApp will not resize an oversized file to fit: a video over the accepted size or length is refused rather than quietly reduced.
| What you are sending | What the help pages allow |
|---|---|
| Video shared in a chat | 100 MB at 720p on a fast link, 64 MB at 480p on a slow one, per the How to send media page |
| Video via the troubleshooting page | 64 MB on all platforms, 32 MB at 360p on a slow connection |
| Any media, older page | 16 MB, about 90 seconds to 3 minutes of video |
| Video in Status | 30 seconds maximum duration |
| Any file sent as a document | Up to 2 GB, and it is not compressed the same way |
Every figure above was read from WhatsApp's public help pages on 2026-10-01. These numbers have changed more than once, so the one your own app enforces is the only one that decides whether a send goes through.
How to compress a video for WhatsApp
- Add your video. Drop an MP4, MOV, WebM or MKV file into the compressor. It is read from your disk into the page, so nothing is uploaded anywhere. Clips under 200 MB and a few minutes long are the comfortable range.
- Set resolution and frame rate first. Choose 720p and 30 fps, which matches what WhatsApp targets on a fast connection. If the file is still too big, step down to 480p and then 360p, the levels the app falls back to on a slow link.
- Adjust the quality slider second. Leave it in the Balanced band unless you need more savings, then move it down one band at a time and watch the size the tool reports.
- Keep MP4 output. MP4 with H.264 plays inline on every desktop and mobile client, which is the point of sending a clip as media.
- Download and send. The tool shows the before and after size on each run, so you can re-run with different settings as often as you like. Your original file is untouched.
The loop is quick because nothing is destructive: change a setting, compress, read the new size. There is no daily limit and no account, so you can iterate until the file fits.
Which settings to use
The quality slider is not a percentage and it is not a size target. It maps to a video quality value called CRF, where a lower number means better quality and a larger file. The mapping is fixed, so you can reason about it:
| Slider label | Slider range | CRF | What it is for |
|---|---|---|---|
| Best | 100 | 20 | A very short clip you want clean |
| High | 75 to 99 | 28 to 20 | Clips that should look sharp at full screen |
| Balanced | 50 to 74 | 36 to 28 | The default. A sane starting point for most clips |
| Small | 25 to 49 | 43 to 36 | Fitting a tight cap on longer or busier footage |
| Smallest | 1 to 24 | 51 to 44 | Last resort. Blockiness becomes visible on motion |
Resolution and frame rate usually do more than the quality slider. Halving the resolution cuts the pixel count to a quarter, and halving the frame rate removes roughly half the frames the encoder has to describe. Both are easier to spare than sharpness, because a 720p clip at good quality reads as clean, while a 1080p clip at low quality reads as blocky on a phone screen.
| Your footage | Resolution | Frame rate | Quality |
|---|---|---|---|
| Phone video shot in 4K or at 60 fps | 720p | 30 fps | Small |
| Screen recording or tutorial | 720p | 30 fps | Balanced |
| Short clip under 30 seconds | Original | 30 fps | Balanced |
| Talking head, mostly static | 480p | 24 fps | Small |
Rather than guessing at megabytes, use the size the tool reports after each run. Compress once at 720p, 30 fps and Balanced, read the result, and step down only if it is still over the cap you are aiming for. That costs one extra run and removes the guesswork.
Send as media or send as a document
There are two ways to get a video across, and the choice matters more than any compression setting.
| As media, inline in the chat | As a document | |
|---|---|---|
| Size limit | The media cap, 16 MB to 100 MB depending on which page you read | Up to 2 GB |
| Compression | WhatsApp re-compresses it, so quality drops | Not compressed the same way |
| How it arrives | Plays inline in the thread | A file the recipient opens |
| Best for | Short clips meant to be watched in place | Long or higher quality video, or when fidelity matters |
If the clip is short and meant to be watched in the thread, compress it and send it as media. If it is long, or the quality matters, sending it as a document is the honest answer, and no amount of compression will beat it.
What this compressor cannot do
These are the cases where the tool stops being the right answer, and it is worth reading them before you invest time.
- It has no "make it exactly 16 MB" field. The compressor is quality first, so you choose a quality level and the size follows. Hitting a precise byte target needs two-pass encoding with a calculated bitrate, which is a desktop FFmpeg job rather than a browser one.
- Audio is fixed at 128 kbps. There is no audio bitrate control, so a music clip will not shrink through the audio track. It is fine for voice and acceptable for music, but it is not adjustable here.
- WebM output uses VP8, not VP9. The WebM path exists for compatibility. H.264 in MP4 gives a smaller file at the same visual quality, so MP4 is the better default for WhatsApp.
- Resolution only goes down. Choosing 1080p will not upscale a 720p source. It only stops anything taller than the selected height from passing through.
- It processes one file at a time. There is no batch queue here, so compressing several clips means running them in turn.
- The first run downloads about 30 MB. That is the FFmpeg engine, which is cached afterwards. It is the cost of doing the encoding on your machine instead of someone else's.
- Long files are slow. A few hundred megabytes will take a while, because the work happens on your device. Trimming first is always faster than compressing footage you are going to cut anyway.
- It cannot make WhatsApp accept a file it refuses for length. If the problem is duration rather than size, trimming is the fix, not compression.
Why compress in the browser instead of uploading
The obvious alternative is a converter site: send the video to a server, get a smaller one back. That works, and it is reasonable for a clip you do not mind handing over. It is a poor fit for what people actually send through WhatsApp, which is often a private chat recording, an internal screen, a document walkthrough or a family video.
| Aihangsoft | Upload-based converter | |
|---|---|---|
| Where the video goes | Stays in the browser tab | Sent to their servers |
| Account | Not needed | Sometimes required for larger files |
| Size and daily limits | None beyond your own memory | Often capped, sometimes watermarked |
| Setting control | Quality, resolution, frame rate, format | Usually a preset or a slider |
| Works offline | Yes, after the first load | No |
The trade-off is speed. A server with real hardware encodes faster than a laptop, and browser memory sets a practical ceiling on how long a video you can process. For the short clips the WhatsApp limits actually apply to, that trade-off is usually worth taking.