How to compress an iphone mov for whatsapp
- Step 1Get the .mov off the iPhone — Use the file directly on the iPhone (open the tool in Safari), AirDrop it to a Mac, or import it. The tool reads HEVC
.movand H.264.movalike — no conversion needed before this step. - Step 2Open the WhatsApp compressor — Go to /video-tools/whatsapp-compressor. It runs in the browser on Mac, Windows, or iPhone, so the MOV never uploads anywhere.
- Step 3Drop in the MOV — Add the iPhone clip. The tool probes its duration, frame rate, and resolution locally to plan the H.264 encode that lands near 15 MB.
- Step 4Let it transcode to H.264 MP4 — The encode runs hardware-accelerated via WebCodecs where available (fast on Mac / newer iPhones), or FFmpeg.wasm libx264 otherwise. The fixed 15 MB target means there's nothing to configure.
- Step 5Download the MP4 — Save the result. It's a standard H.264 MP4 under 16 MB with audio muxed back at 96 / 128 kbps AAC — no longer an HEVC
.mov. - Step 6Send it on WhatsApp — Attach the MP4 in WhatsApp. It's under the cap and in a universally compatible format, so it sends inline and plays correctly on the recipient's device.
iPhone MOV vs the WhatsApp-ready MP4
What changes when you transcode an iPhone source through this tool.
| Property | iPhone source (.mov) | After this tool (.mp4) |
|---|---|---|
| Container | MOV (QuickTime) | MP4 (with +faststart) |
| Video codec | HEVC / H.265 (default) or H.264 | H.264 (avc1 / libx264) |
| Bit depth / range | Often 10-bit, sometimes HDR (Dolby Vision) | 8-bit SDR (tone-mapped if HDR) |
| Size | Large — easily over 16 MB | Targeted to 15 MB |
| WhatsApp behavior | Re-encoded or plays as a file | Accepted inline, plays as video |
iPhone resolutions and where to process them
Heavier iPhone sources decode faster on desktop. Mobile software-fallback guardrails apply only when WebCodecs hardware encode isn't available.
| iPhone capture | Decode weight | Best processed on | Note |
|---|---|---|---|
| 1080p HEVC | Moderate | Phone or desktop | Hardware path is quick on newer iPhones / Mac |
| 4K 30 HEVC | Heavy | Desktop (or hardware path) | Software fallback on a phone may stall |
| 4K 60 / HDR HEVC | Very heavy | Desktop | Tone-mapped to SDR; trim first if large |
| 1080p H.264 (older) | Light | Phone or desktop | Simplest case — re-encode to fit 15 MB |
Cookbook
iPhone-specific transcode recipes. HEVC source in, WhatsApp-ready H.264 MP4 out, always fitting the 15 MB target.
Standard 1080p iPhone HEVC clip
The everyday case: a 1080p HEVC .mov that's too big for WhatsApp. The tool transcodes to H.264 and fits 15 MB; on a Mac or newer iPhone the hardware path makes it quick.
Source: iPhone HEVC .mov, 1080x1920, 28 s, 44 MB Plan: 15 MB target, audio 96 kbps, video ~4.2 Mbps Output: ~14.6 MB H.264 MP4 Result: sends inline on WhatsApp, plays everywhere
4K HEVC: process on desktop
A 4K HEVC clip is heavy to decode. On desktop the hardware or software path handles it; on a phone's software fallback it may stall or get downscaled. Desktop is the safe choice for 4K iPhone sources.
Source: iPhone 4K HEVC .mov, 3840x2160, 20 s, 110 MB Where: desktop (hardware encode if available) Plan: 15 MB target, video ~5.8 Mbps Output: ~14.5 MB H.264 MP4 (downscaled by encoder budget) Note: on a phone software fallback this would downscale to 720p
HDR / Dolby Vision tone-mapped to SDR
iPhones can record 10-bit HDR (Dolby Vision). WhatsApp's pipeline is 8-bit H.264, so the tool tone-maps to SDR. Expect slightly different highlights/colors — necessary for compatibility, and WhatsApp would flatten HDR anyway.
Source: iPhone HDR HEVC .mov, 1080p, 25 s, 52 MB Process: decode 10-bit HDR -> encode 8-bit SDR H.264 Output: ~14.6 MB H.264 MP4 (SDR) Note: minor highlight/color shift vs the HDR original
Long iPhone clip: trim then transcode
A multi-minute iPhone clip won't look good squeezed into 15 MB. Trim to the highlight first (lossless, instant), then transcode the cut. This is the highest-quality path for long sources.
Source: iPhone HEVC .mov, 1080p, 3 min, 200 MB Step 1: lossless-trimmer -> best 30 s (no re-encode) Step 2: this tool -> 15 MB H.264 MP4, ~3.9 Mbps Result: sharp, sends inline; far better than 3 min at 15 MB
Older iPhone H.264 .mov
Pre-HEVC iPhones (and clips shot in 'Most Compatible' mode) save H.264 in a .mov. The tool still re-encodes to MP4 at 15 MB — lighter to decode than HEVC, so it's the fastest case.
Source: iPhone H.264 .mov ('Most Compatible'), 1080p, 30 s, 35 MB
Plan: 15 MB target, video ~3.9 Mbps
Output: ~14.6 MB H.264 MP4
Note: light decode -> quick even on the software fallbackEdge cases and what actually happens
4K HEVC source stalls on a phone's software path
Process on desktop4K HEVC is heavy to decode, and on a phone's FFmpeg.wasm fallback it can stall or run out of memory. Process 4K iPhone clips on desktop, where the hardware or software path has more headroom, or trim the clip first. The 80 MB mobile software-path cap will also reject many 4K sources outright.
HDR / Dolby Vision flattened to SDR
ConvertediPhone HDR (Dolby Vision) clips are 10-bit; WhatsApp's pipeline is 8-bit H.264, so the tool tone-maps to SDR. Highlights and colors can shift slightly versus the HDR original. This is unavoidable for compatibility — and WhatsApp would flatten an HDR file on its own re-encode anyway, so doing it here under control is the better outcome.
iPhone source over 80 MB on the mobile software path
Rejected on mobile WASMOn a phone without WebCodecs hardware encode, the tool refuses sources over 80 MB — common for 4K or long iPhone clips. Either process on desktop, or trim the MOV first with the lossless trimmer to bring it under the limit, then transcode the smaller cut on the phone.
High-frame-rate (60 / 120 / 240 fps) iPhone clip
SupportediPhone slow-motion and 60 fps clips transcode to H.264 fine, but more frames per second means each frame gets less of the 15 MB budget. For slow-motion you usually want the slow-mo effect baked in (export from Photos as the slowed version) before transcoding, so the clip plays as intended on WhatsApp.
iPhone 1080p downscaled to 720p on mobile software path
Auto-downscaledIf your iPhone uses the FFmpeg.wasm fallback (rather than hardware WebCodecs), a 1080p source is downscaled to 720p to fit the phone's memory. Newer iPhones on a current Safari use the hardware path, which preserves resolution. For guaranteed full resolution on a big iPhone clip, use a Mac.
Long iPhone clip squeezed into 15 MB
Quality floorA multi-minute iPhone clip at 15 MB gets a low bitrate and looks soft, regardless of how good the HEVC source was. Trim to the highlight first with the lossless trimmer so the budget concentrates on a shorter clip — this matters more for high-detail iPhone footage.
Output is .mp4, not .mov
By designThe tool always outputs MP4, never MOV — that's the point of transcoding for WhatsApp, since MP4/H.264 is the universally compatible target. If you specifically need a MOV container for another workflow, this isn't the tool; the transcoder offers broader container control.
Output slightly over 15 MB
By designSingle-pass bitrate targeting approximates the size, so an iPhone clip can land a little above 15 MB after transcode. The 1 MB margin under WhatsApp's 16 MB cap absorbs this, so the MP4 still sends inline. The tool logs a soft warning if it overshoots but still delivers the file.
Frequently asked questions
Why won't my iPhone video send on WhatsApp?
Two reasons usually stack: iPhone .mov files are large (HEVC at high resolution), so they exceed WhatsApp's 16 MB cap; and HEVC inside a MOV container doesn't always play on every recipient's device. This tool fixes both — it transcodes to H.264 MP4 (universally compatible) and fits the 15 MB target so the clip sends inline.
Does it convert HEVC to H.264?
Yes. iPhones record HEVC (H.265) by default, which WhatsApp handles poorly. The tool decodes the HEVC source and re-encodes to H.264 MP4 — the format every WhatsApp client decodes reliably. The output is avc1 (hardware path) or libx264 (fallback), never HEVC.
Will my 4K iPhone clip work?
Yes, but process it on desktop for the smoothest result — 4K HEVC is heavy to decode, and on a phone's software fallback it may stall or hit the 80 MB rejection limit. On desktop (or the hardware path) the tool transcodes 4K sources to a 15 MB H.264 MP4; for very large 4K clips, trim first.
What happens to HDR / Dolby Vision iPhone video?
It's tone-mapped to 8-bit SDR, because WhatsApp's pipeline is built around 8-bit H.264. Highlights and colors may shift slightly from the HDR original. This is necessary for compatibility — and WhatsApp would flatten HDR on its own re-encode regardless, so converting it here under control gives a better result.
Does my iPhone footage get uploaded?
No. The transcode runs entirely in your browser via WebCodecs or FFmpeg.wasm, whether you're on an iPhone, a Mac, or a PC. Your .mov never leaves the device — a real advantage over compressor apps that upload to a server. Only an anonymous processed-file counter is recorded for signed-in users.
Can I do this directly on my iPhone?
Yes — open the tool in Safari and pick the clip from Photos. Newer iPhones use the hardware encoder (fast, full resolution); older ones fall back to software, which downscales 1080p+ to 720p and rejects sources over 80 MB. For big or 4K clips, a Mac is smoother. See the mobile-fix guide.
What size and format do I get?
A standard H.264 MP4 targeted to 15 MB, which clears WhatsApp's 16 MB cap with a 1 MB margin. There's no codec or size selector — H.264 MP4 at 15 MB is the WhatsApp-ready combination, so the output is fixed and predictable.
My iPhone clip is long — should I trim it first?
For anything over a minute or two, yes. The 15 MB budget gives a long clip a low bitrate, so it looks soft no matter how good the HEVC source was. Trim to the highlight with the lossless trimmer (instant, no re-encode), then transcode the cut for a much sharper result.
Will the sound from my iPhone video survive?
Yes. Audio is re-encoded to AAC and muxed back in — 96 kbps for clips under 30 seconds, 128 kbps for longer — with the rest of the 15 MB budget going to video. Silent clips spend the whole budget on picture.
Can I keep the .mov container instead of MP4?
No — this tool always outputs MP4, which is the point for WhatsApp compatibility. If you need a MOV container for editing or another workflow, use the transcoder, which offers broader container and codec control. For WhatsApp specifically, MP4/H.264 is what you want.
What about slow-motion iPhone clips?
They transcode fine, but bake in the slow-motion effect first — export the slowed version from Photos — so the clip plays at the intended speed on WhatsApp. High frame rates also split the 15 MB budget across more frames, so a short slow-mo clip fits better than a long one.
How large an iPhone source can the tool handle?
Up to the tier file-size limit (1 GB free) on the hardware path. On a phone's software fallback the practical cap is 80 MB — above that the tool refuses to avoid crashing, which catches many 4K iPhone clips. For large sources, use desktop or trim first.
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.