How to fix "video too big for whatsapp" on your phone
- Step 1Open the tool in your phone's browser — When WhatsApp says the video is too big, switch to your browser and go to /video-tools/whatsapp-compressor. No app install — it loads as a normal web page.
- Step 2Pick the video from your phone — Tap to choose the clip from your camera roll. The file stays on your phone — the tool reads it locally and never uploads it.
- Step 3Let it use your phone's hardware encoder — On most modern phones the tool runs a hardware H.264 encode via WebCodecs — fast and easy on the battery. There's nothing to configure; the target is a fixed 15 MB.
- Step 4Wait for the on-device encode — The encode runs in the tab. On the hardware path it's quick; on the software fallback it's slower and respects the mobile guardrails (no >80 MB sources, >720p downscaled).
- Step 5Save the compressed MP4 to your phone — Download the result to your camera roll or files. It's a standard H.264 MP4 under 16 MB, with audio muxed back at 96 / 128 kbps AAC.
- Step 6Send it from WhatsApp — Go back into WhatsApp, attach the compressed file, and send. It's now under the cap, so WhatsApp accepts it inline without the 'too big' error.
Mobile encode paths and their guardrails
What happens on your phone depends on whether the browser can use the hardware encoder. The guardrails only apply on the software fallback, and only on mobile.
| Phone path | Speed | Resolution handling | Size guardrail |
|---|---|---|---|
| WebCodecs hardware H.264 (preferred) | Fast, battery-light | Preserves source resolution | No special mobile size cap (tier limit only) |
| FFmpeg.wasm software fallback | Slower, heavier on the tab | Downscales sources over 720p | Rejects sources over 80 MB |
| Desktop (for comparison) | Fast on hardware, OK on software | Preserves resolution | No mobile guardrails apply |
Phone vs a compressor app
Why a browser tool beats installing a compressor app on your phone.
| Concern | This browser tool | Typical compressor app |
|---|---|---|
| Install | None — opens in the browser | App-store download + permissions |
| Camera-roll access | Only the one file you pick, on-device | Often broad media-library permission |
| Upload | Never — encodes on your phone | Some apps upload to a server |
| Cost / ads | Free, no ads in the encode | Often ad-supported or paywalled |
Cookbook
Phone-first scenarios. The common thread: stay on your device, use the hardware encoder when you can, and respect the software-fallback guardrails.
Typical 'too big' clip, fixed on a modern phone
A 30-second clip from a recent phone is often 30-45 MB — well over the cap. On a modern phone the hardware encoder fits it to 15 MB quickly and preserves resolution.
Phone: modern Android / iPhone, WebCodecs available
Source: 1080x1920, 30 s, 38 MB ('too big' in WhatsApp)
Path: hardware H.264 encode, resolution kept
Output: ~14.6 MB MP4 -> sends from WhatsApp, no errorOlder phone falls back to software and downscales
On a phone where the browser can't use the hardware encoder, the FFmpeg.wasm path kicks in. A 1080p source is downscaled to 720p so the encode fits the phone's memory and finishes instead of crashing.
Phone: older device, no WebCodecs H.264 Source: 1080x1920, 25 s, 30 MB Path: FFmpeg.wasm fallback -> downscaled to 720p Output: ~14.5 MB 720p MP4 -> sends fine Note: slight resolution drop, but it actually completes
Source over 80 MB on the software path
If the phone is on the software fallback and the file is over 80 MB, the tool stops with a clear message rather than crashing the tab. The fix is to trim first.
Phone: software fallback path
Source: 1080p, 2 min, 95 MB
Result: tool refuses (>80 MB on mobile WASM)
Fix: trim to ~30 s with lossless-trimmer first (instant),
then compress the smaller cut on your phoneTrim on the phone, then fit
For a long clip on mobile, the lossless trimmer is the partner step — it cuts without re-encoding, so it's fast even on a phone, and the smaller cut then sails through the compressor.
On your phone: Step 1: lossless-trimmer -> cut 3 min clip to best 30 s Step 2: this tool -> 15 MB H.264 MP4 Step 3: send from WhatsApp All on-device, no app, no upload.
iPhone .mov picked straight from Photos
iPhones save HEVC .mov files that are large and not always WhatsApp-friendly. The tool transcodes to H.264 MP4 and fits 15 MB. On the hardware path this is fast; the dedicated iPhone guide has more detail.
Source: iPhone HEVC .mov, 1080p, 28 s, 44 MB Path: hardware H.264 (or software fallback if needed) Output: ~14.6 MB H.264 MP4 -> sends from WhatsApp See: /video-tools/solutions/compress-iphone-mov-for-whatsapp
Edge cases and what actually happens
Source over 80 MB on a mobile software fallback
Rejected on mobile WASMWhen your phone can't use the hardware encoder and runs FFmpeg.wasm, the tool refuses sources over 80 MB and says so, because a phone's WebAssembly heap can't host the decoder and encoder together on a file that large without crashing. Trim the clip first with the lossless trimmer (instant, no re-encode) or run it on desktop.
1080p+ source on the mobile software path
Auto-downscaledOn the FFmpeg.wasm fallback the tool downscales sources taller than 720p to 720p before encoding, trading a little resolution for a finished file instead of an out-of-memory crash. If you need to keep full resolution, use a browser with WebCodecs H.264 support (the hardware path preserves it) or run the tool on desktop.
Phone runs out of memory mid-encode
OOM errorEven within the guardrails, a borderline source can exhaust the phone's WASM heap. The tool catches the out-of-memory condition and returns a plain message suggesting a shorter or smaller-resolution source, rather than dumping a crash. Trimming first almost always resolves it.
Browser tab is backgrounded during the encode
Keep it foregroundedMobile browsers throttle or suspend background tabs to save battery, which can pause or interrupt a running encode. Keep the tab in the foreground and the screen awake until the download appears. On the (faster) hardware path this window is short; on the software fallback it's longer, so don't switch apps mid-encode.
Resolution dropped to 720p on an old phone
By designIf your output came back at 720p when the source was 1080p, your phone used the software fallback and the tool downscaled to keep the encode within memory. This is intentional — a finished 720p clip beats a crashed 1080p one. For full resolution on mobile, the hardware path (newer browsers) preserves it.
No app-store download required
ExpectedThis isn't an app — it's a web page, so there's nothing to install and no camera-roll permission to grant beyond picking the single file you choose. That's the whole point of fixing it 'on your phone' this way: no app footprint, and no risk of a compressor app uploading your video.
Output slightly over 15 MB
By designSingle-pass bitrate targeting on a phone, like on desktop, approximates the final size, so the result can land a little over 15 MB. The 1 MB margin under WhatsApp's 16 MB cap absorbs it, so the file still sends from WhatsApp without the 'too big' error.
Long clip still looks soft after compressing on the phone
Quality floorCompressing on the phone doesn't change the math — the 15 MB budget gives a long clip a low bitrate regardless of device. If a multi-minute clip looks soft, trim it on the phone with the lossless trimmer first, then compress the shorter cut for a sharper result.
Frequently asked questions
Do I need to install an app to fix this on my phone?
No. This is a browser tool — open it in Chrome on Android or Safari on iOS and it runs as a web page. There's no app-store download, no broad camera-roll permission, and no risk of an app uploading your video. You pick one file, it compresses on-device, and you send it from WhatsApp.
Will my phone be fast enough to compress the video?
On most modern phones, yes — the tool uses your phone's hardware H.264 encoder via WebCodecs, which is fast and battery-friendly. Older phones fall back to a software encoder that's slower, with guardrails (no sources over 80 MB, 1080p+ downscaled to 720p) so the tab finishes instead of crashing.
Why did my output come out at 720p when my video was 1080p?
Your phone used the software fallback, which downscales sources over 720p to 720p to keep the encode within the phone's memory. It's a deliberate trade — a finished 720p clip beats a crashed 1080p one. To keep full resolution on mobile, use a browser that supports WebCodecs H.264 (the hardware path preserves resolution) or compress on desktop.
It says my file is too big to compress — what now?
On the mobile software path the tool refuses sources over 80 MB because a phone's memory can't handle them. Trim the clip first with the lossless trimmer — it's instant and doesn't re-encode — then compress the smaller cut, or run the tool on desktop where the 80 MB limit doesn't apply.
Does my video get uploaded when I use this on my phone?
No. The entire encode runs in your phone's browser via WebCodecs or FFmpeg.wasm. Your camera roll never leaves the device, which is a real advantage over some compressor apps that upload your clip to a server. Only an anonymous processed-file counter is recorded for signed-in users, and it's optional.
Does it work the same on iPhone and Android?
Yes — it's the same browser tool on iOS Safari and Android Chrome. Both prefer the hardware encoder when available. iPhone HEVC .mov files are transcoded to H.264 MP4; the iPhone MOV guide covers that case in detail.
What size does it compress to?
A fixed 15 MB target, which clears WhatsApp's 16 MB cap with a 1 MB margin for container overhead. There's no slider — the cap is the constraint, so the target is fixed for predictable output. The result is a standard H.264 MP4 you send straight from WhatsApp.
Should I keep the tab open while it works?
Yes — keep the browser tab in the foreground and the screen awake until the download appears. Mobile browsers suspend background tabs to save battery, which can interrupt the encode. The hardware path is quick; the software fallback takes longer, so don't switch apps mid-encode.
Will it keep the sound when compressing on my phone?
Yes. Audio is re-encoded to AAC and muxed back in (96 kbps under 30 seconds, 128 kbps for longer clips), with the rest of the 15 MB budget going to video. If the source is silent, the full budget goes to picture.
My phone video is several minutes long — will it look bad?
Possibly — the 15 MB budget is fixed, so a long clip gets a low bitrate on any device. Compressing on the phone doesn't change that math. For a sharp result, trim to the highlight first with the lossless trimmer, then compress the shorter cut on your phone.
How big a source can my phone handle?
On the hardware path, up to the tier file-size limit (1 GB free). On the mobile software fallback, the practical cap is 80 MB — above that the tool refuses to avoid crashing. If you're hitting the limit, trim first or move to desktop.
Can I send the compressed clip right from WhatsApp afterward?
Yes — that's the workflow. Save the compressed MP4 to your phone, switch back to WhatsApp, attach it, and send. Because it's now under 16 MB, WhatsApp accepts it inline with no 'too big' error and without running its own quality-killing re-encode.
Privacy first
Every JAD Video tool runs entirely in your browser via WebCodecs and FFmpeg (WebAssembly). Your video files never leave your device — verified by zero outbound network requests during processing.