MOV Compressor

How to Compress MOV Files Online

1. Upload Your MOV Files: Drag and drop, or click "+ Add Files" to pick MOV recordings from iPhone, Mac, or a camera card. Batch is supported — queue several iPhone clips or a folder of ProRes shots together.
2. Pick a Compression Mode: "Target file size (%)" is the default and easiest — drag the slider toward 50% to roughly halve the file. Use "Specific file size" to hit an exact cap (e.g. 24 MB for a Gmail attachment), "Constant Quality" / "Constraint Quality" for a fixed CRF, or "Constant Bitrate" / "Variable Bitrate" if you need a precise Mbps figure for a streaming target.
3. Resize, Trim, or Re-codec (Optional): Keep the original codec for a quick re-pack, or drop down to H.264 / HEVC under Video Codec for much smaller files. Apply a "Resolution Preset" (4K → 1080p, 1080p → 720p) for further savings, leave "Auto Scale" on to let xconvert pick a sane resolution for your target size, or set a "Trim" range to keep only the part you need.
4. Compress and Download: Click Compress. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after one hour — no sign-up, no watermark, never shared.

Why Compress MOV Files?

MOV is Apple's QuickTime container, and it's what every iPhone and Mac camera writes by default. The container is fine — it's the codecs inside (Apple ProRes for pro work, HEVC for HDR/Dolby Vision, H.264 for "Most Compatible") that make MOV files balloon. Apple notes that ProRes files are up to 30x larger than HEVC files; a one-minute 4K HEVC clip is roughly 170 MB, while the same minute in ProRes can run several gigabytes. Compression brings these down to sizes you can actually email, upload, or archive.

• Get under the 25 MB Gmail cap — Personal Gmail caps outgoing attachments at 25 MB; a 30-second iPhone 4K HEVC clip is already over that. Targeting 22-24 MB ("Specific file size") gives you headroom for MIME encoding overhead, which inflates payload by roughly 33%.
• Shrink iPhone ProRes for upload — ProRes is built for editing, not delivery. Re-encoding a 6 GB/min ProRes clip to H.264 at CRF 23 typically yields a file under 100 MB/min with no visible quality loss on phone or laptop screens.
• Free up iPhone and iCloud storage — iCloud's free tier is 5 GB. A single afternoon of 4K HEVC family video can fill it. Pre-compressing archive copies before uploading to Google Photos, OneDrive, or external SSD saves both quota and upload time.
• Speed social uploads — Instagram, TikTok, and YouTube re-encode whatever you give them. Uploading a 2 GB MOV when 200 MB carries the same on-feed quality just wastes bandwidth and stalls Reels/Shorts publishing.
• Hit Slack / Discord / WhatsApp limits — Discord's free tier dropped to a 10 MB upload cap in September 2024, Slack free workspaces cap individual files at 1 GB, and WhatsApp tops out at 2 GB per file. Compression is the difference between "sent" and "file too large."
• Preserve the MOV container — Unlike converting MOV to MP4, staying in MOV keeps Apple metadata (Live Photo pairings, slow-mo tags, HDR ramps) intact for Final Cut Pro and iMovie roundtrips.

MOV Codec Cheat Sheet — Why Your File Is So Large

Sizes are rough order-of-magnitude figures for typical iPhone / camera defaults; exact size depends on bitrate, frame rate, and scene complexity.

CRF & Target-Size Quick Reference

Constant Rate Factor (CRF) is the quality knob inside H.264 and HEVC. Lower = better quality and bigger file; higher = smaller file. The widely-cited FFmpeg encoding guidance puts the sane range for H.264 at roughly 17-28 (18 = visually lossless, 23 = default, 28 = small but watchable); HEVC uses a similar scale but a slightly higher number gives equivalent visual quality.

Frequently Asked Questions

Why is my iPhone MOV so much larger than friends' MP4 videos?

iPhones record either HEVC (Settings → Camera → Formats → "High Efficiency") or H.264 ("Most Compatible"), in a MOV container. H.264 MOVs are roughly twice the size of an equivalent HEVC clip. If you also shoot ProRes (iPhone 13 Pro and newer, 256 GB+ models), Apple notes the files can be up to 30x larger than HEVC — a few gigabytes per minute at 4K is normal. The friend's "MP4" is almost certainly already-compressed H.264 or HEVC that has been re-encoded by Instagram, WhatsApp, or AirDrop conversion.

Will compression damage quality?

It's lossy — bits get removed — but at moderate settings the loss is invisible at normal viewing distances. CRF 20-23 on H.264 / HEVC, or "Target file size (%)" between 50-70%, is the sweet spot where files shrink dramatically while the picture still looks clean on phone, tablet, and laptop screens. Quality degradation becomes noticeable on a 4K TV at close range, or after multiple generations of re-compression.

Should I keep the MOV container or convert to MP4?

If you're staying in Apple's ecosystem — Final Cut Pro, iMovie, Photos library — keep MOV; the container preserves Apple-specific metadata and timecode tracks. If you're sharing with Windows users, Android phones, or uploading anywhere on the web, converting MOV to MP4 is friendlier; the container difference is cosmetic but MP4 has fewer "won't open" edge cases on non-Apple hardware.

How small can I make a MOV without it looking bad?

At the same resolution, expect 30-60% reduction with no visible loss. If you also drop 4K → 1080p, total reduction is typically 75-85%. If the source is ProRes, 90%+ reduction to H.264 is routine because ProRes uses very light intra-frame compression by design — you're just throwing away storage overhead, not picture detail.

Can I compress a MOV without re-encoding (lossless)?

True lossless compression of an already-compressed H.264 / HEVC MOV is roughly impossible — those codecs are already near the limit of what general-purpose compressors can do. What you can do is repackage (change container) or trim — both are bit-for-bit lossless. If the source is uncompressed or ProRes, re-encoding to ProRes Proxy is "visually lossless" and roughly one-quarter the size.

Will my Live Photo, slow-motion, or HDR metadata survive?

Slow-motion (the frame-rate ramp) and HDR transfer characteristics survive a re-encode if the output codec supports them — HEVC carries HDR10 and Dolby Vision metadata; H.264 only supports SDR. Live Photo pairing is a Photos.app construct, not part of the MOV itself, so it doesn't transfer when you process the.mov in isolation. For Live Photos, export the still + video pair separately from Photos first.

Does this work on iPhone, iPad, and Mac directly in the browser?

Yes. xconvert works from any modern browser — Safari, Chrome, Firefox, and Edge, desktop and mobile — and the file is uploaded to our servers for compression. There's no app to install. On iPhone, share a video from Photos → "Save to Files" first, then upload from Files; iOS doesn't let websites pull directly from the Photos library.

Is there a file size limit, and are my files private?

You can upload large MOV files (multi-GB ProRes clips are fine). Files are uploaded over HTTPS, processed, and auto-deleted from xconvert servers shortly after; we never share or store originals long-term, and there's no watermark or sign-up.

What if I only need to compress one part — can I trim first?

Yes. Set "Trim" to a Time Range before compressing and only the selected segment is encoded — usually the fastest way to drop a multi-minute MOV under an email or Discord cap without losing visual quality. You can also use the dedicated Trim MOV tool if you want to cut without changing any codec settings.