How to shrink a video file without making it look bad
Phone video is enormous for one reason: phones record at a very high bitrate to keep editing headroom. For sending, that headroom is pure weight — and dropping it is usually invisible on the screen the video will be watched on.
What a minute of phone video actually costs
These are roughly the figures iOS itself shows under Settings → Camera → Record Video; Android flagships are in the same range.
| Recording setting | Approx. per minute | Ten minutes |
|---|---|---|
| 720p, 30 fps | ~40 MB | ~0.4 GB |
| 1080p, 30 fps | ~65 MB | ~0.65 GB |
| 1080p, 60 fps | ~90 MB | ~0.9 GB |
| 4K, 30 fps | ~170 MB | ~1.7 GB |
| 4K, 60 fps | ~400 MB | ~4 GB |
The jump from 1080p/30 to 4K/60 is roughly six-fold. If you are about to send a ten-minute clip, the recording setting decided months ago is doing more to your file size than anything you can do now.
The three levers, in order of effect
1. Bitrate — the dominant one. Bitrate is how many bits per second the encoder is allowed to spend. Everything else is a proxy for it. Halving the bitrate halves the file, and up to a point it is genuinely hard to see, because phone recordings allocate far more bits than the picture needs. This is the lever to pull first.
2. Resolution — the one you notice least. 4K has four times the pixels of 1080p. If the video will be watched on a laptop, a phone, or sent into a chat app that will re-encode it anyway, those pixels are being thrown away at the other end regardless. Exporting a 4K clip at 1080p typically lands around a quarter of the size and looks the same on anything short of a large TV.
3. Codec — free savings, with a compatibility catch. H.265 (HEVC) reaches roughly the same visual quality as H.264 at around half the bitrate. AV1 does better still. The catch is playback: H.264 plays literally everywhere, H.265 is now widely but not universally supported, and older Windows machines may need a codec. If you know what the recipient will open it on, H.265 is free money. If you do not, H.264 is the safe answer.
Practical recipes
- Fastest, no tools: on iPhone, open the clip in Photos, tap the crop/edit tools and trim off the dead time at the start and end. Most phone clips have several seconds of pocket and fumbling at both ends, and trimming is lossless in a way re-encoding is not.
- Phone, one step: share the video to any "compress video" utility, or on iOS use Files → share → Compress. Good enough for cutting a clip under an email limit.
- Desktop, best quality per megabyte: HandBrake, free on Windows/macOS/Linux. Pick the Fast 1080p30 preset and set the quality slider (RF) to around 22–24. Lower RF is bigger and better; 22 is visually transparent for most content, 28 starts to show.
- Command line:
ffmpeg -i in.mp4 -vcodec libx264 -crf 23 out.mp4. CRF 23 is the sane default; 18 is near-lossless and much bigger, 28 is small and visibly softer. - Do not screen-record a video to shrink it. It re-encodes a re-encode, drops frames, and captures at whatever your screen is doing.
When re-encoding is the wrong answer
If the video is evidence, source footage you will edit, or something someone else will grade or archive, do not re-encode it — every pass loses information permanently and there is no undo. Send the original and change the delivery method instead. A 4 GB original is not an email problem to be solved with a codec; it is a file that needs a transfer that can carry 4 GB, resume when it breaks, and expire afterwards.
More guides
Six ways to get a file from your phone to a computer — and where each one breaks
Cable, cloud drive, email, messaging apps, local network and transfer services compared: size ceilings, what each one costs you in privacy, and the specific situation where each method falls apart.
Email attachment size limits — and why your file is bigger than you think
The attachment ceiling for Gmail, Outlook, Yahoo, iCloud, Proton and Zoho, why encoding makes your file about 33% larger in transit, and the four ways past the limit.
What end-to-end encryption actually protects — and what it does not
The difference between HTTPS, encryption at rest and true end-to-end encryption, why the key matters more than the cipher, and the four things E2EE will never save you from.
Try SendMyFile
Encrypt a file in your browser and hand it over with a 9-digit code. No account, and it deletes itself.
Try SendMyFile