Compress MOV
Compress one MOV up to 50 MB locally into H.264 MP4 or MOV. Defaults cap the short edge at 1080 px and remove GPS data; file size may increase.
How to use
- Choose one MOV: Drop a .mov onto the box or click to pick it. One file per run, up to 50 MB. Any video is accepted, but if the file isn't a MOV the page says so and points you at the general video compressor.
- Pick the output format: Leave Output format on Convert to MP4 (recommended) for the widest playback, or choose Keep MOV when an editor or an Apple app only takes .mov. Either way the picture is re-encoded to H.264.
- Set quality and resolution: Quality runs High (larger file), Recommended (balanced) and Smaller (size first). Resolution defaults to Up to 1080p, which is the setting that makes 4K footage finish in a sensible time; Up to 720p is smaller again, and Keep original resolution applies no resolution cap, but odd dimensions are rounded down to even numbers and rotation is applied when needed.
- Compress, watch, save: Click Compress MOV. The first run spends a while fetching the engine before any percentage appears, and Cancel works throughout. When it finishes you see the size before and after, a preview player when supported, or a download card if playback is unavailable, and Download — Save to device on a phone.
How to compress a MOV without uploading it
Pick one MOV up to 50 MB, choose MP4 or MOV as the output, set a quality step and a resolution cap, and this page hands back a re-encoded H.264 file you can preview if your browser supports the output container, then save. The work happens in the browser tab, so the recording never leaves your phone or computer.
The engine is ffmpeg.wasm, a build of FFmpeg compiled to WebAssembly and downloaded with the page. There is no server fallback anywhere in the code: a file your device can't manage ends in an error message, not in an upload. Nothing is stored either — close the tab and the result is gone, which is the point if the clip is of your kids, your home or a client's site.
Before any encoding, the file is read once to work out its length, codec, resolution, rotation, HDR flags, shoot date and track list. A damaged download, a half-transferred recording or something that only wears a .mov extension fails at that point with a note that the file isn't a video we can read, rather than after minutes of pointless work. An audio file with no picture in it is caught by the same pass.
Re-encoding needs the multi-threaded build of the engine, which needs SharedArrayBuffer, so this page is served with cross-origin isolation. An up-to-date Chrome, Edge or Firefox supports it; private windows and some in-app browsers switch it off, and there the tool stops you on the click — before it spends about 31 MB on an engine that could not have run.
MP4 or MOV, and which quality to choose
Convert to MP4 → .mp4, H.264 (default) Keep MOV → .mov, H.264 High → CRF 23 · Recommended → CRF 28 · Smaller → CRF 32 Up to 1080p → short edge capped at 1080 px (default) Up to 720p → short edge capped at 720 px
Convert to MP4 is the default because H.264 inside an MP4 is the combination with the broadest built-in support, and that solves the other half of the MOV problem: an iPhone clip recorded in HEVC (H.265) often shows a black frame or a codec complaint on a Windows PC, while the same footage re-encoded to H.264 just plays. Keep MOV exists for editing software and Apple apps that only accept .mov — and note that this is not a container swap in disguise. Both options genuinely re-encode the picture to H.264, so HEVC is not preserved in either.
Quality is H.264's constant rate factor, the number the encoder uses to decide how much data each scene deserves. A higher number means a smaller file and a softer picture, so the three steps run in a fixed order on the same footage: Smaller below Recommended, Recommended below High. The reference block in the next section lists what each step produced on one synthetic 4K clip, with the conditions that produced those numbers.
The resolution cap applies to the short edge, so Up to 1080p limits a landscape clip to 1080 pixels tall and a portrait one to 1080 wide. It only ever shrinks: footage already below the cap is never enlarged. Keep original resolution is not quite untouched either — odd dimensions are rounded down to even ones, so a 641×481 source comes out 640×480, because H.264's 4:2:0 colour needs even numbers.
A reasonable default for a phone recording is Recommended with Up to 1080p. Go to Smaller with Up to 720p when a size limit matters more than detail, and reach for High only when you plan to edit the result afterwards.
Got an MP4, MKV, WebM or AVI instead? Compress Video runs the same engine without the MOV-specific defaults.
4K, HDR and the 50 MB ceiling
Desktop FFmpeg 9.0.2; synthetic 4-second 3840×2160 HEVC 10-bit MOV; not a browser benchmark Source → 8.32 MiB, HEVC 10-bit with HLG tags, mono AAC Recommended + Up to 1080p → 1920×1080, 431 KB High + Up to 1080p → 1920×1080, 1.21 MiB Smaller + Up to 1080p → 1920×1080, 289 KB Recommended + Keep original resolution → 3840×2160, 3.45 MiB
Longer, high-bitrate iPhone recordings can exceed the 50 MB limit per file. A file above the limit is skipped with a note, and this page has no trimming of its own — shorten the clip in the Photos app first, then compress the short version. We have no measured megabytes-per-minute figure for phone recordings, so this page doesn't quote one.
Capping at 1080p is also the speed setting. Browser-based decoding has far fewer pixels to chew through at 1080p than at 4K, and the difference is big enough to be the difference between waiting and giving up; we have no measured frame rate from the browser, so no number is quoted here either. There is no overall time limit — a slow job that is still making progress is left alone — but if the encoder goes 75 seconds without any sign of life it is treated as stuck and stopped. A first failure is automatically retried once with faster, simpler encoder settings.
HDR is the one case where the result can look worse in a way quality settings won't fix. Output is always 8-bit YUV 4:2:0, and no tone mapping is applied, so 10-bit HDR footage may come back looking grey or flat on some screens. The tool warns you when it detects HDR instead of pretending otherwise. Keep the original of anything you care about that was shot in HDR.
The block above is a parameter check rather than a prediction: this tool's exact arguments were run in desktop FFmpeg 9.0.2 on a generated test pattern, which compresses very differently from real camera footage, and the sample is only four seconds long. What it does show is which lever moves the size most — the resolution cap, not the quality step. For your own clip, the page prints the before and after sizes when the run finishes.
What survives the compression, and what doesn't
Kept: the first real video track, the first audio track, the date and time the clip was shot, and the orientation — a portrait video stays portrait. The shoot date is written back deliberately under both metadata settings so the file still sorts by date when you put it back in a photo library. Sound is decided by the first audio track: if it is already AAC it is copied across untouched, avoiding a second round of loss, and if it is anything else it is re-encoded to AAC — 128 kbps for mono or stereo, and 64 kbps per channel up to 384 kbps for multichannel sound. A clip with no audio comes out silent.
Removed by default: the GPS coordinates, the device make and model, the software name and the rest of the global metadata, including Apple's own QuickTime location fields. That is the privacy-relevant part of a phone recording and the reason to run a video through this page before posting it. Untick Remove location, device model and other capture details if you would rather keep all of it; then nothing but the shoot date is touched.
Dropped whatever you choose: every audio track after the first — a MOV with two soundtracks loses the second, and the result card tells you how many there were — plus subtitle tracks, timecode and data tracks, and any video track beyond the first, such as an embedded cover image. HEVC and 10-bit are not preserved, as the output is fixed at 8-bit H.264. There is no lossless mode and no option to change only the container.
The playback index is written to the front of both the MP4 and the MOV, so the file can start playing while it is still downloading from a shared drive or a chat. On a phone, Save to device opens the system share sheet when the browser offers one and simply downloads the file when it doesn't — it is not guaranteed to be a share menu.
Photos with GPS data in them are the other half of this job: Compress Image handles those.
Getting an iPhone clip under an email or upload limit
Start from the limit in front of you. A personal Gmail account refuses attachments over 25 MB and offers a Drive link instead, chat apps apply their own ceilings to video sent in a conversation, and job or school portals often stop at 5 or 10 MB. Since this page takes files up to 50 MB, the realistic task is bringing a clip of a few dozen megabytes under a cap, not squeezing a half-hour recording.
If Recommended with Up to 1080p isn't enough, press Start over and run the original again with Smaller and Up to 720p. Don't compress the output a second time: each additional H.264 encode can discard detail; rerun the original when comparing settings. When the result barely moved, or came out bigger than the source because the original was already tightly compressed, the tool says so and suggests the next setting rather than quietly handing you a useless file.
If even Smaller at 720p comes out above the cap, these settings have not met your target; trim the clip, send a link, or use the target-size tool. And if you need a specific number rather than a quality step — under 25 MB, exactly — that is a different job from this one.
Need to hit a size limit instead of choosing a quality step? Use Compress Video to Target Size.
Frequently asked questions
- Can I compress a MOV without losing quality?
- Not literally — the picture is re-encoded to H.264, and that is lossy by design. What you control is how much is given up: High (CRF 23) keeps the most detail, Recommended (CRF 28) is the balanced default, and Smaller (CRF 32) prioritises file size. For everyday viewing on a phone or laptop, Recommended usually looks fine; if you need a pixel-perfect copy, keep the original.
- Should I convert the MOV to MP4 or keep MOV?
- Convert to MP4 unless something specifically requires .mov. MP4 with H.264 plays on Windows, Android, smart TVs and in browsers without extra codecs, so when a MOV refused to open somewhere, that is the difference. Keep MOV is there for editing software and Apple apps that only accept that extension — the picture is re-encoded to H.264 in both cases.
- Why won't my iPhone MOV play on Windows, and does this fix it?
- Recent iPhones record in HEVC (H.265), which many Windows installations can't decode out of the box, so the clip shows a black frame or a codec error. Because this tool always re-encodes the picture to H.264, the file it gives back plays on those machines. Renaming .mov to .mp4 does not achieve the same thing: that changes the extension and leaves the HEVC video inside.
- Is my video uploaded to a server?
- No. The compression runs inside your browser tab with ffmpeg.wasm, and the code contains no server fallback at all — if your device can't finish the job it reports an error instead of sending the file anywhere. Close the tab and nothing is left behind, which makes it usable for footage you wouldn't hand to a stranger.
- Does it remove the GPS location from an iPhone video?
- Yes, by default. The global metadata — GPS coordinates, device make and model, software name, and Apple's QuickTime location fields — is dropped, and only the date and time the clip was shot is written back so it still sorts correctly in a photo library. Unticking Remove location, device model and other capture details keeps all of it instead.
- How much smaller will my MOV get?
- Output size depends on the source bitrate, scene detail, quality setting and resolution cap; it can be smaller, unchanged or larger. In a desktop FFmpeg reference run with this tool's parameters, a synthetic 4-second 4K HEVC 10-bit MOV of 8.32 MiB came back as 431 KB at Recommended with Up to 1080p. A generated test pattern compresses very differently from real footage, so that is an illustration, not a forecast. The page reports your own before and after sizes, and tells you when the result barely changed.
- Will HDR, subtitles or a second audio track survive?
- No to all three. Output is fixed at 8-bit H.264 with no HDR-to-SDR tone mapping, so HDR footage may look grey or flat; subtitle, timecode and data tracks are dropped; and only the first audio track is kept, so a MOV with two soundtracks loses the second one. The result card tells you how many audio tracks the source had.
- Can I compress several MOV files at once, or one bigger than 50 MB?
- No — one file per run, up to 50 MB. Larger files are skipped with a note saying so. Beyond that limit the real constraint is your device's memory, since the whole video is handled inside the tab. For a batch, run the files one after another; for a longer 4K recording, trim it in the Photos app or export a smaller version first.