How to compress video for WhatsApp (2026 guide)

Q: What codec does WhatsApp use?

WhatsApp re-encodes videos to H.264 (AVC) inside an MP4 container with AAC audio. If you upload H.264 already inside the size cap, WhatsApp ships it as-is — quality stays intact. Upload H.265 or HEVC and WhatsApp will re-encode it down to H.264, losing quality in the process.

Q: Will compressing my video lose quality?

Yes, but you control how much. H.264 at CRF 23 is visually lossless to most viewers; CRF 28 is mildly soft but acceptable for messaging; CRF 32 starts to look obviously compressed. Aim for CRF 23 first and only push higher if you're still over the size cap.

Q: Why does WhatsApp make my video look so bad?

Because WhatsApp's own server-side compression is tuned for the worst-case network. When you upload a 4K HEVC source, WhatsApp re-encodes it to 480p H.264 at a low bitrate. Pre-compressing to 1080p H.264 under the 16 MB cap means WhatsApp ships your version instead of mangling it.

WhatsApp’s 16 MB mobile cap is the most common reason people search for a desktop video compressor. The platform’s own in-app compression is tuned for the worst-case network: phone-cellular-in-a-tunnel. That’s why your 4K iPhone clip arrives on the other side looking like a smudge.

The fix is to compress the video yourself, before WhatsApp gets to it. This guide walks the exact math, the codec choice, and the click path in Video Forge to get there.

TL;DR

WhatsApp’s per-file cap is 16 MB on the mobile app and 100 MB on WhatsApp Web/Desktop. To stay under 16 MB at decent quality on a one-minute clip: H.264, 1080p, CRF 23, AAC audio at 128 kbps. That math gives you about 1.9 Mbps total bitrate. At higher CRF (lower quality), you can fit longer clips. Open Video Forge, drop the file in, click the WhatsApp destination tile, hit Convert. The app does the bitrate math for you.

The actual size limits

WhatsApp’s video upload limits, verified as of May 2026:

Channel	Max file size	Notes
Mobile (iOS / Android)	16 MB	Hard cap. Files above this are rejected.
WhatsApp Web	100 MB	But the recipient on mobile still sees a compressed re-encode.
WhatsApp Desktop	100 MB	Same caveat as Web.
WhatsApp Business API	16 MB	For media messages over the Cloud API.

A few things worth noting before you start compressing:

The cap is the upload cap, not a quality cap. A 5 MB H.264 clip will pass through; a 15 MB clip will pass through. WhatsApp’s own re-encode step kicks in mostly when the source is HEVC, ProRes, or anything with weird metadata it doesn’t want to ship as-is.
AVI, MKV, and MOV are not allowed. WhatsApp only accepts MP4 (and a couple of mobile-format variants). MKV will fail at the upload step.
Both caps apply to the original file, not to anything WhatsApp does to it after upload.

The bitrate math

For a target file size cap, the formula every video tool uses is:

target_kbps = (max_size_mb × 1024 × 1024 × 8) / (duration_seconds × 1000)
              − audio_kbps

Plug in 16 MB, 60 seconds, 128 kbps of audio:

target_kbps = (16 × 1024 × 1024 × 8) / (60 × 1000) − 128
            = 2235 − 128
            = ~2107 kbps total video bitrate

Most modern H.264 encoders will produce that file size with CRF ~22 at 1080p. Video Forge’s WhatsApp destination tile does this computation for you per-video so you don’t have to.

For longer clips you have to either drop the resolution (720p or 480p) or push CRF higher (lower quality). A two-minute 1080p clip won’t fit under 16 MB without going to 540p or accepting visible compression.

The codec choice

Use H.264 (AVC). Always. (For why H.264 still wins over H.265 and AV1 for chat-platform delivery, see the codec comparison.) Here’s why:

WhatsApp ships H.264 as-is inside the size cap. Upload anything else and the server re-encodes it down to H.264 anyway, but at a much lower bitrate than you’d have picked.
H.264 plays on every phone, browser, and platform built in the last 15 years.
It’s older than H.265/HEVC and AV1, which means slightly larger files at the same quality — but at the file sizes WhatsApp cares about, the difference is too small to matter.

Skip H.265, AV1, VP9, and ProRes for WhatsApp. They’ll either be rejected or aggressively re-encoded.

For audio: AAC at 128 kbps. Lower than that and dialogue gets crunchy. Higher than that is wasted bytes in a 16 MB budget.

The step-by-step in Video Forge

If you’re using Video Forge to handle the math, here’s the click path:

Drop your video onto the queue (drag-and-drop, or click Browse). The app reads metadata via ffprobe and shows the spec — resolution, codec, duration, size.
Pick the WhatsApp tile in the Send To section. The app computes the target bitrate for your clip’s specific duration so the output lands under 16 MB with the highest quality the math allows.
(Optional) Generate the 5-second preview. Video Forge renders a representative sample using the exact encoder settings the full job will use, so you can verify it looks right before committing to the full encode. Side-by-side with the original.
Convert. Output lands in the same folder as the source by default, with the suffix _whatsapp.mp4. The progress bar shows percent, encode speed (e.g. 1.4×), and ETA.

If the source is already under 16 MB and the codec is H.264, Video Forge remuxes instead of re-encoding — much faster and the quality is identical to the source.

What if you’re not using Video Forge

If you want to do this with ffmpeg directly, the equivalent command for a 60-second 1080p clip is:

ffmpeg -i input.mov -c:v libx264 -crf 23 -preset medium \
       -vf "scale=-2:1080" -c:a aac -b:a 128k -movflags +faststart \
       output.mp4

Two notes:

-movflags +faststart moves the MP4 header to the front of the file so it plays before the whole thing finishes downloading. Always include it for chat-friendly delivery.
-preset medium balances encode time and file size. Slower presets give smaller files but take longer.

For two-pass (target an exact file size), it’s two commands chained together sharing a logfile. Video Forge automates this — if you want the manual version, that’s also documented in the How to target a specific file size post.

What if you’re still over 16 MB

In order of pleasantness:

Trim the clip — usually the easiest win. Most messaged videos have 30 seconds of dead time you can lose. Video Forge’s trim panel lets you set in/out points without re-rendering twice.
Drop to 720p — invisible on a phone screen, halves the file size.
Push CRF to 26 — slight softening, still usable for messaging.
Drop to 30 fps if the source is 60 fps — the file gets smaller and most chat viewers won’t notice.
Compress with HEVC instead — only if your recipient is on an iPhone newer than 2017 and you know they’ll be on iMessage instead of WhatsApp (WhatsApp re-encodes HEVC anyway).

FAQ

What is the maximum video size on WhatsApp? WhatsApp’s hard cap is 16 MB on the mobile app and 100 MB when you upload via WhatsApp Web or WhatsApp Desktop. Above that, the message is rejected before it even starts to send.

What codec does WhatsApp use? WhatsApp ships H.264 (AVC) inside an MP4 container with AAC audio. Upload H.264 already and WhatsApp passes it through. Upload H.265, ProRes, or VP9 and WhatsApp re-encodes it, costing quality.

Will compressing my video lose quality? A small, controlled amount. CRF 23 is visually lossless to most viewers. CRF 28 is mildly soft but acceptable for messaging. CRF 32 looks obviously compressed.

Why does WhatsApp make my video look so bad? Because WhatsApp’s server-side compression is tuned for the worst-case network. Pre-compressing to 1080p H.264 under the 16 MB cap means WhatsApp ships your version instead of mangling it.

Can I send a 1 GB video on WhatsApp? Not in one piece. You can upload up to 100 MB via WhatsApp Web/Desktop. For larger files, send a Google Drive or Dropbox link instead.

Video Forge handles the bitrate math, codec choice, and aspect handling for ten destinations including Discord, iMessage, email, and vertical formats. Download for macOS or Windows — first 10 conversions free, $5 lifetime after.